When mentoring designers, the single most important question I need them to ask themselves is, “How exactly does this proposal make users’ lives better?” Often time, designers easily fall into the trap of personal bias. In the world of UX psychology and mental model, this can be referred as “Design Model” (or the problem-solver’s mental model). Unaware of the potential gap between Design Model and User Model, the proposal can work well for the person who designs it, but not necessarily for the actual users; Why is that? “Designers are likely to be experts in how the system works, whereas users may have a limited or incorrect understanding of the complex system.” Users don’t know everything about your system. They just react from what they are seeing, and react based on their past experience (as known as Jacob’s Law). At Trumid, we have a robust process to gain insights from actual users and proxy users, so that we don’t fall into the trap of “shoot first, and ask question later”. https://lnkd.in/e8Urx2fu
How to avoid personal bias in UX design: Trumid's approach
More Relevant Posts
-
📚 My Go-To UX Design Reading List (After 5+ Years in the Field) Over the years, I’ve learned that no amount of tools or frameworks can replace a strong foundation in how people think, feel, and interact with what we design. I often share these books with newer designers I mentor and they’ve shaped how I approach both user advocacy and product strategy. Here are a few that have stuck with me: 🔹 The Design of Everyday Things: Don Norman A timeless classic. It changed the way I see the world — from doors and buttons to entire systems. It’s the perfect starting point for understanding why usability matters. 🔹 Don’t Make Me Think: Steve Krug Simple, clear, and direct, just like good UX. I recommend this to anyone starting out in digital design because it nails the principles of intuitive interaction and visual clarity. 🔹 UX Team of One: Leah Buley A must-read if you’ve ever worn all the hats; researcher, designer, strategist, facilitator. It’s practical and validating for solo or small-team designers navigating cross-functional environments. 🔹 Design for a Better World: Don Norman Norman’s newer work, but with a broader mission: designing not just for usability, but for ethics, sustainability, and humanity. It’s a powerful read for anyone thinking beyond product screens. 🔹 Designing for the Digital Age: Kim Goodwin (Currently Reading) At over 700 pages, it’s dense but incredibly insightful. Goodwin dives deep into process, collaboration, and design leadership in a way few books do. I’ve found revisiting these books at different stages of my career always reveals something new, especially when mentoring or building design culture within a team. #UXDesign #ProductDesign #DesignThinking #UserExperience #CareerGrowth #DesignLeadership #Mentorship #UXCommunity
To view or add a comment, sign in
-
-
While learning UX, I thought I was learning design. But really, I was learning patience. Empathy. And listening. At first, I wanted to jump straight to colors, buttons, wireframes the fun stuff. But UX doesn’t reward speed. It rewards understanding. Because every time I rushed a flow, I missed what the user was really trying to say. Every time I assumed, I designed the wrong solution. Every time I listened really listened the problem became clear. UX teaches you that people don’t always say what they mean. Sometimes their frustration hides in silence. Sometimes their confusion lives between clicks. And your job as a designer is to pause long enough to notice. Now, when I design, I don’t just look for answers. I look for patterns. For emotions. For the story behind the action. Learning UX has made me slower but in the best way. More thoughtful. More human. And more aware that good design isn’t just seen. It’s felt. What’s one lesson UX has taught you beyond design?
To view or add a comment, sign in
-
Do you skip user research because you're under tight deadlines? We listen, we don't judge. One golden rule I learnt from my facilitator as a woman techsters fellow about UX design is this: "Test with real users first, so you don't design in a vacuum and create something nobody wants." If you were trained in human-centered design, you already know that this wasn't just advice. It was a principle. Unfortunately, many UX designers have launched projects on assumptions and intuition, running on confidence and experience. How did those projects go? To be honest, they might go okay. Get approved by and the designs look polished. But what do you do when user feedback comes in later? Here are 10 reasons it matters: ✅ User Empathy: Reveals real pain points you might miss ✅ Risk Reduction: Catches usability issues before launch ✅ Stakeholder Confidence: Backs decisions with data, not opinions ✅ Design Validation: Confirms your solutions actually work ✅ Cost Savings: Prevents expensive post-launch fixes ✅ Innovation Insights: Uncovers opportunities you didn't expect ✅ Team Alignment: Creates shared understanding of user needs ✅ Accessibility Awareness: Identifies barriers for diverse users ✅ Competitive Edge: Delivers experiences users actually prefer ✅ Career Growth: Builds your credibility as a strategic UX designer What's your relationship with user research? Do you make time for it, or do you skip it when deadlines get tight?
To view or add a comment, sign in
-
-
UX Design intersects with a lot of disciplines, and I recently found myself applying lessons from an unexpected place: the military leadership book, Extreme Ownership by Jocko Willink & Leif Babin. While it's about combat and business, the core principles of taking ownership have massive implications for how we operate as UX Designers. Here are my top 3 takeaways for the UX Community: 1. Total Responsibility for Output Quality: If a shipped product contains a usability failure, the designer cannot attribute the issue solely to development constraints or product management shifts. The designer must retrospectively identify the failure point in their own process: Was the rationale Keep It Simple? Was the communication of the user needs Prioritized and Executed effectively? This mindset ensures proactive rather than reactive problem-solving. 2. Leading the Cross-Functional Team: The principle of "Cover and Move" (Seamless Collaboration) involves breaking down the silos between design, engineering, and product. The UX Designer is responsible for ensuring mutual support, anticipating dependencies, and proactively aligning all functions toward the strategic objective (Commander's Intent), even if they are not the official project lead. 3. The Absence of Ego: In a field driven by creative solutions, the directive to "Check the Ego" is vital. Ownership requires the humility to acknowledge when user research invalidates a favored design solution. The overarching mission—creating an optimal and effective user experience—must always supersede personal attachment to a concept. Extreme Ownership serves as a powerful reminder that leadership is not a position; it is a mindset. Implementing this mindset requires disciplined self-assessment and a commitment to continuous improvement. By adopting Extreme Ownership, UX professionals can transition from contributors to true leaders of the product lifecycle, driving accountability and ensuring the highest standards for every user experience delivered.
To view or add a comment, sign in
-
Lately, I have been thinking a lot about equity-centered design. This image from my Coursera Google UX Design course caught my attention. It looks simple, yet it carries such depth. We often believe fairness means treating everyone the same way, but real fairness, true equity, recognizes that people start from different places and need different kinds of support to thrive. In psychology, even individuals of the same age, height, or background think, feel, and process experiences differently. Still, many of us, myself included, sometimes expect others to act or understand a situation the same way we would. That is where equity-centered design comes in. It teaches us that designing with empathy means seeing beyond sameness and understanding individual needs. It is not just about accessibility or inclusion; it is about truly caring for the user’s well-being and creating spaces where everyone can succeed, not just fit in. Image credit: cropped from a video in my Coursera Google UX Design course. #ProductDesigner #IShowedUpToday #Equity
To view or add a comment, sign in
-
-
UXers: 🚫 Don’t discount the power of building stakeholder trust. Everyone gets excited to dive in and start fixing design problems, ⚙️🤸and that makes sense, because fixing problems can be so fun and gratifying, that so many of us have based our careers on it… BUT, telling a product owner, VP, or director of IT what a bad job they did on their product when they’ve sincerely invested time and energy into it…is just going to get their backs up (even if it's disguised with an optimistic "I know you don't realize, but this could be so much better"). If that’s your MO, it will be hard to get them to trust you, consider your suggestions, or let you in on their goals and upcoming projects. The designers and researchers I’ve seen make incredible moves in their careers and become major contributors to showstopping products didn’t do any of it by “getting their way.” Instead, they got good at understanding what others need, acknowledging those needs, serving up the highest quality work possible, and establishing mutual trust. 👉 Trustworthy UXers are always doing these three things: - Tying the work back to ROI and business objectives 🎯 (not using isolating and jargon-y design terms and talking only about the user's needs, the understand their is a business and a budget behind everything) - Honing “soft skills” 💜 (the unsexy things like being organized, responsive, communicative, empathetic, etc.) - Committing to excellence on every little task 🏅(competing with themselves to one-up their last project, pushing to create more delight and be more resourceful, scrappy learners) Don’t forget that your training is a privilege you’re leveraging to help others. Step 1: You understand what your stakeholders need. Step 2: You help your stakeholders understand what users need. Step 3: Your stakeholders help you achieve what’s needed. Step 4: You both help the users. You won't get far if you can't do Step 1 and fully appreciate, respect, consider, or integrate your stakeholders’ perspectives into the work you're doing. Let me know if this resonates. I’ll leave you with a link to a soft skills blog: https://lnkd.in/gHCA6PRh #SoftSkills #StakeholderEngagement #UserExperience #ProductDesign
10 Must-Have Soft Skills for UX Designers https://outwitly.com To view or add a comment, sign in
-
This is a great read on soft skills and stakeholder trust by Sara Fortier. While focused on UX, it's not limited to that field. Whether you’re designing products, leading teams, or recruiting top talent — trust is the real currency. I love this reminder that success doesn’t come from “getting your way,” but from understanding what others need, communicating effectively, and delivering excellence every time. #Leadership #SoftSkills #Collaboration #UX #GrowthMindset
CEO & Founder @ Outwitly Inc. | Staffing UX & Service Design at Scale | Coaching & Elevating Workforces | Design Thought Leader
UXers: 🚫 Don’t discount the power of building stakeholder trust. Everyone gets excited to dive in and start fixing design problems, ⚙️🤸and that makes sense, because fixing problems can be so fun and gratifying, that so many of us have based our careers on it… BUT, telling a product owner, VP, or director of IT what a bad job they did on their product when they’ve sincerely invested time and energy into it…is just going to get their backs up (even if it's disguised with an optimistic "I know you don't realize, but this could be so much better"). If that’s your MO, it will be hard to get them to trust you, consider your suggestions, or let you in on their goals and upcoming projects. The designers and researchers I’ve seen make incredible moves in their careers and become major contributors to showstopping products didn’t do any of it by “getting their way.” Instead, they got good at understanding what others need, acknowledging those needs, serving up the highest quality work possible, and establishing mutual trust. 👉 Trustworthy UXers are always doing these three things: - Tying the work back to ROI and business objectives 🎯 (not using isolating and jargon-y design terms and talking only about the user's needs, the understand their is a business and a budget behind everything) - Honing “soft skills” 💜 (the unsexy things like being organized, responsive, communicative, empathetic, etc.) - Committing to excellence on every little task 🏅(competing with themselves to one-up their last project, pushing to create more delight and be more resourceful, scrappy learners) Don’t forget that your training is a privilege you’re leveraging to help others. Step 1: You understand what your stakeholders need. Step 2: You help your stakeholders understand what users need. Step 3: Your stakeholders help you achieve what’s needed. Step 4: You both help the users. You won't get far if you can't do Step 1 and fully appreciate, respect, consider, or integrate your stakeholders’ perspectives into the work you're doing. Let me know if this resonates. I’ll leave you with a link to a soft skills blog: https://lnkd.in/gHCA6PRh #SoftSkills #StakeholderEngagement #UserExperience #ProductDesign
To view or add a comment, sign in
-
I spent 43 hours learning UX design. Best tip? Design like your user is drunk. Here are 31 world-class rules to keep in mind: 1. Talk to your users like a friendly guide at a party—casual, clear, and fun. Explain like a drunk friend needs directions. 2. With first-time users, keep it simple. Introduce complexity step by step. 3. Encourage users when they try something new; avoid overexplaining. 4. Hide complexity by default. People prefer the status quo—don’t force changes. 5. Focus on Jobs-to-be-Done: design around outcomes, not features. Align with fast, intuitive decisions (System 1 thinking). 6. The closer users are to their goal, the faster they move. Design experiences that help them progress efficiently. 7. Every step matters. From A → B, ask: “What happens in between?” 8. Let users experience the product before asking them to commit to a trial. 25–40% cancel day one to avoid feeling trapped. 9. Reduce cognitive load. Minimize mental effort when moving from A → B. Users ignore unrelated content naturally. 10. Make sure every feature works. Broken features = instant loss of trust. 11. During onboarding, first show value before teaching how to use it. Reinforce with social proof. 12. Don’t just tell—show visually. Short videos or demos beat paragraphs. 13. When asking for notifications, give 1 clear, compelling reason to opt in. 14. Pair necessary but unattractive actions (“should do”) with motivating rewards (“want to do”). 15. users value first—like a free widget—then ask for a trial. Reciprocity works. 16. Ease users into your ecosystem before an upsell or paywall: a. Show you understand their goals b. Show features that help c. Present a personalized path to upgrade 17. Post-purchase matters. Empower users to fully utilize the product. System 1 thinking = intuitive experiences. 18. Onboarding surveys do’s: ✨ Start simple 💚 Show value 🎯 Focus on goals 👂 Personalize 🏢 Mind Conway’s Law (avoid gaps from team silos) 19. People agree to a big task after saying yes to a small one. 20. Validation of action matters. Use social proof near CTAs to boost confidence. 21. Looks matter. Better design = perceived better value. 22. People remember highlights + endings. Smooth offboarding leaves a lasting good impression. 23. Make cancellations clear. Uninstall ≠ subscription canceled. 24. Use friction wisely: - When thoughtful decisions are needed - To prevent mistakes - To help users choose correctly 25. Leverage loss aversion carefully. Real stakes work, fake ones backfire. 26. Maintain visual hierarchy. Step back, simplify, highlight core functions first. 27. Don’t forget about readability. 28. Write with an eraser. Explain concepts with as few words as possible. 29. Social proof helps decisions. Include faces, names, links, and consistent placement. 30. Let others market for you. Compare your product to competitors’ cons. 31. Sell transformation, not features. People buy a better version of themselves.
To view or add a comment, sign in
-
The next generation of designers is already here — and they’re 12 years old. For the past three years, I’ve been teaching web and UX/UI design to kids at Skillbox. I mentored 50+ students, helping them explore UX/UI, prototyping, and visual storytelling. Together we created 100+ projects — from school apps to flower delivery services, all with real UX logic, animations, user tests, and research. But here’s what fascinates me most: These kids don’t learn design the way we did. They live it. They jump into Figma like it’s a sketchbook. They don’t overthink “Can I do this?” — they just open Figma and start creating. They understand user flow without hearing the term “UX.” They test prototypes because it’s fun, not because it’s required. Their projects often look like the work of junior designers: polished, thoughtful, with user flows and responsive design. They intuitively understand usability and accessibility — things many professionals still struggle to learn. And when they use AI — they don’t “implement it.” They just…use it. Because they were born into a world where AI is normal. They don’t overthink the future of design — they’re already shaping it. It sharpened my skills in UX research, design systems, and communication — because guiding a 12-year-old through interface logic requires clarity and structure like nothing else. It also improved my soft skills: patience, clear feedback, adapting communication styles, and being flexible with unexpected ideas. Teaching them reminded me that the future of design is in good hands — hands that type faster, think wider, and collaborate effortlessly with AI. It also reminded me why I fell in love with design in the first place: curiosity, courage, empathy, and play. The next generation isn’t waiting for permission to create — they’re already doing it. #webdesign #ux #education #kids #edtech #creativity #designthinking #inspiration #futureofdesign #design #ai
To view or add a comment, sign in
-
-
UX Constellation Series — Part 2: The Birth of the UX Constellation Model Where Experience, Strategy, and Nonlinearity Converge https://lnkd.in/gyV-CtX9 Every model begins with a frustration. For me, it was the persistent gap I kept encountering between what we teach in classrooms and what is truly needed in the field. In education, students were mastering the tools—wireframes, design systems, prototypes. In agencies, teams were pressured to deliver outputs faster and cheaper. But beneath all of this, something fundamental was missing: strategy, reflection, and nonlinear thinking. The Core Problem Design Thinking gave us a powerful foundation, but in practice it was too often misinterpreted as a linear checklist: empathize, ideate, prototype, test. Students treated it as a recipe to follow, rather than a flexible mindset. Professionals executed steps but rarely integrated business logic, psychological insight, or systems thinking. The consequences were clear: - Education was producing skilled tool operators, but not design leaders. - Industry was treating UX as surface polish, rather than strategic value. A Turning Point Through years of teaching and running a UX agency, I realized we needed a different approach: - A model that could hold complexity without collapsing into rigid phases. - A model that encouraged combination, exploration, and reflection, not just execution. - A model that treated UX as strategy, not decoration. That was the birth of the UX Constellation Model. Why a Constellation? A constellation is not a line—it is a web of points that only gain meaning when connected. UX, too, must be understood as a network of interconnected elements: - Data, AI, Inclusivity, Business Strategy, Interaction Design, Aesthetics, Technology Integration, and Psychology. Designers can navigate these points freely, creating strategies that respond uniquely to context, rather than following a single path. Reflection The UX Constellation Model represents a paradigm shift: From executing tasks → to shaping systems. From following recipes → to designing meaning. In the next episode, we’ll explore the first element: Data as a UX design core.
To view or add a comment, sign in
-
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development