How to Implement User-Centric Design Thinking

Most UX Designs Fail for One Simple Reason Nobody Knows Who They're For. Great UX isn’t about pixels or layouts. It’s about people. And if you don’t define them clearly, you’re designing blind. Here’s how to identify your real users in 5 clear, practical steps 👇 1️⃣ Research Before You Design. → Forget assumptions they’re expensive. → Talk to real people. Watch how they behave. → Use surveys, interviews, and analytics to see what they actually need, not what you think they need. 2️⃣ Understand Their Goals. → Users don’t care about your product. → They care about progress. → Find out what success looks like for them and make your design the bridge that gets them there. 3️⃣ Segment with Purpose. → Not every user is your user. → Categorize them beginners, experts, buyers, decision makers. → Clarity brings focus. Focus builds usability. 4️⃣ Build Personas That Feel Real. → Turn numbers into narratives. → Give your users names, routines, and frustrations. → When everyone on your team can picture the same person, the design starts making sense. 5️⃣ Map the Experience. → Every user takes a path of awareness → curiosity → action. → Trace every step. → Where do they start? Where do they struggle? Where do they convert? That map is your design blueprint. That’s it. Five steps. Simple. Practical. Game changing. If you skip defining your users, your design will skip connecting with them. —------------------------------------------------------------------------------- P:S: If you found this useful, share it with your team or save it for your next UX project. Because great design doesn’t start with wireframes it starts with understanding humans.

The best products don’t start with features. They start with empathy. Too many teams build from the inside out. They jump straight from idea to execution.  Then wonder why adoption lags or feedback stings. Design Thinking flips the process. It starts with the user, not the roadmap. At its core is one powerful question: 👉 “What does this person truly need?” The 5 phases of Design Thinking help you answer that step by step, with real users in mind: 🤝 Empathize → Watch how people use products → Ask, don’t assume → Uncover unspoken needs → Understanding comes before building. 🎯 Define → Turn insights into a sharp problem → Frame it from the user’s perspective → Be specific → A well-defined problem reveals the path forward. 💡 Ideate → Generate lots of ideas → Mix bold with practical → Build on others’ thinking → The breakthrough often hides behind the obvious. 🛠 Prototype → Create quick, scrappy versions → Sketches, mockups, or demos → Speed > polish → A rough prototype beats a perfect theory. 🧪 Test → Put it in front of real users → Watch where they get stuck—or light up → Refine or pivot fast → Testing separates assumptions from reality. Design Thinking isn’t a straight line. 🔁 You’ll loop back.  🧠 Rethink.  🤝 Adjust. But every cycle brings you closer to something people actually want. Because products don’t win on features alone. They win when they’re built with empathy at the core. 👉 Repost to help more founders turn empathy into better products. Follow Christian Rebernik for more on startup leadership and product thinking.

I posted this image last month and a lot of people asked for a breakdown — not the theory, but how each stage actually works in a real project. Here’s the reminder this visual was meant to give: Understand → Ideate → Test → Implement is not a straight line. It’s a loop. You return to previous stages every time new data proves you wrong. Example from my own work: I was designing a dashboard for a SaaS product. The UI looked polished and was already “ready for handoff,” until usability testing showed that 4 out of 6 users couldn’t correctly interpret the main metric. So we had to loop back: → Understand: clarify user mental model → Ideate: restructure hierarchy + labels → Test: validate again with a quick prototype → Implement: only then ship the updated version The design didn’t change visually — the clarity did. Task success rate went from 42% to 91%. That’s real UX. Not a clean slide with arrows — but constant informed rewinding. A few things people underestimate in real projects: • “Understand” is not only interviews — it’s business goals, constraints, and success criteria • “Ideate” is not Dribbble-style wireframes — it’s structured problem solving • “Test” is not just moderated sessions — analytics, heatmaps, and field feedback count too • “Implement” doesn’t end at handoff — onboarding, content, states, and accessibility are still design The process doesn’t fail. What fails is expecting it to work in one direction. What is your take on this? #uxdesign #productdesign #designprocess #userexperience #uxresearch #uidesign #uxworkflow #designthinking #uxstrategy #usabilitytesting #saasdesign #uxcasestudy

Before you write a single requirement, consider this: Are you solving the right problems? To ensure your product aligns with user needs and supports your business goals, start with a problem framing session and design thinking workshop. Why? By involving users early and identifying relevant problems, you can: 1. Identify which problems and feature requests are truly relevant. 2. Uncover pain points users experience. 3. Align features with your business goals to maximize impact. The benefit? Designers gain clarity on user priorities, while diverse perspectives uncover fresh insights to overlooked challenges—ensuring solutions that align with both user needs and business objectives. The result: • A more user-centric product. • No wasted development resources on irrelevant features. • A stronger competitive edge. Start by framing the problem to uncover what will have the most impact, and include designers and user testing to build smarter, more effective products.

Not a hack: Want your engineers to be more user-centric? Introduce them to the why-how laddering exercise. Instead of jumping to “we need a notification system,” you climb up with “why”: 🟡"Why add notifications?" → "Users miss important updates" 🟡"Why do they miss them?" → "They only check weekly" 🟡"Why is that a problem?" → "Issues compound, causing frustration" Then back down with “how”: 🟡"How to keep them informed?" → "Alert for critical changes" 🟡"How to define critical?" → "When action is needed within 24h" 🟡"How to implement?" → "Start with email, add push later" This is also useful during interviews: note who asks "why" before proposing "how," it reveals engineers who think in problems, not just features. In hundreds of technical interviews, you'll find maybe one or two engineers who instinctively start investigating the problem before diving into solutions. Centering Gemography's vetting process (we help teams scale with pre-vetted remote product engineers) around this kind of thinking has changed the game for us and our clients. Once you go user-centric, you can't go back. Nurture the mindset, and hire for it.

Do you sometimes feel frustration, as you are building a product to get the management off your back, rather than address the users? Here are 6 ways to become user-centric again: 1) Prioritize in a transparent way This is a great place to start. If your backlog is prioritized based on data and potential opportunity, risk, and cost, it will be easier to put forth user-centric initiatives ahead of those that came from upstairs. At the very least, you will have a good basis for an educated discussion. 2) Utilize users' perspective using user stories and personas If your team understands the users and their problems, it will be easier to craft something great that will later appeal to the same users. Just keep up the empathy of creating something by people for other people, and not get some metric magically go up! 3) Make user feedback public If everyone in the company can see the themes that come from user feedback, it will be way harder to ignore it in favor of some corporate nonsense. Let those voices be heard by everyone! 4) Have the NPS and user ratings at the forefront The same goes for a single metric representing the general product sentiment. If the number is low or, worse, is going down and everyone can see that, the responsible Product Manager has to react. 5) Focus on your product goals Now, upstairs mandates might not be the only distraction you face when trying to improve your product. To survive them all, focus on one thing: your product goals. This will allow you to demonstrate you are doing what you are asked for and you can use user feedback and points 1-4 to pursue those goals. Thus, it's like killing 2 birds with 1 stone. However, you can also simply: 6) Have the confidence to say "No" Not all company/legal/management requests can be ignored. Sometimes changing the law or a wider company initiative will require you to comply and that is OK! However, there will also be times when someone will try to force your compliance. This is where you need to be confident, and exercise your Product Manager's independence, especially when there is no data to support a specific request. There you go! My 6 ways you can become a user-centric Product Manager. How about you? Do you address your users or your management first and foremost when developing your product? Sound off in the comments! #productmanagement #productmanager #usercentricity

💡Combining Design Thinking, Lean UX, and Agile A combination of Design Thinking, Lean UX, and Agile methodologies offers a powerful approach to product development—it helps balance user-centered design with efficient concept validation and iterative product development. 1️⃣ User-centered foundation (Design Thinking): Begin by understanding the needs, emotions, and problems of the end-users. ✔ Start by conducting user research to identify and understand user needs. ✔ Gather insights through direct interaction with users (e.g., through interviews, surveys, etc.). Spend time understanding users' behavior, focusing on "why" rather than "what" they do. ✔ After gathering research, prioritize the most critical user insights to guide your design focus. Create a 2x2 matrix to prioritize insights based on impact (high vs low business impact) and feasibility (easy vs hard to implement) ✔ Begin brainstorming potential solutions based on these prioritized insights and formulate a hypothesis. Encourage cross-functional collaboration during brainstorming sessions to generate diverse ideas. 2️⃣ Hypothesis-driven testing (Lean UX): Lean UX helps quickly validate key assumptions. It fits perfectly between Design Thinking's ideation and Agile's development processes, ensuring that critical hypothesis are validated with users before actual development started. ✔ Formulate a testable hypothesis around a potential solution that addresses the user needs uncovered in the Design Thinking phase. ✔ Conduct experiment—develop a Minimum Viable Product (https://lnkd.in/dQg_siZG) to test the hypothesis. Build just enough functionality to test your hypothesis—focus on speed and simplicity. ✔ Based on the experiment's outcome, refine or revise the hypothesis and repeat the cycle. 3️⃣ Iterative product development (Agile): Once the Lean UX process produces validated concepts, Agile takes over for incremental development. Agile's iterative sprints will help you continuously build, test, and refine the concept. Agile complements Lean UX by providing the structure for frequent releases, allowing teams to adapt and deliver value consistently. ✔ Break down work into small, manageable chunks that can be delivered iteratively. ✔ Embrace iterative development—continue refining your product through iterative build-measure-learn sprints. Keep the user feedback loop tight by involving users in sprint reviews or testing sessions. ✔ Gather user feedback after each sprint and adapt the product according to the findings. Measure user satisfaction and track usability metrics to ensure improvements align with user needs. 🖼️ Design thinking, Lean UX and Agile better together by Dave Landis #UX #agile #designthinking #productdesign #leanux #lean  

Poor user experience? Your product might look good, but if it doesn’t align with human factors and ergonomics, you’ve missed the mark. Is your product visually appealing but ergonomically frustrating? Here’s why and how to fix it. hashtag #userexperience #HumanFactors #Ergonomics #ProductDesign 💡 Consideration: How We Use a User-Centric Approach to Solve Poor User Experience 1. Understanding the User: We dig deep to understand not just what the user wants, but what they physically and psychologically need, aligning with principles of human factors and ergonomics. 2. Feedback Loops: Real-world testing and analytics help us grasp how users are truly interacting with your product, allowing for design adjustments rooted in actual experience. 3. Iterative Design: Version 1 is just the start. We iterate based on user feedback and ergonomic assessments, ensuring a user-friendly end product. 4. Multi-disciplinary Teams: Our design and engineering teams collaborate to harmonize form, function, and human factors, taking into account both aesthetic and ergonomic considerations. 5. Accessibility: By making your product accessible, we expand your brand’s reach and ensure it fits a wide range of user needs, guided by ergonomic principles. 6. Attention to Micro-Interactions: Details matter. Whether it’s a button’s responsiveness or the layout of a menu, we integrate human factors to elevate the entire user experience. hashtag #UserCentricDesign #HumanFactors #Ergonomics #industrialdesign #productdesign #productdevelopment #userexperience If you find that your product falls short in user experience, particularly in ergonomics and human factors, let’s talk. We can turn that frustration into user delight. ----- I'm Jonathan Thai , a seasoned Silicon Valley designer with over a decade under my belt bringing products to life. Through Hatch Duo LLC and more, I've crafted, invested, and steered ventures to the forefront of innovation. Considering a game-changing product or venture? Check out our design studio here: www.hatchduo.com

Here to there? Stay close to your users. Good design depends on understanding users at every step of the decision-making process. This week, I saw two teams handle this very differently. Company A Followed a step-by-step process through the company, with many internal decision points. At each stage, different people added input. While they did include some user feedback, it often got diluted as it moved up and down through layers of management. This made the design feel more focused on company opinions than actual user needs. Company B Instead of following the internal decision path, this team created a vline from users directly to the design, connecting early ideas to the final concept. A strong leader used UX metrics to integrate user insights at key points, cutting through layers of internal debate. Rather than involving every team at every step, they used feedback to guide decisions and inform the final direction. It’s easy to see which team moved faster and stayed closer to what users need. To build great design, from start to finish, companies need to include users throughout, not just at the beginning or end. Relying too much on internal opinions leads teams away from the real problems users face. When teams follow their instincts and use user feedback at every step, they build momentum and make smarter decisions without getting stuck in internal issues. That’s how great design gets done. #productdesign #uxmetrics #productdiscovery #uxresearch

Simple, yet powerful advice when implementing: Be the end user. This works for: → Reports & dashboards → Declarative configuration → Flows or Apex Having worked on dozens of Salesforce implementations, I see the difference a user-focused approach can make. One of the biggest issues I see? Many possible scenarios in Flows Little of them are handled Complex layouts with data overload Little relevance, no filtering From new admins to experienced architects. Everyone can fall into this trap. And I know it's costing teams time and user satisfaction. To build for the end user, BE that user, and ask yourself: What information do I need to give? What fields should be pre-populated? What kind of information should be visible to support my decisions? What errors I'm likely to encounter? What paths I might want to choose? When you build for yourself, you build better for others. This approach ensures your system feels intuitive and user-friendly. --- Found this helpful? Like 👍 | Comment ✍ | Repost ♻️