The flow that finally worked. The research that quietly changed a roadmap. The redesign that made a confusing thing simple. Now answer honestly: did anyone notice?

Probably not. Because when UX is done well, nothing happens. No complaints. No support tickets. No confused users. No drama. The product just works, people just use it, and everyone moves on with their day.

Nobody warns you about this when you enter the field. This issue is about the paradox at the center of UX work, why it quietly affects your career and your confidence, and how to handle it without becoming bitter or burning out.

In This Issue:

• The paradox nobody warns you about

• Why bad design gets noticed and good design does not

• What invisibility costs you, professionally and personally

• The invisible work behind the invisible work

• How to make your impact visible without ruining the work

• Resource Corner

The Paradox Nobody Warns You About

There is a paradox at the heart of design, one no one really warns you about when you are just starting out: the better your work is, the less likely anyone is to notice it. Nielsen Norman Group

Every other discipline gets to show its wins. Engineers ship features people can see. Marketers point to campaigns and numbers. Sales closes deals. UX, when it succeeds, produces an absence. An absence of friction. An absence of confusion. An absence of complaints.

Good design is like oxygen. Essential but unnoticed until it is missing. UX Tigers

Think about the doors you have not noticed. The ones where your hand just went to the right spot and the thing opened and you walked through and kept moving. No friction, no confusion, no tiny moment of feeling slightly dumb in public. That door did its job perfectly. Nobody is writing a review about it. UX Tigers

That door is your career. You are building hundreds of those doors. And the silence that follows good work is simultaneously the proof that it worked and the reason nobody is thanking you for it.

Become a UXCON26 Volunteer

UXCON26 is coming October 8 and we are building the team that makes it all happen behind the scenes.

Volunteering at UXCON26 means being part of one of the most anticipated UX events of the year. You will be surrounded by some of the sharpest minds in the field, contributing to a day the community will remember, and connecting with practitioners, leaders, and speakers who are shaping where this industry is going next.

If you are passionate about UX, love bringing people together, and want to show up for this community in a meaningful way, we would love to have you on the team.

Click to Apply

Why Bad Design Gets Noticed And Good Design Does Not

This is not unfair luck. It is how human attention works, and understanding it makes the invisibility easier to carry.

We do not spend our time thinking about how good the chair is that we are sitting in. We only come to realize the flaws of a design when it cannot perform the function it is supposed to. UX Design

Human brains are wired to conserve energy. When an experience flows smoothly, the brain stays in autopilot. Nothing gets flagged. Nothing gets remembered. The experience does not register as an experience at all. It registers as just doing the thing.

Friction is what wakes the brain up. The form that will not submit. The button that does not do what it promised. The navigation that hides the one thing you came for. These moments register. They generate emotion. They get remembered, complained about, screenshotted, and posted.

Which means the entire feedback system of the world is structurally biased toward noticing design failure and ignoring design success. Users do not praise a great UX. They simply use it without frustration. Your best work is competing for attention against an attention system that is designed not to give it any. LinkedIn

What Invisibility Costs You, Professionally And Personally

It would be nice to end the story there. Embrace the silence, take pride in the craft, move on. But the invisibility has real costs that deserve naming.

🔴 Promotion conversations are built on visible impact

When leadership discusses who gets promoted, the question is what has this person visibly done. The engineer shipped twelve features. The marketer grew the channel. The UX practitioner... prevented hundreds of problems nobody ever saw? Avoided redesigns that never had to happen? Prevention does not present well. Absence has no slide deck.

🔴 Budget decisions follow visible value

Teams whose value is visible get resourced. Teams whose value is invisible get questioned. When cuts come, the function whose impact is hardest to point to is the most exposed. This is part of why UX teams were hit so hard in the layoff waves. The work was good. The evidence was silent.

🔴 It quietly erodes your own confidence

This is the personal cost that compounds. You can know intellectually that your work matters while emotionally absorbing years of nobody noticing it. The absence of feedback starts to feel like an absence of value. Practitioners who have done excellent work for years sometimes struggle to articulate their own impact, not because it was not there, but because nobody ever reflected it back to them.

If you have ever felt like you are doing more than what your role seems to define, you probably are. And that invisible layer of work is not extra. It is the craft. UXPin

The Invisible Work Behind The Invisible Work

The interface that nobody notices is only the surface layer of what goes unseen. Underneath it sits an entire body of work that is invisible even to the people on your own team.

The stakeholder conversation that prevented a bad idea from reaching the roadmap. The research finding that quietly killed a feature that would have failed. The twenty versions that were explored and rejected before the one that shipped. The accessibility decisions that meant the product worked for everyone and therefore generated no complaints from anyone. The questions asked in a kickoff that reframed the entire problem.

If you take requirements at face value, you can still design something. But if you spend time unpacking them, asking why something is needed, how it will be used, what success looks like, the problem often changes. And with it, the solution. UXPin

That unpacking is invisible. The disasters you prevented are unprovable. Nobody can see the version of the product that would have existed without you. And yet that difference, between what shipped and what would have shipped, is arguably the truest measure of what a UX practitioner contributes.

How To Make Your Impact Visible Without Ruining The Work

The answer is not to make the design louder. The design should stay invisible. The answer is to make the work around the design visible. There is a difference.

✓ Document the before, every time

The single most powerful habit. Screenshot the old flow. Record the confused usability session. Save the support ticket volume. Capture the baseline metric. Invisible work becomes visible the moment you can show what it replaced. Without the before, your after looks like nothing happened. With it, the same after tells the whole story.

✓ Translate absence into numbers

Support tickets that dropped. Error rates that fell. Task completion time that shortened. Drop-off that decreased. These are absences made measurable. They are the closest thing prevention has to a slide deck. Track them even when nobody asks, because by the time someone asks it is too late to establish the baseline.

✓ Narrate the decisions, not just the outcomes

Share the rejected versions. Explain what the research ruled out. Walk stakeholders through why the simple-looking solution took three weeks. Often the most powerful design choices are the ones nobody sees happening, until the results become impossible to ignore. People cannot value reasoning they never saw. Showing the thinking is not self-promotion. It is making the craft legible. Index.dev

✓ Claim prevention out loud

“This redesign means we will not need the support documentation we were planning.” “This finding saved us from building a feature users would not have adopted.” Prevention claims feel awkward because they point at things that did not happen. Make them anyway. Nobody else is keeping that ledger for you.

✓ Reflect your colleagues’ invisible work back to them

The fastest way to change a culture that ignores invisible work is to start noticing it in others. When a researcher’s finding quietly reshapes a decision, say so in the meeting. When a designer’s flow ships and nothing breaks, point out that nothing breaking was the achievement. A team that names invisible work creates the conditions where everyone’s invisible work counts.

📦 Resource Corner

The Design of Everyday Things by Don Norman
The book on why good design disappears and bad design screams. If you have never read it, this is the foundational text on everything in this issue. If you read it years ago, it reads differently once you have lived the paradox.

Articulating Design Decisions by Tom Greever
The most practical guide to making your reasoning visible to stakeholders who only see the surface. Directly addresses the gap between doing good work and getting credit for it.

Measuring the User Experience by Tullis and Albert
How to turn absences into numbers. Essential for building the evidence base that makes invisible impact legible to people who make budget and promotion decisions.

Do the Most Good by Mina Markham
A talk worth rewatching about once a year on doing meaningful work whether or not anyone is watching. Genuinely restorative when the invisibility is wearing on you. Index.dev

The Invisible Work of Design
A short, honest read on the paradox itself. Worth bookmarking for the days when the silence gets loud.

💭 Final Thought

If you are a practitioner and you often feel like your best work keeps vanishing into the background, take heart. That is often the clearest sign you are doing it brilliantly. Nielsen Norman Group

The user who never noticed your navigation found what they needed. The customer who never contacted support completed their task. The person who never thought about your form filled it out and moved on with their life. Thousands of small moments where nothing went wrong, because you made sure nothing would.

That is the job. It has always been the job. You pushed. It opened. That is the whole story. UX Tigers

But do not confuse the work being invisible with you being invisible. The design should disappear. Your contribution should not. Keep the before screenshots. Track the absences. Narrate the decisions. Claim the prevention. Make the craft legible even as the craft itself stays silent.

Because the silence was never emptiness. It was thousands of doors, opening exactly when someone expected them to.

You built those.

--- The UXU Team

→ What the data says about who is actually using AI at the highest level
→ Why the gap between you and leadership is wider than you think
→ What happens when that gap becomes visible in the wrong moment
→ The working session built to close it before it costs you

There is a conversation happening in leadership right now that most practitioners are not part of.

It is not about whether to use AI. That decision has already been made. It is about which people on the team actually know how to use it in a way that moves the organization forward, and which ones are still figuring it out.

A new report from Notion surveyed more than 6,000 workers across 10 countries to understand where organizations actually stand with AI adoption. One finding cuts deeper than the rest.

That means the people deciding who gets promoted, who gets the interesting projects, and who gets let go when budgets tighten are not using AI the way you are using it. They are not using it to brainstorm or draft. They are using it to make decisions, build systems, and scale output in ways that are fundamentally changing what they expect from the people around them.

And most of them have not told you that directly. They do not have to. It shows up in the questions they ask in meetings. It shows up in the feedback that feels slightly off but you cannot name why. It shows up in the moment someone newer to the team answers a question faster than you did and you notice the room shift.

The Gap Is Not About Tools

This is not a story about who knows more software. The report is clear on that. The practitioners moving fastest are not the ones with the longest list of AI tools in their stack. They are the ones who have figured out how to use AI to do work they previously could not do, to make sharper decisions, and to communicate value upward in language that lands with the people who control resources.

That is a positioning skill. A communication skill. A career skill.

And it is exactly the kind of skill that does not come from a tutorial.

🟢 EVENT

Upskill AI: Repositioning For The New Economy
📅 July 23, 2026 · 12 to 4PM
📍 Silver Spring Civic Building, Silver Spring, MD

Four hours. Your actual resume, your actual pitch, your actual positioning, rebuilt in real time using AI tools and led by three founders who are operating at the level your leadership is already at.

Jake DiBattista · Founder & CEO, Buddy
Evan Katz · Founder & CEO
Yao Adantor · Founder & CEO, UXU

RSVP HERE!

They have hired. They have been hired. They have repositioned themselves and built teams through this economy. They are not coming to tell you what AI is. They are coming to work with you on how you show up to a market that has already moved.

You leave with a finished output, sharper positioning, and one specific next step you chose before you walked out the door.

The gap between where leadership is and where most practitioners are is not closing on its own. Every week you wait is a week someone else in your organization is closing it instead.

RSVP HERE!

📚 Resource Corner

→ The Great Renovation: Notion’s Global AI Transformation Report · The full data on where organizations and individuals actually stand with AI right now
→ 10 Best AI Resume Tailoring Tools in 2026 · Which tools pass ATS screening and which are overhyped
→ The 6 Best AI Resume Builders in 2026 · Free and paid options worth exploring before July 23

Final Thought

The distance between where you are and where leadership expects you to be is not a performance problem. It is an information problem. And information problems have solutions.

The UXU Team

The most-used design tool after Figma is now an AI. 46.6% of managers are vibe coding. A skill that did not have a name two years ago is now sitting in the middle of how UX work actually gets done, and a lot of practitioners are learning it quietly so nobody clocks that they were behind. Index.devIndex.dev

If you have been hearing the term and nodding along without being totally sure what it means or how to start, this issue is for you. No hype, no gatekeeping. What it is, why it matters, and a concrete way in.

In This Issue:

• What vibe coding actually is (and is not)

• Why it took over so fast

• What it means for designers vs. researchers

• The bar has already moved past “I made a prototype with AI”

• A practical starting point for this week

• Resource Corner

What Vibe Coding Actually Is (And Is Not)

Let’s clear this up first, because the term confuses people.

Vibe coding is building working software by describing what you want in plain language and letting AI generate the code. You type “a signup screen with email and password, then a dashboard showing recent orders” and you get a functional, clickable, real thing. Not a Figma mockup that looks interactive. Actual working code running in a browser.

Vibe coding is not “learning to code,” and it is not classic no-code either. It sits in between. You are not writing the code by hand. You are also not dragging pre-built blocks around a template. You are directing an AI to build something real, then refining it through conversation. UX Tigers

For UX practitioners, the significance is specific. The thing you design and the thing the user actually experiences have always been separated by a handoff, a translation, a gap where intent gets lost. Vibe coding collapses that gap. You can build the real experience yourself, test it, feel it, and iterate on it, without waiting for anyone.

Why It Took Over So Fast

A year ago this was a niche curiosity. Now it is mainstream. The speed is worth understanding.

The tools got genuinely good. Lovable and Bolt.new came to dominate the prototyping space, enabling users to create full-stack apps using natural language commands without local setup. Lovable reached $300 million in annualized revenue by January 2026, less than a year after launch. That is not slow adoption. That is a tool meeting a need the field did not know how to name yet. Nielsen Norman Group

The output stopped looking like a toy. Bolt.new emphasizes speed with instant browser-based previews. Lovable is particularly effective for design-focused React apps. These are producing things that look and behave like real products, not rough sketches with placeholder text. Nielsen Norman Group

And the market started rewarding it. Vibe coding, AI prototyping, and research with tools like NotebookLM are now considered baseline technical skills for UX, alongside traditional Figma and usability testing. What was a nice-to-have became a line item on what practitioners are expected to bring. Smashing Magazine

What It Means For Designers vs. Researchers

The same shift lands differently depending on your role.

🔵 For designers

The handoff gap shrinks dramatically. You can build the actual flow, not a prototype that approximates it. You can test real interactions, real states, real edge cases that static mockups hide. The advice now is to build flows, not just screens. Code out the full journey: signup, dashboard, settings, logout, and push it live. Designers who can take an idea all the way to something clickable and real have a different kind of leverage in a room than designers who hand off a file and hope. Smashing Magazine

🔵 For researchers

This is more nuanced, and the data shows it. 39.1% of researchers feel less secure right now, the highest anxiety of any role. But 17.4% feel more valuable. The researchers thriving are the ones integrating AI into their practice rather than waiting for permission. Index.dev

For research, vibe coding is not about replacing your methods. It is about testing faster. Instead of describing a concept to participants or showing them a flat prototype, you can put a working version in their hands and watch them actually use it. You can build a realistic stimulus for a study in an afternoon instead of waiting weeks for design and engineering resources. The research value is in the realism and the speed, not in becoming a builder.

The Bar Has Already Moved Past “I Made A Prototype With AI”

This is the part that matters most and gets missed.

In 2026, nobody is impressed by “I made a prototype with AI” anymore. Everyone has seen stunning UI generated in an hour. Everyone has seen demos that look flawless on the first screen, then completely fall apart on the second. UX Tigers

That last line is the whole game. AI is very good at the first screen. It is much worse at consistency, at the second and third screen, at proper states, at a coherent system that holds together across an entire flow. Generating something that looks good is now trivial. Generating something that actually works as a real, consistent product is not.

What is impressive today is a practitioner who can take an idea and turn it into something that feels like a real product: with rules, consistency, a design system, proper behavior, and a process you can trust. This is exactly where vibe coding transforms from a trend into a real craft. UX Tigers

This is good news for UX people specifically. The thing that separates a flashy demo from a real product is exactly the thing you are trained in: systems thinking, consistency, states, edge cases, the discipline of making something hold together. AI handles the generation. Your UX judgment is what makes the output actually good. The skill is not prompting. It is knowing what good looks like and directing the tool toward it.

There is one real caution worth naming. Around 45% of AI-generated code contains vulnerabilities, and human oversight remains critical for security and quality. For production-level work, traditional programming is still indispensable. Vibe coding is for prototyping, testing, and communicating. It is not a shortcut to shipping production software without engineers. Knowing that line keeps you credible. Nielsen Norman Group

Edward Cupps isn’t blaming AI for the job market, he’s challenging the narrative.

The biggest shake-up didn’t start with AI. It started after COVID.

AI will change how we work. It will boost efficiency. But the real conversation is bigger than replacing jobs, it’s about adapting to a changing industry.

Are we asking the right questions, or just chasing the loudest headlines?

🎟️ Hear Edward Cupps and other industry leaders unpack the future of UX, AI, and innovation at UXCON26.

Secure your spot today!

A Practical Starting Point For This Week

Not a course. Not a rabbit hole. Avoid the “YouTube rabbit hole.” Do not spend hours watching. Here is a way in that takes an afternoon. Smashing Magazine

✓ Pick one tool and build one thing

Start with Lovable or Bolt.new. Both are browser-based, no setup. Pick one small, real flow. A login screen leading to a simple dashboard. Describe it in plain language and watch it build. The first time it generates something clickable from your sentence, the whole thing clicks.

✓ Rebuild something that already exists

Pick a favorite app and rebuild its UI. Recreate real apps in code. It is design weightlifting for your hands and brain, not just your eyes. Copying something real teaches you the gap between what looks right and what actually behaves right far faster than building from scratch. Smashing Magazine

✓ Build a full flow, not a single screen

This is where you learn the actual lesson. Do not stop at a landing page. Code out the full flow: signup to dashboard to settings to logout. The moment you go past the first screen is the moment you discover where AI breaks and where your UX judgment becomes essential. Smashing Magazine

✓ Turn a real complaint into a prototype

Grab App Store reviews or posts where users complain. “The dark mode toggle is hidden” becomes your next vibe-coded prototype. Solve real problems with live, clickable builds instead of static mockups. This is also how you build portfolio pieces that show judgment, not just output. Smashing Magazine

✓ For researchers: build a study stimulus

Take a concept you would normally test with a flat prototype and build a working version instead. Put something real in front of participants. Watch how differently they engage with something they can actually use versus something they have to imagine.

📦 Resource Corner

Lovable
The tool that defined this category. Browser-based, natural language, particularly strong for design-focused React apps. The best starting point for most UX practitioners. Free tier is enough to learn on.

Bolt.new
The speed option. Instant browser-based previews, excellent for validating an idea in thirty minutes before committing to anything more involved. Pairs well with Lovable depending on the task.

The Complete Vibe Coding Guide for Designers (Muzli)
The single best written guide on this for UX practitioners specifically. Honest about where the craft actually lives now versus the easy demo. Read this before you start.

Figma Make
If you live in Figma already, this is the lowest-friction way to start, since it builds AI generation into the tool you are already using. Good for designers who do not want to leave their existing workflow.

State of Prototyping Spring 2026 (UX Tools)
The full survey data behind this issue. 1,478 practitioners on how they actually work now. Worth reading directly to understand where the field genuinely is, not where the hype says it is.

💭 Final Thought

Vibe coding sounds like a threat if you frame it as “now everyone can design.” It is not. What it actually does is raise the value of the thing UX people have always been good at.

When anyone can generate a screen that looks good, the screen that looks good stops being valuable. What becomes valuable is the judgment to know whether it actually works. Whether it holds together across a flow. Whether it serves the person using it or just looks impressive in a demo. That judgment is the craft, and the craft is yours.

The practitioners pulling ahead right now are not the ones who can prompt an AI. Everyone can do that. They are the ones who can take what the AI produces and apply real UX thinking to make it into something that actually works.

The tool is new. The skill underneath it is the one you have been building all along.

Open Lovable. Build one flow. See for yourself.

--- The UXU Team

In the first 3 seconds, they scan your opening case study title and first visual. If it doesn’t immediately signal impact, they’re already mentally moving to the next candidate. In the next several seconds, they’re skimming for metrics, outcomes, and evidence of strategic thinking.

That is the whole window. Hiring managers get 200+ applications for senior roles and spend an average of 6 to 8 seconds on the initial portfolio scan before deciding to dig deeper or move on.

Here is the uncomfortable part: that is not enough time to read your thoughtful process documentation. It is barely enough time to scan your headlines and metrics. Most designers and researchers build their portfolio like a thesis, something to be read start to finish. Hiring managers treat it like a trailer. If yours takes two minutes to get to the good stuff, they are already gone.

This issue is about designing for how portfolios are actually consumed, not how you wish they were.

In This Issue:

• The 6-second scan and what it means

• Why storytelling beats screenshots (with the data)

• The metrics move: from “improved UX” to real numbers

• What researchers should show that designers should not

• A practical fix list for this week

• Resource Corner

The 6-Second Scan And What It Means

The numbers are brutal and worth internalizing.

📊 Hiring managers get 200+ applications for senior roles and spend 6 to 8 seconds on the initial scan.
📊 94% of first impressions are design-related, which means your portfolio itself has to demonstrate good UX before anyone reads a word.
📊 Most portfolios fail the “3-second test”: can someone glance at any section and instantly understand what it is and why it matters?

Think of your portfolio like a landing page, not a journal. Nobody watches a 3-minute trailer that takes 2 minutes to get to the good stuff. The reader wants to know immediately: is this worth my time?

The practical implication changes everything about structure. Your most impressive result belongs at the very top, in the title, before the reader has scrolled. Not buried in the results section at the bottom of case study three. The scan happens top-down and fast, and if the top does not hook, the bottom never gets seen.

Your portfolio isn’t a record of your career. It’s a strategic highlight reel for where you’re headed next. Treat every scroll as a pitch.

Why Storytelling Beats Screenshots

Here is the thing that separates portfolios that get callbacks from ones that get crickets, and it is not visual polish.

A hiring manager reviewing dozens of portfolios will remember a strong story over a collection of screenshots. UX is not about aesthetics. It’s about problem-solving. A good story explains why you made key decisions, not just what you did. Companies don’t hire people to make things look nice. They hire them to solve business problems.

The data backs this up clearly. From studying UX hiring, the portfolios that perform best are the ones that explain thinking and demonstrate a user-centric mindset. Not the flashiest. The clearest.

Storytelling makes your portfolio compelling, but documentation is what makes it credible. It gives hiring managers the evidence they need to evaluate your rigor and trust your conclusions. Without it, you could claim your work increased profits 12x, but with no methodology or supporting artifacts, that claim doesn’t hold water.

A good case study has a shape: problem, context, process, solution, results. But the shape alone is not the story. The story lives in the why. Why you chose that method. What went wrong. What constraint forced a hard tradeoff. What changed over time. Adding real constraints, feedback loops, and what changed makes your work feel realistic and job-ready. Perfect projects where everything went smoothly read as fiction. The messy, honest journey reads as experience.

One more discipline: length. The goal is structured storytelling that shows decision-making from start to finish, typically within 500 to 600 words per case study. Detail should serve clarity, not volume. Overloading with raw research and endless screenshots dilutes the narrative that actually gets you hired.

AI can now do in seconds what used to take you a week. So where does that leave you?

Every week there’s a new tool that drafts wireframes, writes copy, generates user flows, even portfolio creation, the things that used to be your job security. And the question quietly sitting underneath all of it is: if AI can produce the deliverable, what exactly am I bringing to the table?

The answer isn’t panic. It’s positioning. UXCON26 brings together practitioners from Netflix, The New York Times, Target, and more who are already working through this exact shift, alongside Don Norman, the person who defined what user experience even means in the first place.

October 8. One day. The conversations that actually answer the question.

Secure your spot

The Metrics Move: From “Improved UX” To Real Numbers

This is the single highest-leverage change most people can make.

“Improved UX” is about as meaningful as saying “we made it better.” Better how? Better by what measure? Better for whom? Senior practitioners speak in business metrics because that’s the language executives understand.

Look at the difference. Here is what a strong results section actually looks like:

▸ Increased mobile banking adoption by 56%, driving $2.4M in cost savings through reduced branch visits
▸ Simplified an 8-step transfer process to 3 steps, increasing completion rate by 41%
▸ New biometric login reduced authentication time from 25 seconds to 2 seconds
▸ Proactive error messaging cut support tickets by 28%

Notice the structure. The most important result is stated first, giving the reader the key takeaway instantly. Each line connects a design decision to a measurable outcome. This is scannable in the 6 seconds you actually get.

And if you do not have hard numbers? You still have options. Even small-scale projects can demonstrate measurable change: improved usability test success rates, reduced task completion time, clearer information hierarchy. If hard metrics are unavailable, qualitative outcomes and structured feedback can still demonstrate impact. “Users completed the task without assistance in 9 of 10 sessions, up from 3 of 10” is a real result even without a revenue figure attached.

The point is to prove it mattered, not just to show what you did.

What Researchers Should Show That Designers Should Not

This matters, because research portfolios are not design portfolios with different screenshots. They are a different artifact.

UX research portfolios aren’t meant to impress with polished visuals. They’re meant to reveal how you think. While design portfolios highlight the final product, research portfolios should focus on how you informed that product: what questions you asked, how you gathered data, and what decisions your work influenced.

As one Google UX Research Lead put it: your portfolio isn’t a research readout to stakeholders, it’s a self-portrait of you as a researcher. That reframe takes the pressure off making it flashy and puts it where it belongs, on demonstrating rigor and judgment.

For researchers specifically:

▸ Lead with the decision your work influenced, not the methodology. “My research killed a feature the team had already started building” is a stronger opening than “I ran 12 interviews.”
▸ Show your reasoning, not just your methods. Explain why you chose usability testing over a survey. Otherwise it reads like you ticked research off a checklist.
▸ Include the artifacts as evidence, not decoration. Affinity diagrams, personas, and journey maps show process, but insights are more valuable than screenshots of interview scripts. Link the finding to what changed because of it.
▸ Demonstrate influence beyond the project. If you improved how the team does research, standardized a process, made insights more accessible, show that. It signals you think beyond your own work.

A Practical Fix List For This Week

Concrete, in priority order.

✅ Rewrite your top case study title to state your best result. Not “Redesigning the checkout.” Try “Cut checkout abandonment 34% by simplifying an 8-step flow to 3.” Lead with the outcome.

✅ Run the 3-second test on every section. Glance at each one. Can you tell what it is and why it matters instantly? If not, tighten the heading and surface the key point.

✅ Replace every vague claim with a number or a specific qualitative result. Hunt down every “improved,” “enhanced,” and “better.” Make each one concrete.

✅ Cut a project. Digital hoarding kills portfolios. A smaller portfolio with strong storytelling and clear impact beats a large one with shallow explanations. Remove your weakest case study entirely.

✅ Have a non-designer read it. Pick someone who is not in the field. If they cannot understand what you did and why it mattered, it is too dense. This is the fastest reality check available.

✅ Start a “document while you design” habit. Screenshot flows, capture feedback, note decisions as you go. Drop them in a Notion or Figma folder weekly. These breadcrumbs become portfolio gold and save you from reconstructing everything from memory later.

📦 Resource Corner

UX Portfolio Guide: How Senior Designers Get Hired in 2026 (UX Playbook)
The clearest breakdown of the 6-second scan and the 5 things senior portfolios do differently. Directly actionable, honest about what actually moves hiring managers.

UX Research Portfolios That Get You Hired (User Interviews)
21 templates and real UXR portfolios that landed jobs, with strong guidance on storytelling versus documentation. The single best resource specifically for researchers.

How to Write UX/UI Case Studies That Get You Hired (Interaction Design Foundation)
Uses classic story structure (exposition, conflict, climax) to make case studies memorable. Excellent on turning a dry process into a narrative people actually want to read.

Growth.Design Case Studies
Comic-style product teardowns that are a masterclass in visual storytelling and applying psychology. Study the format to learn how to make your own case studies scannable and memorable.

27 Best UX Portfolio Examples (UXfolio)
A current, curated set of real portfolios with analysis of why each works. Useful for seeing the 500-to-600-word case study discipline applied across different career stages.

💭 Final Thought

There is a hard truth buried in all of this, and it is oddly freeing once you accept it.

Your portfolio is not a monument to everything you have done. Nobody has the time or interest to consume it that way. It is a pitch, read in seconds, by someone with 199 other tabs open, who is looking for a reason to say yes or a reason to move on.

That sounds harsh, but it points directly at what to do. Make the yes easy to find. Put your best result where they cannot miss it. Tell the story of how you think, because how you think is what they are actually hiring. Prove it mattered with a number or a concrete outcome. And cut everything that does not serve that.

If your portfolio isn’t landing interviews, it’s usually not because you’re not talented. It’s because it isn’t making the right impression in the window you actually get. Shift from showing what you did to proving why it mattered.

The people who tell the clearest story about their impact are the ones who get hired. Not the ones with the most projects or the prettiest screens.

Open your portfolio. Read only the first 6 seconds of it. Fix what those 6 seconds say.

--- The UXU Team

→ What 6,000 workers just revealed about where AI adoption actually stands
→ The gap nobody is talking about honestly
→ What happens if you do not close it
→ The working session built for exactly this moment

A new report from Notion surveyed more than 6,000 workers across 10 countries to understand where organizations actually are with AI. Not where they say they are. Where they actually are.

The finding that should stop every UX practitioner in their tracks: 57% of organizations are still at the earliest stage of AI adoption. Most teams are using AI to brainstorm and draft. Not to run workflows. Not to make decisions. Not to do the work that actually moves organizations forward.

But here is what does not make the headline.

The companies investing most aggressively in AI are also the ones saying their employees are not prepared to use it. That number climbs from 48% at the earliest stage all the way to 68% at the most advanced. The further along an organization is with AI, the wider the gap between what they have built and what their people know how to do with it.

The more advanced the company, the more behind their employees feel.

If you are a designer, researcher, content strategist, or anyone working in the UX space right now, this data is describing your situation. Your organization has already made a bet on AI. The tools are there. The expectations are shifting. Quietly, and faster than most people realize, the definition of what makes someone valuable at work is changing.

And most practitioners are still trying to figure out where they fit.

The Part Nobody Says Out Loud

This is not showing up in performance reviews yet. It is not in the job description. But it is in the room during every product review, every research readout, every design critique where someone asks a question you are not sure how to answer anymore.

The practitioners who are pulling ahead right now are not the ones who know the most tools. According to the same report, they are the ones who have figured out how to use AI to do work they previously could not do, make better decisions faster, and communicate value to the people who control budgets and headcount.

That is a specific skill. And it is learnable. But it does not come from watching a webinar or reading another article about prompt engineering.

It comes from doing the work. In a room. With people who have already figured it out.

🟢 EVENT

Upskill AI: Repositioning For The New Economy
📅 July 23, 2026 · 12 to 4PM
📍 Silver Spring Civic Building, Silver Spring, MD

This is a 4-hour working session, not a lecture. You will sit down with your actual resume, your actual pitch, and your actual positioning and rebuild them using AI tools that are already reshaping how hiring works right now.

Led by three founders who have hired, been hired, repositioned, and built through this economy from the inside:

Jake DiBattista · Founder & CEO, Buddy
Evan Katz · Founder & CEO
Yao Adantor · Founder & CEO, UXU

They are not here to teach theory. They are here to work with you on the thing that actually matters: how you show up to this market, today.

You will leave with a finished output, sharper positioning, and one specific next step you chose before you walked out.

The gap between where organizations are and where they expect their people to be is not closing on its own. Six months from now you will either be someone who closed it or someone who is still thinking about it.

RSVP HERE!

Spots are limited and this one fills fast.

📚 Resource Corner

→ The Great Renovation: Notion’s Global AI Transformation Report · The full data behind what AI adoption actually looks like across 10 markets right now
→ 10 Best AI Resume Tailoring Tools in 2026 · Which tools actually pass ATS screening and which are overhyped
→ The 6 Best AI Resume Builders in 2026 · Zapier’s breakdown including free options worth starting with

Final Thought

The data already told you where things are heading. The only question left is what you do with that information.

The UXU Team

You spent six weeks on a redesign. The flows were clean. The hierarchy was solid. The stakeholders nodded. You shipped it. And then… users still dropped off at the same point.

You have been there. Every UX practitioner with more than six months on the job has been there. And here is what was probably missing: behavioral psychology. Users don’t make decisions logically, they make them emotionally and instinctively. Design for the screen and you optimize pixels. Design for how people actually decide and you influence outcomes.

The best part? Most UX practitioners are already applying behavioural psychology. They just don’t know the names for it. And naming them matters, because labelling gives you the language to defend your decisions, educate stakeholders, and go deeper.

This issue names the principles, backs each with data, and gives you a way to apply every one.

In This Issue:

• Why the brain takes shortcuts (and why that is good news)

• 🧠 6 principles worth knowing by name

• The data that proves they move real metrics

• The ethical line you do not cross

• A practical audit for your own product

• Resource Corner

INDEPENDENCE DAY OFFER

This weekend we have been thinking about that a lot in relation to this community. Because what we see every day in the UX space is practitioners who know things need to change, who feel the shift happening around them, who are ready to invest in what comes next. And then the moment passes.

The UXCON26 Independence Day discount closes tonight at midnight. It has been live since Friday and this is the last time we will mention it.

October 8 is the day this community comes together. Don Norman, the person who gave this field its name, headlines a lineup of practitioners from Netflix, The New York Times, Target, UserTesting, and Skylight. People doing work that matters at the highest level, in a room built for honest conversation about where UX is actually going.

The lowest price this ticket will be, ending tonight.

Grab the offer

Why The Brain Takes Shortcuts

Start here, because it reframes everything.

The human brain is designed to take mental shortcuts. We don’t analyze every decision in a purely rational manner. Instead, we use heuristics to simplify decision-making. These shortcuts are not flaws. They are how a limited-capacity brain navigates an overwhelming world efficiently.

For practitioners, this is genuinely good news. It means human behavior, while it feels unpredictable, actually follows well-documented patterns. As idiosyncratic as individuals are, the way people process information, remember tasks, and make decisions follows consistent, researchable rules.

Which means you can design for them. Not by manipulating people, but by aligning your interface with how their minds already work. When you design with the grain of human cognition instead of against it, tasks feel effortless. When you design against it, everything feels like friction, no matter how clean the visuals.

🧠 6 Principles Worth Knowing By Name

Each of these has a name, a mechanism, and a direct application. Learn the names. They are how you turn instinct into a defensible design decision.

1️⃣ Hick’s Law → fewer choices, faster decisions

The more options a user sees, the longer every decision takes, until they make no decision at all. When you overwhelm users with information, they don’t make better decisions. They make no decision, or they leave.
▸ Apply it: Limit choices per screen. Group related items. Use smart defaults. Offer templates instead of blank starts.

2️⃣ Progressive Disclosure → reveal complexity gradually

Give users exactly what they need at this step, nothing more. The rest can come later, when it’s relevant.
▸ Apply it: That 10-field signup form you’re debating? Break it into steps with context at each one. Show advanced options only when the user reaches for them.

3️⃣ Social Proof → people follow other people

People decide how to behave by relying on what others have done. It is one of the most powerful trust signals available.
▸ Apply it: Surface real user reviews, testimonials, usage numbers, and endorsements at the moment of hesitation. Incorporating reviews and social shares has proven effective at establishing trust and engagement.

4️⃣ The Zeigarnik Effect → we remember what’s unfinished

Humans dislike leaving things incomplete. Incomplete tasks create a low-level mental tension that pulls people back to finish them.
▸ Apply it: Progress bars during onboarding. Checklists showing remaining steps. “Your profile is 70% complete.” The unfinished bar nags in a way that drives completion.

5️⃣ The Framing Effect → how you say it changes the choice

The same information presented differently produces different decisions. Frame shapes perception before logic gets involved.
▸ Apply it: Frame benefits as solutions to pain points (”Spend less time on X”). Present pricing around savings or added value. Use visual cues to emphasize the option you want chosen.

6️⃣ The Peak-End Rule → people remember the peak and the ending

Experiences are remembered based on their most intense moment and how they end, not the average of the whole thing.
▸ Apply it: Build one genuinely delightful moment into a key interaction. End onboarding on a celebratory high with a clear next step. The last impression disproportionately shapes the memory.

The Data That Proves They Move Real Metrics

These are not soft ideas. The numbers behind them are strong.

📊 In the US, 18% of online shoppers abandon carts because checkout feels too long or complicated, and another 17% leave for the same reason even when they already planned to buy. That is roughly a third of intending buyers lost to friction that behavioral design directly addresses.

📊 Great design can increase profit margins by up to 32%. Design is not decoration on top of the business. It is a lever on the business.

📊 Reducing choice through curation measurably raises both satisfaction and conversion. In e-commerce, understanding decision fatigue and simplifying options has become a standard way to lift results, because too many choices overwhelm users into leaving.

📊 Clearly showing outcomes reduces hesitation and builds trust. The more concrete and benefit-focused an experience feels, the easier it is for people to say yes. Framing is not cosmetic. It changes conversion.

The through-line: every one of these principles targets the exact moment a user hesitates, and hesitation is where revenue, trust, and retention quietly leak out of a product.

The Ethical Line You Do Not Cross

This is where behavioral design gets serious, and where responsible practitioners separate themselves.

The same principles that reduce friction can be twisted into manipulation. Persuasion helps users make decisions that serve them. Manipulation pressures them into decisions that serve only you. The difference is who benefits.

The rules worth holding to:

▸ Do not fake scarcity. Claiming a product is nearly sold out just to force a purchase is dishonest, and increasingly illegal.
▸ Use urgency signals sparingly and truthfully. “3 people are viewing this” should only appear if it is real.
▸ Respect autonomy. Provide clear information and real choices. Persuade, do not coerce.
▸ Respect privacy. Personalization should help, not feel like surveillance.

The goal is to improve the experience and facilitate navigation, not to pressure or harass users with malicious tactics. Every principle in this issue can be used to help a user get what they came for faster, or to trick them. Use them for the first. The second is now a legal liability, not just an ethical one.

A Practical Audit For Your Own Product

Run your product through these questions this week.

✅ Count the choices at your biggest decision point. Too many? Apply Hick’s Law. Cut, group, or default your way to fewer.

✅ Find your longest form. Can it become a progressive, multi-step flow with context at each stage? Almost always yes.

✅ Locate your moment of hesitation. The point where users pause before committing. Is there social proof there? If not, add it.

✅ Check your onboarding for a progress indicator. No sense of unfinished progress? The Zeigarnik Effect is going unused.

✅ Read your key CTA and pricing copy. Is it framed around user benefit and pain relief, or around features? Reframe toward outcomes.

✅ Find your product’s ending moments. Task completion, checkout success, trial end. Are they flat? The Peak-End Rule says the ending shapes the entire memory. Make it land.

📦 Resource Corner

Thinking, Fast and Slow by Daniel Kahneman
The foundational text on how people actually make decisions. Dense but essential. Every principle in this issue traces back to the two-system model of thinking Kahneman lays out here.

Laws of UX by Jon Yablonski
The cleanest reference for Hick’s Law, the Zeigarnik Effect, the Peak-End Rule, and more. Bookmark it and pull it up every time you need to name and defend a design decision.

18 User Psychology Concepts for UX Design (Userflow)
A practical, current catalogue of psychology principles with specific application examples for each. One of the best free references for turning theory into interface decisions.

How to Use Behavioural Psychology in UX (UX Playbook)
Ben McCarthy-Jones on applying these principles and, crucially, selling them to stakeholders. The section on why naming principles gives you leverage is worth the read alone.

Psychology for UX: Study Guide (Nielsen Norman Group)
A structured path through the psychology that matters most for UX. Ideal if you want to build real depth here rather than collect isolated tricks.

💭 Final Thought

There is a quiet shift that happens when you stop designing screens and start designing for minds.

You stop asking “does this look right” and start asking “what is the person thinking, feeling, and deciding at this exact moment, and does my design work with that or against it.” The first question produces attractive products. The second produces products that feel effortless, the ones people use without friction and cannot quite explain why they prefer.

The principles are not secrets. They are documented, researched, and available to anyone willing to learn the names. What separates practitioners who use them well is not knowledge. It is the discipline to apply them in service of the user, at the exact moments where a little less friction makes all the difference.

Learn the names. Apply them with the person’s interest at heart. Watch effortless stop being an accident and start being something you can design on purpose.

Open your product. Find one moment of hesitation. Fix it with one principle.

Then find the next.

--- The UXU Team

They try again. Same message. They have no idea why. Was it their card? Your site? A typo? They give up and leave. You just lost a sale, not because your product was broken, but because four words failed to tell someone what to do next.

That is the power of microcopy. The tiny, functional text that lives on buttons, in error messages, in form labels, in empty states, in the half-second a user is deciding whether to trust you or leave. It is the most overlooked skill in UX and one of the highest-leverage things any practitioner can get good at.

This issue is a hands-on guide. What microcopy actually is, why it matters more than its size suggests, and specific, practiceable techniques you can apply to your own product this week.

In This Issue:

• Why four words can make or break a flow

• The numbers that prove microcopy is not a nice-to-have

• The three rules that fix most bad microcopy

• A practical framework for error messages

• Why this is one of the safest skills to invest in right now

• Resource Corner

but first…..

Happy 4th of July from UXU. Here’s a little something.

Independence Day feels like the right moment to celebrate the people who chose a field built entirely around making things better for other humans. That is not a small thing. That is the whole point.

This weekend we are marking the holiday with a special discount on UXCON26 tickets, available from Friday July 4 through Monday July 6 only. Four days to lock in the best price this ticket will be before we head into the final stretch toward October 8.

Don Norman headlines a lineup that includes practitioners from Netflix, The New York Times, Target, UserTesting, and Skylight. Three keynotes. Two panels. Workshops. One day built around the conversations this community has been waiting to have out loud.

The offer closes Monday at midnight.

Grab the offer

Why Four Words Can Make Or Break A Flow

Microcopy works in the exact moments where users are most likely to abandon. The error. The hesitation. The point of commitment. The empty screen where they do not know what to do.

Tiny words remove roadblocks. Microcopy serves as a guide when users take specific actions and builds trust and empathy. Effective microcopy is clear, concise, fits the visual style, and fills a need. Without it, people hesitate, make mistakes, or abandon tasks. Designlab

The reason it punches so far above its weight is timing. A landing page headline reaches someone who is browsing. Microcopy reaches someone who is acting, at the precise moment the action might fail. A confused user at a button is one bad sentence away from leaving and one good sentence away from completing the task.

Conversion copywriting does not solely deal with words. It is deeply intertwined with UX and how those words are displayed. You must connect the copy to the design work, otherwise the disciplines pull in different directions. Site Builder Report

This is why microcopy is a UX skill, not a marketing one. It is not about persuasion. It is about removing the friction in the exact spot where friction is most expensive.

The Numbers That Prove Microcopy Is Not A Nice-To-Have

Skeptical that text this small moves real metrics? The data is unusually strong.

📊 Luke Wroblewski’s study on inline validation found that showing immediate feedback in forms led to 22% more successful submissions, 22% fewer errors, and 31% higher satisfaction. That is from microcopy attached to form fields. Small text, large outcome. Designlab

📊 One documented case showed that adding a “View Package” link above an “Add to Basket” button led to a 17.18% increase in conversions. A single line of well-placed text. Designlab

📊 Industry data finds that every dollar invested in UX yields a return of $100, and increasing the UX budget by 10% can lead to an 83% increase in conversions. Microcopy is one of the cheapest UX interventions available and one of the highest returning. Designlab

The reason these numbers are so strong is that microcopy fixes problems at the point of failure. You are not trying to attract someone new. You are stopping someone who already wanted to complete the task from giving up at the last moment. That is the cheapest conversion you will ever earn.

The Three Rules That Fix Most Bad Microcopy

Most bad microcopy fails the same handful of ways. Fix these three and you fix the majority of it.

✅ Rule 1: Clear beats clever

Keep explanations short and simple to minimize misinterpretation. Use as few words as you can, but enough to clarify what you mean. Personality has its place, but never at the cost of clarity. A funny error message that does not tell the user what went wrong is worse than a plain one that does. When in doubt, choose the version that gets the person unstuck fastest. Site Builder Report

✅ Rule 2: Tell people what to do, not just what happened

This is the single most common microcopy failure. “Invalid input” describes a problem. “Enter your date of birth as MM/DD/YYYY” solves it. Every error, every empty state, every dead end should answer the user’s real question, which is always some version of “okay, so what do I do now?”

✅ Rule 3: Reduce anxiety at the moment of commitment

The points where users commit are the points where they hesitate. On a subscription signup, microcopy like “You’ll be billed on the 1st of every month” and “Change or cancel anytime” helps people understand exactly what they are committing to. A small reassurance at the moment of doubt removes the friction that kills conversions. Tell people what happens next before they have to wonder about it. Lovable

A Practical Framework For Error Messages

Error messages are where microcopy matters most and where it most often fails. Research from Baymard found that the content of the error message itself greatly impacts the user’s ability to quickly recover and get back on track. Site Builder Report

Here is a reliable structure. A good error message does three things in order:

→ Say what happened, in plain language
Not “Error 422.” Not “Invalid input.” Say the actual thing: “We couldn’t find an account with that email.”

→ Say why, if it helps them fix it
“This usually means the email was typed differently when you signed up.” Only include this if it actually helps. If it does not, skip it.

→ Say what to do next
The most important part and the one most often missing. “Try another email, or reset your password.” Always give the user a path forward.

Run your own product’s error messages through this. For a checkout page where a customer enters the wrong shipping address, a message like “We couldn’t verify that address. Check the postcode and try again” works because it names the problem and gives a next step. Most error messages in most products fail at least one of these three steps. Fixing them is some of the fastest, cheapest UX improvement available. Site Builder Report

Why This Is One Of The Safest Skills To Invest In Right Now

In a moment where AI is automating large parts of UX production, microcopy is worth understanding clearly.

AI does help here. AI now handles the first draft of routine microcopy like button labels, error messages, and tooltips. But first draft is the key phrase. AI can generate a competent error message. It cannot know that your specific users are anxious first-time buyers who need extra reassurance, or that your brand voice is warm rather than corporate, or that this particular error happens most often to people who are already frustrated. Case Study Club

A brilliant product with confusing microcopy dies in onboarding. A simple product with clear, human words thrives. Case Study Club

The judgment about what the right words are for this user, in this moment, in this product’s voice, remains human. AI gives you a draft. Knowing whether the draft is right for your actual users is the skill. And it is a skill that compounds, because it sharpens your sense of the user’s emotional state at every point in a flow, which makes you better at the rest of UX too.

For content designers and UX writers specifically, this is your moment to go deep on the part of the work AI cannot do. For designers and researchers, microcopy fluency makes everything you produce sharper. It is one of the few skills with no real downside to investing in.

📦 Resource Corner

Microcopy: The Complete Guide by Kinneret Yifrah
The definitive book on the subject. Practical, example-driven, and the single best resource for going from “I write okay microcopy” to “I write microcopy that measurably improves products.” Worth every page.

Writing Microcopy: A 2026 Guide for Ecommerce UX (Shopify)
Specific, current, and full of real examples across checkout, forms, and error states. One of the most practical free resources available for applying microcopy to real flows.

The Definitive Guide to UX Writing 2026
Strong on how AI is changing the discipline and where human judgment stays essential. Useful for understanding where to position yourself if you want to specialize.

Nicely Said by Nicole Fenton and Kate Kiefer Lee
A foundational book on writing for digital products with clarity and humanity. Broader than microcopy but directly relevant, and a genuinely enjoyable read.

UX Content Collective
Courses, community, and ongoing resources specifically for content design and UX writing. The best place to go deep if microcopy turns out to be the part of this work you want to build a specialization around.

💭 Final Thought

It is easy to dismiss microcopy because it is small. A few words on a button. A line under a form field. A sentence on an error screen. How much could it possibly matter?

More than almost anything else you will touch, because it operates at the exact moments where users decide whether to continue or quit. The headline gets someone interested. The microcopy gets them through. And no amount of beautiful visual design rescues a flow where the words at the critical moment leave someone confused and stuck.

The best part is that this is immediately practiceable. You do not need a new tool or a course or permission. Open your own product right now. Find one error message that describes a problem without offering a solution. Rewrite it to tell the user what to do next.

That one change, repeated across a product, is the kind of work that quietly lifts conversion, reduces support tickets, and makes the whole experience feel like someone was actually thinking about the person on the other side.

Because someone was. That someone is you.

--- The UXU Team

Applications are going out. Responses are not coming back. Practitioners with real experience are finding themselves in a market that seems to have quietly rewritten its rules without telling anyone. It is not about effort. It is not about talent. It is about knowing how to position yourself inside an economy that has already moved on.

That is exactly what this workshop was built to address.

Upskill AI: Repositioning For The New Economy July 23, 2026 · 12 to 4PM · Silver Spring Civic Building, MD

Four hours. Your real resume. Your real pitch. Real AI tools. A room full of UX practitioners who are done waiting for the market to come back to them and ready to meet it where it actually is.

Led by Jake DiBattista, Evan Katz, and Yao Adantor, three founders who have built, hired, and navigated this economy from the inside. They are not teaching theory. They are teaching what is actually working right now.

You will not leave with notes. You will leave with a finished output, sharper positioning, and one clear next step you identified before you walked out the door.

Spots are limited and this one will fill.

RSVP HERE!

And if July is where the work starts, October is where the community comes together.

UXCON26 · October 8

Don Norman coined the term user experience. He is 88 years old, still publishing, still pushing, and he will be in the room with this community on October 8. Alongside him: practitioners from Netflix, The New York Times, Target, UserTesting, and Skylight doing the highest level work in the field right now.

One day. Eleven speakers. The conversations this community has been waiting to have out loud.

RSVP HERE!

The community is moving. Both of these rooms are part of that movement.

The UXU Team

What happens in the next minute decides almost everything.

Most drop-offs happen during the first session. Even small moments of friction can push users away quickly. And the bar for how fast you need to deliver value has dropped sharply. The AI onboarding benchmark is now around 60 seconds to value, with the strongest flows giving users useful output from very little input. everyday uxeveryday ux

Sixty seconds. That is the new standard. This issue is a hands-on playbook for designing the most consequential minute in your entire product, whether you are a designer shaping the flow or a researcher trying to understand why people leave.

In This Issue:

• Why the first session decides everything

• The 60-second standard and where it came from

• The most common onboarding failures

• A practical framework for the first minute

• What researchers should be doing here

• Resource Corner

but first….

Become a UXCON26 Volunteer

UXCON26 is coming October 8 and we are building the team that makes it all happen behind the scenes.

Volunteering at UXCON26 means being part of one of the most anticipated UX events of the year. You will be surrounded by some of the sharpest minds in the field, contributing to a day the community will remember, and connecting with practitioners, leaders, and speakers who are shaping where this industry is going next.

If you are passionate about UX, love bringing people together, and want to show up for this community in a meaningful way, we would love to have you on the team.

Click to Apply

Why The First Session Decides Everything

Onboarding is not a phase users patiently move through. It is a test they are running on you, often unconsciously, and they are looking for a reason to quit.

The onboarding phase is when you are at the highest risk of losing a user, especially if the experience is complicated and clunky. UX Tigers

The reason is simple psychology. A new user has invested almost nothing. There is no sunk cost holding them. Their tolerance for confusion is at its lowest point in the entire customer lifecycle because they have no proof yet that the payoff is worth the effort. Every second of friction is weighed against a near-zero commitment, which means even small obstacles tip the scale toward leaving.

This is also the moment with the highest leverage. Get it right and you have a user who has felt the value, formed a habit, and crossed the line from curious to committed. Get it wrong and the best product in the world never gets a second chance to prove it.

The 60-Second Standard And Where It Came From

The expectation around onboarding speed has shifted dramatically, and AI is the reason.

Onboarding has moved into a new phase. AI tools and product growth agents are making onboarding more outcome-driven. AI can help users create, configure, or organize something useful before they fully understand the product. everyday ux

This changed what users expect everywhere, not just in AI products. Once someone experiences a tool that delivers a useful result in under a minute, every other product gets measured against that. 80% of organizations want future customer experiences to be highly personalized and anticipatory in real time, and nearly 90% of onboarding teams planned to use AI and automation in their flows. everyday ux

The core principle behind the 60-second standard is “value before understanding.” You do not need the user to fully comprehend your product before they feel its benefit. You need to get them to a useful outcome fast, and let understanding follow. The old model of a guided tour explaining every feature is being replaced by getting the user to one real win as quickly as possible.

The Most Common Onboarding Failures

These are the patterns that kill first sessions. Most products commit at least two of them.

🔴 Asking for too much before giving anything

The signup flow that demands name, company, role, team size, use case, and a credit card before the user has seen a single moment of value. Every field you ask for before delivering value is a chance for the user to reconsider. Earn the right to ask by giving something first.

🔴 The feature tour that explains instead of delivers

The walkthrough that points at every button and panel while the user waits to actually do something. The best flows hand-hold users through an interactive walkthrough while helping them set up their account and complete a first real action, rather than just describing features. Showing someone the controls is not the same as getting them to their destination. UX Tigers

🔴 Burying the moment of value

Every product has an “aha moment,” the point where the user first feels why the product matters. The most common onboarding mistake is putting that moment too far in. If your value lives five steps deep, most users never reach it. The job of onboarding is to pull that moment as close to the start as possible.

🔴 Treating every user the same

First-time users see simplified interfaces while experienced users get advanced options. Adaptive onboarding reduces cognitive overload by showing only what matters at the moment. A returning user forced through the same beginner tour as a first-timer is a user you are actively annoying. Onboarding should adapt to who is actually arriving. Uxplaybook

A Practical Framework For The First Minute

Here is a structure you can apply to your own onboarding this week.

✓ Step 1: Define your moment of value precisely

Before designing anything, answer one question: what is the single moment where a new user first feels “oh, I get it, this is useful”? Not a feature. A felt outcome. For a design tool, it is seeing their first real design appear. For a writing tool, it is the first useful draft. Name that moment exactly. Everything else in onboarding exists to get the user there faster.

✓ Step 2: Map the shortest path to it

Onboarding strategy starts before the first screen. Map the user’s mental model, identify the moment of value, and design the shortest possible path from signup to that first success. Count the current steps between signup and value. Then ruthlessly cut. Every step you remove between arrival and the aha moment increases the odds the user stays. Slickplan

✓ Step 3: Deliver value before demanding information

Flip the usual order. Let users experience something useful first, then ask for the details you need. The credit card, the profile setup, the team invitation can all come after the user has felt why your product is worth the effort. Give, then ask.

✓ Step 4: Use microcopy to set expectations and reduce anxiety

Even a small welcome message or tooltip can set expectations and improve the experience. Tell users what is about to happen, how long it will take, and what they will get. “This takes about a minute and you will have your first project set up by the end” removes the uncertainty that causes people to bail. Nielsen Norman Group

✓ Step 5: Make the first win obvious and celebrate it

When the user reaches the moment of value, mark it. A subtle confirmation, a clear “you just did the thing” signal. A subtle animation after completing an action reassures users that it was successful. People need to feel the win, not just technically achieve it. The feeling is what makes them come back. Uxplaybook

UXCON26 - Inspire & Connect

The best UX professionals don’t just keep up with change. They help shape it.

UXCON26 is where the conversations defining the future of design happen. It’s where researchers, designers, product leaders, and innovators come together to exchange ideas, challenge assumptions, and leave with practical strategies they can apply immediately.

This year’s theme, Inspire & Connect, reflects what our industry needs most: meaningful collaboration in a world that’s changing faster than ever. And with Don Norman headlining, you’ll hear from the pioneer whose work laid the foundation for human-centered design—and whose thinking continues to influence how we build products in the age of AI.

Whether you’re looking to sharpen your skills, expand your network, or gain fresh perspectives from some of the brightest minds in UX, UXCON26 is where you need to be.

Don’t just watch the future of UX unfold. Be in the room helping shape it.

Grab Your Ticket

What Researchers Should Be Doing Here

Onboarding is one of the richest and most underused areas for research, and the findings tend to be unusually actionable.

🔵 Watch real first sessions, do not just read the funnel

Analytics tell you where people drop off. They do not tell you why. Watching a real person go through your onboarding for the first time, ideally someone who has never seen the product, reveals the exact moments of confusion that the funnel only hints at. The hesitation before a button. The re-reading of an instruction. The visible “wait, what do I do now” moment. That is where the gold is.

🔵 Find the gap between your intended value moment and the real one

The moment you think delivers value and the moment users actually feel it are often different. Research surfaces that gap. Sometimes the thing your team is most proud of is not what makes users light up. Sometimes a small, overlooked feature is the real hook. Only research tells you which.

🔵 Test the first session with genuinely new users, repeatedly

The single most common research mistake in onboarding is testing with people who already understand the product. Your team, your power users, your stakeholders all carry knowledge a new user does not have. Onboarding research is only valid with people experiencing the product cold. Recruit for true newness and protect that in your study design.

📦 Resource Corner

Onboarding UX Examples: What AI Is Changing (Userpilot)
A walkthrough of real onboarding flows from 30+ tools, with specific attention to how the 60-second standard is reshaping first experiences. Practical and example-heavy.

17 Best Onboarding Flow Examples (Whatfix)
A catalogue of real onboarding flows broken down by what works and why. The best single reference for seeing patterns across products before designing your own.

The Elements of User Onboarding by Samuel Hulick
The foundational resource on onboarding strategy. Older but still the clearest articulation of why value-first onboarding beats feature-first. The teardown approach is worth studying.

Adaptive Onboarding in 2026
Specific breakdown of how personalized and adaptive onboarding works in practice, with context on serving different user types within a single flow.

Hooked by Nir Eyal
On how products build habits in the critical early period. Use it to understand the psychology, and pair it with an ethical lens, since the same principles can be used well or manipulatively.

💭 Final Thought

You spend months building a product. Users decide whether it is worth their time in about a minute. That asymmetry feels unfair, but it is the reality every product faces, and the only response is to take that minute as seriously as it deserves.

The shift to the 60-second standard is not really about speed for its own sake. It is about respect. Users are telling you, through their behavior, that their time and attention are valuable and that the burden is on you to prove your product earns them quickly. Onboarding done well is an act of respect for that. It says: we know your time matters, here is something useful, fast.

Get the user to one real win before they have a chance to doubt you. Everything else, the features, the depth, the mastery, has time to unfold later. But only if you win the first minute.

Open your own onboarding. Time how long it takes to reach the first moment of real value.

Then start cutting.

--- The UXU Team

This is not a technical failure but a design one, and it has been building for years.

Researchers studying public trust in AI describe a “trust paradox” in which strong confidence in AI’s raw capabilities coexists with profound skepticism about its intentions and ethical grounding. Users are willing to believe the system is competent. They are far less convinced it is on their side.

• 20% of executives trust AI systems to make the right decisions (Deloitte, 2024)

• 88% of product leaders say trust frameworks will be a core differentiator by 2026 (McKinsey)

• 70% of detected AI bias exploits occur in regional, non-English languages

What Went Wrong with HCD

Human-centered design was supposed to prevent this drift. The philosophy — designing technology around human needs, cognition, and limits — was a corrective to systems built for efficiency at the expense of the people using them. For decades it worked. Then something shifted.

“Somewhere along the way, HCD shifted from being a philosophy to becoming a process.”
— Vaibhav Kulkarni, Medium, November 2025

When HCD is reduced to a checklist i.e. conduct user interviews, build personas, run a usability test etc, it loses the moral weight that made it powerful.

Research from the Journal of Engineering Design confirms that although HCAI is a significant topic in academia, industry practices lag considerably. Design teams that follow HCD rituals without embedding its values find themselves shipping systems that are technically impressive and humanly alienating.

The Skepticism Is Legitimate

It is tempting to frame AI skepticism as a communication problem — “if only we explained the technology better, users would trust it more.” But the skepticism, in many cases, is the appropriate response.

AI systems have caused real harm when poorly designed, developed, or deployed. Research has documented AI limitations including bias, lack of explainability, the absence of causal models, and serious ethical failures. The AI Incident Database and the AIAAIC database have recorded thousands of AI-related accidents.

The goal for UX professionals is not to dissolve skepticism but to calibrate it. Designing for what researchers call “calibrated trust”, a balanced relationship in which users appropriately rely on AI, understand its limits, and maintain a healthy degree of critical engagement.

When AI “hallucinates,” it is more than a system error. It is a collapse of trust. As Smashing Magazine noted in its September 2025 guide on the psychology of trust in AI, trust has become the invisible user interface. Users who are deceived once, even unintentionally, often disengage entirely. The 2026 UX landscape is littered with tools that technically work and practically go unused.

The Designer’s New Brief

If the period from 2023 to 2025 was about proving AI could work, 2026 is about proving it can be trusted. That shift repositions UX from decorator to architect. The central question is no longer “Can AI work?” but “Can AI be trusted?” — and that question lands squarely in the hands of experience designers.

“The designer’s new role is that of a behavior architect, balancing automation with human agency, making autonomy transparent, and ensuring that every interaction reinforces confidence rather than erodes it.”
— Aubergine Solutions, Designing for AI Agents, 2025

Three principles are emerging as the foundation for this work:

1. Transparency by design. AI systems must show their work. Whether it is a loan decision, a diagnosis, or a content recommendation, users need to see why the system reached a conclusion. A result without justification breeds the exact skepticism teams are trying to overcome.

2. Meaningful human control. Researchers define HCAI systems as those designed to augment human capabilities while ensuring meaningful oversight throughout the AI lifecycle — not systems that quietly accumulate authority. The degree of human control must be deliberate, visible, and recoverable.

3. Inclusive from the start. Inclusive design ensures AI works for everyone, not just the demographics represented in development teams. With nearly 70% of detected bias exploits occurring in non-English languages, designing for global diversity is not optional but a prerequisite for trust.

Where Human Designers Remain Irreplaceable

A recurring concern in design communities is that AI will displace the professionals working to make it more humane.

The evidence points the other direction. What is shifting is the nature of the work, and for those willing to adapt, the shift is toward greater strategic importance, not obsolescence.

AI provides user data, heatmaps, and engagement metrics, but humans interpret this data to create interfaces that are intuitive and emotionally resonant. Automation handles variation testing and content optimization, freeing designers to focus on storytelling, user empathy, and ethical framing. The firms that are winning in this landscape are not those who automated their design process — they are those who used AI to go faster while humans decided where to go.

UXCON26 — Inspire & Connect

Everything this issue has covered, trust, transparency, the crisis of confidence between humans and AI systems, will be at the center of the conversation at UXCON26.

Our theme Inspire & Connect, carries more weight than it might seem. The act of connecting — designer to designer, researcher to practitioner, idea to community — is itself a form of resistance against the drift this issue describes. Human-centered design does not happen in isolation. It never did.

This year’s headliner Don Norman, the person who gave our profession much of its foundational language, has spent decades arguing that technology must serve human needs, not the other way around. His presence at UXCON26 is not just a marquee booking. It is a statement about what this moment calls for: a return to first principles, delivered by the person who articulated many of them.

If you believe UX professionals have a responsibility to close the gap between AI capability and human trust, UXCON26 is where that conversation continues, in person, with the people doing the work.

Grab Your Ticket

Looking Ahead

For us UX professionals, this is the mandate. Human-centered design in the era of AI skepticism is not about defending users from technology. It is about building systems where trust is earned interaction by interaction, through transparency, through control, through genuine inclusion, until skepticism is not a barrier to adoption but a healthy, calibrated feature of how people engage with AI at all.

That is not a technical problem. It never was.

Resource Corner

1. How UX design can help build trust in AI systems
   Aubergine Solutions, 2025

2. The design psychology of trust in AI: crafting experiences users believe in
   UXmatters, November 2025

3. Trust is the new benchmark for AI, and UX owns the outcome
   CMSWire, February 2026

4. UX and AI in 2026: from experimentation to trust
   CleverIT Group, March 2026

5. Human-centred design in the age of automation: reclaiming the human in the loop
   Vaibhav Kulkarni, Medium, November 2025

6. Designing for AI agents: a human-centered approach for 2025
   Aubergine Solutions, September 2025

7. Predictions for AI in 2025: collaborative agents, AI skepticism, and new risks
   Stanford HAI, December 2024

8. The psychology of trust in AI: a guide to measuring and designing for user confidence
   Smashing Magazine, September 2025

9. Human-centered AI: advancing ethical, transparent, and context-aware systems
   ScienceDirect, Technology in Society, March 2026

__ The UXU Team

I’ve been thinking about this a lot lately.

Not because AI is new or because every company seems to be talking about it. Mostly because I’ve been noticing the same questions coming up again and again in conversations with professionals across different industries.

Some people are actively looking for their next role. Some are worried about layoffs. Others are doing well in their current position but can’t shake the feeling that the ground is shifting beneath them.

The common thread is uncertainty.

The reality is…….

People aren’t necessarily asking how to become AI experts. They’re trying to understand something much more practical:

• How is work changing?

• Which skills are becoming more valuable?

• What should I be paying attention to?

• If I had to compete in today’s job market, would I be ready?

I've heard these questions from UX researchers and designers, marketers, operations professionals, government employees, product teams, customer experience leaders, administrators and many more. Different industries. Different roles. Similar concerns.

These aren’t easy questions to answer. The amount of information out there can be overwhelming, and much of it feels disconnected from the realities of everyday work.

That’s one of the reasons we’re hosting Upskill AI: Repositioning for the New Economy.

This isn’t a workshop about chasing the latest AI trend. It’s a chance to step back, make sense of what’s happening, explore practical ways AI can support your work, and think more intentionally about where you want to go next.

This workshop may be a good fit for you if:

• You’ve been wondering whether you’re focusing on the right skills for the future.

• You’ve thought of experimenting with AI tools but aren’t sure where to start.

• You’re considering a career move and want to understand how the market is evolving.

• You’re feeling overwhelmed by the amount of AI advice online and want practical guidance instead.

• You want to learn alongside other professionals who are asking similar questions.

My hope is that you’ll leave with something many of us are looking for right now: a little more clarity and a little more confidence about where to focus next.

At the end of the day, most of us don’t need more noise. We need a better understanding of what matters and where to focus our energy.

If this resonates with you, I’d love for you to join us.

Reserve your spot →

__ Yao

The UX field is no longer in freefall, but it's not business as usual either. Over the last three months a clearer picture has emerged:

AI is reshaping the craft, multimodal interaction is becoming mainstream, ethical design is shifting from best practice to legal requirement, and the job market is stabilizing with a sharper split between those who can demonstrate impact and those who can't.

The designers who thrive will go deeper, not just faster. Here's everything you need to know — and do — right now.

What’s Actually Changing in UX Right Now

• 73% of designers say AI as a collaborator will have the most impact in 2026

• 93% are already using generative AI tools like ChatGPT, Claude & Midjourney in their work.

• 54% report clients want AI features without clear use cases

Source: Lyssna survey of 100 UX/UI/product designers, Dec 2025

Trend 01: Agentic AI is the new frontier for UX design

AI that works on behalf of users; booking appointments, managing tasks, completing workflows, is shifting UX from reactive to proactive. 60% of designers believe AI agents will have a major impact in 2026.

The design challenge is no longer just “how does a user interact with a screen” but “how do users trust and oversee systems acting for them.”

This is creating entirely new interaction paradigms around delegation, oversight, and failure recovery. Designers who can model these scenarios will be first in line for the most interesting roles in the market

Trend 02: Generative UI: interfaces rebuilt in real time

Generative UI uses AI to reconstruct layouts on the fly based on user intent. A beginner sees simplified tools; an expert sees advanced features automatically surfaced. Content gets condensed or expanded based on context.

The UX implication: designers must now think in systems and intent models, not fixed flows. Adaptive layouts, context-aware navigation, and “situational UX” are replacing static screen design.

Trend 03: AI as copilot, not autopilot — trust is the core problem

The industry is course-correcting from AI-as-oracle to AI-as-thoughtful-collaborator. Leading products are designing AI that is present, optional, and asks before it acts. According to Nielsen Norman Group’s State of UX 2026 report, trust is becoming a central design problem, people who’ve been burned by AI features are slower to adopt new ones.

Trend 04: Accessibility as default, powered by AI

53% of designers expect AI-powered accessibility tools to have a major impact this year, the highest ever. The framing is shifting from accessibility as a compliance checklist to accessibility as a design quality signal. AI is enabling dynamic font scaling, color adaptation, and cognitive load reduction in real time.

Trend 05: Visual craft is back — but with purpose

After years of safe, minimal interfaces, 2026 is seeing a return to intentional visual design. Motion that explains, typography that breathes, and interfaces with a clear personality are re-emerging — not as decoration but as trust signals. Behance’s 2026 design trends report notes that designers who combine AI workflows with strong visual craft will lead, while purely functional interfaces risk feeling indistinct as component libraries commoditize the baseline.

How to Position Yourself in a Stabilizing Market

“The UX job market isn’t disappearing — it’s evolving and maturing. Roles are more specialized and expectations are shifting.”

— UX Design Institute, March 2026

Nielsen Norman Group’s State of UX 2026 report describes the field as finally stabilizing after years of volatility — but with a catch: senior and generalist roles are recovering faster than entry-level positions, which remain scarce (The supply-to-demand ratio currently sits at 2.5 designers for every open role.). The competitive advantage has shifted from “I know UX tools” to “I can demonstrate business impact.” Here’s how to move.

What the market is actually paying

The salary gap between mid and senior levels has widened, and it hinges less on years of experience than on whether you can tie your work to measurable outcomes. A portfolio that documents process, decisions, and results carries more weight in 2026 than any certification alone.

1. Pick a vertical and own it

   Pick one emerging technology — agentic AI, conversational UI, AI accessibility — and become the go-to UX expert for that space.

2. Learn to speak in metrics

   Build fluency in conversion, retention, task success rates, and NPS. A design decision without a business case is increasingly hard to justify.

3. Double down on research

   As AI generates more interfaces faster, the premium on genuine user understanding grows. Research skills, especially qualitative, are increasingly rare and valued. Your data informs not just designs but AI training sets too.

4. Add AI fluency to your toolkit

   54% of US workers say AI skills are critical for career stability, yet only 4% are pursuing AI education.

   The gap is your opportunity. Prompt engineering, AI workflow design, and LLM UX patterns are skills few designers have — yet.

Trying to figure out what AI means for your career?

You’re not alone.

Many professionals are asking the same questions: What skills should I be learning? What work is becoming more valuable? What can AI actually help me do? How do I stay competitive without becoming an engineer?

That’s exactly what we’ll explore in Upskill AI: Repositioning for the New Economy, a 4-hour hands-on workshop designed to help you make sense of AI, build practical skills, and leave with a clearer sense of your next move.

📅 July 23, 2026 | 📍 Silver Spring, MD

Reserve Your Spot

Resource Corner

1. State of UX 2026: Design Deeper to Differentiate

   Nielsen Norman Group · Jan 16, 2026 · Kate Moran, Raluca Budiu, Sarah Gibbons

2. UX Design Trends 2026 (Survey of 100 designers)

   Lyssna · Dec 23, 2025

3. The UX Job Market in 2026: The Most In-Demand Skills & Roles

   UX Design Institute · Mar 20, 2026 · Emily Stevens

4. What’s Next: 7 UI Design Trends of 2026

   Tubik Studio Blog · Apr 6, 2026

5. AI & UX Design: Navigating the Market Realities in 2026

   UX Playbook · Dec 31, 2025

6. Design Trends 2026

   Behance · 2026

7. The AI Talent Race: Top AI Jobs to Watch in 2026

   Onward Search · Jan 2026

8. Why Learn AI According to Job Recruiters

   edX · Feb 9, 2026 · Janice Mejías Avilés

Your 30-day positioning checklist

1. Audit your portfolio — does it show process, decisions, and measurable outcomes, or just deliverables?

2. Identify one AI-adjacent vertical (agentic UX, conversational design, AI accessibility) and start a personal project or case study in it

3. Complete one AI-focused course — the UX Design Institute’s AI Fundamentals for UX is a solid starting point or better yet, register for our AI Worskhop

4. Run a Figma AI or Flowstep session to prototype something in under an hour — log what the AI got wrong and right

5. Benchmark your current or target salary using Glassdoor, Levels.fyi, and PayScope before your next negotiation

6. Attend a local UX event or community session and upskill your AI skills — our upcoming workshop is a great place to start

AI Upskilling Worskhop

__ The UXU Team

Share

Someone brings you a problem, a brief, a deadline. You research, you wireframe, you test, you ship. You do it well. You do it consistently. And then one day you look up and realise the product decisions are happening somewhere you are not invited, the AI tools are doing the first three rounds of ideation before you open a file, and nobody is quite sure what your role is supposed to be anymore.

Not because you did anything wrong. Because you were very, very good at the version of this job that no longer needs you to do it alone.

In This Issue:

• The executional trap and how good practitioners fall into it

• What is actually being automated and what is not

• The new shape of UX influence

• Why “a seat at the table” is the wrong goal

• How to reposition yourself before someone repositions you

• Resource Corner

Happy Juneteenth from UXU. Here’s a gift.

Freedom means something different to everyone who carries it. But at its core it has always been about the right to take up space, to be seen, to bring your full self into the room and have it matter.

That is exactly what UXCON26 is built around.

This weekend, in honor of Juneteenth, we are opening early bird pricing on UXCON26 tickets from Friday June 19 through Sunday June 21 only. It is our way of saying thank you to a community that shows up, asks hard questions, and refuses to let the work be less than it should be.

October 8 is the day the UX community comes together. Don Norman, the person who gave this field its name, headlines a lineup that includes practitioners from Netflix, The New York Times, Target, UserTesting, and Skylight. Three keynotes. Two panels. Workshops. One room full of people who still believe great design changes lives.

The offer closes Sunday at midnight.

Claim your discount

The Executional Trap

Here is how it happens, and it happens to the best people.

You join a team. You are skilled, you are reliable, you learn the product fast. You become the person who delivers. Stakeholders learn they can hand you a problem and you will come back with something good. This feels like success, because it is success, at first.

But over time, a pattern sets in:

• You are handed problems. You do not define them.

• You are brought in after the strategy conversations.

• You are handed the brief after the decisions.

• You are asked for solutions to problems you were never consulted about framing.

Slowly, without anyone intending it, your role becomes execution. Smart, high-quality execution. But execution nonetheless.

NN/g’s State of UX 2026 put it plainly: available roles are increasingly demanding breadth and judgment, not just artifacts. The practitioners who are thriving are not the ones who do UX best in the traditional sense. They are the ones who have moved upstream, into the problem definition, the strategic framing, the decisions about what gets built and why.

What Is Actually Being Automated

Let us be specific, because vague anxiety is not useful.

What AI tools are genuinely absorbing right now:

• Early ideation

• Pattern-based wireframing

• Usability heuristic checks

• Basic research synthesis

• Copy generation and asset production

• First-draft flows

Work that used to take days now takes hours. Work that used to take hours now takes minutes. This is real, it is accelerating, and pretending otherwise is not a strategy.

What AI tools cannot do:

• Sit in a room with a frustrated sales team and figure out that the product problem is actually a positioning problem

• Notice that the research finding everyone is ignoring is the most important one in the deck

• Build the trust with an engineering lead that makes them pick up the phone before a bad decision gets locked in

• Know which stakeholder needs to hear something a certain way, or not yet, or from someone else entirely

NN/g’s research on the return of the UX generalist is clear on this: the skills that cannot be replaced are the strategic-oriented ones. Adaptability, judgment, the ability to synthesise across disciplines. Those compound. The deliverables do not.

The practitioners who are scared are the ones whose value lived primarily in the craft of production. The practitioners who are not scared are the ones who were always doing something harder to name: the judgment calls, the organisational navigation, the translation between user reality and business decision.

If you have been doing that work, you have something the tools do not. If you have not, this is the moment to start.

The New Shape of UX Influence

For a long time, UX influence looked like great artifacts. The beautiful deck. The airtight research report. The prototype that made the room go quiet.

That still matters. But it is table stakes now, and table stakes do not get you influence anymore.

The new shape of UX influence is harder to put in a portfolio. It looks like this:

Being the person who reframes the brief before work begins. IDEO has built an entire methodology around this idea, that the quality of your question determines the quality of your solution. Most teams skip straight to answering. The practitioner who slows that down and reshapes the question is doing the highest-value work in the room.

Being the person who connects the user insight to the business metric. Not “users are frustrated” but “this friction point is the primary driver of the drop-off that is costing us this number.” Speaking the language of the people who make budget decisions is not selling out. It is getting your work taken seriously.

Being the person who builds relationships across the organisation. Not just within the design function. One real relationship in engineering, finance, or operations, someone who trusts your read and will tell you what is actually being discussed, is worth more than a hundred LinkedIn connections.

Being the person who can say, calmly and with evidence, that the team is solving the wrong problem. And be believed.

None of this replaces craft. All of it extends it into territory that is genuinely hard to automate.

Why “A Seat at the Table” Is the Wrong Goal

UX practitioners have been told for a decade that the goal is a seat at the table. Get into the strategy meetings. Be present when decisions get made.

The problem with this framing is that it positions you as a supplicant. You are asking for access to someone else’s conversation. And access granted can be access revoked.

The practitioners who have real influence do not have a seat at the table. They have shaped what the table is discussing. There is a difference, and it is not subtle.

Positional authority gets you into the room, but it does not make people trust your judgment. Trust in your judgment comes from a track record of being right about things that mattered, communicated in ways people could act on. That shift does not happen through org chart maneuvering. It happens through consistent, visible, well-communicated judgment over time.

How to Reposition Yourself Before Someone Does It for You

This is not a dramatic career pivot. It is a series of small, consistent moves in a different direction.

Move upstream on every project you can. Before you open a design tool, ask: what is the problem we are actually solving, for whom, and how do we know? Make those questions your first deliverable, not your opening ritual.

Learn the number your stakeholders care about. Not vaguely, specifically. What is the metric that determines whether your product area is considered successful this quarter? Make that number your number. Track it. Reference it. Connect your design decisions to it explicitly.

Start communicating decisions, not just designs. When you share work, lead with what you decided and why, not what you made. The artifact is evidence of the decision. The decision is what gets remembered.

Build one real relationship outside design. Not a networking contact. A person in engineering, finance, product, or operations who trusts your read on things and will tell you what is actually being discussed. Organisations run on informal information. If you only have it from inside your function, you are seeing a fraction of the picture.

Use AI aggressively for the execution layer. Not because the craft does not matter, but because time you free up from production is time you can redirect toward the strategic and relational work that compounds. Practitioners who are using the tools well are not being replaced. They are creating capacity that slower-moving peers do not have.

📦 Resource Corner

State of UX in 2026 by Nielsen Norman Group — The clearest annual read on where the field actually is right now. The 2026 edition is direct about what is changing and what practitioners need to prioritise. Worth bookmarking and returning to quarterly.

The Return of the UX Generalist by NN/g — The research case for why broad skills, adaptability, and strategic thinking are becoming more valuable than deep specialisation. Useful ammunition for internal conversations about how your role should evolve.

Articulating Design Decisions by Tom Greever — The most practical guide to making your reasoning visible to stakeholders who only see the surface. Directly addresses the gap between doing good work and getting credit for it. The 2nd edition is available via O’Reilly.

Org Design for Design Orgs by Peter Merholz and Kristin Skinner — The clearest framework for understanding where design influence comes from structurally, and what organisational shapes produce it or destroy it. Essential context for anyone navigating where their team sits and how to grow its footprint.

The Making of a Manager by Julie Zhuo — Written by a former VP of Product Design at Facebook. Every chapter is relevant whether you manage people or not. One of the best books written on how influence actually works inside organisations.

What Is Design Thinking by IDEO U — A short, sharp read on why reframing the problem is the most important design skill. Useful for anyone who wants language and a framework for moving upstream on their projects.

Mind the Product: UX content library — The language and frameworks your product partners are using. Understanding them makes you easier to work with and much harder to sideline.

💭 Final Thought

The field is not dying. It is shedding a skin.

The version of UX work that was primarily about production, about being the person who could translate a brief into a finished artifact faster and better than anyone else, that version is under genuine pressure. Not gone, but no longer sufficient on its own.

What is not under pressure is judgment. Context. The ability to sit with ambiguous, high-stakes, politically complicated problems and come back with a frame that makes the path forward clearer. That has always been the harder and more valuable half of this work. It just did not always need to be the visible half.

It does now.

The practitioners who will look back on this period as the moment their careers accelerated are the ones who decided, consciously, to move in the direction of the hard work rather than the comfortable work. Who started treating organisational navigation as a design problem. Who used the tools to buy back time and spent that time on the things that compound.

You already know how to make complicated things simple. You have always known how to understand what people actually need versus what they say they want.

Apply that to your own career. Figure out what the organisation actually needs from you right now. And go be that, before someone decides they can manage without you.

You cannot automate your way to influence. But you can design for it.

The UXU Team

→ Why AI made job applications faster and somehow less effective
→ The July 23 workshop built to fix that, in real time
→ Who’s leading the session and what you’ll leave with

The Resume Problem Nobody’s Talking About

You’ve asked AI to fix your resume. It gave you back something that reads like everyone else’s resume.

You’ve rewritten your LinkedIn headline more than once this year. You’ve pasted your experience into a prompt and gotten output that’s technically correct and somehow says nothing about you.

That’s not a YOU problem. It’s an everyone problem right now. AI got fast before most people figured out how to use it for something that actually matters: positioning yourself for what the job market looks like today, not three years ago.

This is exactly what our upcoming July workshop is all about.

🟢 EVENT SPOTLIGHT

Upskill AI: Repositioning For The New Economy

📅 July 23, 2026 · 12:00–4:00 PM
📍 Silver Spring Civic Building, Veterans Plaza, Silver Spring, MD

4 hours. Your real resume, your real pitch, your real positioning, worked on with AI tools and 3 founders who’ve actually used them to hire, build, and grow.

No templates to fill in later. No slides to forget by the weekend. You leave with something finished that you can show to others, and a clear next move of what to do with your newly acquired skill.

Book A Remaining Slot

Who’s In The Room

Jake DiBattista · Founder & CEO, Buddy
Evan Katz · Founder & CEO
Yao Adantor · Founder & CEO, UXU

RSVP HERE

Three people who’ve hired, been hired, pivoted, and rebuilt. They’re not here to talk about AI in the abstract. They’re here to use it with you, on the thing that matters most right now: how you show up to the market.

What you’ll walk away with:
✅ A finished AI-powered tool you built during the session
✅ Clarity on where your skills fit right now
✅ Language that lands in interviews and networking
✅ One specific next step, chosen before you leave

Final Thought

This isn’t a lecture. It’s a turning point, and spots are running out.

Don't Be Left Out!

The UXU Team

That era is ending. Regulatory pressure from the EU’s European Accessibility Act, a $8 trillion global disability market, and a growing body of research proving that inclusive products simply perform better have converged into a single, undeniable signal: designing for everyone is no longer a values statement. It is a competitive strategy and in today’s issue, we’ll discuss where we are, where we’re going, and what you need to do right now.

In this edition we’ll cover:

• The State of Play

• The Regulatory Landscape

• 7 Shifts in Inclusive Design

• The Practitioner Roadmap

• Resource Corner

The State of Play

• 1.3B people globally live with some form of disability — 15% of the world population

• $8T global market potential of customers with disabilities and their networks (Return on Disability Group)

• 69% of users with access needs click away from websites they find difficult to use — taking spend with them

Sources: WHO, Return on Disability Group 2020, Click-Away Pound Survey

Over 70 million adults in the United States, more than 1 in 4, live with a disability. People with disabilities in the US alone control $490 billion in collective disposable income. And yet the majority of digital products still fail basic accessibility audits. Automated tools, when teams bother to run them at all, catch only 30–40% of real accessibility barriers. The rest require human testing, which most organizations skip entirely.

“Most companies overlook this substantial consumer segment despite these impressive figures. This oversight isn’t just an ethical mistake — it’s a missed chance for growth.”

— Bricx Labs Inclusive Design Analysis, 2026

• Companies that lead on disability inclusion realize 1.6x more revenue, 2.6x more net income, and 2x more economic profit than their peers, per a landmark Accenture study that has now been replicated across industries.

• Companies making products available to all see a 28% increase in revenue, because accessible designs reach four times as many consumers.

• The World Economic Forum found disability-inclusive businesses report 30% higher profit margins.

These are structural advantages available to any organization willing to prioritize inclusion from the start rather than retrofit it at the end.

AI can now do in seconds what used to take you a week. So where does that leave you?

Every week there’s a new tool that drafts wireframes, writes copy, generates user flows, the things that used to be your job security. And the question quietly sitting underneath all of it is: if AI can produce the deliverable, what exactly am I bringing to the table?

The answer isn’t panic. It’s positioning. UXCON26 brings together practitioners from Netflix, The New York Times, Target, and more who are already working through this exact shift, alongside Don Norman, the person who defined what user experience even means in the first place.

October 8. One day. The conversations that actually answer the question.

Secure your spot

back to where we stopped….

The Regulatory Landscape

Compliance Is No Longer Optional.

The European Accessibility Act (EAA), now in force since June 28, 2025, mandates accessibility for a broad range of products and digital services across all 27 EU member states — including e-commerce, banking, transport, and telecommunications.

This regulatory shift has a direct career implication: fluency in WCAG standards, accessibility auditing, and inclusive design documentation is rapidly moving from a niche specialization to a baseline expectation. Teams that have embedded accessibility into their design systems and development pipelines before a compliance audit arrives are in a fundamentally different position than those scrambling to retrofit.

Seven Shifts Defining the Next Generation of Inclusive Design

SHIFT 01: From compliance to genuine usability - the “second-class experience” problem

Designers and researchers are increasingly recognizing that meeting legal standards does not automatically produce a usable or welcoming experience. When accessibility accommodations feel hidden, awkward, or clearly bolted on, users notice - and they remember.

SHIFT 02: People with disabilities at the table - not as an afterthought, but from day one

More organizations are involving people with disabilities early in the design process — in discovery research, usability testing, and design critique - rather than as a final accessibility review checkbox. When inclusive design is informed by real use cases and real users from the start, fewer costly fixes are needed later.

SHIFT 03: AI as an accessibility enabler - but with firm limits

In practice, AI is being used to identify accessibility issues at scale, summarize remediation priorities, restructure documents, and detect patterns in user research data. However, 89.3% of practitioners still validate AI-generated accessibility test results with human testers - a recognition that AI catches patterns, not context.

The emerging view: AI lowers the barrier for teams to produce more accessible products at speed, but it does not replace the judgment required to evaluate complex, real-world edge cases. Human expertise remains the floor, not the ceiling.

SHIFT 04: Multimodal interaction as an accessibility requirement, not a feature

As voice, gesture, camera input, and haptics become standard interaction modes, the overlap between multimodal UX and accessibility becomes undeniable. For products serving users in high-distraction environments - healthcare workers, drivers, field technicians - and for users with motor, vision, or cognitive differences, multimodal design has shifted from an enhancement to a usability requirement.

Designers who prototype across input modes and understand how to create seamless fallbacks between them are building skills directly applicable to accessibility-first product work.

SHIFT 05: Ethical design systems - bias reduction and AI boundaries built in

Design systems are evolving to include ethical guidelines: how to reduce bias in AI-powered features, define boundaries for data use, maintain fairness across diverse populations, and document accessibility requirements at the component level. This trend reflects a maturation in how teams think about their design systems — not as a library of UI components, but as a codified set of organizational values made operational.

SHIFT 06: User-defined preferences as the new design baseline

Reduced motion, high contrast, dark mode, text scaling, and captions are shifting from optional settings to expected defaults. Products that honor what users have already told their operating system about how they want to interact signal respect, reduce cognitive load, and build trust.

SHIFT 07: Inclusive design beyond the screen - physical, spatial, and environmental

Digital accessibility is expanding into everything connected to technology - smart devices, kiosks, payment terminals, AR/VR environments, and packaged goods. These interfaces create new barriers when they rely on touch, reach, speed, or fine motor control.

Designs that tackle these barriers and create disability access improve experience for everyone, and designers who can think across physical and digital contexts will be increasingly valued.

Six Principles for Building an Inclusive Design Practice

Knowing the trends is only half the work. Here is how to operationalize inclusive design across your team, portfolio, and career - at any level of seniority.

Research with, not about

Include people with disabilities in every research phase - interviews, card sorts, usability tests, and critique sessions. Make it a standing practice, not a special study. Document participation rates in your case studies to signal your commitment.

Embed accessibility in your design system

Every component in your library should carry accessibility annotations - keyboard behavior, ARIA roles, contrast ratios, focus order. A design system without these is incomplete. Start with your most-used components and work outward.

Test beyond automated tools

Automated scanners catch 30–40% of issues. Build manual testing with screen readers (NVDA, VoiceOver, JAWS) and keyboard-only navigation into your QA cycle. Even one hour per sprint of manual accessibility testing dramatically improves real-world outcomes.

Learn the regulatory landscape

Understand WCAG 2.1/2.2 at the AA level and how it maps to the EAA, ADA Title III, and Section 508. Knowing which standards apply to your client’s product and why - makes you a more credible and valuable partner in product conversations.

Make the business case fluently

Know the numbers: $8T global disability market, 1.6x revenue advantage for inclusive leaders, 28% revenue increase from accessible design, 69% abandonment rate for inaccessible sites. You should be able to make the ROI case for inclusive design in two minutes, without slides.

Document your inclusive design process

Your portfolio needs to show inclusive design decisions explicitly - who was included in research, which accessibility standards were targeted, what tradeoffs were made and why. This level of process documentation distinguishes senior practitioners in hiring reviews

Emerging Role To Watch

Resource Corner

1. 7 Inclusive Design Trends to Watch in 2026
   Equal Accessibility LLC · Mar 17, 2026

2. State of Digital Quality in Accessibility 2026

   Applause · Apr 2026 (survey of software dev, QA, product & accessibility professionals)

3. Inclusive & Accessible UX Design Trends: How Regulations and User Needs Are Shaping Digital Products

   USAenlinea · May 2026

4. Why Accessibility Is Becoming a Bigger Design Priority in 2026

   Daily Business Group · Jun 2026

5. European Accessibility Act: Complete Compliance Guide 2026

   AllAccessible · updated Jun 2026

6. EAA and WCAG: A Guide to EU Accessibility Compliance

   Aquent · Oct 2025

7. 8 Proven Inclusive Design Examples from Top Brands (2026 Update)

   Bricx Labs · 2026

8. The Business Case for Inclusion: Why Disability Inclusion Matters Today

   Disability Belongs™ · Feb 2026

9. Industry Literature Review: Business Case for Disability Inclusion

   Disability:IN & Accenture (landmark study, 2023 update)

10. The Business Case for Digital Accessibility

    W3C Web Accessibility Initiative (WAI) · evergreen

11. Closing the Disability Inclusion Gap with Business Leadership

    World Economic Forum

12. Accessible XR in 2026: What Meta Horizon Worlds Teaches Us About Inclusive VR Design

    Equal Entry · Feb 25, 2026

💭 Final Thought

It is tempting to read all of this as a numbers story. The $8 trillion market. The 1.6x revenue advantage. The penalties. And those numbers matter, because they are what finally moved inclusive design from the bottom of the backlog to the center of the strategy.

But the numbers were never the reason. They are just the argument that finally worked.

Behind every statistic is a person who clicked away because a form would not work with a screen reader, or who assumed, again, that this product was not built with them in mind. The retrofit era is ending. The teams that build inclusion in from the first sketch will not just pass the audit. They will make products that work for more people, more of the time, which was the point before anyone attached a dollar figure to it.

Build it in. Not because the law says so, though it does. Because the people on the other side of the screen have been waiting long enough.

--- The UXU Team

If an AI generates the interface based on each user’s behavior, context, and needs in real time, what exactly did you design?

Not a hypothetical. This is already happening. Research shows AI-generated interfaces matched human expert-designed work 44% of the time, produced in seconds rather than days. Products are shipping adaptive interfaces that reorganize themselves based on how individual users actually behave. The screen a power user sees is different from the screen a first-time user sees, not because of A/B testing, but because the interface is generating itself dynamically. Medium

The role of UX in this environment is not gone. It is fundamentally different. And most of the field has not caught up to what that difference actually means in practice.

In This Issue:

• What AI-native design actually means

• How the job is changing in specific, concrete ways

• What practitioners need to own when the interface generates itself

• What this means for researchers specifically

• The skills that matter most in this shift

• Resource Corner

What AI-Native Design Actually Means

There is an important distinction that is getting lost in most conversations about AI and UX.

Adding AI features to a product is not the same as designing an AI-native product. A chatbot in the corner of a screen. A smart search bar. An AI-generated summary. These are features. They live inside an interface that was designed the traditional way.

An AI-native product is different. The interface itself is not static. In 2026, AI is embedded into the interaction layer itself. It predicts what a user needs before they articulate it and shortens task flows by surfacing relevant actions at the right moment. UX Design

If a user always checks “Orders” first in an app, the interface starts placing it higher in the navigation. The homepage highlights “Track Order” instead of showing random promotions. The system is not following a design spec. It is following behavioral logic that a practitioner set up, and then adapting from there on its own. Smashing Magazine

AI is no longer an experimental add-on. It is now a core design workflow, with tools generating production-quality UI built from a team’s actual component library. Slickplan

The screen you design is increasingly a starting point, not a final state.

How The Job Is Changing In Specific, Concrete Ways

🔵 From designing screens to designing constraints

Instead of handing off fixed screens, practitioners are crafting constraints, safety rails, and evaluation criteria that shape how model-driven interfaces operate. They are designing the rules that generate interfaces on the fly, adapting to what each user needs in that specific moment. Medium

What does that actually mean day to day? It means the Figma file is no longer the primary artifact. The logic document is. The decision tree that governs when the interface adapts, how far it adapts, what it can never do regardless of what the model predicts. That is the design work. And most practitioners have never been trained to do it.

🔵 From delivering specs to defining evaluation criteria

When an AI generates an interface, someone has to decide what good looks like. Not in a single review session. As an ongoing standard the model is held to. What constitutes a helpful adaptation versus a confusing one? What user behavior signals should trigger a change and which ones should be ignored? What is the failure state and how does the system recover from it?

These are design questions. They do not live in a prototype. They live in documentation, in test criteria, in the ongoing evaluation of whether what the system is generating is actually serving the person using it.

🔵 From solving for the average user to solving for the range

Traditional UX design produces a single interface that works reasonably well for most users. Adaptive design produces a range of interfaces that each work specifically for one user’s context and behavior pattern. A first-time user sees progressive onboarding. A power user sees a condensed task interface. A user who consistently ignores a feature sees a cleaned-up layout without it. UX Design

Designing for a range is harder than designing for an average. It requires understanding not just what most users need but what different users need in different moments, and building the logic that serves each of them without requiring a separate design for each.

Upskill AI: Repositioning For The New Economy July 23, 2026 · 12 to 4PM · Silver Spring Civic Building, MD

Four hours. Your real resume. Your real pitch. Real AI tools. A room full of UX practitioners who are done waiting for the market to come back to them and ready to meet it where it actually is.

Led by Jake DiBattista, Evan Katz, and Yao Adantor, three founders who have built, hired, and navigated this economy from the inside. They are not teaching theory. They are teaching what is actually working right now.

You will not leave with notes. You will leave with a finished output, sharper positioning, and one clear next step you identified before you walked out the door.

Spots are limited and this one will fill.

RSVP HERE!

What Practitioners Need To Own When The Interface Generates Itself

This is the part that gets underspecified in most conversations about adaptive design.

When an AI generates the interface, someone still needs to own the quality of what gets generated. That ownership does not disappear because the output is dynamic. It shifts.

→ The ethical guardrails Practitioners need to craft safety rails that shape how model-driven interfaces operate. An adaptive interface that serves user behavior patterns can also reinforce harmful ones. A system that learns a user spends more time in the app when they are anxious and adapts to maximize that time is technically working as designed. It is also a dark pattern at an algorithmic scale. Practitioners need to define explicitly what the system is not allowed to optimize for, not just what it should. Medium

→ The transparency layer Users interacting with an adaptive interface have a right to understand that it is adapting. In 2026, design is more about control and trust. Instead of debating how to use AI, the conversation is about how transparent and controllable it should be. Designing the moment where a user can see why their interface looks the way it does, and change it if they want to, is a distinct and important design problem that AI-native products are mostly not solving well yet. FullStack

→ The failure modes What happens when the model makes a wrong prediction? What does the interface look like when the personalization fails? Most adaptive systems are designed for the success case. The failure case, where the interface rearranges itself in a way that confuses the user or makes a critical function harder to find, needs to be designed for explicitly.

What This Means For Researchers Specifically

Research in AI-native products is a fundamentally different practice from research in static products. And most research teams are applying static-product methods to a dynamic-product context.

🔵 Usability testing a moving target

If the interface adapts based on user behavior, the interface one participant sees in a usability session may be different from the one another participant sees. The traditional usability testing protocol, where everyone experiences the same thing, does not map cleanly onto adaptive systems. Researchers need methods that can account for variability in what is being tested.

🔵 Research has to go upstream of the logic

In a static product, research informs design decisions made by practitioners. In an adaptive product, research needs to inform the rules the system uses to make decisions automatically. That is a different level of involvement. Researchers need to be present when the behavioral logic is being defined, not just when the interface is being tested. The question “what should trigger this adaptation” is a research question. It rarely gets treated as one.

🔵 Longitudinal research becomes essential

A single usability session shows you what the interface looks like on day one. It tells you nothing about how it evolves over time as the system learns from behavior. Understanding whether the adaptations the system is making are actually helpful, or whether they are creating new friction, requires research conducted over time with the same users. That is a bigger investment than most research teams are currently set up to make.

The Skills That Matter Most In This Shift

Not a comprehensive list. The specific things that matter for navigating this transition.

✓ Systems thinking over screen thinking

The ability to think about how a product behaves across many different users in many different contexts, rather than designing a single experience and assuming it generalizes. This is a different cognitive mode from traditional UX and it is one that practitioners who have worked on large-scale or data-heavy products tend to have more naturally.

✓ Writing clear logic and decision criteria

Practitioners are being evaluated on their ability to guide AI, correct it, and define the parameters it operates within. That requires being able to write down, clearly and specifically, what the system should do under which conditions. Not a design spec. A decision framework. If you cannot write the rule, the system cannot follow it. Nielsen Norman Group

✓ Evaluating AI output critically

Treating AI like a junior designer who is ambitious but needs direction produces better outcomes than either blind trust or blanket rejection. The skill is knowing when what the system generated is good enough, when it needs guidance, and when it has gone somewhere it should not. That judgment develops through regular, critical engagement with AI output, not occasional use. Slickplan

✓ Research methods that work on dynamic systems

For researchers, this is the most urgent skills gap. Behavioral analysis, longitudinal methods, and research that can account for interface variability are going to be essential for evaluating adaptive products. These are not skills most research training programs cover well yet.

📦 Resource Corner

UX Design Shifts You Cannot Ignore in 2026 (UX Collective) The most grounded practitioner-level breakdown of what is actually changing inside design teams right now. The section on designing constraints rather than screens is worth reading carefully.

UXPin Forge The tool most ahead of this shift. Generates designs using a team’s actual React components, producing output that is immediately usable rather than requiring hours of rework. Worth understanding how it works even if you do not use it daily.

Adaptive Personalization in UX Specific breakdown of how behavioral personalization is being implemented in products right now, with practical context on what UX teams need to provide for it to work well.

Designing AI Products: The Practitioner’s Guide (O’Reilly) One of the most complete resources available on what UX practice looks like when the product you are designing has AI at its core rather than as a feature layer.

Continuous Discovery Habits by Teresa Torres Increasingly relevant as research needs to be continuous rather than episodic in adaptive product environments. The framework for embedding ongoing discovery into product development maps directly onto the needs of AI-native product teams.

💭 Final Thought

The job title is the same. The job is not.

Designing screens for a static product and defining the rules and constraints for an adaptive one require genuinely different skills, different thinking modes, and different definitions of what done means. The practitioners navigating this well are not the ones who learned to use AI tools. They are the ones who changed how they think about what they are actually making.

You are not making a screen anymore. You are making a system that generates the right screen for the right person at the right moment. That is more interesting than what came before. It is also harder. It requires deeper understanding of user behavior, sharper logic skills, and a different relationship with research as a continuous practice rather than a project phase.

When you design with clarity, empathy, and strong judgment, trends become opportunities instead of threats. Index.dev

The field is not moving away from human-centered thinking. It is demanding more of it, applied earlier in the process, at a level of precision that static design never required.

That is the work now. Get upstream of it.

--- The UXU Team

And the market still feels like it is speaking a different language than the one you learned.

Maybe you are mid-career and suddenly fielding questions in interviews you were never trained to answer. Maybe your team got cut and you are doing the work of three people with the title of one. Maybe you are watching colleagues get replaced by tools that did not exist eighteen months ago and wondering quietly if your role is next. Maybe you are just tired of feeling like you are working harder than ever and moving slower than you should be.

You are not imagining it. The field changed. Fast. And not everyone got the memo at the same time.

What you need is not another online course. It is not a thread of tips. It is a room full of people who are living inside the same questions you are, and the voices who have actually figured some of it out.

That room exists. It is called UXCON26.

Secure your spot

Meet Jeremy Miller

Jeremy Miller has been in design since the early 2000s. He knows what this field looked like before it was called UX, and he knows what it takes to grow inside it when the rules keep changing.

Through his podcast Beyond UX Design, Jeremy has been making one argument consistently: the practitioners who last are not always the most technically skilled. They are the ones who know how to build relationships, navigate organizations, and make people believe in the work. That conviction is at the center of everything he does, including how he will hold the room on October 8.

He co-founded Edge Kase Design Co. in 2024 and has spent years mentoring practitioners at every stage of their careers. He is the right person to guide this day.

UXCON26 is not a day of back to back slides you close your laptop on and forget. It is the one day of the year where this community gets honest about what is actually happening in the field, what is working, what is not, and what comes next for the people who care enough to show up.

Join Jeremy Miller at UXCON26

The community is the point. Come be part of it.

The UXU Team

Companies largely kept using them anyway.

Then regulators started paying attention. And the conversation changed completely.

In 2026, UX decisions are under legal scrutiny, especially when they manipulate users into giving consent or make it harder to refuse. What was once a question of professional ethics is now a question of legal liability. And the settlements are large enough that nobody can pretend this is still just a design philosophy debate. Case Study Club

In This Issue:

• What actually changed legally and when

• The settlements that made executives pay attention

• The most common dark patterns still in production right now

• Where the line sits between persuasion and manipulation

• What this means for every UX practitioner

• How to audit what you have already built

• Resource Corner

What Actually Changed Legally And When

The shift did not happen overnight. It built across several years of regulatory action and then accelerated sharply.

As of February 2024, the Digital Services Act explicitly prohibits many dark patterns for large platforms operating in the EU, with fines up to 6% of global annual turnover. That is not a slap on the wrist. For a large platform, 6% of global turnover is an existential number. Uxplaybook

In the US, the FTC’s position hardened significantly. The FTC explicitly targets any user interface designed to manipulate users into decisions they would not otherwise make, reinforcing that compliance is not just about legal disclosures but about the overall user experience. The FTC now treats dark patterns as a form of deceptive or unfair trade practice under Section 5 of the FTC Act. IxDF

In the EU under GDPR, consent must be freely given and informed, so dark patterns that obscure opt-out options or pre-select consent can invalidate it entirely. In the US, California under CCPA and CPRA explicitly prohibits the use of dark patterns to interfere with privacy choices. Case Study Club

The regulatory direction is consistent across markets and it is not reversing. Every major economy is moving toward treating manipulative design as a legal issue rather than an ethical preference.

The UX landscape looks different than it did two years ago.

A practical day to reset how you work in UX

This is not a talk about AI. It is four hours of actual work, your resume, your positioning, your pitch, built inside the tools that are reshaping how hiring works right now. No theory. No slides to forget by Thursday. Just a room full of people who are serious about their next move, doing the work together, led by people who do this for a living.

You leave with something finished. A clearer read on where your skills belong in this economy. And one specific next step you chose before you walked out.

For anyone in this community navigating a transition, a layoff, or just a quiet feeling that the map has changed and nobody handed you a new one.

RSVP HERE!

back to where we stopped….

The Settlements That Made Executives Pay Attention

Arguments about ethics rarely move product roadmaps. These numbers did.

💰 Amazon: $2.5 billion

Amazon’s settlement included internal emails showing executives deliberately designed confusing cancellation processes. The “roach motel” pattern, easy to subscribe and nearly impossible to cancel, cost the company a settlement that made international headlines and resulted in mandatory redesigns across their subscription flows. Site Builder Report

💰 Epic Games: $245 million

Epic Games paid $245 million for dark patterns deterring cancellations. Fortnite’s interface was found to have deliberately confused children into making unintended purchases. The FTC described the design choices as intentional, not accidental. Site Builder Report

These are not edge cases or regulatory overreach against bad actors. These are major, recognizable companies whose UX teams built flows that crossed a line the law had drawn. The practitioners who built those flows were not trying to harm users. They were optimizing for conversion metrics someone higher up had prioritized. That distinction does not appear to matter much in a settlement.

The Most Common Dark Patterns Still In Production Right Now

It is 2026. Consumers are more privacy-aware, regulation is tighter, and conversations around ethical data practices are mainstream. And yet dark patterns are still everywhere. Lovable

Here are the ones most likely to still be sitting in products you work on or have worked on.

🔴 Roach Motel Easy to get in, deliberately difficult to get out. Subscription signup is three clicks. Cancellation requires navigating to account settings, finding a buried link, answering a retention survey, declining a downgrade offer, and then confirming twice. This is the pattern that cost Amazon $2.5 billion and it is still the default for a significant percentage of subscription products.

🔴 Confirmshaming Opt-out language designed to make the user feel bad about saying no. “No thanks, I don’t want to save money.” “I prefer to stay uninformed.” The copy is technically accurate. It is also manipulative by design. These practices exploit cognitive biases to manipulate users into taking actions they did not intend. UXpilot.ai

🔴 Hidden costs A price that looks competitive until checkout, where fees, taxes, and “service charges” inflate the total by 30% in the final step. The FTC’s rules now cover hidden fees and deceptive design that impairs user autonomy. What the industry called “price anchoring” regulators are increasingly calling deception. IxDF

🔴 Consent by default Pre-checked boxes for marketing emails, data sharing, and third-party partnerships. The user technically had the ability to opt out. The design made it easy to miss. Consent obtained through default settings or misleading prompts does not constitute valid consent under current regulatory standards. Case Study Club

🔴 Misdirection Visual hierarchy, color, and button sizing deliberately engineered to draw attention to the option the company wants and away from the option the user might prefer. The “Accept All” button is large, colorful, and prominent. “Manage preferences” is small, grey, and positioned where the eye does not naturally land.

🔴 Urgency and scarcity manipulation “Only 2 left!” when inventory is not actually limited. “Sale ends in 10:00” on a timer that resets every time the page loads. These patterns are among the most studied in behavioral economics and among the most legally scrutinized in current regulatory guidance.

Where The Line Sits Between Persuasion And Manipulation

This is the question every UX practitioner working on conversion-focused products is going to face more directly in the coming years.

The distinction regulators have drawn is cleaner than the industry has historically wanted to admit.

Persuasion provides genuine information that helps users make informed decisions aligned with their interests. Manipulation deliberately impairs decision-making through deception, pressure, or exploiting cognitive biases. Site Builder Report

Highlighting a genuine benefit is persuasion. Hiding a rejection option to prevent the user from seeing it is manipulation. Making a product genuinely easy to sign up for is persuasion. Making it deliberately hard to leave is manipulation.

The regulatory standard is this: does the interface subvert user autonomy? If the answer is yes, it is a dark pattern regardless of whether that was the intent. Intent is not the test. Effect is. Site Builder Report

This matters enormously for practitioners. A product manager who tells you “make the cancel button harder to find” is asking you to build something that may now carry legal liability. That is a different conversation than it was three years ago and practitioners need to be equipped to have it.

What This Means For Every UX Practitioner

This is not only a designer problem. It is a field-wide one.

Researchers who do not flag manipulative patterns in usability testing are contributing to their survival. Strategists who optimize purely for funnel metrics without considering whether the funnel respects user autonomy are building the brief that makes the dark pattern possible. Designers who implement what they are told without pushback are the last line of defense that sometimes does not hold.

Designers who can recognize and reject dark patterns, offering ethical alternatives that convert better, are among the most sought-after profiles in the market in 2026, especially in finance, e-commerce, and B2C services managing DSA compliance. Uxplaybook

The field shift here is significant. Ethical UX used to be a values argument that got overruled by business priorities. It is now a risk argument that gets taken to legal and compliance teams. The leverage practitioners have to push back on manipulative design requests has increased considerably because the stakes for the company have increased considerably.

Using that leverage requires being able to name the pattern, cite the relevant regulation, and propose an alternative that achieves the business goal without the legal exposure. That is a different skill set than designing a better interface and hoping someone listens.

How To Audit What You Have Already Built

Not a full compliance exercise. A starting point that surfaces the highest-risk areas.

✓ Map every exit flow in your product Cancellation, unsubscribe, data deletion, opt-out. How many clicks does each take? How many of those steps exist to help the user versus to change their mind? Compare the exit flow length to the signup flow length. If the exit is meaningfully longer and more difficult, that asymmetry is worth examining closely.

✓ Review every consent interface Pre-checked boxes. Default-on settings. Consent bundled with terms of service. Cookie banners where “Accept All” is visually prominent and “Reject All” requires a second screen. Each of these is flagged specifically in current regulatory guidance as a potential violation.

✓ Read your own urgency copy critically Is the scarcity real? Is the deadline real? Does the timer reset? Fabricated urgency that creates false pressure on a user decision is explicitly named in FTC guidance as a deceptive practice.

✓ Run a usability session specifically looking for confusion Ask participants to opt out of marketing. Ask them to find the cancellation option. Watch where they hesitate, where they click the wrong thing, where they give up. Confusion that benefits the company is not neutral UX. It is a risk.

✓ Document what you find and share it Businesses are now expected to document consent practices and maintain records for several years. Practitioners who surface dark patterns, document the finding, and escalate it are building an organizational record that matters both ethically and legally. Practitioners who notice something and stay quiet are in a more exposed position than they might realize. IxDF

📦 Resource Corner

Deceptive Design Harry Brignull’s original dark patterns reference site, updated regularly. The Hall of Shame is one of the most useful resources for recognizing patterns in the wild. Required reading before any conversion flow audit.

FTC Dark Patterns Report: Bringing Dark Patterns to Light The actual FTC guidance document. Specific, readable, and essential if you are working on any US-facing product with subscription flows, consent mechanisms, or checkout.

Dark Pattern Avoidance Checklist 2026 Practical audit checklist for consent flows specifically. Covers GDPR, CPRA, and DSA requirements in plain language. Download it before your next audit.

Ketch: Dark Patterns Are Now Illegal Clear breakdown of where each major regulation sits on specific pattern types. Useful for building the business case when pushing back on a dark pattern request internally.

Laws of UX The broader ethical and psychological framework behind good UX decision-making. Understanding why dark patterns work psychologically makes it easier to design alternatives that achieve legitimate business goals without manipulation.

💭 Final Thought

The practitioners who built Amazon’s cancellation flow were not bad people. They were probably optimizing for the metrics they were given, shipping what stakeholders approved, and moving on to the next sprint. That is how most dark patterns get built. Not through malice. Through incentive structures that reward conversion and do not penalize manipulation.

What changed is that the external consequences are now large enough to change the internal incentive structures. A $2.5 billion settlement has a way of getting legal, compliance, and the executive team interested in what the UX team is building and why.

That attention is uncomfortable. It is also an opportunity. Practitioners who understand the regulatory landscape, can name specific patterns and their legal implications, and can propose compliant alternatives that still achieve business goals are bringing something genuinely valuable to the table right now.

The ethics of user-centered design were always supposed to protect users from exactly this. The law just caught up and gave the argument some teeth.

— The UXU Team

Cast your mind back to 2022……..

The conversation was strong, intense, and mostly theoretical. ChatGPT had just launched. Designers and researchers were arguing on Twitter and Linkedln about whether AI would ever be capable enough to touch real UX work. The general consensus was: not anytime soon. Maybe in a decade. The craft was too human, too nuanced, too contextual for a machine to replicate.

That consensus aged badly. Very badly.

This is not a “the robots are coming” piece. It is something more specific and more useful: an honest look at what AI can actually do to UX work right now, in 2026, and what that means for everyone in this field.

In This Issue:

• What everyone got wrong about the timeline

• What AI is actually doing in UX right now

• 🔍 A or B? Guess which one ChatGPT made

• The part that still requires a human

• What to do with all of this

• Resource Corner

What Everyone Got Wrong About The Timeline

In 2022, the predictions were measured in decades. Some said five years before AI could produce anything useful in a design context. Most assumed the creative, empathy-driven nature of UX work made it uniquely resistant.

The actual timeline was closer to two years.

The UI and UX design landscape changed fundamentally between 2025 and 2026. What once took designers three to four hours to wireframe now happens in minutes. UX Design

What changed was not one breakthrough. It was a cascade of them arriving faster than the field could process. Image generation went from novelty to usable. Language models went from autocomplete to reasoning. Design tools started embedding AI directly into existing workflows rather than asking practitioners to switch to new ones. Modern AI understands design systems, maintains visual hierarchy, and outputs production-ready code, not static mockups that require hours of cleanup. UX Design

The people who predicted slow progress were not wrong about the difficulty. They were wrong about the compounding speed of iteration in AI development. What looked like a long road in 2022 turned out to be a very short one.

The UX landscape looks different than it did two years ago.

A practical day to reset how you work in UX

This is not a talk about AI. It is four hours of actual work, your resume, your positioning, your pitch, built inside the tools that are reshaping how hiring works right now. No theory. No slides to forget by Thursday. Just a room full of people who are serious about their next move, doing the work together, led by people who do this for a living.

You leave with something finished. A clearer read on where your skills belong in this economy. And one specific next step you chose before you walked out.

For anyone in this community navigating a transition, a layoff, or just a quiet feeling that the map has changed and nobody handed you a new one.

RSVP HERE!

back to where we stopped….

What AI Is Actually Doing In UX Right Now

Not hypothetically. Right now, in 2026, these are the things AI is doing inside real UX workflows.

🔵 Generating wireframes and user flows from a text prompt

Tools like UX Pilot generate wireframes, high-fidelity screens, and complete user flows from text prompts or reference images, including proper component hierarchy, spacing, and layout logic. A designer types “e-commerce checkout flow for a fashion brand, mobile-first, three steps” and gets a structured, editable multi-screen flow in seconds. Over two million high-fidelity designs have been generated on UX Pilot alone. Nielsen Norman Group

🔵 Building directly inside Figma with AI

Figma Make, Anima’s Buddy, and Google Stitch all allow practitioners to generate and iterate on designs directly inside Figma without leaving their existing workflow. This is not a separate tool you export from. It is AI embedded inside the place designers already work, generating and editing at the speed of a conversation. Index.dev

🔵 Going from sketch to high-fidelity to code in one pass

Tools like Banani let you upload a hand-drawn sketch to create a lo-fi wireframe, convert it into a high-fidelity UI with text prompts, and export production-ready code for development. The entire journey from rough idea to developer handoff, which used to take days, is now a single workflow measured in hours. LinkedIn

🔵 Producing visual assets, newsletter graphics, and marketing materials

You already know about this one because we used it. The header image for this newsletter was generated with ChatGPT Images 2.0. It took ninety seconds. Which brings us to the part of this issue we have been building toward.

🔍 A or B? Guess Which One ChatGPT Made

We gave ChatGPT a brief: design a checkout flow screen for a mobile e-commerce app. Clean, modern, minimal. Then we gave the same brief to ChatGPT again.

[Image A] [Image B]

Take a good look. One is the first attempt. One is the refined version.

A

B.

If you guessed A was made by a human designer, you are wrong.

If you guessed B was made by a human designer, you are also wrong.

Both were generated by ChatGPT. There was no human designer involved in either image. That is the point.

This is not a trick to make AI look impressive. It is an honest demonstration of where the tool actually is in 2026. Two years ago, this output would have looked like a rough starting point at best. Today it looks like something a designer produced. The gap between AI output and professional design work has narrowed faster than almost anyone in this field predicted.

What the comparison actually reveals is not that AI has become a designer. It is that the definition of design is splitting. Visual production is one thing. Design thinking is another. AI is genuinely capable of the first. It is not capable of the second. And understanding that distinction is the most important thing a UX practitioner can hold onto right now.

The Part That Still Requires A Human

• AI generated both those images. It did not decide whether either of them was right for the actual user trying to complete a purchase on a bad signal at 11pm with three items in the cart and a discount code that might not apply.

• That is the work. Not the visual. The decision about whether the visual serves the human in the specific moment they encounter it.

• AI tools eliminate the grunt work that kept talented professionals stuck pushing pixels instead of solving actual user problems. That framing is useful but incomplete. The more honest version is: AI handles the production layer. The judgment layer, understanding what a specific user actually needs in a specific context and making a considered decision in response to that, remains irreducibly human. UX Design

• For researchers, the same logic applies. AI can transcribe a session in minutes. It can pull surface-level themes from fifty interviews in seconds. What it cannot do is sit in a session and notice that a participant said one thing while their behavior showed something completely different. It cannot feel the tension in a moment where a user is clearly frustrated but too polite to say so. It cannot make the interpretive leap from what it observed to what it actually means for what should be built.

The most exciting development for practitioners in 2026 is AI that augments their work rather than trying to replace them. That framing only holds if practitioners stay clearly positioned on the side of the work that requires human judgment. The ones who are thriving are not the ones who ignored AI. They are the ones who used it to compress the time spent on production and redirected that time toward the thinking that actually matters. everyday ux

What To Do With All Of This

✓ Use the tools. Actually use them, not just read about them

The productivity gap between practitioners using AI tools and those who are not is real and widening. Teams using AI tools are shipping features 40 to 60% faster than those still wireframing manually. That is not a marginal difference. Staying out of the tools because the conversation feels unresolved is not neutrality. It is falling behind. UX Design

✓ Know what you are compressing and what you are protecting

Use AI for generation, iteration, and production. Protect the time you spend on research, synthesis, strategic framing, and judgment. Those are not the same category. The practitioners who are using AI well are the ones who are clear about which parts of their process AI is improving and which parts it is not allowed to shortcut.

✓ Stay upstream of the output

The most dangerous position in a world where AI can generate UX outputs on demand is to be the person who polishes and ships those outputs without interrogating them. That is a role that will get smaller. The valuable position is upstream: defining the problem, setting the direction, evaluating whether what was generated actually works for the people it was designed for.

✓ Build fluency with prompting as a skill

The quality of what AI produces is directly tied to the quality of how you direct it. A vague prompt produces a vague output that looks specific. A well-constructed prompt that includes context, constraints, user context, and clear success criteria produces something you can actually use. Prompting well is a learnable skill and it is becoming as important as knowing how to run a good research session.

📦 Resource Corner

UX Pilot The most purpose-built AI tool for UX work right now. Generates wireframes, high-fidelity screens, and complete user flows from prompts. Over 100,000 Figma plugin installs. Worth testing before forming opinions about what AI can and cannot produce.

Figma Make AI generation built directly into Figma. If your team already lives in Figma, this is the lowest-friction entry point into AI-assisted design workflows.

ChatGPT Images 2.0 The tool behind the images in this newsletter. The April 2026 update changed the quality significantly. Try it on a real brief before deciding what it is capable of.

Anima Design to code, AI wireframing, and Figma-native workflow. Particularly strong for teams that want to reduce the gap between design and engineering handoff.

Toools.design: Best AI Tools for UX Designers 2026 The most current comprehensive roundup of AI tools across the design workflow. Updated regularly and honest about what each tool is actually useful for versus what the marketing claims.

💭 Final Thought

The people who said AI would take years to matter in UX were not trying to mislead anyone. They genuinely underestimated how fast the compounding would happen. Most of us did.

What nobody should underestimate now is how fast the next two years will move.

The practitioners who were caught flat-footed in 2022 had an excuse. The pace of change was genuinely surprising. The practitioners who get caught flat-footed in 2028 will not have the same excuse. The direction is visible. The tools are available. The only variable is whether you engage with them deliberately or wait until the gap becomes impossible to close.

AI would take over your job. That sentence was written in future tense two years ago.

Read it again in the present tense and ask yourself honestly where you stand.

--- The UXU Team

What they actually want is innovation without risk. Which is just... work.

Calvin Robertson has a different take. The best leaders don’t wait for the perfect idea to land fully formed. They test fast, adapt faster, and create the kind of space where teams can build what actually moves the business forward. That’s not recklessness, that’s calculated risk. And it’s the trait most leadership cultures quietly punish while publicly claiming to reward.

It’s one of those truths that’s obvious once someone says it out loud. The hard part is what you do with it after.

Calvin is bringing that conversation and a lot more to UXCON26.

One day. October 8th. Silver Spring Civic Center, Maryland. A room full of practitioners who care enough about the future of leadership, design, and innovation to show up in person and wrestle with the hard questions together.

Don't wait... Secure your spot

Not ready to wait until October?

Good. Don’t.

July 23rd · 12:00–4:00 PM Silver Spring Civic Building at Veterans Plaza, 1 Veterans Pl, Silver Spring, MD 20910

Four hours. No keynotes. No trend roundups. Just you, your actual resume, your actual positioning, and real people giving real feedback - with AI tools that help you move faster and a room full of professionals who are serious about what comes next.

You walk in unclear. You walk out with something finished.

RSVP HERE!

Two events. One question underneath both of them: are you ready to do something about where you’re headed?

See you there.