UX Digest ⭕️

I Thought I Already Knew How to Do Research

A reflection on the difference between collecting findings and actually synthesizing them into insights. The key shift is building a traceable chain from evidence to patterns, interpretations, and product decisions

NNG: Do Participants Say Less to AI Than to Human Moderators?

In a controlled study, participants spoke 45% less with AI moderators, while AI-led interviews were 37% shorter and much more moderator-dominated. The result suggests AI moderation can reduce participant elaboration, although more talking does not automatically mean better insights

Prototyping: We’re Trying Hard to Design the Right Solution, But Did We Design the Right Path?

A product can be built for the right audience while the path to its value still ignores their needs. The author uses Inflow’s 37-step onboarding for people with ADHD to show why reducing friction and demonstrating value before collecting sensitive data can matter

AI: Vibe coding alone

Vibe coding let the author turn a decade-old budgeting spreadsheet into a working tool without a developer — and made her question what gets lost when everyone starts replacing colleagues with AI. The punchline comes later: the tool wipes her data, and Claude can’t help her recover it

Opinion: Why Researchers Need to Build

Researchers lose context when insights pass through reports, designers, and developers before becoming a product. Learning to prototype and build lets them turn research directly into testable solutions without becoming full-time engineers

Design: If You Don’t Get Lost in a City, a Designer Probably Did Their Job Well

Copenhagen’s public transport shows how wayfinding, consistency, and progressive disclosure can make a complex system feel effortless. Good design gives people the right information at the right moment and often works best when users barely notice it

Basics: Low Fidelity - A Concept First Approach to Design

Low-fidelity prototypes help teams test the concept before visual polish makes a weak idea look convincing. Their value is not speed itself, but exposing gaps, inviting critique, and making problems cheaper to fix early

@uxdigest

What Are UXers’ Ways of Understanding Product Features

Four lenses for evaluating any feature: the job it does, the behaviour it shapes, its place in the system, and the friction it creates. The best question may be the simplest: if this feature didn’t exist, what would users actually do instead?

The Problem with “UX Theater”

Research becomes UX theater when it produces workshops and reports but never changes the product. A sharp rule from the article: share the decision, evidence, and next step — not a 100-page deck no one will open

The Devaluation of Discovery

As execution gets faster and cheaper, teams are increasingly tempted to skip discovery and jump straight to solutions. The uncomfortable consequence: AI can help you build the wrong thing faster than ever

🎟️ NNG: Neurodivergence - What is it and Why Does it Matter

Neurodivergent users can face challenges with executive function, communication, and sensory processing. The practical takeaway: design for simplicity, clarity, control, and support — because neuroinclusive design often improves the experience for everyone

Tools: 10 UX Research Tools for Different Research Methods in 2026

A practical map of 10 research tools matched to specific methods — from recruitment and moderated testing to diary studies, IA, analytics, and repositories. The core rule is simple: choose the research method first, then pick the smallest tool that supports it without duplicating your stack

AI: 8 voice AI UX patterns

A map of 8 emerging Voice AI patterns — from avatar calls and AI phone agents to dictation and ambient assistants. The useful part is how each pattern changes the agent’s perceived role, and with it the UX rules for turn-taking, interruption, memory, and recovery

Prototyping: The Death Of The Button - Why The Best Interface Is No Interface

Intent-driven design replaces chains of menus, filters, and forms with one goal the system executes for you. The provocative shift: future UX may be judged less by interaction quality and more by how completely the interface disappears

@uxdigest

Persistent lessons in human-centered automation

A 1980s photocopier study and a grocery-store robot point to the same lesson: people interact with automation based on what they think it can do, not what it was designed to do. In the agentic era, managing expectations and making system intent visible may matter more than adding another interface

NNG: Test Complex Interactions Earlier with AI Prototyping

AI prototyping makes it possible to test complex interactions — filters, dashboards, conversational AI — much earlier with realistic working prototypes. In one Ramp case, the team found a confusing edit-tracking issue that static screens simply couldn’t reveal

Prototyping: Coupons, Vouchers, Gift Cards, and Credit - Four Things That Look Alike and Aren’t

Coupons, vouchers, gift cards, and credit may look interchangeable in an interface, but they follow different rules and user expectations. Treating them as one pattern can create surprisingly confusing checkout experiences

AI: We Used to Test Buttons. Now We Test Chaos

AI makes UX testing less deterministic: the same input can produce different outputs, errors, and paths. So instead of checking one “correct” flow, researchers increasingly need to test ranges of behaviour, edge cases, and how gracefully the system fails

Case Study: Bypassing Institutional Distrust - UX Lessons from Redesigning Philanthropy

A case study on designing philanthropy around distrust rather than trying to “fix” it with better UI. The strongest insight: money may flow upward to institutions, while trust flows sideways through local communities — so the service had to follow the trust, not the org chart

@uxdigest

The UX of Anxiety Reduction

Good UX can reduce “micro-anxiety” by making actions predictable, reversible, and easier to understand. A useful shift: design not for attention, but for intention — so users know what will happen next and whether they can recover from a mistake

Effectiveness of AI Moderators: A Literature Review

A review of 10 studies finds AI moderators roughly comparable to humans on procedural tasks, but weaker where judgment matters — especially probing and knowing when to go off-script. The verdict is nuanced: AI looks promising for structured, high-volume research, but not yet for discovery and emotional nuance

NNG: AI Can Help Write an Article, but It Can’t Stand Behind It

NN/g uses AI for rewriting, formatting, repurposing content, and even critiquing arguments — but not for final judgment. Their core rule is simple: AI can help think, but a human expert still has to understand, evaluate, and stand behind every published claim

Process: How to Structure a Jira Backlog — Epics, Stories and Priorities That Actually Work

A practical guide to keeping Jira useful instead of turning it into a graveyard of tickets: clear hierarchy, ruthless ranking, and detailed work only near the top. The sharpest rule: polishing a story you won’t touch for six months is usually waste because it will change before you get there

AI: From the Red Dust to the Agent Age

A researcher reflects on moving from ethnography in rural Africa to automating parts of research with AI agents. The key lesson: before automating research, you first have to make expert judgment explicit — including rules for what counts as an insight and when contradictions must go back to a human

Case Study: Designing RootCause to Make Plant Diagnosis Less of a Guessing Game

A case study of RootCause, an AI app that diagnoses sick plants from a photo and turns confusing online advice into clear care steps. A nice detail: a plant chatbot was added not just for answers, but to make diagnosis feel less stressful and more human

@uxdigest

UX in 2027 may be less about interfaces and more about behavior

A look at how UX may shift from designing fixed flows to defining how adaptive and agentic systems behave. The article covers generative interfaces, AI-assisted research, design systems for machines, trust, permissions, reversibility, and accessibility. The central idea is worth keeping: designers may draw fewer predetermined paths and spend more time defining the boundaries within which software is allowed to create its own

NNG: We Still Need Long-Form Copy

Short attention spans haven’t killed long-form content: some topics are simply too complex to compress without losing clarity or trust. NN/g argues that longer copy still matters when users need depth, confidence, or strong SEO and AEO signals. The useful part is not “write more”, but structure long content so people can scan it through summaries, bullets, callouts, bolding, and visuals

AI: How people looked for information using AI

A usability study with 20 disabled people and family members on how they actually search with AI, Google, and other sources. People switched tools depending on the task: AI was more attractive for complex, personalised questions, while trusted websites and search remained important for high-stakes topics. One especially telling finding: some participants blamed themselves when AI gave a poor answer, assuming they had simply written the wrong prompt

Writing: Billing approvals that don’t feel like a trap - the exact warning microcopy patterns

Billing microcopy should answer five things before the user confirms: how much they’ll pay, when they’ll be charged, what changes, whether they can undo it, and whether there are extra costs. The article breaks this into practical patterns like “you’re about to”, “here’s what changes”, and a receipt preview. One especially useful detail: showing the exact path to downgrade makes reversibility feel real instead of theoretical

Basics: The UX of Human Connection - Why Client Experience Starts Before the Product

UX starts before anyone sees the product — in the first meeting, the tone of communication, and the questions a team chooses to ask. The article argues that curiosity and informal human moments can uncover better insights than polished presentations or rigid agendas. In one CRM project, a simple question about how salespeople actually start their day helped the team avoid building several unnecessary features

@uxdigest

Nine Design Fixes for Your UX Research Reports

Nine practical ways to make research reports easier to read and harder to ignore: clearer structure, stronger hierarchy, better contrast, more whitespace, consistent charts, and reusable templates. The authors make a very UX-ish point — a research report is itself an interface with two users: the researcher creating it and the stakeholder reading it. MeasuringU even usability-tested its own report template and went through four iterations before settling on the current version

The user belongs to everyone, which is the same as belonging to no one

When everyone on a product team “owns the user”, responsibility for actually understanding them can disappear. The author shows how overlapping research by UX and Product can turn into a data-quality problem when interview framing and methods aren’t shared. His practical fix is surprisingly small: agree upfront who researches, who is consulted, and who makes the call

NNG: Using AI for UX Work - Study Guide

NN/g’s practical map of where AI already fits into UX work — from research planning and analysis to prototyping, writing, service design, and workshops. The guide is less about “AI will replace UX” and more about choosing specific tasks where it can genuinely help without outsourcing judgment. The research section alone covers synthetic users, AI-moderated interviews, survey writing, digital twins, and why analysis still shouldn’t be handed over completely to AI

Experience: Learnings from Experience Design Micro-Projects at NID

A two-week experiment in designing tiny experiences around emotions like restlessness, adventure, and optimism — often with just a day to research, prototype, and test. The projects range from an endless staircase timer to chocolate as a trigger for hope and motion-activated “fireflies”. The best lesson comes at the end: even a handful of people was enough to break assumptions and reshape almost every prototype

AI: The feature is cheap to code, so we might as well build it. (Probably not)

AI makes features dramatically cheaper to build, but implementation is only a fraction of their real cost. Every new feature adds maintenance, support, friction, complexity, and eventually makes removing it a product decision of its own. The uncomfortable takeaway: when almost anything can be built, deciding what not to build becomes the harder skill

Opinion: What first dates can teach us about becoming better, safer researchers

What first dates can teach researchers about rapport, awkward silences, knowing when to end a conversation, and trusting your instincts. The authors connect familiar dating situations with practical research skills — from making interviews feel less like a checklist to planning fieldwork with exits, check-ins, and even a code word. A useful reminder that researcher safety deserves as much preparation as participant safety

Basics: Persona Is Not a Document, It’s a Decision Tool

A persona is useful only when it helps a team make product decisions, not when it simply describes age, job title, and favourite apps. The author suggests building personas around context, goals, pain points, behaviour, motivation, and decision drivers — then using them to prioritise features and UI choices. A good test is simple: can your persona help explain what you should avoid building?

@uxdigest

Unlocking UX Secrets: How 1 Hour of Session Recordings Transformed Trendyol Seller Panel

Just one hour of watching session recordings (Hotjar) revealed a massive pain point: sellers suffering the "scroll of death" for bulk actions, forced to scroll back to the top after selecting items. Three iterative designs later, a bottom-positioned sticky toolbar triggered by checkbox selection won—proving that quick, unbiased observation in natural workflow can uncover insights no survey or interview could, without spending extra budget or bothering busy users

NNG: The Custodial Era of UX - Cleaning Up After AI

AI lets teams build faster than UX can evaluate, creating UX debt: interfaces that "technically function" but confuse users, overload features, and skip foundational questions about whether something should exist at all. UX's new custodial role isn't just janitorial cleanup—it's triaging what to keep, accelerating evaluation (rapid user panels, checklists), and adding UX knowledge to generation (Design.md, design systems)—because the goal is to prevent the next mess, not just clean it up

Prototyping: Rethinking Data Visualisation - A UX Approach To Dashboards That Actually Drives Decisions

Most dashboards fail because they're built from available data, not from a specific operational question—so they show numbers without driving decisions. The fix is upstream: define context (what question are we answering?), audience (familiarity + accountability), and insight (what should change after seeing this?), then design the visualization to serve that, not the other way around—because the right chart isn't about simplicity, it's about appropriate complexity for the person and the decision at hand

AI: Thoughtful AI implementation for UXR leaders

AI skeptic or not, set a north star: AI should support, not replace, research quality (craft, assessment, revision). Preserve core skills with clear guidelines (don't use AI for research questions, do use it for data cleaning, label AI output), and frame every tool conversation around risk vs. reward—because in the rush for efficiency, we risk losing the human processing time that produces real insights

Design: My “Book of Sorcery” Taught Me Design Before the Internet Did

Before the internet, a fine art diploma taught design through observation and limitation: hand-drawn ads, lettering from a book of 30 fonts, and a physical "book of sorcery" of clippings from magazines and packaging. That instinct to collect and trust what "looks right" later met research training—behavioral psychology, HCI, accessibility—transforming instinct from the answer into the first question: why does it look right, to whom, and under what assumptions?

@uxdigest

The gap between what user research surfaces and what gets built

It isn't a quality problem—it's a translation problem: qualitative insights don't become backlog items because there's no formal process to bridge the formats. The fix is to embed decision-makers in synthesis, translate findings into prioritization-ready format (impact + effort), and track their status like bugs—otherwise, research remains an expensive activity with no measurable value

NNG: AI Can't Replace Real Research in Empathy Mapping

AI can help organize existing research into empathy maps, but it cannot replace real user evidence—because plausible, generic quotes (e.g., "I wish the app would ask before swapping") are not the same as specific, messy details from real sessions (e.g., "It swapped my oat milk for whole milk and charged me before I saw the notification"). Before reaching for AI, ask: am I organizing real data or generating data I don't have? If the answer is the latter, the map needs more research, not more AI

Prototyping: Using content design to fix UK emergency alerts

The UK emergency alert about wildfires was well-intentioned but failed its users: dense text, redundant language, weak visual hierarchy, and unhelpful signposting made it harder to scan in a moment of stress. A content redesign—shorter sentences, direct "do not" commands, clear paragraphs, and a specific URL—cut reading time from 19 to 14 seconds and dropped the reading age from 17.6 to 14.6, proving that in an emergency, every word and second counts

Experience: We need a survey — a UX research story

When a stakeholder says "we need a survey by Tuesday," the real skill isn't asking for more time—it's starting with the question, not the method, and doing credible research within imperfect conditions. Fast research means reducing scope, focusing on the most critical questions, and making deliberate trade-offs (e.g., 5 relevant users instead of 20 later)—and sometimes the method itself evolves as findings emerge, because research is about following the evidence, not sticking to a plan

AI: Craft still matters, but it’s about outcomes

Craft isn't about pixels anymore—when AI makes production cheap, real craft moves to choosing the right problem and curating AI output with taste. To keep it, write your standards down (so the machine applies your rules), keep research a weekly habit, and always put a human review at the end—because AI fails quietly, and fluent confidence without verification is just fiction

Design: Why People Ignore Perfectly Designed Buttons

People ignore perfectly designed buttons not because of color, size, or placement, but because of the trust problem (uncertainty about what happens next), decision fatigue (too many choices already made), and identity questions (not ready to be the person who clicks it). The fix isn't polishing the button—it's building the right emotional state, trust, and narrative momentum before it appears, because a button is just the answer to a question the experience needs to ask first

@uxdigest

Five Ways to Use Rapport When Moderating

Good moderation isn't just reading a script—it's building trust through preparation (know your audience's lingo), deliberate ice-breaking, and a verbal toolkit (purposeful pauses, neutral expressions, camera eye contact). But watch for the failure mode: mutual people-pleasing that makes disagreement feel impolite, and use rapport as a final screening step—because a few warm-up questions can catch a participant who never should have qualified

Why Users Don’t Experience Your Interface the Way You Designed It

The gap between your Figma file and reality is shaped by the curse of knowledge (you can't unsee your design decisions), context collapse (users are distracted, stressed, rushing), mental model mismatches (they expect different logic), and accessibility oversights. The fix isn't more testing, but treating it as genuine inquiry: test in real contexts, involve people who disagree with you, and cultivate humility—because users experience your design through their own reality, not yours

NNG: We Still Need Long-Form Copy

Despite shrinking attention spans, long-form copy still matters—because some things are inherently complex, require trust, or need SEO and AEO benefits. The key isn't cutting words, but making them scannable with summaries, bullet points, callouts, bolding, and visuals to improve comprehension and engagement with content over 1,000 words

Prototyping: Designing High-Performance User Experiences for Data-Heavy Dashboards and Analytics Products

Consumer design patterns (clean cards, progressive disclosure) fail in data-heavy expert tools—experts need density, bulk actions, and state preservation, not simplicity. The craft lies in balancing density, clarity, and speed: dense tables with strict alignment, keyboard shortcuts, and transparent permissions—because friction isn't clicks, but the gap between how work actually happens and how software forces it

AI: Researcher-in-the-loop

Instead of asking if AI will replace researchers, ask who keeps research honest when everyone can self-serve. The researcher-in-the-loop model makes researchers governors of the system: they set rules (sourcing, confidence, escalation), route low-risk questions to AI tools, and keep high-risk ones for humans—because a confidently wrong AI is worse than no answer

Design: How Good Design Will Save the World

Good design isn't loud—it's invisible, seamless, and accessible, solving problems without being noticed. The best designers focus not on articulating every use case, but on delivering what people really want (like the snooze button: a simple reprieve in a complex world), and make accessibility the core, not an afterthought—because true design considers both the space and the user, creating experiences that work for everyone, not just the able-bodied

@uxdigest

Designing Flow in SSX 3: A Cognitive Psychology & Game UX Analysis

A cognitive psychology analysis of SSX 3 shows how the game sustains flow through a risk/reward trick system (adrenaline → Ubertricks → Super Uber), adaptive audio that gives real-time feedback, and a progressive mountain structure that balances challenge with skill. It satisfies Self-Determination Theory (competence, autonomy, relatedness) through trial-and-error learning, free exploration, and community-building — showing how arcade design can coordinate mechanics, audio, and progression for deep immersion

Atomic UX research: How to pilot a repository with a Claude skill

A Claude skill automates atomic UX research in Notion — handling experiments, facts, insights, and recommendations while cross-referencing new findings against existing data to surface patterns. It saves ~4 hours per study by cutting administrative work, keeping humans in the loop for decisions like interpreting nuance and framing questions

🎥 NNG: 3 Steps to Scope Your Broad Research Study
Proper scoping is tied to timelines, research efficiency and the usefulness of your outputs. Learn how to scope your studies for optimal impact

Prototyping: Why a Single Red Dot Can Hijack User Behavior for Weeks

A red dot isn't just a UI element—it's a psychological trigger that creates an open loop in the brain, hijacking attention through the Zeigarnik effect and triggering a cortisol spike via evolutionary color-coding. When combined with variable rewards, this tiny circle can turn a productivity tool into a slot machine, creating compounding micro-anxieties that degrade focus and trust over weeks, not minutes

AI: Measuring the UX of AI

Measuring the UX of AI chatbots starts with standard UX metrics (usability, usefulness, effectiveness), but to truly understand the experience, you need to dig into specialized constructs like AI Productivity, Trust, Dependency, Anxiety, and Personification—each requiring validated items. The authors propose a framework with initial item sets for these five dimensions, but note that the real work lies in psychometric validation with real user data to see which items actually hold up and how they connect to higher-level outcomes like brand attitude and continued use

Opinion: From UX to AX - Why I Think We’re Not Just Redesigning Interfaces, We’re Redesigning Trust

We're moving from UX to AX (Agentic Experience), where the core challenge isn't mapping deterministic flows, but designing for probabilistic systems that act autonomously—shifting the design job from screens to behavior and relationships. The five real pillars of this new discipline aren't about capability, but about restraint: intent alignment, controllability, explainability, emotional intelligence, and co-evolution, because trust isn't earned by how much an agent can do, but by knowing exactly when to pause and ask

The channel is going on vacation until the end of the summer, thank you for being with me all this time, see you in September

@uxdigest

The Psychology of Why Confirmation Dialogues Get Ignored

Confirmation dialogs are a psychological failure—they force a slow, analytical System 2 response onto a fast, automatic System 1 workflow, meaning users click through them without reading, driven by habit and the desire to resolve an interruption. The fix isn't better copy or redder buttons, but designing for reversibility (undo, soft deletes) and using 'good friction' like typing-to-confirm for truly irreversible actions, because a warning that appears daily becomes invisible noise

NNG: Why You Need Mentorship and How to Get It Right

Mentorship isn't just for juniors—research shows it leads to more promotions, higher pay, and less burnout for both mentees and mentors, yet many avoid it due to misconceptions about its value or who it's for. The key to success lies in choosing the right mentor (internal or external, candid and compassionate), setting clear goals and cadence, and actively putting advice into practice—because a mentor who sees you act on their guidance is far more invested in your growth

Prototyping: The Beautiful Lie of the Progress Bar - Why We Trust Fake Progress Over Honest Waiting

Fake progress bars work because uncertain waits (spinning wheels) create anxiety, while progress bars convert uncertainty into a finite wait, occupying attention and managing the Zeigarnik tension — users prefer the lie for the sense of forward momentum. Use the Three Tiers framework: indeterminate (<2s, spinner), perceptual (2-30s, non-linear fake bar with easing), determinate (>30s or step-based, honest step counts); never compress step-based workflows — it breaks trust and triggers reactance

Experience: How I designed a system that 95% of non-technical users could use without support

The secret to 95% of non-technical users using a complex system without support isn't removing features, but matching the software to their existing mental models—like organizing a poultry platform around "batches" instead of individual birds, because that's how farmers actually think. The real breakthrough came from observing their workarounds (physical calendars, crate-based counting) and asking open-ended questions, then designing workflows that felt familiar enough that they barely had to learn them at all

AI: I Stopped Waiting for Engineers to Validate My Ideas

The real bottleneck for designers isn't ideas, but waiting for engineering validation—so with AI-assisted development, you can now prototype working solutions yourself, turning problems into interactive experiments in days instead of weeks. This shift isn't about replacing engineers, but about expanding design's role from creating screens to testing systems and decisions, proving that the hardest part of a transit app isn't the map, but reducing the uncertainty of waiting

Front: Why a Website Works for Some Visitors, but Not Others

A website isn't a fixed object, but a partnership between a server and a browser—and every visitor brings a unique environment (cache, cookies, extensions, device) that can make the same site work flawlessly for one person and break for another. The key isn't asking "does it work?", but understanding where the problem lives: try an incognito window to isolate browser-specific issues, and for owners, monitor analytics for early warnings before a single visitor complains

Opinion: The Invisible Weight - Why Your “Simple” Interface is Exhausting Your Users

Minimalism isn't about empty screens, but about invisible cognitive taxes—and aggressively stripping away visual cues often forces the user's brain to work harder, not less. A clean interface can actually be cognitively exhausting when it hides context behind ambiguous copy or progressive disclosure, turning 'simple' into a frustrating puzzle for your users

@uxdigest

NNG: No New Name Has Replaced “UX”

Despite ongoing debates about renaming the field, a survey of 604 professionals found that "UX" remains the dominant, spontaneous term (appearing in 70% of responses), while alternatives like "experience design" or "human-centered design" are fragmented and rare.
The data suggests that job roles shape terminology (e.g., product managers say "product"), but no single alternative has emerged as a replacement—so the real work isn't finding a new label, but clearly communicating UX's contribution to decisions, outcomes, and risk reduction

Prototyping: Why Skeleton Screens Feel Faster (Even When They Aren’t)

Skeleton screens aren't just a visual trick—they work because they replace the anxiety of an unknown wait with a predictable structural map, letting the brain relax and perceive time differently. But the moment that skeleton doesn't perfectly match the final layout, you trigger a devastating layout shift that shatters user trust and makes the product feel broken, proving that the illusion of speed is only as good as its stability

AI: Designing with web standards - The playbook for this AI moment

We're living through 1999 again—AI interfaces (ChatGPT, Claude, Gemini) are the new browsers, each with its own proprietary patterns, and without shared standards, we're rebuilding the same broken, inconsistent experiences across every tool. The playbook from Jeffrey Zeldman's web standards movement is clear: name the patterns (confidence, citations, reasoning) before vendors lock them in, build a coalition of practitioners, and make the business case (cost, reach, accessibility)—because standards win when agreeing becomes cheaper than diverging

Case Study: How We Redesigned TikTok Like a Real Product Team in Five Weeks

Through 3 rounds of testing and iteration, the team used Figma Make to prototype solutions for button control, algorithm transparency, and viewing time — increasing brand trust from 5.5 to 7.5 (+36%). Key changes: swipe-to-dismiss "Not Interested," algorithm dashboard with feed tuner, and Screen Time Pledge (forced exit). 81.8% said they'd recommend the redesigned version

Experience: We Thought We Understood the User

A product manager thought they understood the warehouse process from requirements docs — until visiting the site revealed workers had quietly moved a key step much earlier in the workflow, and nobody had filed a change request. The lesson: requirements capture the paper version, not real adaptations; discovery means going where the work actually happens and asking what the floor knows that you're missing

Opinion: The Friction Paradox - Why Adding Steps to Your Product Actually Builds More Trust

We've been taught that every click is a tax on the user, but in high-stakes moments, removing all friction doesn't build confidence—it triggers suspicion, making users feel rushed and unsure about their decisions. The secret isn't eliminating friction, but distinguishing bad friction (bureaucratic, confusing) from good friction (educational, confirmational)—where a deliberate pause or extra step acts like a speed bump, forcing the user to slow down and actually own their choice

@uxdigest

Transitioning from Graphic Design to UX

Moving from graphic design to UX doesn’t mean starting over. Most core skills are directly transferable and serve as a strong foundation to become a great UX designer

Prototyping: The Enterprise Software Delusion - We Design for the Buyer and Blame the User

Enterprise software fails because buyers (executives) buy for compliance, but users get bloated interfaces designed for audits, not action — "resistance" is really just increased cognitive load. The fix: measure Time to Core Value, involve users in demos, reduce mandatory fields, and absorb complexity to present a simple path — align incentives with human reality

AI: I Didn’t Start With AI, I Started With People

A UX researcher studied top human agents to inform an AI assistant: the best agents don't just answer — they first understand the customer's situation, make sure solutions are understood, and introduce products by asking about habits first, then recommending benefits (not promotions). The key insight: AI should start by understanding context, not answering; recommendations should feel like helpful suggestions, and some situations still need human judgment — AI should prepare and escalate, not replace

Case Study: Improving Recommendation Controls on Netflix

Users separate rating (thumbs up/down for watched content) from dismissing unwanted recommendations, and they're unwilling to spend time managing preferences — they need a lightweight, visible action on the card. The solution: a context menu with optional reasons (already watched, not interested, fewer like this) followed by confirmation with Undo — because control alone isn't enough; the interaction must feel worth the effort

Opinion: Everything you know about UX is probably wrong

A reflection on "User Experience Foundations": UX isn't a deliverable or a role — according to ISO 9241-210, it's a person's perceptions and responses, meaning you can only design the conditions for experience, not the experience itself. Key principles: you are not the user, behavior-based research (contextual inquiry) beats opinion-based surveys, users must be involved throughout, and UX accounts for anticipatory, episodic, and cumulative experience — not just the moment of use

Basics: Product Managers Don’t Need More Data. They Need Better Questions

Product managers don't need more data — they need better questions; teams with 14 dashboards can measure everything but still can't answer "should we keep building this" because data tells you what happened, not what to do next. The fix: before collecting any metric, write down the exact decision it's meant to inform and what answer would change it — good questions must be built deliberately, before instrumentation

Interesting: Understanding shisha as a different experience of smoking

NHS research found that shisha smokers often don't see it as "proper smoking" — it's social, seasonal, and positive, so they don't report it in standard smoking questions designed for regular cigarette use. Testing "Have you smoked any of these tobacco types for 1 year or longer?" caused confusion for episodic holiday users, showing that shisha requires different mental models and question design, not just being slotted into cigarette-based journeys

@uxdigest

Agile UX and its associated challenges

Don Norman's critique of Agile UX: "Norman's Law" — on the day a project is announced, it's already late and over budget — because Agile sacrifices user research for coding, when research should be a continuous practice, not a phase. The fix: continuous research, Design Sprints to compress understanding before coding, and reframing procrastination as "time to think" — building feature by feature without overall coherence leads to products that fail

NNG: UX-Context Design - Using UX Knowledge to Inform AI-Generated Design

NN/g introduces "UX-context design" — as AI generates more interfaces, research output shifts from human deliverables to machine-readable context (standards, research insights, user/world models) that guides AI tools and prevents generic output. Examples: DESIGN.md (visual identity) and UX.md (research, interaction standards, glossary) — never-finished files that live alongside code and make research a continuously curated source of truth, not a one-time handoff

AI: AI in UX Research - What Changes When the Researcher Is Also the Model

A critical framework for AI in UX research: distinguish three roles — assistant (transcribing real human data, low risk), proxy (synthetic personas, treat as hypotheses, not findings), and researcher (agentic AI running the whole pipeline, highest risk, especially when the same model generates and interprets data). The key principle: no model has a nervous system — keep a human in the judgment call, check for circularity, and treat synthetic output as a hypothesis, not a finding

Opinion: Beyond Jobs to Be Done - Why Technical Fluency Is Now a Research Requirement

JTBD works from individual intention, but in technical categories (enterprise software, AI, infrastructure), outcomes are shaped by non-human actors (data rules, integrations, models) — treating these as background produces research that's right about what buyers want but wrong about what happens. The fix: actor-network theory — map all actors (human and non-human) that change the outcome, requiring researchers who can read technical arrangements, not just interview buyers

Basics: Basic Tools & Techniques Every Product Manager Should Master for User Research

A product manager's guide to user research: surveys for quantitative feedback at scale, interviews to uncover the "why," and observation tools (Google Analytics, Hotjar, Amplitude) to watch what users actually do — because people often say one thing and do another. The cycle: survey → interview → observe → build → measure → learn; combine qualitative and quantitative data to validate assumptions before making decisions

@uxdigest

UX and NPS Benchmarks of Health Insurance Websites (2026)

A 2026 benchmark of 8 health insurance sites found SUPR-Q scores dropped from the 67th percentile in 2018 to the 30th — below average — with negative NPS (-14%) and usability at the 21st percentile. Top frustrations: finding providers, claims info, and slow performance; users struggle to find vital information when they need help most

NNG: A Concrete Definition of “Product Sense” (and How to Build It)

NN/g defines product sense as recognizing when current problems match past successes/failures and estimating how similar solutions will work — built through closing the full loop: face problems, choose solutions, measure outcomes, reflect. Strong product sense also means knowing when patterns don't apply; develop it by staying through entire cycles, documenting hypotheses before results, and reflecting — AI can rob you of this if you don't follow through

Prototyping: The Architecture of Guilt - How Duolingo Weaponized Negative Emotion to Build a Design System

Duolingo's design system abandoned "delight" for negative reinforcement — using loss aversion (streaks as fragile assets), a passive-aggressive mascot (Duo as emotional lever), and Streak Freeze as a shock absorber for inevitable failure. The ethical tension: persuasive design helps users achieve goals, but coercive design creates artificial anxiety — retention metrics measure compliance, not happiness, and the ultimate test is whether users feel empowered or trapped

AI: Where Does AI Actually Help in UX Research, and Where Does It Fall Short?

AI excelled at competitor analysis, ideation (HRV validation), and storyboards — but failed at interview scripts (leading questions, missing behavioral insights), transcript synthesis (missing fragmented emotional patterns), and ambiguous card-sorting decisions. The lesson: speed isn't insight; the human role is noticing what users couldn't explain and connecting scattered signals

Experience: How I Research Apps That Don’t Exist in My Country

A designer in Nepal shares methods to research geo-restricted apps: UI libraries (Mobbin), YouTube tutorials (raw usability footage), Reddit/Google reviews (user frustration), and "borrowed eyes" (friends sharing screens) — safer and cheaper than VPNs/APKs, which she cautions against. The key: losing daily access forced her to become more resourceful, treating tutorials as research and building relationships with people still in the target market

Basics: What is Product Discovery Research? A Product Manager’s Guide

A guide to product discovery research: it investigates user needs before committing to a solution — distinct from market research (sizing demand) and usability research (testing existing products) — using methods like user interviews (behaviour, not opinions), contextual inquiry (watching users in their environment), Jobs-to-be-Done, assumption mapping, and concept testing. Common mistakes: leading with the solution, asking about the future, confusing volume for quality, and not sharing findings with engineering — good discovery is scoped to a specific decision and proportionate (5–8 interviews often enough)

Interesting: The Waiting Room Problem in UX

The "waiting room problem" in UX is the gap between what users say ("it's fine") and what their behavior reveals — surveys capture polite, conscious responses, not subconscious discomfort. Good wait states answer three questions: is something happening? how long? what next? — uncertainty, not time, is the real enemy, and this is a retention problem with a design-shaped root cause

@uxdiest

The UX Secret Hidden Inside Human Memory

A deep look at how human memory shapes UX: the "remembering self" (Kahneman's peak-end rule) dominates evaluation — the most intense moment (peak) and the ending carry disproportionate weight, while duration is largely ignored. Key implications: design for recognition (not recall), chunk information for working memory (~4 items), and run a "memory audit" — users remember peak and ending moments, not routine interactions

The Loneliness of Layoff: How to Actually Support Someone

A first-hand reflection on layoff — losing work, community, stability, and self-worth — and how the silence from former colleagues compounds the pain while mental health is fragile. How to help: just show up, send a simple text ("this sucks"), make introductions if you can — be present, not perfect

🎥 NNG: 4 Mistakes to Avoid When Presenting Complex UX Maps

UX maps clarify complexity but are often presented poorly. Prepare audiences by communicating early, speaking plainly, and focusing on collaborative outcomes

Prototyping: The Text Box Isn’t the Finish Line - How Interfaces Are Evolving Past Chat

A critique of the AI default to chat interfaces: the text box won because it's the fastest wrapper around a language model, not because it's best for humans — it pushes the burden of "magic words" onto users, strips context, and offers no working surface. The next interface should fit how humans work: show multiple zoom levels, bake context into the interface, give a real canvas to sculpt on, and use multiple senses — moving from "painting felt like typing" to "typing feels like painting."

AI: Building my own AI Research Assistant

A UX researcher built a custom AI agent (using Atlassian Rovo) to automate transcript organization and debriefing — cutting synthesis time from 1–3 days to a few hours, with no hallucinations or lost insights. Key: define functions in sequence, set a persona with clear do's/don'ts (no bias, no conclusions), and document behavior and output — the goal is freeing time for real analysis, not replacing researchers

Experience: I measured how pop-up notifications affect reading

A UX experiment found pop-up notifications dropped reading comprehension from 5.5/7 to 3.7/7 — even brief interruptions carried a cognitive cost, with the real damage being the mental effort to recover focus. The takeaway: designers should ask "does the user need to see this right now?" not just "how do we make it visible?" — timing matters as much as visibility

Opinion: Designers are sharpening knives for the wrong fight

Everyone is arguing about craft, taste, and standards (how to build) while ignoring the real fight — deciding what's worth building and for whom (strategy). AI made building free, so the old constraint (being wrong cost money) is gone; teams now build beautiful products nobody wants because no one stopped to ask "who is this for and why should it exist?"

Basics: The Science of Attention - Why You Use Some Products Every Day and Others Not

A breakdown of why some products become daily essentials while others get abandoned: friction (effort to use), habit loops (cue-routine-reward), identity alignment, cognitive load, trigger accessibility, novelty decay, and the return threshold (value vs. effort). Products that stick are low-friction, attach to existing cues, provide immediate rewards, align with identity, and exceed the return threshold — helping consumers buy better and designers build products that actually get used

Interesting: Why Sleep Is More Important Than Exercise (And the Lesson I Learned the Hard Way)

Sleep isn't the reward after work — it's what makes the work possible; training hard on 5 hours of sleep stalls progress because recovery (muscle repair, hormone balance, memory, immune function) happens during sleep. Poor sleep also undermines cognitive performance, decision-making, and appetite regulation — the most productive thing you can do tonight is actually sleep

@uxdigest

Understanding Alpha Inflation

Alpha inflation occurs when running multiple statistical tests at p < .05 — 20 tests give a 64% chance of at least one false positive, not 5%. Methods to control it (Bonferroni, Tukey) reduce false alarms but increase misses (Type II errors), so the decision depends on whether a false alarm or a missed real difference is more costly in your context

Why Technical Context Matters in UX Research (And How to Capture It Properly)

UX research in "clean room" conditions (perfect prototypes, high-speed internet) creates a false reality — when products hit the real world (slow databases, legacy systems, patchy networks), they fail. The fix: conduct on-site observations, map architecture with engineers, simulate real conditions (throttle networks, test on actual devices), and bridge design-engineering early

Some Bugs Don’t Throw Errors. They Just Make People Give Up

A founder watched a real user struggle and found "silent bugs" — problems that don't throw errors (logs are spotless) but quietly do the wrong thing (folder index lag, background refresh wiping unsaved edits). These bugs create churn with no signal: users don't report them, they just give up — and the only way to find them is watching real people use the product

NNG: Don’t Outsource the Learning - Why Human-Led Research Still Matters in the Age of AI

Even if AI matches research output quality, human-led research remains essential because research produces both findings (which AI can generate) and learning — the shared experience of observing users and being moved by their stories, which can't be outsourced. Stories engage the brain deeply, drive empathy and action, and the self-generation effect means the effort of deriving insights makes them memorable; protect the parts where learning lives (moderating, observing live, interpreting), and use AI only for support work that teaches nothing

Prototyping: Aesthetically Pleasing, Functionally a Disaster

A UX critique of a stunning but broken AI model selector: the beautiful grid implies every model supports every effort level, but real capabilities don't align — unsupported combinations create unsolved states, and Ultra breaks the mental model by leaving the scale as a dramatic glowing lever. The takeaway: polish is a layer, not proof — good UI earns attention, but good UX survives interaction; the live version is less cinematic but more honest because it maps one control to one decision

AI: Research Was Never About Speed, and AI Proves It

Research was never about speed — AI takes execution (transcription, first-pass synthesis) but leaves judgment (interpreting nuance, framing questions), which was always the point. The risk of flattening comes from process failures (treating summaries as findings, skipping raw data), not the tool — the cheaper execution gets, the more deliberate judgment must be

Opinion: You’re Ignoring Your Best UX Research Tool

Your support inbox is one of your best UX research tools: every support conversation is a raw usability test where users describe the gap between expectation and reality — patterns across tickets reveal design problems that analytics alone can't explain. Spend 20–30 minutes weekly reviewing support conversations, look for recurring language, and bring insights into design critiques — research happens every time a user struggles, not just when you schedule it

Basics: Stop Interviewing Your Users. Go Watch Them Work

A practical guide to Contextual Inquiry: instead of interviewing users (which gets polished summaries), go watch them work in their actual environment — people can't accurately tell you what they do because expertise hides in invisible micro-decisions. Key principles: be the apprentice, go where the work is, build a partnership, interpret out loud, and convert "solution" questions into "how do people actually work?" questions

@uxdigest

Ethnography: The UX Research Skill

Ethnography in UX means observing everyday behavior and asking why, not just asking users what they want — as shown in a gift-giving project where younger adults personalized gifts (identity) while older adults preserved traditions (responsibility). The lesson: products exist inside social relationships (Venmo emojis, Spotify playlists), and observing workarounds can reveal features — like Bank of America's "Keep the Change" (round-up savings), which came from watching mothers round up checkbook entries, not user requests

What a UX audit is actually testing (and why most designers get it wrong)

A UX audit that starts with a checklist is a "presence check," not a real audit — it tells you whether elements exist, not whether they function (a returns policy in legal language, a ghost "Add" button, cross-sells before trust signals). Key tests: the 5-second test (does navigation require translation?), the scroll test (price, rating, CTA, trust signal visible before scrolling), the thumb-only test (tap targets on mobile), and edge cases — then prioritize by funnel stage

NNG: Does Your Form Really Need a Dropdown List?

An NN/g guide on dropdown lists: they work best in a narrow sweet spot (5–10 options, secondary to the main task, or part of a grouped layout) — avoid for too few options (radio buttons), too many (combobox), familiar data (text input), or visual comparison (button grids). Dropdowns are a tradeoff, not a default: ask how many options, whether users need to see them all, and whether the layout benefits from hiding them

AI: Agentic AI is the perfect machine for creating unused documents faster

Agentic AI is the perfect machine for creating unused documents faster — it produces polished artifacts that look professional but contain no real insight, because most organizations are built to receive familiar forms, not to think. The danger isn't bad work looking bad; it's mediocre work looking better than ever, and the real test is whether the artifact changes a decision, not whether it fills a template

Prototyping: The Neuroscience of UX Design - A Complete Guide

A guide connecting neuroscience to UX: the 50-millisecond verdict (visual appeal judged before conscious thought), Fitts's Law (target size/distance), Hick's Law (more options = slower decisions), and working memory limits (~3-4 items) explain why best practices work. Good UX strips unnecessary cognitive load; as AI generates interfaces faster, understanding these mechanisms may be the human designer's last edge

Experience: Research is not a deliverable

A case study on building qualitative research in a metrics-obsessed organization: the author trained customer support agents (trained to give answers, not ask questions) to conduct semi-structured interviews — turning problem-solvers into empathetic listeners through mock interviews (scores went from 6s to 10s). The result was a self-sustaining research machine with an AI analysis pipeline — proving research is not a one-off deliverable, but a discipline built into the organization's culture and workflow

Design: Rethinking Sparkles in the Age of AI

HP's UX research found sparkle icons now signal "AI" to users regardless of style — subtle differences went unnoticed (64% saw no difference) and didn't convey "AI-ness." Context matters: sparkles work on familiar AI territory (chat, images) but confuse on printers/documents; reserve them for real AI actions and add context in unfamiliar places

Basics: The Difference Between What Customers Say and What They Mean

A short reflection on a core product insight: customers are excellent at describing their problems but not always good at describing solutions — teams mistake requests (more filters, export button) for needs, build what was asked, and still leave the original problem unsolved. The job is to uncover intent behind requests: ask "what are customers trying to accomplish?" not "what do they want?" — because the insight comes from understanding why the request exists

@uxdigest

The Reversal of Adaptation

AI still feels hard even as it gets smarter because we're adding intelligence to systems built on old assumptions — forcing users to "translate" their situations into system language instead of systems adapting to humans. The key idea is "The Reversal of Adaptation": for decades humans adapted to software; now software can adapt to humans, but we're automating the old relationship instead of redesigning it

The Direction Was Different. The Distance Wasn’t

A simple evening walk in the opposite direction felt easier — same distance, same route, but fewer interruptions and decisions at crossings — leading to a reflection on cognitive load in product design: users don't experience products through dashboards or step counts, but through moments of mental effort. The key insight: good design isn't always about removing steps or making things faster; it's about arranging work so interruptions feel natural and the user's rhythm isn't broken

🎥 NNG: What are Design Specs?

When designs get rejected in dev review, missing specs are often the culprit. A solid spec covers layout, interactions, requirements, and project scope

Prototyping: Designing For Distressed Users - Why Mental Health Apps Shouldn’t Follow Every UI Fashion

Mental health apps suffer from 95% 30-day abandonment partly because trendy UI patterns (hidden navigation, low contrast, gamified streaks) create cognitive friction and emotional mismatch for users already in distress. Design should be evaluated by: cognitive load, emotional alignment, navigational reliability, accessibility, and engagement integrity — meeting users at their capacity rather than adding effort when they have the least to spare

AI: Beyond speech-to-text - rethinking voice note transcripts

A case study exploring voice note transcripts across Snapchat, Instagram, iMessage, and WhatsApp found transcripts are a utility feature with no translation, copying, or feedback. Proposed improvements include sender editing, receiver translation/copying, and a feedback loop; testing showed cleaner designs win, but trust in accuracy remains the biggest gap

Design: Headless Design System

A headless design system separates structure from identity: maintain one master component library and swap its Foundation variables with a project-specific "Head" library (colors, typography). This keeps a single source of truth, propagates updates automatically, and scales across multiple brands without duplicating components

Basics: Five research questions that provide the foundation for good design

Adobe's framework asks five evidence-based questions: right audience, real use cases, unmet user needs, solution effectiveness, and team fit — shifting from "I think" to "I know" by treating assumptions as hypotheses to be tested with real users. Each question forces teams to ground decisions in evidence rather than personas or "we think" frameworks

@uxdigest

Taming Chaos

Key lessons from a webinar on sustainable systems: understand your environment before changing it, break changes into small steps, document to create shared language, allow controlled chaos for creativity, and treat systems as living things that need continuous feedback. The best system isn't the most organized one — it's the one people actually want to use

NNG: The 5 Qualities of Site-Specific AI Chatbots

An NN/g framework for site-specific AI chatbots: handoff willingness (escalate to humans), flexibility (handle adjacent questions and errors), proactivity (suggest next steps), emotional responsiveness (acknowledge situations), and transparency (identity, capabilities, rationale, privacy). Getting these right builds trust; getting them wrong creates a barrier between users and help

Prototyping: How we reduced IPO application time from 5 mins to 10 secs

A case study on HDFC Securities' IPO flow: users had already decided how much to apply for before opening the app, yet the old flow forced multiple decisions — so they reduced application time from 5 minutes to 10 seconds with a one-click default. They also fixed the post-application black box by making status visible and guiding disappointed users to other IPOs, working with engineering to solve underlying system gaps instead of masking them with UI

AI: UX Research + AI in 2026

UX research in 2026 is shifting from retrospective to predictive, and AI improves consistency and democratizes access — but the sharpest risk is synthetic users (bias laundering, misrepresentation, accountability gap), which can't reveal needs teams didn't anticipate. The field's choice isn't speed vs. rigor but convenience vs. accountability; a researcher's signature should still mean a real person's voice is underneath it

Opinion: After 14 Years in UX, One Thing Surprised Me About Users

After 14 years in UX, the author's biggest realization: users don't care about beautiful screens — they care about getting things done and solving problems. The real insight comes from asking "why" behind user suggestions and observing real behavior (not just listening to stated feedback), because the best UX lessons come from watching people struggle and succeed in everyday life

Design: The Framework I Use Before Designing Any Product

A five-phase pre-design framework: interrogate the origin story, map the behavioral gap (study workarounds), design the failure state first, check information asymmetry, and apply the reversibility test. The core principle: production is cheap, judgment is expensive — the designer's real value is asking uncomfortable questions that kill bad ideas before they become costly mistakes

@uxdigest