<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bijith Kunchammed on Medium]]></title>
        <description><![CDATA[Stories by Bijith Kunchammed on Medium]]></description>
        <link>https://medium.com/@bijith08?source=rss-a93e93198ee4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AVf4OcPBK7R_KQzaTE79kg.png</url>
            <title>Stories by Bijith Kunchammed on Medium</title>
            <link>https://medium.com/@bijith08?source=rss-a93e93198ee4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:04:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bijith08/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Unhook]]></title>
            <link>https://medium.com/design-bootcamp/unhook-29462d1959b6?source=rss-a93e93198ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/29462d1959b6</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[humanity-first]]></category>
            <category><![CDATA[hooked]]></category>
            <dc:creator><![CDATA[Bijith Kunchammed]]></dc:creator>
            <pubDate>Mon, 08 Jun 2026 15:57:42 GMT</pubDate>
            <atom:updated>2026-06-08T16:33:24.578Z</atom:updated>
            <content:encoded><![CDATA[<h4>Confessions of a UX Addict. What happens when a UX designer realizes they are the victim of their own user retention strategies?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZlLjCFSKTdA3h9T3ORMFnw.png" /><figcaption>designing to Unhook</figcaption></figure><p>A few months ago, I was setting up Google Family Link for my daughter.</p><p>I went through the whole thing — app limits, screen time budgets, content filters, bedtime restrictions. I spent about 45 minutes making sure her phone couldn’t trap her. Making sure the feed would slow down. Making sure she’d have to actually choose to keep scrolling instead of just falling.</p><p>When I was done, I felt like a responsible parent.</p><p>Then I picked up my own phone and opened Instagram.</p><p>I didn’t set a timer. I didn’t have a bedtime restriction. I had no app limit, no content filter, no one watching whether the feed was taking more than it was giving. I just opened it, the way I open it twenty times a day, and I scrolled until something interrupted me.</p><p>I’ve been a UX designer for over twenty years. I’ve built consumer apps. I’ve designed the flows, the notifications, the onboarding sequences, the engagement hooks. I know exactly how these things work. I’ve won awards for making them work well.</p><p>And I set up a protection system for my child that I have never once considered building for myself.</p><p>That’s the thing I can’t stop thinking about.</p><h3>How Hooked Got Into Everything</h3><p>In 2014, Nir Eyal published <em>Hooked</em>. If you work in product or design, you probably know it. Trigger. Action. Variable reward. Investment. A four-step framework for building products that people return to habitually.</p><p>It was genuinely useful. It explained something that designers had felt intuitively but couldn’t articulate — why some products stuck and others didn’t. It gave us a theory. And designers, who had been operating largely on instinct and good taste, loved having a theory.</p><p>The problem is what we did with it next.</p><p><em>Hooked</em> was written for consumer social apps. It was describing a specific product category, in a specific moment, for a specific kind of user — an adult, with full information, choosing freely to use a product.</p><p>But frameworks don’t stay where they’re put.</p><p>By 2016 it was in mobile gaming. By 2018 it was in health and fitness apps — the ones with streaks that made you feel guilty for taking a rest day. By 2020 it was in enterprise software, where I’ve watched sales dashboards gamified with leaderboards and “at risk” badges that made human beings feel like metrics. And now, in 2024, it’s baked into every AI product being shipped — every nudge, every suggested action, every “you haven’t checked in today” prompt is a trigger wrapped in good intentions.</p><p>We didn’t ask whether the framework should spread. We just noticed that it worked, and we used it.</p><h3>The People Who Named It</h3><p>To be fair, some people did ask.</p><p>The Center for Humane Technology — Tristan Harris and others who had worked inside the machine — gave us the systemic critique. They named the attention economy as a public health problem. They made policymakers and parents pay attention. That was genuinely important work.</p><p>Don Norman, who gave us human-centred design in the first place, started arguing that human-centred isn’t enough. That our moral radius as designers needs to expand beyond the user in front of us — to the people the product touches, the families it sits inside, the sleep it disrupts, the anxiety it compounds. He called it humanity-centred design.</p><p>Both of these things are right.</p><p>But neither of them gave me — gave us, working practitioners building real products for real clients — a vocabulary for the opposite. A way to talk about it in a design review. A framework for the unhook.</p><p>CHT said the system is broken. Norman said think bigger. And I went back to my desk and kept designing notification systems, because the client wanted higher open rates and I didn’t have a better language.</p><p>That’s the gap I’ve been trying to close.</p><h3>What I Started Noticing</h3><p>Once you see it, you can’t unsee it.</p><p>The streak in Duolingo. I used to admire it as a retention mechanic. Now I watch people — myself included — open the app not because they want to learn Spanish, but because they don’t want to break the number. The goal has migrated. You’re no longer doing it for the thing. You’re doing it for the record of having done it.</p><p>The like counter. We designed that to tell you something useful — people responded to what you shared. But what it actually does is install a checking behaviour. You post. Now you need to know. Then you need to keep knowing. Every few minutes, the pull. Not because anything has changed. Because the uncertainty is designed to be unresolvable.</p><p>The typing indicator. Three dots. Someone is composing a reply. You cannot leave now. You are being held in an app by punctuation. Social obligation, manufactured by a UI element, because someone on a product team knew that presence creates retention.</p><p>The autoplay countdown. Five seconds before the next episode starts. Stopping requires an active decision. Continuing requires nothing. Inertia, weaponised. The default was chosen deliberately. And it was not chosen for you.</p><p>Every one of these was a design decision. Made by a designer. Probably not unlike me.</p><h3>The Asymmetry That Bothers Me Most</h3><p>Here’s what I keep coming back to.</p><p>The people most harmed by these patterns are not the people who were imagined when they were designed.</p><p>A 32-year-old product designer in Bangalore — someone like me — has context. I know what a streak is. I’ve read <em>Hooked</em>. I can, in theory, make a somewhat informed choice about whether to let it work on me.</p><p>A first-generation smartphone user in Tier 3 India, encountering a financial literacy app for the first time, has none of that context. The mechanics are invisible. The designer’s knowledge advantage is total. And I have designed for that person too.</p><p>An employee using enterprise software they didn’t choose, with engagement mechanics built into their performance dashboard, has no exit. The hook is inside their working day. And I have designed for that person too.</p><p>Same patterns. Wildly different power dynamics. Wildly different ethical weight.</p><p>We designed them without making that distinction. We learned a framework, and we applied it uniformly. The person with the most information and the most choices got the same product as the person with the least.</p><h3>Five Things I’m Trying to Do Differently</h3><p>I’m not here to tell you to stop building products that people use. That would be absurd. What I’m trying to articulate — what I’ve spent the last year trying to build into my own practice — is a different set of questions to ask before the engagement mechanic goes in.</p><p><strong>The first is literacy.</strong> Before any rule, any limit, any control — can the user see how this works? Not the usage data. The intent. This feature uses a variable reward loop. This notification is timed for when cortisol is lowest. This streak is designed to activate loss aversion, not to help you learn. If you can show someone exactly how the mechanic works and they still choose to use it, it’s honest. If you have to hide the mechanic for it to function, something is wrong.</p><p><strong>The second is agency.</strong> Platform defaults are not neutral. They’re chosen for the platform’s engagement, not for the user’s life. What would it look like to give users a blank page — with recommended healthy starting points, grounded in research — and let them write their own terms? News at 8am and 6pm only. Autoplay off. Feed limited to people I actually know. Off by 9:30pm. Their rules. The device as a servant, not a warden.</p><p><strong>The third is environment over willpower.</strong> Every solution we’ve designed for digital overuse puts the burden on the human. Resist the notification. Delete the app. Set a timer. But willpower is finite and unreliable, and you are asking one person to out-muscle a system that has thousands of engineers working in the other direction. The better question is: how do we change the conditions instead of the resolve? When the environment shifts — when the feed slows, when the reward becomes slightly less variable, when the path of least resistance is presence instead of scroll — the pull weakens without anyone having to fight themselves.</p><p><strong>The fourth is signal preserved.</strong> The fear of unhooking is missing something real. A genuine emergency. A message from someone who matters. Breaking news that changes things. This is a legitimate fear, and it’s exactly what engagement-first design exploits to keep notifications on. The answer isn’t less — it’s separation. What the user defines as genuinely important should reach them always, frictionlessly, immediately. Everything else — the streak reminders, the algorithmic nudges, the engagement bait — operates within rules the user has set. Nothing important is lost. Everything extractive is contained.</p><p><strong>The fifth is the whole person.</strong> The phone emits radiation. It tracks location. It shapes sleep, relationships, the development of children who watch adults use it. Designing for the whole ecosystem means taking responsibility for all of this, not just the interface. A device designed for human flourishing doesn’t just show you how long you’ve used an app. It understands what you were doing instead — and whether that was better.</p><h3>What It Could Look Like</h3><p>I’ve been sketching what an OS designed around these five principles would actually look like. Not a new product — a design brief for the infrastructure that already exists.</p><p>A Hook Map: open any app and see, plainly, exactly how it’s designed to keep you. Variable reward loop. Social comparison mechanic. Streak anxiety trigger. Labelled. Not hidden.</p><p>A Gap screen: what you said you wanted from this app versus what you actually do. Shown once, gently, without judgment.</p><p>Your Rules: a blank page with recommended healthy starting points. You write the terms. The device holds them — not by blocking or locking, but by quietly shifting the environment when you’re in the spaces and times you said mattered.</p><p>A Quiet Mode: not do not disturb. Something more considered. The phone knows you’re home, that your family is present, that you said this time was yours. It becomes slightly less interesting. Not useless. Just less insistent.</p><p>A Whole Self view: radiation levels, privacy exposure, sleep impact, usage patterns in the context of your actual life — not as guilt, but as information. The device aware that it exists in a body, a home, a family.</p><p>None of this requires technology that doesn’t exist. The sensors are there. The APIs are there. Apple and Google have all the plumbing. What they’ve chosen to build on it is control and surveillance. This is a choice to build care instead.</p><h3>The Question I Can’t Answer Yet</h3><p>I set up Family Link for my daughter because I understood what the product was doing and I didn’t want it done to her without her knowledge or consent.</p><p>I haven’t done the same for myself. Not really. Not in any way that’s honest.</p><p>And I build these products. That’s the part I sit with.</p><p>I don’t think I’m a bad designer. I think I was working within a framework that felt like craft and turned out to also be extraction. I think most of us were. The best engagement mechanics I ever designed — the ones I was proudest of — were the ones that worked so well the user didn’t notice they were being held.</p><p>That’s not a neutral thing to be good at.</p><p>So here’s what I want to leave you with. Not an answer. A question that I think is worth carrying into your next project, your next design review, your next conversation with a client who wants higher DAU.</p><p>Does this feature need the user to come back — or does it need the user to flourish?</p><p>Those two things are not always in conflict. But they are not the same thing. And for most of the products we’ve built, for most of the last decade, we designed for the first one and called it the second.</p><p>I’d like to know what happens when we start designing for both.</p><p><em>Bijith Kunchammed is Co-founder and Head of UX at AufaitUX, an award-winning UX design agency with studios in Bengaluru, Calicut, Palo Alto, and Sharjah.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29462d1959b6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/unhook-29462d1959b6">Unhook</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Prettier Your AI Prototype, the Deeper Your Design Debt]]></title>
            <link>https://medium.com/design-bootcamp/the-prettier-your-ai-prototype-the-deeper-your-design-debt-067367e1abf3?source=rss-a93e93198ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/067367e1abf3</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-with-ai]]></category>
            <category><![CDATA[design-debt]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <dc:creator><![CDATA[Bijith Kunchammed]]></dc:creator>
            <pubDate>Tue, 19 May 2026 07:24:32 GMT</pubDate>
            <atom:updated>2026-05-19T07:24:32.966Z</atom:updated>
            <content:encoded><![CDATA[<p><em>After 20 years in IT, I’ve watched the same crisis play out in slow motion. AI tools have hit fast-forward.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kk5RnWKgvulQPpkZh388ig.png" /></figure><p>I‘ve sat in enough product reviews to recognise the pattern.</p><p>The roadmap is healthy. Velocity is good. The design looks polished — genuinely polished, especially now that AI tools are in the workflow. And somewhere in the back half of the deck, there’s a line item: <em>“UX cleanup / design inconsistencies.”</em> Underfunded. Unscheduled. Quietly moved to next quarter.</p><p>That line item is design debt. And unlike the technical kind, it doesn’t throw errors. It doesn’t break a build. It just sits there, compounding — in the friction your users experience, in the support tickets you attribute to other causes, in the churn you blame on pricing.</p><p>I gave a talk on this at UXINDIA 2023. What I didn’t fully anticipate then was how dramatically AI tools would change the speed at which design debt accumulates — and how much harder they’d make it to see.</p><h3>First, what design debt actually is</h3><p>The term borrows from technical debt — the implied cost of rework when shortcuts taken now create constraints later. But design debt is structurally different, and that difference matters.</p><p>Technical debt is legible. A poorly written function will eventually break something measurable. Design debt manifests as <em>friction</em> — a checkout flow that requires one extra confirmation, a dashboard that forces users to build a mental model before they can act, a navigation pattern that’s almost right but not quite. None of these trigger incident reports. They just quietly erode conversion, retention, and trust.</p><p>The cost isn’t borne in your sprint cycles. It’s borne in your user behaviour — in every moment someone pauses, backtracks, or gives up and calls support instead.</p><p>There are several ways design debt enters a product: rushed decisions, unenforced design systems, features added without restructuring the information architecture underneath them. But the source that makes all the others worse is the one that’s hardest to fix — the absence of a feedback loop between what users actually do and what the design team knows. Without that loop, debt is invisible by definition. You can’t measure what you’re not looking for. And you can’t fix what you never see accumulating.</p><h3>The false confidence problem comes first</h3><p>Before we talk about AI as an accelerant, we need to talk about why design debt was already hard to escalate — because AI has made this underlying problem significantly worse.</p><p>Design risk has always had a visibility problem. In a well-run organisation, rough artefacts signal open questions. A wireframe with annotations that say “this flow is unvalidated” or “user research pending” creates room for the right conversation. Stakeholders know to push back. Designers know to flag uncertainty.</p><p>AI-generated outputs short-circuit that signal entirely.</p><p><strong>A product manager presented with a polished AI-generated prototype feels differently about proceeding to development than they would looking at a rough wireframe. </strong>The prototype <em>looks</em> resolved. It implies that design problems have been solved. The visual quality communicates completeness even when the underlying user insight is absent.</p><blockquote><em>AI-generated design artefacts are increasingly indistinguishable from research-validated ones — to everyone except the users who have to use them.</em></blockquote><p>The escalation signals that would previously flag design risk — rough artefacts, visible uncertainty, explicit annotation of open questions — are being replaced by outputs that communicate false resolution. Stakeholders who approve work based on visual quality are systematically underestimating the unvalidated assumptions embedded in what they’re approving.</p><p><strong>The downstream effect: </strong>products ship with confident, beautiful interfaces built on unverified assumptions about how users think, what they prioritise, what language they use. When those assumptions are wrong — and without research, some percentage of them always will be — the cost of correction is substantially higher than validation would have been at the discovery stage. How much higher depends on your product, your user base, and how deeply the wrong decision has been embedded. But every practitioner who has managed a significant product rework knows the ratio is painful.</p><h3>AI as accelerant: the mechanism</h3><p>Generative design tools have genuinely changed what a small team can produce in a week. That’s the pitch, and it’s not wrong.</p><p>But velocity applied without direction is how you build a highway to the wrong city.</p><p>AI tools are optimised for output generation — screens, components, copy variants, motion specs. They are not, by nature, optimised for validating whether that output solves the right problem for the right user. The practical consequence, from what I’ve observed across audits: teams using AI-assisted design produce significantly more screens in the same time — but each additional screen represents an additional unvalidated design decision. The output scales. The insight doesn’t.</p><p>When I review products from teams that adopted AI tooling aggressively without adjusting their research process, I see the same pattern: beautiful interfaces, inconsistent mental models. Individual screens that look production-ready. User journeys that collapse at the third step because nobody stress-tested the handoffs between them. Design debt that is cosmetically invisible but behaviourally catastrophic.</p><p>Early in my career, working on a 10,000-page website redesign for a major airline — integrating booking, check-in, and frequent flier systems into a coherent user experience — the sheer scale of the work forced a discipline that AI now makes it easy to bypass. You couldn’t generate your way through information architecture that complex. You had to understand how users moved through it, where they got lost, what they actually needed at each decision point. Slowness was a forcing function for rigour.</p><p>AI removes that forcing function. The debt accumulates faster precisely because production friction — the thing that used to make you think before you made something — is gone.</p><h3>The double-edged sword: AI can also surface debt</h3><p>This is not an argument against AI tools in design. It’s an argument for using them with clear-eyed awareness of what they can and cannot do.</p><p>Used deliberately, AI tooling is genuinely useful for <em>identifying</em> existing design debt. Consistency checking at scale — flagging when components deviate from the design system, surfacing accessibility violations, identifying where language patterns break down across a product — is something AI can assist with faster than manual audit. Tools like Stark have moved accessibility checking from a periodic review into a continuous layer. Design system governance tools are beginning to flag drift between what’s in the library and what’s actually shipped. These are real capabilities, even if they’re still maturing.</p><p>The distinction is in how teams frame AI’s role.</p><p><strong>AI as production accelerator only:</strong> You go from brief to deliverable faster. Debt accumulates faster and quieter, because the review rigour hasn’t scaled with the output velocity.</p><p><strong>AI also as audit layer:</strong> You use it to continuously check what has been produced against established standards — design system compliance, accessibility, content consistency. Debt gets caught earlier, when it’s still cheap to fix.</p><p>Most teams are doing the first almost exclusively. The economic incentive is obvious — faster output is immediately legible as productivity. Systematic audit doesn’t show up on a velocity dashboard. So it gets deprioritised, then dropped, then forgotten until a redesign project surfaces what’s been quietly accumulating for eighteen months.</p><h3>What actually works</h3><p>The answer isn’t to slow down. It’s to make sure speed is applied to the right things.</p><p><strong>Research precedes generation — even a little research.</strong> The temptation with AI tools is to go from brief to prototype in hours. The problem isn’t the speed; it’s skipping the step that determines whether you’re building the right thing. Research doesn’t have to be exhaustive to be directional. In my experience, even three to five qualitative sessions with real users will surface the two or three assumptions most likely to be wrong — the ones that, if unchecked, become the expensive design decisions you’re living with two years later. AI-generated screens built on a validated problem definition are significantly more durable than those built on a brief alone.</p><p><strong>Design systems are the debt firewall — but only if they’re enforced.</strong> A maintained design system is one of the highest-leverage investments a product organisation can make against design debt. The problem is that AI generation tools don’t automatically respect your system. Teams using AI to produce components that then get manually reconciled with the design system are doing double work. The governance question — how does AI-generated output get reviewed for system compliance before it moves to development? — needs an explicit answer, not an implicit assumption that someone will catch it.</p><p><strong>Treating “teams that do research” and “teams that use AI” as the same population.</strong> The practitioners I’ve seen navigate this well aren’t choosing between research and AI — they’re using AI to make research more efficient. Synthesis, pattern identification across interview transcripts, generating hypotheses from behavioural data. That’s the compounding advantage: AI applied where it adds rigour, not just where it adds speed.</p><p><strong>Making validation status visible on every artefact.</strong> The false confidence problem is partly a communication problem. If every design artefact that enters a review carries an explicit note on its validation status — what has been tested, what assumptions remain open, what research it’s based on — stakeholders can’t mistake polish for proof. This sounds administrative. In practice, it’s one of the more effective ways to keep the right conversations happening at the right time.</p><h3>The question that matters</h3><p>Design debt is ultimately a risk management issue, not a design team issue. The decisions that create it — timelines that compress research, roadmaps that don’t budget for debt retirement, adoption of AI tooling without governance frameworks — are made at the leadership level.</p><p>The cost structure is asymmetric. Validation at the discovery stage is the cheapest intervention in the design process. Correction after development is substantially more expensive. Correction after a product has shipped and trained a user base to work around its failures is more expensive still — not just in engineering time, but in the retraining cost, the support overhead, and the trust you’ve spent with users who expected something better.</p><p>AI tools have shifted the economics of design debt in a direction that demands more leadership attention, not less. The barrier to producing designed artefacts has dropped to near zero. The barrier to producing artefacts that reliably serve real users has not moved.</p><p>That gap — between production velocity and research rigour — is where design debt lives. It’s always been there. It’s just growing faster now, and looking more convincing while it does it.</p><p>The question isn’t whether your product has design debt. Every product does. The question is whether you’re managing it — or waiting to be surprised by it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=067367e1abf3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-prettier-your-ai-prototype-the-deeper-your-design-debt-067367e1abf3">The Prettier Your AI Prototype, the Deeper Your Design Debt</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your UX research didn’t fail. Your expectations did.]]></title>
            <link>https://medium.com/design-bootcamp/your-ux-research-didnt-fail-your-expectations-did-ffd9cfb355e4?source=rss-a93e93198ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffd9cfb355e4</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Bijith Kunchammed]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 08:07:14 GMT</pubDate>
            <atom:updated>2026-04-23T08:07:14.585Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Why “we already knew that” is the most misunderstood response a research team can hear`</strong></h4><p>There’s a moment that happens in almost every research readout.</p><p>The findings go up on screen. The patterns are clear. The team walks through what users said, what they struggled with, what they needed. And somewhere in the room – usually from someone with a VP or C in their title comes the comment:</p><blockquote><strong>“This is what we already knew. Nothing new here.”</strong></blockquote><p>And just like that, months of fieldwork, synthesis, and careful analysis get quietly filed under <strong><em>not worth it</em></strong>.</p><p>I’ve seen this happen enough times that I want to name it directly: this isn’t a research failure. It’s an expectation failure. And it’s one that the design and research community hasn’t done a good enough job of getting ahead of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5hmFktfRffPaF8ndIhG--A.png" /></figure><h3>The wrong question executives are asking</h3><p>When a senior leader walks into a research readout, they’re often – consciously or not – asking: <strong><em>“What surprised us?”</em></strong></p><p>That’s the wrong question.</p><p><strong>Research isn’t an idea generator</strong>. It’s not a revelation machine designed to surface the unexpected and overturn assumptions. Those moments happen, yes. But they’re not the point.</p><blockquote>The real question research answers is: “What do we now know well enough to act on?”</blockquote><p>That shift – from <strong>surprise</strong> to <strong>certainty</strong>– is the whole ballgame. And most business leaders have never been told this clearly.</p><h3>Why “obvious” outcomes are actually good</h3><p>Here’s a useful test. Take any finding that felt obvious after the research. Now ask yourself:</p><blockquote>Before we ran this study – was every decision-maker in this room aligned on that point? Would we have built the same thing without it?</blockquote><p>Almost always, the answer is no.</p><p>What felt “obvious” in the readout was often a point of quiet disagreement before it. Different teams had different mental models. Leadership had one set of assumptions; product had another; engineering had a third. Research doesn’t just surface insight – it <strong>resolves ambiguity </strong>and creates a shared version of reality that the whole organisation can build from.</p><p>That’s not obvious. That’s foundational.</p><h3>The confidence machine</h3><p>Here’s the most useful reframe I’ve found for explaining the value of research to people who aren’t inside the process:</p><blockquote>Research isn’t a treasure map. It’s the tool that tells you whether you’re digging in the right place – before you hire the excavation crew.</blockquote><p>The outcome of good research<strong> isn’t “we found something new</strong>.” The outcome is “<strong>we now know which direction to commit to, and why.</strong>”</p><p>In a business context, that’s not a soft outcome. That’s risk reduction. That’s the difference between a $2M build that solves the right problem and a $2M build that solves the problem your team assumed existed.</p><h3>What executives should actually expect from UX research</h3><p>If you’re a VP, a CEO, or any leader who sits outside the day-to-day design process, here’s a more accurate set of expectations:</p><p><strong>Research will confirm things</strong>. That’s not failure. Confirmation means you were right and now you can move faster because you don’t have to hedge.</p><p><strong>Research will align your team.</strong> Often the real value isn’t the insight itself but the shared language it creates. When research says it, everyone agrees. When one team member says it, it’s an opinion.</p><p><strong><em>Research will occasionally surprise you. </em></strong>When this happens, pay attention. These moments are the ones that prevent the most expensive mistakes.</p><p><strong><em>Research will slow you down slightly to speed you up significantly</em></strong>. The teams that skip discovery to move faster are the ones who rebuild the most.</p><h3>A different way to measure research success</h3><p>Stop measuring research by how surprising the findings are. Start measuring it by how confidently the team moves after the readout.</p><p>Did the next decision happen faster? Did the room stop arguing about what users want? Did the brief get sharper? Did the scope get smarter?</p><p>Those are the outcomes that matter. And they rarely make it into a highlight reel but they show up in every product that actually works.</p><p>The next time someone in your organisation says “we already knew that” after a research readout, resist the urge to defend the research. Instead, ask them: <strong>“So why hadn’t we acted on it yet?”</strong></p><p>That question usually answers itself.</p><p>–</p><p>Written from 20+ years of working at the intersection of enterprise design and business strategy. If this resonated, I’d love to hear how your organisation talks about research value – drop a response below .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffd9cfb355e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/your-ux-research-didnt-fail-your-expectations-did-ffd9cfb355e4">Your UX research didn’t fail. Your expectations did.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HAID framework for how human designers and AI should actually divide the work]]></title>
            <link>https://medium.com/@bijith08/ai-wont-replace-ux-designers-it-will-expose-which-ones-were-never-really-doing-ux-5ffe0ae310a1?source=rss-a93e93198ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ffe0ae310a1</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-process-with-ai]]></category>
            <category><![CDATA[ux-process]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Bijith Kunchammed]]></dc:creator>
            <pubDate>Tue, 14 Apr 2026 10:13:45 GMT</pubDate>
            <atom:updated>2026-04-17T02:58:37.142Z</atom:updated>
            <content:encoded><![CDATA[<h3>Framework for how human designers and AI should actually divide the work</h3><p><em>After Observing new wave of AI tools in UX, here’s a framework suggestions for how human designers and AI should actually divide the work — and why getting that division wrong will cost you more.</em></p><p>Every few months, a new wave of AI tooling arrives with the implicit promise that UX design is next in line for automation. Figma plugins that generate interfaces from prompts. AI that writes microcopy. Synthetic users that simulate research. Tools that turn a brief into a prototype in minutes.</p><p>Most UX practitioners respond to this in one of two ways: defensive dismissal (“AI can’t replace human empathy”) or uncritical adoption (“I just use it for everything now”). Both responses miss the more useful question.</p><p>Not: <em>will AI replace UX designers?</em></p><p>But: <em>which parts of what UX designers currently do actually require a human — and which parts never did?</em></p><p>After ten years of enterprise UX practice, I’ve come to a position that’s uncomfortable for both camps. AI has already taken the parts of UX that were always production work. What’s left — the parts AI structurally cannot do — is what UX was always supposed to be about. The practitioners who thrive are the ones who recognise this clearly enough to redesign how they work.</p><p>What follows is a framework I’ve been developing for how UX teams should structure their process in the AI era — not as a reaction to AI, but as a deliberate design of where human judgement and AI capability each do their best work.</p><p>Our team would like to call it as <strong>HAID framework: Human + AI in Design.</strong></p><h3>First — be honest about what AI has already taken</h3><p>Before proposing what humans should protect, it’s worth naming what AI has genuinely replaced — because pretending otherwise makes the rest of the argument less credible.</p><p>AI can generate UI variants at speed. It can write first-draft microcopy. It can produce wireframe structures from a prompt. It can summarise usability test transcripts, synthesise patterns from interview data, create component structures, and generate accessibility-flagging reports. <a href="https://www.nngroup.com/articles/ai-ux-getting-started/">The Nielsen Norman Group has documented</a> how AI tools are already meaningfully accelerating the production phases of UX work.</p><p>If your value as a UX practitioner is primarily in producing these things quickly, that value has been substantially compressed. Not destroyed — but compressed. The speed advantage is gone. The volume advantage is gone.</p><p>What remains is everything that requires presence, trust, accumulated judgement, and the ability to notice what wasn’t recorded.</p><p>· · ·</p><h3>The HAID framework — five phases, two lanes</h3><p>The framework structures the UX process across five phases. In each phase, two questions are answered explicitly: what should AI do here, and what must a human do here — and crucially, what goes wrong when those boundaries are crossed.</p><h4>01 Discover — human-led, AI-assisted</h4><p><strong>What AI does</strong></p><p>Transcribes and tags interview recordings</p><p>Preliminary pattern-spotting across session data</p><p>Desk research and competitive landscape synthesis</p><p>Generates first-draft screeners and discussion guides</p><p><strong>What the human does</strong></p><p>Conducts contextual observation and fieldwork</p><p>Builds trust with resistant or constrained users</p><p>Recognises the unexpected finding not in the data</p><p>Makes ethical calls in real time with vulnerable users</p><p>What goes wrong if inverted: AI analyses what was recorded. It cannot recognise what wasn’t recorded but should have been. The finding that changes a project almost never comes from tagged data — it comes from a researcher noticing something nobody thought to code for.</p><blockquote>From the work · Community platform for rural India</blockquote><blockquote>When we conducted ethnographic research with rural gamers in tier 3–4 cities, our research plan was built around session flows and progression mechanics. Field observation revealed something entirely outside the brief — that playtime was organised around erratic electricity schedules, shared devices between households, and social group dynamics invisible from urban assumptions. No AI analysing existing datasets would have surfaced this. It required a researcher present in the environment, noticing something the protocol hadn’t anticipated.</blockquote><h4>02 Define — human-led, AI-challenged</h4><p><strong>What AI does</strong></p><p>Generates alternative problem framings from research data</p><p>Identifies logical gaps in the proposed problem statement</p><p>Stress-tests assumptions against existing evidence</p><p>Produces first-draft personas from synthesised data</p><p><strong>What the human does</strong></p><p>Synthesises conflicting findings into a defensible statement</p><p>Reads organisational context never written in any brief</p><p>Decides which AI-generated challenges are valid</p><p>Owns the problem definition with the client</p><p>What goes wrong if inverted: AI-generated problem statements are coherent and well-structured. They will miss the insight that came from the thing nobody said out loud in the session — the political dynamic, the history of the failed system, the unstated fear driving the brief.</p><h4>03 Design — collaborative, AI generates, human judges</h4><p><strong>What AI does</strong></p><p>Generates structural options and UI variants at speed</p><p>Produces microcopy drafts and content structure</p><p>Flags accessibility issues in component designs</p><p>Creates design system documentation</p><p><strong>What the human does</strong></p><p>Decides which direction to pursue and why</p><p>Protects unconventional decisions from research insight</p><p>Recognises when a generated option is technically valid but contextually wrong</p><p>Defends decisions under stakeholder pressure</p><p>What goes wrong if inverted: AI optimises for visual coherence and conventional patterns. It will not protect an unconventional decision that came from a specific field finding — because it has no access to that finding’s weight. The best-looking option wins. The right option loses.</p><blockquote>From the work · BiCXO executive dashboard</blockquote><blockquote>The BiCXO platform went through three structural pivots during design — each triggered by a discovery finding that contradicted what the design system would naturally have produced. An AI working from the brief would have generated a sensible, conventional executive dashboard. What the research demanded was something structurally different: a 30-second clarity constraint that made every layout decision counterintuitive until you understood why. That judgement — and the ability to defend it in a stakeholder room — was irreplaceably human. The platform won the DNA Paris Design Award 2023.</blockquote><h4>04 Validate — human-led, AI-analysed</h4><p><strong>What AI does</strong></p><p>Transcribes and analyses usability sessions</p><p>Identifies patterns across multiple sessions at speed</p><p>Severity-scores findings against defined criteria</p><p>Generates first-draft findings reports</p><p><strong>What the human does</strong></p><p>Recruits appropriately and builds session rapport</p><p>Adapts protocol when something unexpected surfaces mid-session</p><p>Reads the AI analysis against what was observed in the room</p><p>Adds the interpretation layer the data alone cannot produce</p><p>What goes wrong if inverted: AI produces findings that are accurate but incomplete. The finding that changes the project often comes from noticing something no one would think to tag in a transcript — a pause, a look away, an off-script comment that unlocks the real problem.</p><blockquote>From the work · ID Fresh field sales</blockquote><blockquote>During validation research for the ID Fresh mobile platform, usability sessions revealed friction points that appeared in the transcript data. But the finding that drove the most significant redesign — that field agents were switching between the app and a mental checklist because the app’s step sequencing didn’t match their physical workflow — came from watching body language, not from analysing what was said. The AI analysis was accurate. It missed the most important thing. A 40% reduction in data entry errors followed the redesign built on that observation.</blockquote><h4>05 Deliver — AI-accelerated, human-owned</h4><p><strong>What AI does</strong></p><p>Generates handoff documentation and annotations</p><p>Produces developer-ready asset specifications</p><p>Maintains design system and changelog documentation</p><p>Creates accessibility compliance checklists</p><p><strong>What the human does</strong></p><p>Presents findings to specific stakeholder audiences</p><p>Defends design decisions when development constraints arrive</p><p>Decides what to protect versus what to compromise</p><p>Stays in the room through development — not just handoff</p><p>What goes wrong if inverted: Design decisions get made in development because nobody was there to defend them. The handoff document was thorough. The human wasn’t present. The gap between a final design file and a shipped product is where most UX quality is lost — not in research, not in design, but in the translation.</p><blockquote>From the work · Roca compliance system</blockquote><blockquote>The Roca tax and compliance platform replaced a fragmented SharePoint system used by legal and finance teams across multiple factories. The handoff documentation was comprehensive. What protected the design through development was a practitioner in the room when developers proposed simplifications to the case management hierarchy — simplifications that would have reintroduced the exact fragmentation the design had resolved. AI cannot have that conversation. A human who understands why the decision was made can.</blockquote><p>· · ·</p><h3>The one principle the framework rests on</h3><blockquote><em>Use AI to eliminate everything that doesn’t require judgement. So humans can spend all their time on everything that does.</em></blockquote><p>This reframes the AI threat entirely. AI doesn’t threaten UX practitioners who are spending their time on presence, trust, interpretation, and defence of research-grounded decisions. It threatens practitioners whose primary value was producing things quickly — variants, documentation, copy, components.</p><p>The former is UX. The latter was always production work that happened to live inside UX teams.</p><p><a href="https://hbr.org/2023/08/how-to-use-ai-to-do-practical-things-a-new-guide">Harvard Business Review’s research on AI augmentation</a> consistently shows that the highest-value human contribution in AI-assisted workflows is not generating outputs — it’s evaluating them. Knowing which AI-generated option is right for this context, this user, this constraint. That evaluation capability is built from accumulated experience with real users in real situations.</p><p>Which is, incidentally, exactly what a decade of rigorous UX practice produces.</p><p>· · ·</p><h3>What this means for how you hire, train, and structure UX teams</h3><p>If the HAID framework is correct, a few implications follow for how design teams should be built and evaluated.</p><p><strong>Hire for field presence, not just tool fluency.</strong> The practitioner who can conduct ethnographic research in a Tier 3 city, build rapport with a sceptical compliance officer, and notice the off-script moment that changes the project direction is more valuable than ever. The practitioner who is primarily skilled at producing polished deliverables quickly has had their primary advantage taken.</p><p><strong>Invest in synthesis, not just research.</strong> The gap between observation and insight is where most teams leak value. AI can pattern-match. It cannot weigh. Training your team to synthesise conflicting findings into a defensible design decision — and to document why — is the highest-leverage capability investment a design leader can make right now.</p><p><strong>Keep humans in the room through delivery.</strong> The HAID framework’s fifth phase is the most neglected. AI can produce extraordinary handoff documentation. But design quality is protected or lost in the conversations that happen after handoff — when a developer asks “can we simplify this?” and someone needs to say “no, here’s why.” That person needs to exist and needs to be present.</p><p>The era of AI doesn’t diminish the value of UX. It clarifies it — stripping away the production work that was always adjacent to the real discipline and leaving only the work that required a human to do it properly.</p><p>For practitioners who were doing that work, this is an opportunity. The production burden lifts. The judgement work expands.</p><p>For practitioners whose value was in the production — it’s a more urgent conversation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ffe0ae310a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Steve Jobs was right, and so is user research.]]></title>
            <link>https://medium.com/design-bootcamp/steve-jobs-was-right-and-so-is-user-research-500f0b22b90e?source=rss-a93e93198ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/500f0b22b90e</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[steve-jobs]]></category>
            <category><![CDATA[ux-process]]></category>
            <dc:creator><![CDATA[Bijith Kunchammed]]></dc:creator>
            <pubDate>Wed, 08 Apr 2026 05:02:51 GMT</pubDate>
            <atom:updated>2026-04-14T22:24:05.143Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Steve Jobs was right. And so is user research.</strong></h3><h4>Everyone quotes Jobs to dismiss user research. They’re reading him wrong, and it’s costing their products.</h4><p>Bring up user research in almost any product meeting, and someone will eventually say it. You know the quote. <em>“</em><strong><em>People don’t know what they want until you show it to them.”</em></strong> Attributed to<strong> Steve Jobs,</strong> deployed as a conversation-ender, used to justify skipping discovery and getting straight to building.</p><p>I’ve heard it dozens of times across ten years of enterprise UX. And every time, I think the same thing: they’re misreading him.</p><p>Jobs wasn’t arguing against understanding users. He was arguing against a specific, genuinely useless kind of research like asking users to imagine products they’ve never seen. That’s a real failure mode. Focus groups generating feature wish lists, surveys asking “what would you want in your next phone?” Jobs was right to dismiss all of that. Users can’t design what doesn’t exist yet.</p><p>But here’s what gets lost in the quote: Jobs and his teams were <strong><em>obsessive observers.</em></strong> They studied how people actually lived with technology. Where the friction was. What people were tolerating that they shouldn’t have to. The iPod didn’t come from a user saying “I want a thousand songs in my pocket.” It came from noticing that people were burning CDs, managing files manually, and using underpowered MP3 players. Something that nobody had resolved the gap between having digital music and actually enjoying it. That’s a discovery finding. That’s the kind of research Jobs was doing, even if he’d never have called it that.</p><blockquote><strong><em>Jobs didn’t ask users what to build. He observed what they were struggling with and then imagined the resolution. That sequence is exactly what good discovery is designed to produce.</em></strong></blockquote><p>The distinction matters enormously, because getting it wrong has real consequences for how product teams work.</p><figure><img alt="Two-column comparison table. Left column titled ‘What Jobs rejected’ lists: asking users what features they want, focus groups generating wish lists, asking users to imagine unseen products, treating user requests as a product roadmap. Right column titled ‘What great discovery does’ lists: watching how users behave not what they say, finding workarounds users built around broken experiences, identifying unmet needs users can’t articulate, understanding the frustration a new product can resolve." src="https://cdn-images-1.medium.com/max/1024/1*AY0GBLJHQx5dTBOaRBmXgQ.png" /><figcaption>What Jobs rejected versus what great discovery actually does</figcaption></figure><h3>Great ideas don’t live in a designer’s head</h3><p><em>This is the part most design blogs won’t say plainly: the designer’s imagination is the least reliable source of good design ideas.</em></p><p>That’s not a criticism of designers. It’s a structural observation. A designer working from a brief is working from assumptions — their mental model of the user, the client’s stated requirements, analogies from products they’ve seen before. Those inputs produce competent, often attractive work. They rarely produce the insight that changes how a product actually gets used.</p><blockquote><strong>From the work</strong></blockquote><blockquote>When we began our research with rural gamers in tier 3–4 cities across India exploring how low-income players in small towns engage with mobile gaming our most experienced designer had a confident model of session flows and progression mechanics before fieldwork started. Early ethnographic sessions revealed that these gamers organised playtime around erratic electricity, shared devices, and social group dynamics in ways that defied urban assumptions. The engagement strategies that emerged bore almost no resemblance to that first model. The good idea wasn’t invented. It was discovered.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a04OLFjtGLojv0I8LdfaDg.png" /><figcaption>Our research team with rural gamers in tier 3–4 cities across India</figcaption></figure><p>I’ve watched this pattern repeat across every significant project in ten years. The idea that moved the needle was almost never the one somebody walked in with. It was the one that emerged from the collision between what we assumed and what we found.</p><p>· · ·</p><h3>There are four ways discovery produces genuine innovation</h3><p>Not all research surfaces breakthrough insight. But across a decade of UX, four patterns appear consistently when discovery produces something transformative.</p><p><strong>The unexpected workaround.</strong> Users have already solved the problem you’re designing for, badly, using tools never meant for it. The workaround is the real brief. People burning CDs and managing files manually wasn’t a feature request for the iPod. It was the unmet need that made the iPod obvious once someone was paying close enough attention. <a href="https://www.researchgate.net/publication/240798174_Going_Deeper_Seeing_Further_Enhancing_Ethnographic_Interpretations_to_Reveal_More_Meaningful_Opportunities_for_Design">IDEO’s ethnographic practice</a> is built almost entirely on surfacing exactly these kinds of improvised workarounds — the gap between what a product provides and what users have already built around it.</p><p><strong>The contradicted mental model.</strong> Users organise or understand things differently from how the product team does. Their mental model is always the more correct one — they’re the ones who have to use the product. Any navigation or architecture built on the team’s assumptions will feel perpetually slightly wrong, and no user will ever be able to say exactly why. <a href="https://www.nngroup.com/articles/mental-models/">Nielsen Norman Group’s research on mental models</a> has consistently shown this mismatch to be one of the leading causes of low product adoption in enterprise software.</p><p><strong>The silent struggle.</strong> Users complete a task successfully but with visible hesitation or backtracking they never report — because they assume they’re using it wrong, not that the design is wrong. <a href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">Observation catches what interviews miss entirely</a>, which is why even small-sample usability studies consistently surface the most impactful friction. This is where the most consequential improvements live, invisible until someone goes looking.</p><p><strong>The unasked question.</strong> Users reach for something that doesn’t exist. The gap between what users reach for and what the product offers is often the opportunity competitors haven’t spotted either. Jobs called this intuiting what people would want before they knew to ask. Good discovery is what makes that intuition reliable rather than lucky.</p><p>· · ·</p><h3>But discovery doesn’t happen by accident — it takes deliberate process</h3><p><em>Here’s the part that took me longer to understand: knowing that great ideas come from discovery is not enough. Discovery itself has to be designed for.</em></p><p>When research is treated as optional — good to have when there’s time, first to cut when there isn’t — teams never build the muscle to do it well. And discovery done poorly is worse than none: it produces the confidence of data without the rigour that makes data reliable.</p><p>Jobs had a process, even if he resisted the word. Apple’s product development was obsessively iterative. Prototypes were tested relentlessly. Assumptions were challenged until only the most defensible survived. What looked like visionary intuition from the outside was, from the inside, structured discipline in relentless pursuit of insight. <a href="https://hbr.org/2008/06/design-thinking">Tim Brown of IDEO articulated this</a> as design thinking — the argument that rigorous observation and iteration, not individual genius, is what consistently produces innovation.</p><p>The problem with Jobs as a model is that his particular genius — his ability to synthesise observation into product vision — isn’t teachable or replicable at scale. Which is exactly why Apple struggled so profoundly without him. When insight depends on one person, you have a fragility problem dressed up as a talent strategy.</p><p>Process is the answer to that fragility. A codified discovery process — research protocols, synthesis frameworks, structured critique, documented rationale — means insight-generation lives in the system, not in a specific individual. You don’t need a visionary. You need a method rigorous enough that any skilled team following it surfaces the kind of insight that makes good design obvious.</p><blockquote><strong>From the work · ID Fresh</strong></blockquote><blockquote>The <a href="https://www.aufaitux.com/case-study/id-fresh-ux-research/">ID Fresh UX research project </a>went through three significant structural pivots during discovery each triggered by an ethnographic finding that contradicted an assumption the team had carried into the project about field sales workflows. That’s not research instability. It’s a process working as intended: creating enough checkpoints that insight could change the solution architecture before it reached developers. The streamlined mobile platform cut data entry errors by 40% and delivered operational efficiency gains across field sales.</blockquote><p>In practice, this means: contextual research before any screen is designed. Structured synthesis that turns observations into actionable insights. Architecture validated before visual design begins. Prototype testing — not to confirm what you hope, but to find what’s still wrong. And documented rationale so that the insight survives stakeholder review, developer questions, and the inevitable pressure to simplify something that was designed for a reason nobody now remembers.</p><p>Each stage exists to protect a specific finding from a specific kind of loss. Together they create the conditions for the unexpected discovery that produces genuine innovation. <a href="https://www.nngroup.com/articles/discovery-phase/">Research from the Nielsen Norman Group</a> consistently shows that teams who invest in structured discovery before design spend significantly less time in rework after development begins.</p><p>· · ·</p><h3>So who was Jobs arguing with, really?</h3><p>Go back to the quote one more time. “People don’t know what they want until you show it to them.”</p><p>He was arguing with the market researcher who walks into a room, runs a focus group, and concludes that users want a faster horse. He was arguing with the product manager who mistakes stated preferences for revealed needs. He was arguing against the idea that users can specify innovation for you.</p><p>He was not arguing against understanding what people struggle with. He was not arguing against observation. He was not arguing against the hard work of synthesising insight from behaviour. He built a career on exactly that work.</p><p>The irony is that the people who cite his quote most often to shut down user research are doing the opposite of what made Jobs effective. They’re skipping the discovery that would tell them what to show people and betting that inspiration will fill the gap.</p><p>Sometimes it does. More often it produces a polished product that solves a problem nobody actually had. <a href="https://www.interaction-design.org/literature/article/norman-s-three-levels-of-design">Don Norman’s framework for why products fail</a> points to the same root cause every time: designers optimising for what they can see like aesthetics, features, technical capability rather than for what users actually experience in practice.</p><blockquote><strong><em>Users can’t tell you what to build. But they’ll show you if you build the process to go looking.</em></strong></blockquote><p>That’s the full argument. Great ideas come from discovery. Discovery comes from process. And Jobs was making the same point all along.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=500f0b22b90e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/steve-jobs-was-right-and-so-is-user-research-500f0b22b90e">Steve Jobs was right, and so is user research.</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intellectual Humility — Why UX Designers must Cultivate it]]></title>
            <link>https://medium.com/uxpedia/intellectual-humility-why-ux-designers-must-cultivate-it-d066334e7871?source=rss-a93e93198ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/d066334e7871</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Bijith Kunchammed]]></dc:creator>
            <pubDate>Tue, 20 Jun 2023 08:35:01 GMT</pubDate>
            <atom:updated>2023-07-27T04:36:52.217Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Intellectual Humility</strong> — Why UX Designers must Cultivate it</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ukJvS4A8pZ4iEuG_-FRPEA.png" /></figure><p>When talking about what defines a good UX designer, the focus often revolves around proficiency in design software and general communication/soft skills. But from my experience running a UX agency, I believe we often overlook some essential soft skills, which are integral to growing a career in UX design. One such skill or trait that every UX designer should focus on developing is<strong> Intellectual Humility</strong>.</p><h3>What is Intellectual Humility?</h3><p>Sometimes intellectual humility is confused as a skill or a trait. But the majority defines this as a fully general trait, characterised on how people manage their responses to what they believe. <a href="https://www.templeton.org/discoveries/intellectual-humility">The John Templeton Foundation </a>defines intellectual humility as <em>a mindset that guides our intellectual conduct</em>. In particular, it involves <em>recognising and owning our intellectual limitations</em> in the service of pursuing deeper knowledge, truth, and understanding.</p><p><strong>Intellectual humility is about recognising that there could be gaps in one’s knowledge and that one’s current beliefs might be incorrect. It helps us overcome black and white thinking and allows us to engage constructively with people around us</strong>. This is not something that we are born with, but something that we can gift ourselves.</p><h3>How is it Important in UX?</h3><p>At <a href="https://aufaitux.com/">Aufait UX</a>, we have had some instances where we were asked to completely redo some of our designs when we presented the work to customers. Almost every time, I’ve noticed that the first reaction from our team was to be defensive. As humans, it’s quite natural to feel defensive when receiving criticism, especially when we have invested so much time and energy into creating something. Moreover, customers may not always say things diplomatically, which makes the criticisms feel even harsher.</p><p>But as UX designers, we should be expecting such challenges and rejections and should train ourselves to handle those wisely. Here is where the soft skills come in handy and intellectual humility takes the top place among the soft skills UX designers should cultivate.</p><p>Why? Because in UX, it’s very important to listen to the viewpoints of others, handle criticism and feedback efficiently, and use the feedback as a means to improve your work. When you have spent a lot of time and effort working on a design and receive negative feedback, you may start defending your work and may not be able to recognize the shortcomings in your own point of view. By cultivating intellectual humility, you train yourself to acknowledge the viewpoints of others.</p><h3>3 Qualities of Intellectual Humility in UX Designers</h3><ol><li><strong>Open-mindedness</strong></li></ol><p>“<em>We need to enter the conversation willing to be wrong, willing to admit the limits of our own knowledge, willing to reconsider our evidence, sources, and premises.” — </em>Patricia Roberts-Miller</p><p>A UX designer should be open to accepting that his beliefs might be incorrect and there could be gaps in his knowledge. He should be willing to iterate and refine his designs, which is the whole purpose of UX design. Cultivating intellectual humility helps us overcome self-centered responses. This mindset encourages us to seek out and evaluate ideas and information in such a way that we are less influenced by our own motives and more oriented toward discovery of the truth.</p><p>While your perspective might be a good one, it doesn’t mean that it’s the only one. Listen to every viewpoint that comes your way with an open mind and broaden your perspective. If we can break out of our bubbles that we create with our own ideas, we can understand that some of the things we know were wrong or incomplete. It doesn’t feel like a failure when we accept others’ ideas but will start to feel like an enlightenment.</p><p><strong>2. Listening with a desire to understand</strong></p><p>As a UX designer, you should be able to listen to the perspectives of others, take criticism positively and act without reacting to your emotions. The best way to tackle this is to suppress your immediate emotional responses and give yourself and the other person time to regain composure.</p><p>The importance of Intellectual humility in UX design comes into play especially when<strong> </strong>presenting designs to customers or colleagues and receiving feedback. A less experienced UX designer may not like to listen to people with contradicting viewpoints. They will be listening with a mindset to defend or argue. As you become more mature, you will find great value in listening to different viewpoints with a desire to know the reasons behind them. This is the mindset UX designers should aim for. As soon as you stop thinking about yourself and start thinking of others, your skills as a UX designer will drastically improve.</p><p>A UX designer must always be curious to learn and understand from people, they could be our target users, customers, co workers or even kids. A curious designer is a great asset to any team and pushes the whole team to think out of the box and create innovative solutions.</p><p><strong>3. Accepting mistakes</strong></p><p><em>“Sometimes when you innovate, you make mistakes. It is best to admit them quickly, and get on with improving your other innovations.” — </em>Steve Jobs</p><p>So much in UX is about testing and experimenting. And that means, there will be many instances where you can go wrong. With intellectual humility as your ally, you cultivate the willingness to reconsider your views and handle defensive attitudes. It helps you become more realistic, accurate and empathetic. If you can accept your mistakes when you are in the wrong and inform the other person that you will correct the mistake, it would make the outcome more impactful.</p><h3>From Good UX Designers to Great</h3><p>Always remember that UX designers are not experts, we are facilitators. We build prototypes and wireframes before developing the actual product so that we can change ideas and iterate. When we discuss with subject matter experts and practitioners, we get clearer inputs on what we have designed and should iterate. If we can accept and implement them, with an open mind, the road ahead becomes smoother.</p><p>The fundamental/core of all UX methodologies and tools is about doing iterations and working as a team. Intellectual humility is crucial for it and without this quality one cannot imagine building a good UX. Open mind, curiosity and self awareness are skills you need to cultivate to go from good UX designers to great!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d066334e7871" width="1" height="1" alt=""><hr><p><a href="https://medium.com/uxpedia/intellectual-humility-why-ux-designers-must-cultivate-it-d066334e7871">Intellectual Humility — Why UX Designers must Cultivate it</a> was originally published in <a href="https://medium.com/uxpedia">UXPedia</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>