Kris Morgan

Top UX rule for designing an enterprise-ish app that is trying to acquire new users: Is it better+easier than a spreadsheet? Note I didn’t include ‘simpler’. Simplicity won’t matter at first when you’re trying to bring users over from a spreadsheet. It might actually make your solution less powerful which would work against you.

68

2 Comments

Excited to dive deeper into design systems! 🌟 This article breaks down the “parent-child” relationship between design systems and style guides, showing how they work together to keep designs consistent and efficient. A great read for anyone passionate about design! #designsystem #styleguides #uxdesign https://lnkd.in/eUamsNTH

3

"The strategic design gold rush is over." While this might sound like a scary sentiment at first, I'm choosing to see it as an opportunity for design leadership. It's a chance for reinvention of what role design led teams can play in corporate settings. Users are increasing their demand for simple and straightforward user experiences. Every company continues to need more user and customer advocacy and design leaders are perfectly positioned to be the fabric of that advocacy and stitch together the functions required to deliver it to market. Rather than being relegated to a subordinate capability in product-led companies, design leaders can now redefine their purpose, leveraging their skills in user empathy, strategic experiential planning and continue to tie together the often disparate agendas at play in organizations. #Design #Leadership #Reinvention #Innovation

3

1 Comment

✨ It's not about the artifact, it's about the insight. ✨ Heidi Trost shares her experience with personas that made an impact. 📝 Instead of complex deliverables, she focused on capturing core insights in a few simple phrases in an infographic. These insights tied behaviors to business goals – and that’s what resonated. 📊 It wasn’t about how it looked, but how well it communicated across the team. 🌟 #UXResearch #BusinessGoals #EffectiveCommunication

4

“Be who and where you are.” I’m still processing all of the amazing insights that came out of Clarity: A design systems community conference last week but several themes have been bouncing around in my head since then. → Get smaller and connect - Dan Mall and others talked about a trend towards smaller core design systems with surrounding layers of shared patterns like recipes, all being consumed by teams managing their own local libraries. This results in teams being able to move faster and eliminates the need for design systems folks to feel that have to be a bottleneck. → Be who and where you are - John Voss and others talked about building the system that your users and team need rather than conforming to what larger companies are putting out there or the oversimplified “stereotype” you yourself have unintentionally created for your product. → Listen - Ben Callahan and others talked about the need to reset our current mental models for how design systems teams see our roles and responsibilities. How do we move away from our perceived tactical responsibilities towards more listening and validating of the needs of our consumers and users? 💎 My personal takeaways from all of this have me reframing my own journey with my team from "a series of mistakes" towards "the necessary growth to become the team we are today." → When we implemented that now outdated framework, tried to centralize everything into a single bloated design system, or wrote all of that verbose documentation, we were doing what we needed to do to mature and are a better team as a result. → What my team is going through, we're all going through. The role of design in general is changing across the industry, not just in my organization. How lucky are we, that we have the opportunity to learn from each other as designers? → As team roles change, I’m curious to pivot my default stance away from “defend the designer's role”, and would be curious to see how I can facilitate “design” activities regardless of whether they are done by a designer, product manager, or engineer. I feel so very fortunate to be a part of such an amazing community and love the reminder that when you get a bunch of systems thinkers together in the same room, you're going to see patterns. Thanks again 🖤 Jina A. and all the speakers last week. #clarity2024 #designsystems #design

59

8 Comments

Portfolio tip for design leaders: Unless your values/leadership style/‘how I lead’ slides are unique or clearly showing why they make you a good fit for this specific role, skip all that in your portfolio presentation. It’s a waste of time and if it sounds like what all the other candidates are also doing(which is true 90% of the time), it will make you blend in. Not good: Generic words like empathy, team building, servant leadership etc Good: Super specific values that apply to this role Better: Super specific values that are actually then evidenced in the work you will shortly present

94

11 Comments

UX leaders: Better understand what motivates designers and how you can help them thrive by taking 3 minutes to read this excerpt from Scott Berkun’s new book “Why Design Is Hard”: https://lnkd.in/ev6XyMss

2

What if UX Prioritized the Subjective Over the Quantifiable? The First in a Series on Reimagining UX Design through Philosophy, Embodied Cognition, and Phenomenology "But here’s my issue: have we lost sight of what UX design can and should be? If UX is at a crossroads, it’s not just because of automation or market saturation — it’s because we’ve drifted too far from the philosophical roots that make design meaningful. Instead of constantly optimizing for behavior, we should be stepping back and asking: Are we creating something meaningful? Are we enriching people’s lives? Or are we simply chasing the next KPI?" #ux #uxdesign #hci #userexperience #uxresearch #technology

48

5 Comments

I'm thrilled to share that my latest product and design discovery article is live on Mind the Product! As a consultant, I've observed that the term 'Discovery' can have varying interpretations across different teams. It's not uncommon to encounter a team deeply immersed in a solution yet lacking a shared understanding of the customer opportunity they're addressing. At Lab Zero, we meet clients where they are and advocate for discovery while maintaining flexibility. We often employ lightweight methodologies to foster a shared understanding, even when work is already underway. Teresa Torres' book “Continuous Discovery Habits” is a guide to developing the mindset and practices that enable teams to discover and deliver value to their customers throughout the product development process. Her explanation of the 'Opportunity Solution Tree' helped me articulate a process for asking questions and bridging gaps when joining a new team. The first part of this two-part series looks at reversing the 'Opportunity Solution Tree' to establish a connection between the ongoing solution, customer opportunities, and business outcomes. The second part (coming soon!) will explore strategies for identifying gaps in your team's understanding of customer needs and the necessary measures to mitigate risks before launch. This series will help consultants, new team members, or a struggling team connect with that all-important why and launch valuable experiences for their customers and their orgs. Have you tried something like this with your team? Feedback is appreciated! If you haven't explored Mind The Product's extensive content library, I highly recommend it! In addition to articles about discovery and understanding customer needs, the community has shared insightful perspectives on product leadership, business, and teams. It's a great place to see perspectives on processes and theories informed by real-world use.  #ProductDiscovery #Design #Discovery #ContinuousDiscovery #Onboarding #Risk #CustomerOpportunity #Value #BusinessOutcomes

14

6 Comments

What level, when applying for design leadership positions, is a portfolio no longer necessary? As a leader, I want to see how you manage and lead your team, how you build your teams, and how you position yourself and your team in the organization. If you are a UX or product design manager, chances are you got there because you know what you’re doing. Or is that a naive assumption?

As a design leader, you work for your team—not the other way around. Learn how to keep your #UXteam happy, creative, and always on schedule. https://lnkd.in/eksZbUXM #DesignLeadership #TeamManagement #UXDesign #Productivity

3

Most designers are trained to present work to our peers, but as your career matures, your audience expands to include many other departments who don’t speak “design”. This article resonated with me and offers some sage advice about the use of storytelling and a “business lens” to craft more compelling presentations. #ProductDesign #Storytelling #UserResearch #BusinessObjectives

9

Great writeup on the value design can bring to product organisations irrespective of technoöogical shifts such as AI.

3

Great read about the current and future position of Product Design in tech. Could not agree more. "Design workflows at most tech companies follow an incredible number of structured tasks: for each project, designers must create user personas, user stories, journey maps, wireframes, user interviews, and much more. These concepts originated in the service design industry and initially helped facilitate a very human-focused design process – which, of course, is good. However, driven by a desire from businesses to turn design into a process-heavy, measurable function, we’re filling our time with checklists instead of focusing on the very thing that makes designers relevant: our ability to propose new points of view and delight users with meaningful experiences. These core competences that were inherited from graphic design have been replaced with a poor man’s version of an anthropology major where the act of design is mostly based on averaging user opinions." https://lnkd.in/dwJhER7e

30

GitHub makes collaboration and communication easy when it comes to design systems. We use issues and discussions to track bugs and questions, it helps us build a knowledge base. These tools are surprisingly absent in our design tools, and this needs to change. I am going to change that. #ux #designsystems #equalityintools

4

I recently wrote about design system metrics, including adoption. Adoption can be pushed as a mandate. Having seen hundreds of design systems up close Dan Mall points out that there is no definitive evidence that high adoption doesn’t hurt. But, it certainly doesn’t differentiate between useful design systems and that frankenstack monster that has documentation in Excel with hundreds of links to a private Git repo along with multiple swim lanes with infinite scroll. The only reason why adoption persists as a common metric is because even really bad design systems have the ability to generate significant value. Full article in the comments.

13

5 Comments

The more that designers can think with a business mindset, the more effective they can be at influencing key stakeholders and driving desired outcomes.

1