Chad Thornton

This is a great post for designers moving into management/leadership roles. The nature of your job changes dramatically and it's important to figure out the most effective ways to help your team and the company. As noted in the article, it's very easy to have your time consumed by managerial tasks (operational work). Being deliberate about how you want to spend your time, focusing on the change you want to bring about and working consistently towards that end are critical skills to learn. #UX #Design #DesignLeadership https://lnkd.in/e_g4TRJx

7

2 Comments

Many designers complain that they can’t get their ideas into a product backlog. Most of the time this is true depending on the maturity of your team and if your company sees value in the design field, but most of the time, backlogs are product driven. If you want to advocate how to get your ideas you need to convince how the designs are going to impact the business. Saying to PM’s: “The UI looks bad and outdated” is such a bad pitch and will fall on deaf ears. You need to speak “business” and as a designer you need to know how your ideas can make them money. Now, you’re probably thinking “well how can I do that” considering it’s hard to use ARR on designs. This is where we introduce the RICE framework. https://lnkd.in/exaD4xNY . Learning this will help you know the impact of your designs, the reach of the customer base, how confident you are on the designs and estimations and how much effort the business needs to invest in this idea. I will be writing an in depth post on this soon but thought I’d leave this tip on a Sunday night as I am having the designer insonomia.

8

7 Comments

The Jobs to Be Done framework is crucial for product designers, especially as the line between product managers and designers continues to blur. This article can revolutionize how we approach problem discovery and opportunity identification, offering deeper insights during the design phase. It's a must-read for anyone looking to elevate their design process and deliver exceptional results.

5

Over the years I've tried many approaches to design critiques with the teams I've managed. Without fail these 4 simple principles impact the effectiveness of design critiques greater than anything else when established as ground rules. For presenters: ✦ Describe the problem you're solving ✦ State the target audience* ✦ Specify the feedback you're seeking All of the above can be done in less than a minute, either verbally or in written format. For participants: ✦ Ask questions before comments "I think you should go with blue instead of red" is less effective than first asking "Why did you choose red for this?" The additional context that comes from asking questions will lead to more effective feedback. Design critiques are the easiest and most important thing design teams can do to improve design quality. Alone they are not a silver bullet. But they are the foundation for all other improvements to design quality. If you're not holding regular design critiques (usually weekly), this is step 1 for improving design quality. If you're already holding regular design critiques but not doing the 4 principles above well, this is step 1 for improving your design critiques. Better critiques. Better quality. * "Everyone" is rarely acceptable as the target audience. Even if the feature being presented is intended for everyone, 99% of the time there's a specific segment or archetype you're aiming for. #design #critiques #quality

356

14 Comments

Somtimes the content that can up your UX game comes from unlikly sources. This article puts into context some of the best places to start!

9

This d.MBA episode shares a ton of great nuggets on advocating for design functions and how to have more impact as a designer? #UX #ProductDesign https://buff.ly/47VixoZ

2

I'd like to share some valuable lessons that have completely transformed the way I approach communications. Plus, I've added some tips for product designers and design partners. 💡Case 1: Answer the Question I thought I knew how to answer questions until I got this feedback: "When an executive asks you a question, start with a clear 'yes' or 'no', or state 'I don't know, but I will get back to you by X date'." While variations exist, the key is to answer the question first. Too much information usually doesn't help - Answer the question, then let them ask probing questions. This advice resonated with me so much that I created a desktop wallpaper to look at it every day. 🤝 Case 2: Manage Meeting Effectively Another tip I learned is how to manage meetings. Based on tips from mentors and coworkers, here are three essential points to remember: 1. Why we are here: Ensure every meeting has a clear purpose. No one has time for irrelevant meetings. 2. What we aim to achieve: Clearly define the meeting's objectives. 3. What decisions we will make: Identify decision-makers and criteria.
 Applying this to design meetings, merely sharing in-progress designs often lacks value. Instead, structure the meeting to: 1. Clearly define the meeting's purpose and type: For example, specify if it’s a review and instruct people on the type of review you need. 2. Clarify the objectives: Are we finalizing designs to send to engineering, or aligning on problem statements with products? 3. Identify decision-makers and criteria for decisions: Then, make a decision. Of course, in both cases, summarize the outcome of the meetings and share it right away. ✨ Case 3: Clarify Expectations At workplaces, confusion and fires happen. Sometimes you're not sure what's going on. You don't want to overpromise or overstep, but you need to know what action is required. When I heard this question "What am I accountable for?" in the middle of a foggy meeting, my brain just cleared. Yes. We need clear ownership and accountability to navigate ambiguous situations. It was a sentence that resonated with me, and I still remember how we were able to move on to the next steps. To build on this, I also advise my partners to communicate their asks clearly. I hear a variety of design requests. Some people articulate their asks with intended outcomes, expectations, and timelines, while others just share desires and disappear. Clarity in your asks is key—it's almost a job requirement. Remember, others can't read your mind. If you believe in your idea, it's important to articulate it clearly. #CommunicationTips #ProductDesign #DesignPartnerships

40

6 Comments

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

It’s Thursday! Let’s talk about DESIGN DISCOVERY and how to make it PRACTICAL. Discovery is an essential part of the design process. In discovery, designers build a shared understanding of the problem and the design direction, establishing a foundation for all future design decisions. What does that foundation look like? In PRACTICAL DESIGN DISCOVERY, I describe three kinds of things to put into this foundation: → Principles: Enablers that help you make decisions → Concepts: Ideas that establish a big picture or north star → Models: Representations of the user experience When you draw a conclusion from user research, that’s a principle. When you say “our product is like a concierge for kids activities,” that’s a concept. And when you sketch out a flow chart or wireframe an important screen, that’s a model. Each of these contributes to the foundation that informs further design decisions. You’re not just creating these for yourself. The other people on your team – product managers and business stakeholders and developers – need to contribute to this foundation. These things – principles, concepts, and models – are the way you draw others into the discovery process. Sometimes managers tell designers to cut principles and concepts out of their process. I get it: Models are accessible because they are tangible representations of the final product. Even a flow chart is easier to react to than an unmoored design principle or a big idea. In discovery, however, you can’t model every aspect of a product. The point of discovery is to set the direction. Models provide enough of a view into the final product to get buy-in on that direction. But they’re not the whole picture. Principles provide guidelines for making decisions that the models do not cover. They establish constraints on the design process. Concepts align everyone around the product’s purpose or essence. They paint a picture of what the world looks like with the product in it. Both are helpful for decision-making. You don’t need to break the bank creating principles or concepts, or even models. Use a text file to capture statements as they jump out during the design process, like “never show a data visualization without context or explanation [a principle]” or “this is a mash-up between a to-do list and a calendar [a concept]”. Use models to illustrate principles and concepts. When folks provide feedback on the models, ask them about the concepts and the principles. “You said you were worried about the fields on this screen, but it aligns with our principle of ‘only ask for information when needed.’ Are there circumstances when the principle doesn’t apply?” Every part of the foundation – principles, concepts, and models – is a hook for a conversation with the entire team about the direction of your product. Looking for more ways to refine your discovery practice? Grab a copy of PRACTICAL DESIGN DISCOVERY! https://lnkd.in/dtar-e2

38

2 Comments

Have you ever wondered what makes independent UX design studios stand out in the competitive digital landscape? Having worked with both Fortune 100 giants and small startups, I've seen firsthand how independent UX design studios can provide efficient, creative solutions tailored to client needs—solutions that truly enhance user experience and foster innovation. In my latest article, I dive deep into why independent studios often outperform larger agencies and in-house teams when it comes to UX design. Here are some of the key highlights: ✅ Flexibility and Agility: Without the layers of bureaucracy, independent studios make swift decisions and adapt quickly to client feedback. Imagine getting changes implemented within 24-48 hours instead of the lengthy wait typical in bigger agencies. ✅ Specialized Expertise: We bring deep, diverse knowledge to every project. Our team members have worked across different industries, which gives us the ability to tackle UX challenges from fresh perspectives—something that in-house teams can sometimes struggle with. ✅ Personalized UX Solutions: We don’t believe in one-size-fits-all. Each client has unique needs, and our personalized approach ensures the end product not only meets functional requirements but also resonates deeply with users. ✅ Freedom to Innovate: Independent UX studios operate without the constraints of corporate hierarchies. This independence allows for a creativity-driven environment where we challenge norms and propose innovative solutions, benefiting our clients with impactful, user-centred experiences. If you’re considering enhancing your digital product or need an agile partner to bring your UX vision to life, this article is for you. Dive in and discover how partnering with an independent UX studio could be your best strategic move. Read the full article here: https://lnkd.in/eWTvXdea #UXDesign #UserExperience #IndependentStudios #Innovation #Agility #DesignThinking #AIinDesign #LeanUX

5

Check out the 4 step exercise at the end of the article. Excellent advice.

2

Our company is acquired. Now what? “Business as usual” applies no more to us UX professionals if we must navigate organizational changes. Here are a few questions to consider to handle uncertainty. #UX #productDesign

6

Just attended a UXR session where we discussed the state of UX Research. While it's been around for a few years, it's still in its infancy. Early adopters of the practice are already seeing a significant competitive advantage. In fact, in the next 10 years, it's likely that every company will have a UX Research team. Don't be left behind - invest in UX Research now to stay ahead of the game! #UXResearch #UserExperience #CompetitiveAdvantage

3

Fact: Diverse design teams are faster, more efficient, and produce more innovative products.  Why?  Because diverse teams (teams that consist of people with different skillsets, educational backgrounds, and lived experiences) are simply smarter and more creative than homogenous teams. The diversity of skills and expertise in a multidisciplinary team encourages trial and error and challenging the status quo. This stimulates new kinds of learning and thinking, potentially resulting in breakthrough design solutions that would not have been possible with a single-discipline team. Ready to delve deeper? Read our full article, “Why Multidisciplinary Teams Create Design Better Products”: https://hubs.la/Q02xKCyt0  ---- Hello. We're Delve, a product innovation firm. We help companies bring bold ideas to market through human-centered expertise—strategy, design, engineering. Learn more about product design and development services at Delve: https://hubs.la/Q02xKt8T0 #DEI #diversityday #productdesign

9

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

10 basic lessons of a design system. Being someone who has worked within and created many design systems, brand guidelines, and UI libraries, I've encountered many bumps along the way. What would you add or remove from this list? #designsystem #UX #lessonslearned #basics https://lnkd.in/evFxwP79

2

Research is a function of strategy.  "According to CB Insights, over 90% of all products fail, most commonly due to no market need." Leave yourself time to ask big questions about whether any actually needs your product or service before you decide to launch it. #UXstrategy #UXresearch #Marketresearch

3

1 Comment

Hot take: Product and design are the same job (and designers are better at it). The job is figuring out what to build, why, and communicating that in a way a team can execute against. In big companies I see designers operating like junior PMs anyway — they get briefed into a PRD and then lead the feature from there to shipped. Their edge is they are highly literate communicating visually in addition to verbally. Where designers often get stuck is a belief that their PM will always know more about the problem space and customer needs than they do. In fact, design work is so detail-oriented, I think the opposite is actually true. Designers have to *really* know their customer to translate a PRD into an elegant experience. They just don’t get the same credit for it. TLDR; PMs, level up your visual design skills. The designers are coming. What do you see as the future of the product / design function?

8

1 Comment