Principles of User-Centric Design

Pretty isn’t enough. Products need principles. UX design isn’t about following trends or adding shiny features—it’s about building experiences that actually work for people. Here are the 4 principles I always come back to: 🔸 Understand → Get close to your users. Build personas, map journeys, run interviews. Without empathy, you’re just guessing. 🔸 Ideate → Creativity with direction. Brainstorm, sketch, and wireframe—but always anchor ideas to real user needs. 🔸 Test → Assumptions don’t scale. Surveys, usability tests, A/B tests—these validate if the solution solves the problem. 🔸 Implement → Execution is everything. From accessibility to onboarding to UI polish—this is where trust is built (or lost). When you miss one of these steps, you feel it. When you nail all four, the experience feels natural, seamless, and human. That’s what separates products people tolerate… from products people love. Which principle do you think teams overlook the most—and why? #UXDesign #UIDesign #ProductDesign #DesignThinking #UserExperience

“𝗨𝘀𝗲𝗿𝘀 𝗱𝗼𝗻’𝘁 𝗰𝗮𝗿𝗲 𝗮𝗯𝗼𝘂𝘁 𝗿𝗲𝗽𝗼𝗿𝘁 𝗱𝗲𝘀𝗶𝗴𝗻.” You sure? Because every major study on usability, adoption, and information design says otherwise. Poor design slows decision-making, hides critical insights, and erodes trust. Good design reduces time to value - and makes the difference between used and ignored reports. Let’s talk specifics. These aren’t opinions - they’re proven UX principles, backed by decades of research: 𝗝𝗮𝗸𝗼𝗯’𝘀 𝗟𝗮𝘄 – 𝗨𝘀𝗲𝗿𝘀 𝘀𝗽𝗲𝗻𝗱 𝗺𝗼𝘀𝘁 𝗼𝗳 𝘁𝗵𝗲𝗶𝗿 𝘁𝗶𝗺𝗲 𝘂𝘀𝗶𝗻𝗴 𝗼𝘁𝗵𝗲𝗿 𝘁𝗼𝗼𝗹𝘀. 𝘚𝘰 𝘸𝘩𝘦𝘯 𝘗𝘰𝘸𝘦𝘳 𝘉𝘐 𝘥𝘰𝘦𝘴𝘯’𝘵 𝘣𝘦𝘩𝘢𝘷𝘦 𝘭𝘪𝘬𝘦 𝘵𝘩𝘦 𝘸𝘦𝘣 𝘢𝘱𝘱𝘴 𝘵𝘩𝘦𝘺 𝘬𝘯𝘰𝘸, 𝘪𝘵 𝘧𝘦𝘦𝘭𝘴 𝘣𝘳𝘰𝘬𝘦𝘯. 𝗗𝗲𝘀𝗶𝗴𝗻 𝗶𝗺𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻: Use clear navigation, clickable affordances, and common interaction patterns. 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: Place slicers where users expect filters - top-left or directly above visuals. 𝗟𝗮𝘄 𝗼𝗳 𝗖𝗼𝗺𝗺𝗼𝗻 𝗥𝗲𝗴𝗶𝗼𝗻 – 𝗘𝗹𝗲𝗺𝗲𝗻𝘁𝘀 𝘄𝗶𝘁𝗵𝗶𝗻 𝘁𝗵𝗲 𝘀𝗮𝗺𝗲 𝗯𝗼𝘂𝗻𝗱𝗮𝗿𝘆 𝗮𝗿𝗲 𝘀𝗲𝗲𝗻 𝗮𝘀 𝗮 𝗴𝗿𝗼𝘂𝗽. 𝘛𝘩𝘪𝘴 𝘩𝘦𝘭𝘱𝘴 𝘶𝘴𝘦𝘳𝘴 𝘴𝘤𝘢𝘯 𝘢𝘯𝘥 𝘱𝘳𝘰𝘤𝘦𝘴𝘴 𝘪𝘯𝘧𝘰𝘳𝘮𝘢𝘵𝘪𝘰𝘯 𝘧𝘢𝘴𝘵𝘦𝘳. 𝗗𝗲𝘀𝗶𝗴𝗻 𝗶𝗺𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻: Use whitespace or cards to visually group KPIs, charts, and filters. 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: Group related metrics like Revenue, Margin, and YoY% into a single visual region. 𝗔𝗲𝘀𝘁𝗵𝗲𝘁𝗶𝗰-𝗨𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗘𝗳𝗳𝗲𝗰𝘁 – 𝗔𝘁𝘁𝗿𝗮𝗰𝘁𝗶𝘃𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝗮𝗿𝗲 𝗽𝗲𝗿𝗰𝗲𝗶𝘃𝗲𝗱 𝗮𝘀 𝗲𝗮𝘀𝗶𝗲𝗿 𝘁𝗼 𝘂𝘀𝗲. 𝘌𝘷𝘦𝘯 𝘪𝘧 𝘵𝘩𝘦 𝘣𝘢𝘤𝘬𝘦𝘯𝘥 𝘭𝘰𝘨𝘪𝘤 𝘪𝘴 𝘤𝘰𝘮𝘱𝘭𝘦𝘹, 𝘢 𝘤𝘭𝘦𝘢𝘯 𝘜𝘐 𝘣𝘶𝘪𝘭𝘥𝘴 𝘵𝘳𝘶𝘴𝘵 𝘢𝘯𝘥 𝘳𝘦𝘥𝘶𝘤𝘦𝘴 𝘶𝘴𝘦𝘳 𝘧𝘳𝘶𝘴𝘵𝘳𝘢𝘵𝘪𝘰𝘯. 𝗗𝗲𝘀𝗶𝗴𝗻 𝗶𝗺𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻: Typography, spacing, and alignment aren’t fluff - they’re functional. 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: A well-spaced, readable KPI section increases scan speed and comprehension. 𝗠𝗶𝗹𝗹𝗲𝗿’𝘀 𝗟𝗮𝘄 – 𝗧𝗵𝗲 𝗮𝘃𝗲𝗿𝗮𝗴𝗲 𝗽𝗲𝗿𝘀𝗼𝗻 𝗰𝗮𝗻 𝗵𝗼𝗹𝗱 7 ± 2 𝗶𝘁𝗲𝗺𝘀 𝗶𝗻 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗺𝗲𝗺𝗼𝗿𝘆. 𝘠𝘦𝘵 𝘮𝘢𝘯𝘺 𝘳𝘦𝘱𝘰𝘳𝘵𝘴 𝘰𝘷𝘦𝘳𝘸𝘩𝘦𝘭𝘮 𝘶𝘴𝘦𝘳𝘴 𝘸𝘪𝘵𝘩 20+ 𝘤𝘩𝘢𝘳𝘵𝘴 𝘰𝘯 𝘢 𝘴𝘪𝘯𝘨𝘭𝘦 𝘱𝘢𝘨𝘦. 𝗗𝗲𝘀𝗶𝗴𝗻 𝗶𝗺𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻: Prioritize. Show what matters first. Use drill-through or navigation to reveal detail. 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: Use a landing page with 3–5 high-value metrics and actions. Design is not just decoration. It’s how users understand your data. It’s what makes insights actionable. And it’s the difference between adoption and abandonment. If users don’t care about report design, it’s probably because they’ve never seen what good design can do. #PowerBI #DataViz #UIUX

We will never be user centred because if we ask people what they want, we just won’t be able to deliver it. I’ve heard that a good many times now and at its heart it demonstrates a foundational misunderstanding of what user centred design actually is. Let me expand… 1. ‘User’ was never meant to only mean end users. We need to make sure that the service works for the staff delivering it too. If it’s impossible to deliver for the staff, that isn’t good user centred design. 2. User centred design doesn’t mean throwing away organisation needs. It means starting with user needs and then prioritising the ideas and services that are feasible and viable for the organisation to deliver. 3. People are brilliant at describing their own experiences, but not always great at designing the solution. If we literally ask “what do you want?” we’ll get feature requests. User centred design is more about understanding behaviours, constraints, motivations and pain points, then designing options that are deliverable. 4. User centred doesn’t mean “more work for the organisation” Done well, it reduces failure demand: repeat contacts, avoidable calls, workarounds, rework, complaints. There’s a strong case for linking user pain points to organisational waste points and cost. 5. It’s not a phase you do at the start A lot of resistance comes from assuming research is a big, slow, one-off event. In practice, it’s little and often: test, learn, iterate, keep checking you’re solving the right problem. 6. The “user” includes people who never get invited into the room or don’t use your services yet. User centred design includes actively seeking underrepresented perspectives and folks with accessibility needs and designing services that actually works for them. We can’t afford not to do this in public services. User centred design isn’t about giving everyone what they ask for. It’s about taking responsibility for understanding what people need, then making the trade-offs visible.

When entering unfamiliar territory, it's useful to keep returning to the first principles of User Research: 1/ Start with the assumption that you don't know what users need or how they think. (Epistemic Humility) 2/ What people say often differs from what they do. 3/ Many usage behaviors rely on unspoken, embodied knowledge that users cannot articulate. Research must surface this tacit dimension. 4/ User behaviors are shaped by their environments, tools, social contexts, and constraints - not just by preferences or rational choices. 5/ Research findings are only meaningful to the extent that they represent users' actual contexts, environments, and behaviors. The lab is never the same as the wild. 6/ Users can reliably identify problems they experience but are less reliable at envisioning effective solutions. Their struggles are data; their suggestions are hypotheses. 7/ The models we create of users and their behaviors are always simplifications. The map is not the territory. 8/ Focus research on the zone just beyond what you already know, where uncertainty is highest and learning potential is greatest. 9/ Research can never be comprehensive. Focus on reducing uncertainty in decision-critical areas rather than attempting exhaustive understanding. 10/ Package insights differently for different audiences (designers, engineers, executives) without compromising integrity or nuance.

In uncertainty, I find myself returning to the principles that guide human-centered design - not just as professional tools, but as ways of being with and supporting each other. Start With Listening Before solving, before debating, before convincing - listen. Human-centered design works because it begins with genuine curiosity about other people's experiences, especially experiences different from our own. Listen to understand, not to respond. Seek Multiple Perspectives The best solutions emerge when we engage people who see things differently. In design, we call this "designing for the extremes." In life, it means genuinely learning from people whose experiences challenge our assumptions. Not to win arguments. To understand something we didn't know. Focus on Human Needs When we design, we look past positions to understand underlying needs. Someone might say "I want a quieter room," but what they need is to feel safe enough to rest. Beneath different positions are often shared human needs - safety, dignity, belonging, hope for our families. Test Assumptions, Including Your Own Good design requires humility. We test ideas with real people because we know our assumptions are incomplete. We expect to learn and adjust. What if we brought that same humility to how we engage with each other? Design for Real Conditions We design for people when they're stressed or afraid - not when everything is working perfectly. We plan for moments of crisis, not just calm. Meeting people where they are, not where we wish they were, is both good design and basic kindness. Create Space for Everyone Designing for belonging isn't about making everyone the same. It's about creating environments where different people can all feel "this space was made for someone like me." We achieve that by intentionally considering who might feel excluded. Small Gestures Matter In healthcare design, small things have outsized impact - a place to set your belongings, a chair positioned for eye contact, natural light. They signal: you matter here. We thought about you. The same is true in daily life. A kind word. A genuine question. Choosing not to post the divisive thing. These aren't trivial. They're how we signal to each other: you matter. Moving Forward Human-centered design doesn't solve everything. But its principles - deep listening, genuine curiosity, humility, focus on human needs, creating space for everyone - offer a way forward. We all have a choice in how we show up. I'm choosing to listen more. To stay curious. To look for what we share. To design - in my work and my life - for everyone's belonging.

The 8 Pillars of Exceptional UX Design: A Strategic Framework True UX excellence extends beyond aesthetics. It's a disciplined approach rooted in research, psychology, and strategic alignment. Here are the core components every designer must master: 1. User Research The foundation. Understand real user needs, pain points, and behaviors through interviews, surveys, and testing. Without it, you're designing on assumptions. 2. Interaction Design (IxD) Shape the user journey. Focus on intuitive navigation, clear feedback loops, and purposeful micro-interactions that guide users seamlessly. 3. Information Architecture (IA) Organize content for clarity and findability. A logical structure is critical—even beautiful designs fail with poor IA. 4. Content Design & UX Writing Craft clear, actionable language. Every button label, error message, and piece of onboarding text must enhance understanding and action. 5. Usability Engineering Ensure products are efficient, effective, and satisfying to use. Employ heuristic evaluations and task analyses to eliminate friction. 6. Accessibility (A11y) Build inclusive experiences for everyone. Adhere to standards like WCAG; accessibility is a necessity, not an option. 7. Human-Computer Interaction (HCI) The science behind UX. Integrate principles from cognitive psychology, ergonomics, and systems design to create intuitive human-centered tools. 8. Data, Analytics & UX Strategy Ground decisions in evidence. Use behavioral data and strategic alignment to connect user needs to business goals and measure success. Mastering these disciplines transforms good design into product leadership. Which of these pillars is most critical in your current projects? #UXDesign #UserExperience #ProductDesign #DesignStrategy #InteractionDesign #Accessibility #HCI #UserResearch

Not every design principle should make your product more engaging. Some should protect people. You’ve probably seen Laws of UX, but its creator, Jon Yablonski also runs another brilliant project: humanebydesign.com It’s a framework for building digital products that respect users, not just attract them. Core principles: 1. Resilient → Design for the most vulnerable and anticipate misuse 2. Empowering → Centre on the value products provide to people  3. Finite → Respect people’s time and focus on meaningful content 4. Inclusive → Reflect the full range of human diversity 5. Intentional → Add friction where needed and favour long-term well-being 6. Respectful → Protect attention and digital health 7. Transparent → Be honest, clear, and free of dark patterns Honestly, I teach and implement this way too little myself, still stuck very much in the optimisation game. So this isn’t preaching, it’s sharing. And as usual with Yablonski’s work, the site is beautifully crafted, full of thoughtful illustrations and links to in-depth articles and research on each principle. So dive in, enjoy, just as I will!

Testing user outcomes can reveal what users actually need. A key part of user-centered design is comparing what users want to do (needs) with what they actually experience (outcomes). When we talk about user needs, we’re often describing problems or gaps in their experience. Teams want to address these needs, but I often see them jump ahead and assume their design will automatically lead to better outcomes. Sometimes this is fine. However, it’s often where things go off track. Using intuition is part of design, but there’s a difference between imagining an ideal experience and actually testing whether it works. Here’s a simple way to think about it: USER NEED = Intention This is what users are trying to do. It reflects their goals, motivations or problems they want to solve. USER OUTCOME = Reality This is what users experience after using your product. It includes emotions, behaviors, and results. It may not directly address the user's need. Too often, teams assume that trying to create something that will help users will lead to a good outcome. But in reality: → The product might solve the wrong problem → Users may struggle to complete their task → The experience may lead to frustration or confusion If your work is mostly based on assumptions, here’s how to bring it back to the user need if you're faced with starting with outcomes the business has assigned: 1. Start with assumptions grounded in quick user research 2. Run small tests. We use Helio to collect fast feedback 3. Compare the results to the original need. Did users accomplish what they set out to do? UX metrics help you see where what users need doesn't match what they actually experience. Attitudinal metrics like satisfaction, expectations, usefulness, and engagement can point out the biggest gaps so you can focus on what matters to users. It's great to start with user needs, but the reality is that most teams begin with an idea of the outcome they want to achieve. That’s okay. As long as you keep checking in with users and adjusting based on the feedback you collect. #productdesign #uxmetrics #productdiscovery #uxresearch

Our industry has a blind spot. We’ve believed that if we build great tech, users will come. That's not enough anymore. Whether you're building for end users or developers, the core principles of human-centered design still apply. The framework is simple: • Desirability - do people want it? • Feasibility - can we build it? • Viability - is it commercially viable? Consider that core human needs remain constant. Just as people in the early 1900s didn't need 'a faster horse' but rather 'faster transportation,' today's users don't need 'blockchain,' they need greater freedom, agency, and control. In web3, this looks like: • Freedom to create and capture value • Control over assets and data • Agency in platform and economic decisions The path forward is clear: pair deep technical development with human-centered design. It's not enough to build powerful technology—we must build technology that serves timeless, core human needs.

The user isn't an afterthought. They're the entire point! The project brief is complete. The budget is approved. The stakeholders have weighed in. You're ready to build. But are you building for them? For the people who approved the funding? For the senior leaders who outlined the vision? What about the person who will actually use what you're creating? Too often, their voice is the one we hear last, if at all. This common practice of putting internal opinions before external needs is a path to irrelevance. We get caught up in our own narratives and internal politics. We mistake what we *think* is a good idea for what *is* a good idea. We prioritize features that appease a stakeholder over those that solve a real-world problem. We design for the theoretical user who lives inside our marketing deck. Not for the messy, unpredictable human who will actually interact with our product. A user-centric approach forces us to step outside our bubble and into the lives of the people we serve. It means we stop guessing and start listening. We conduct research, observe behaviors, and analyze feedback. This becomes the very foundation for our decisions. We focus on solving a problem for a person, not just fulfilling a line item on a project plan. Building a case for this shift isn't about challenging authority. It's about presenting a more reliable path to success. → We show stakeholders the true return on investment comes from creating something people actually want to use. → We demonstrate that reducing friction for a user directly translates to increased adoption, loyalty, and revenue. It's about showing that the tangible benefit a user gains is the most reliable metric of success. Afterall, The most successful products aren't born from executive mandates. They're built on the back of genuine user needs. 💬 What's a product or feature you've seen fail because it ignored its users?