AI can generate interfaces in seconds, summarize interviews, analyze feedback, write research plans, produce prototypes, generate code, and turn an idea into something clickable before the rest of the team has finished discussing the problem.

So naturally, people are asking:

What is my role now?
What skills actually matter in 2026?
Will AI replace UX designers and researchers?
If everyone can generate a polished interface, what actually makes a designer valuable?

These aren’t hypothetical questions anymore. They are becoming part of everyday conversations within product and design teams.

Truth is, the future of UX may have less to do with how quickly we can make things and much more to do with how well we decide what should be made in the first place.

This is what we’ll be discussing at UXCON26

This year, we’re taking the conversation beyond “what’s new in UX?”

UX doesn’t happen in isolation anymore. Researchers work with designers. Designers work with engineers. Product managers influence research. Executives influence product decisions. AI is changing everyone’s workflow.

The future of UX won’t be built by one discipline working alone. It will be built by people who can think across disciplines, challenge assumptions, understand people and work together.

The goal isn’t for you to leave with another folder full of slides. It’s for you to leave with a new idea, a new perspective, a new connection or perhaps even a new direction for your career.

Get Your UXCON26 Ticket

The AI problem isn’t that AI can design

It’s that AI can make us skip the thinking.

One of the most interesting conversations happening in design right now isn’t whether AI can produce attractive interfaces. It obviously can. The more important question is whether we can still recognize when we’re solving the wrong problem.

A growing concern within the design community is that AI makes it incredibly easy to move from a vague problem straight into solution generation. Instead of spending time understanding the user, defining the problem and exploring the underlying context, teams can now ask an AI tool to produce 5 interface concepts before the original question has even been properly framed.

Traditionally, UX encouraged us to move through a process of understanding, defining, exploring, testing, learning and iterating. AI makes it incredibly easy to skip several of those steps and go straight to “generate.”

The second process is faster. But faster doesn’t necessarily mean better.

This is why some of the most valuable UX skills in the AI era may actually be the ones that feel least productive on paper: asking better questions, challenging assumptions, recognizing ambiguity, understanding context, interpreting human behavior, making trade-offs and knowing what not to build.

AI can give you ten solutions. Your job is still to know whether any of them deserve to exist.

The interface is changing too

For decades, UX has largely meant designing interfaces for humans. We designed screens, buttons, menus, forms, navigation systems and search experiences intended to help people accomplish something.

We’re now moving into a world where another kind of “user” is beginning to interact with those same systems: AI agents.

Nielsen Norman Group recently highlighted this emerging shift, noting that AI agents can increasingly navigate websites, fill out forms, compare options and execute transactions on behalf of people.

Consider a simple request: “Find me the best flight to New York next Friday, under $800, with one checked bag.”

Traditionally, you would open a website, search for flights, apply filters, compare results and make the decision yourself. As of now, AI agents are performing many of these actions on people’s behalf.

The implication for UX is fascinating. What happens when the person ultimately benefiting from an interface isn’t the person directly interacting with it?

That changes how we think about accessibility, content structure, navigation, forms, permissions, feedback, error handling, authentication and trust. We’re beginning to design systems that need to communicate effectively with both humans and machines.

The idea of a “user” is becoming more complicated, and UX has a significant role to play in figuring out what that means.

The prompt isn’t the interface

There’s another interesting development happening at the same time. AI products have popularized the idea that the interface can simply be a text box: type something, get something back.

Designers are beginning to question whether this actually represents good interaction design.

UX Collective recently explored the argument that the prompt itself isn’t necessarily an interface. We’ve spent decades moving away from command-line interactions toward interfaces that help people understand what they can do. Now we’re giving people an empty box and effectively saying, “Tell the machine what you want.”

That isn’t always simplicity. Sometimes it’s simply transferring the complexity from the system to the user.

Good AI UX therefore isn’t just about building a chatbot. It’s about deciding how much control the user should have, when a system should take initiative, how people understand what the AI is doing, and how they correct it when it gets something wrong.

Recent research into proactive AI agents is already exploring ideas such as calibrated initiative, transparency, contestability, privacy and evaluation beyond simple task accuracy.

In other words, we’re not just designing interfaces anymore. We’re increasingly designing relationships between people and systems that can act.

So, are UX designers becoming less important?

Probably not. But the kind of value they provide is changing.

When production becomes cheaper, judgment becomes more valuable.

If AI can generate 50 interface concepts, generating interface concepts is no longer much of a competitive advantage. If AI can summarize 200 interviews, producing a summary isn’t necessarily the differentiator. If AI can write code, being able to write a small amount of code isn’t automatically what makes you valuable.

The differentiator becomes your ability to determine which output is actually useful.

• Can you spot the missing context?

• Can you identify the dangerous assumption?

• Can you recognize the insight hidden inside contradictory research?

• Can you explain why the obvious solution isn’t the right one?

And perhaps most importantly: Can you influence what the organization does with what you’ve learned?

Figma’s 2026 AI research offers an interesting signal here. Its research found increasing collaboration between traditionally separate roles, with developers participating in design and designers participating in development at significantly higher rates than previously reported.

AI isn’t simply automating design. It is also changing who gets involved in the design process.

The designer increasingly needs to understand technology. The researcher needs to understand product strategy. The product manager needs to understand user behavior. The developer is increasingly involved earlier in the product experience.

The UX professional of the future may therefore be less of a specialist working inside a neatly defined box and more of a connector between customer needs, research, product strategy, design, technology and business.

What should UX professionals actually learn in 2026?

This may be one of the most common questions being asked across the industry: “What should I learn to stay relevant?”

The easiest answer is to produce another list of tools. Learn Figma AI. Learn ChatGPT. Learn Claude. Learn AI prototyping. Learn AI research tools.

And yes, learn them.

But don’t confuse tool fluency with professional growth.

A stronger UX learning strategy for 2026 starts with:

1. Becoming excellent at understanding people.
   Interviewing, observation, contextual inquiry, usability testing, qualitative synthesis and behavioral analysis aren’t becoming less important because AI exists. If anything, the ability to understand people becomes more important as technology becomes more capable.

2. The second skill is problem framing.

   Don’t arrive at the meeting with five solutions simply because AI helped you generate them. Arrive with a better understanding of the problem.

3. The third is learning to work with AI.
   AI can be incredibly useful for research preparation, transcription, initial synthesis, competitive analysis, prototyping, documentation, coding and exploration. But human judgment still needs to remain in the loop. While AI can improve efficiency, removing human interpretation can flatten nuanced feedback into overly rigid categories.

4. And finally, learn to influence.

   Great research doesn’t automatically change decisions. A beautiful design doesn’t automatically get approved. A brilliant recommendation doesn’t automatically become a roadmap item. UX professionals need to understand stakeholders, communicate clearly, negotiate trade-offs, tell compelling stories and make the case for their recommendations.

The UX career question nobody can answer alone

Technology is making it easier than ever to work alone. AI can brainstorm with you, critique your design, write your research plan, generate your prototype and help you code.

But the more we automate individual production, the more valuable human connection becomes.

Some of the most important things in our profession aren’t learned from another tutorial. They’re learned from conversations:

• hearing how another researcher handled a difficult stakeholder,

• discovering how another designer navigated a career transition

• meeting someone who has been solving the exact problem you’ve been struggling with.

That’s what makes a good conference valuable and…….

Get Your UXCON26 Ticket

Resource Corner

If you’re thinking seriously about where UX is heading, these are worth exploring:

• Figma’s 2026 AI Report — research into how designers, developers and product managers are adapting to AI and collaborating across disciplines.

• AI Agents as Users — an introduction to designing experiences that increasingly involve both humans and AI agents.

• The Prompt Is Not an Interface — a look at why conversational AI shouldn’t automatically mean putting a text box at the center of every experience.

• When Design Stops Asking Why — an exploration of what happens when AI makes solution generation easier than problem framing.

The future of UX isn’t something we can predict

But we can participate in shaping it.

AI will continue to change our tools. Interfaces will continue to evolve. Agents will become more capable. Organizations will continue to rethink how product teams work. Some UX roles will change dramatically, while entirely new ones will emerge.

But one thing remains remarkably constant: we’re still designing for people.

The better we understand people, technology, organizations and each other, the better equipped we’ll be to navigate whatever comes next.

__ The UXU Team

We designed what happened when someone tapped a button, opened a menu, filled in a form, or moved from one page to the next. The screen was the interface, and for the most part, designing the screen was the job.

But that definition is starting to feel a little too small.

Today, someone can ask their device a question without touching it. A car can respond to a glance, gesture, or voice command. Headsets can place interfaces directly into physical space. And some products are beginning to remove the visible interface almost entirely.

Welcome to the increasingly multimodal world of UX.

This does not mean screens are going away. Your Figma files are safe. 😅 It means screens are becoming just one part of a much bigger interaction system alongside voice, gesture, movement, context, sound, spatial computing, and even interfaces that seem to disappear altogether.

And that creates a new challenge for UX professionals: How do you design an experience when there is no obvious screen to design?

That is what we are exploring in this issue, including:

• Why voice interfaces are getting interesting again

• What “multimodal” actually means in practice

• The rise of Zero UI and invisible interactions

• The new UX questions these experiences introduce

• Why researchers may have an especially important role to play

• And, of course, this week’s Resource Corner

Why voice finally works this time

Voice has been “the future” for years. The problem was that it rarely felt very futuristic.

Early assistants were awkward, overly literal, and easy to confuse. You had to phrase commands just right, repeat yourself often, and eventually many people simply went back to tapping.

That is changing.

Today’s voice interfaces are much better at understanding natural language, maintaining context, and responding in a way that feels more conversational. That makes them especially useful in moments where screens create friction: driving, cooking, exercising, or whenever your hands and eyes are already busy.

Nike’s Audio-Guided Runs are a good example. Runners get coaching and pacing cues without needing to look at a phone mid-stride. Voice is not a gimmick there. It is simply the better interface for the moment.

That is the bigger shift: voice is not replacing screens. It is becoming one part of a multimodal experience, where the best interface depends on what the user is doing.

What multimodal design actually means

Multimodal design is simply the idea that people should not have to rely on one way of interacting with a product.

Voice, touch, text, gesture, and visuals can work together, with each taking over when it makes the most sense.

Think about asking a smart display for a recipe while your hands are covered in flour. Voice is the easiest way to make the request, but a screen is better for showing the steps. One handles the input, the other handles the output.

That is the real shift: UX is becoming less about designing individual screens and more about designing the handoffs between different modes. A voice command might trigger a visual confirmation. A gesture might prompt audio feedback. The experience has to feel continuous, even when the interaction method changes.

It also makes products more accessible. Giving people multiple ways to interact means they can choose what works best for their abilities, environment, or situation.

The future is not voice instead of screens. It is knowing which mode should do what, and when.

Zero UI and the interfaces you cannot see

Zero UI asks a different question: what happens when there is no screen at all?

Instead of buttons and menus, interaction happens through voice, gestures, sensors, and systems that anticipate what you need.

A thermostat adjusts before you feel cold. A door unlocks as you approach. A product is reordered before it runs out.

In Zero UI, good UX is felt, not seen. The interaction works so smoothly that the interface almost disappears.

But invisible interfaces create new challenges.

How do people know what the system can do?

How do they correct it when it gets something wrong?

And how do they stay in control when the system acts on their behalf?

That is where the real design work begins: making invisible interactions feel helpful without making them feel mysterious, intrusive, or manipulative.

Quick pause...

🎯 UXCON26 · One Day · The Whole Community

Shifts like this one, from screens to systems, are exactly the kind of conversation the field needs to have out loud, in person, with the people actually working through it.

On October 8, 2026, the UX community comes together for a full day built around where this work is really heading.

Headlining is Don Norman, the person who coined the term User Experience. Alongside him are practitioners from Netflix, The New York Times, Target, UserTesting, and Skylight, hosted by Jeremy Miller of the Beyond UX Design podcast.

Three keynotes. Two panels. One room. The conversations that stay with you long after the day ends.

41 DAYS TO GO!!!

Secure your UXCON26 ticket

The new design questions this raises

As interfaces become more multimodal and less visible, the questions UX teams need to ask start to change too.

🔵 What works best in this moment?
Voice is great when hands are busy. Touch is better for precision. Visuals work best for comparison. The goal is not to choose one mode, but to match the interaction to the context.

🔵 How will the user know it worked?
Without a screen, feedback has to be intentional. Sound, haptics, or visual confirmation can reassure users that the system understood them.

🔵 What happens when it gets it wrong?
Voice can mishear. Gestures can be misread. Smart systems can make bad assumptions. Recovery should be just as carefully designed as the ideal experience.

🔵 Does the user still feel in control?
If a product is adapting, predicting, or acting on someone’s behalf, people should know why and be able to change or stop it.

Where researchers fit into all of this

The less visible the interface becomes, the more important it is to understand the person using it.

Voice and multimodal experiences cannot be understood from static screens alone. Researchers need to study how people actually speak, what they expect the system to understand, where they hesitate, and what they do when it gets something wrong.

Context matters even more. A voice interface used while driving, cooking, or multitasking may behave very differently from one tested in a quiet room. That makes in-context research especially valuable.

And as interfaces become less visible, mental models become critical. Researchers will need to uncover what people think the system can do, why they believe it acted, and whether they still feel in control.

📦 Resource Corner

Voice User Interface Design Guide 2026
A practical guide to modern voice UX, with examples of where voice creates real value.

Designing Voice User Interfaces by Cathy Pearl
A foundational resource on conversation design and what makes voice interactions work.

UX Trends 2026: AI, Zero UI, and Adaptive Design
A useful overview of Zero UI and the broader shift from screens to adaptive systems.

Multimodal Design Principles
A good primer on voice, multimodal interaction, consent, and context-aware design.

Designing Agentive Technology by Christopher Noessel
Essential reading on designing systems that act on a user’s behalf while preserving trust and control.

💭 Final Thought

Screens are not going anywhere. What is changing is that they are losing their monopoly on what counts as an interface.

For a field that has spent years defining itself through layouts, hierarchies, and pixels, that is a real identity shift. The work is moving from “how does this look” to “how does this behave”. That is harder, less visible, and considerably more interesting.

The practitioners who navigate it well will be the ones who understood that all of these modes, screen, voice, gesture, and ambient, are just different ways of meeting a human need, and who kept their attention on the need rather than the medium.

The interface is becoming invisible. The thinking behind it matters more than ever.

Start building the literacy now, before the shift finishes without you.

--- The UXU Team

Researchers uncover what customers need. Designers turn those insights into experiences. Product managers balance those needs with business priorities, technical constraints and product strategy.

The better these disciplines understand one another, the better the decisions they can make together.

That’s part of what makes attending UXCON26 as a team valuable.

Who is UXCON26 relevant for?

UX Researchers & Research Leaders

To explore how research practice is changing, learn from peers and bring new approaches back into their organizations.

Product, Graphic, Interaction & UX Designers

To sharpen how they think about users, decision-making, collaboration and the experiences they create.

Product Managers & Product Leaders

To get closer to the conversations shaping research, design and customer experience — and better understand how those disciplines can contribute to stronger product decisions.

CX, Service Design & Strategy Teams

For teams responsible for understanding the customer experience beyond individual product features.

Explore Group Rates

But there’s another benefit to bringing colleagues from different functions:

When your UX researcher, designer and product manager experience those conversations together, the discussion can continue immediately:

Could we apply this to our product?

Are we doing this well today?

Should we rethink how our teams work together?

What should we try when we get back?

That shared experience can be just as valuable as the individual sessions themselves.

Thinking about sending a team?

If your organization is considering sending several people to UXCON26, we’d love to talk.

Whether that’s:

3 UX practitioners, a UX + Product team or a larger cross-functional group, we can help you determine the best option for your organization.

Explore Group Rates

The hardest part of design often has very little to do with design itself.

There is a neat version of product design that many of us are taught.

You receive a problem → understand the user → explore ideas → prototype → test → refine → and hand the solution over.

Then there is what actually happens on product teams.

• The PM has already committed to a launch date.

• Engineering tells you the interaction you designed will add another sprint.

• Leadership wants something that feels “more innovative.”

• Research is pointing in one direction while the business is pushing in another.

• Someone brings up a competitor halfway through the review.

• A stakeholder who was barely involved suddenly has strong opinions about the final design.

Sometimes, after weeks of work, the entire direction changes because of a conversation you weren’t in.

This is the part of design we don’t talk about nearly enough.

For many designers, the hardest part of the job isn’t Figma, prototyping, usability testing, or choosing the right interaction pattern. It’s navigating the people, priorities, constraints, and decisions surrounding the work.

Figma’s research into modern product teams found that 55% of product builders surveyed are already taking on work outside their traditional roles, as the boundaries between design, product, and engineering continue to blur. (Figma)

That shift matters because the designer who thrives on a product team today isn’t necessarily the person who can produce the most polished screens. It’s the person who can operate well inside the system around those screens.

So what should designers get better at?

1. A lot of design problems are actually alignment problems:

Get aligned before you start designing

One of the most common challenges on product teams is that everyone thinks they’re solving the same problem when they aren’t.

Everyone can leave the same meeting believing they are aligned while quietly working toward different outcomes.

Atlassian’s 2025 State of Teams research found that knowledge workers and executives spend roughly 25% of their time searching for information and answers. (Atlassian)

When context is fragmented, alignment becomes harder. Sometimes the most valuable design work happens before a single frame is created. Make sure everyone is solving the same problem.

2. Then there is the problem of getting into the conversation early enough

Get into the room earlier

Many designers know the experience of being brought into a project after the important decisions have already been made.

The feature has been prioritized. The requirements are written. The deadline has been communicated. The technical approach has been discussed.

Then UX gets the request: “Can you design this?”

At that stage, there may be very little actual design left to do. You are mostly shaping a solution that already exists.

Push for earlier collaboration.

Bring engineers into exploration. Involve research before the roadmap is fixed. Ask to join conversations where product decisions are being shaped, not just reviewed.

Figma found that 80% of developers believe businesses would benefit from designers and developers working more closely together, and 55% of front-end developers want to be involved earlier in the design process.

This is a big part of the conversation we’re creating space for at UXCON26.

This year’s conference isn’t only about becoming better at the craft of UX. It’s about becoming better at doing UX inside real organizations, alongside the people who influence whether our work succeeds.

One of the things we’ll be talking about is the realities of working in our industry:

Collaboration, Careers, AI, Research, Leadership, Influence,

and what it takes to create better products when no one discipline controls the entire outcome.

→ Join us at UXCON26

3. The work also requires a lot more influence than authority

Stop presenting screens. Present decisions

One of the biggest career shifts in design happens when you realize that producing a good solution doesn’t automatically mean the organization will choose it.

You may need to convince a PM to reconsider scope, persuade engineering that an interaction is worth the additional effort, help leadership understand why research contradicts their original assumption, or explain why a seemingly small accessibility decision matters.

And most of the time, none of those people report to you, and that means as a designer you have to develop influence.

This is where design rationale becomes much more important than simply presenting a polished screen. If the conversation is reduced to “I like this” versus “I don’t like this,” the person with the most organizational authority will usually win.

The ability to explain why something should be designed a certain way can become just as important as knowing how to design it.

4. The answer isn’t to become the UX police

Learn to make trade-offs

There is a stage many designers go through where everything starts looking like a UX violation.

You learn the principles. You understand accessibility. You study usability heuristics. You become more familiar with research. Then someone proposes something questionable and your instinct is to protect the user at all costs.

Sometimes that pushback is absolutely necessary.
But constantly positioning UX against Product, Engineering, Marketing, or the business usually makes design less influential rather than more influential.

Real product development is an exercise in trade-offs.

There are constraints like deadlines, legacy systems, budgets, technical limitations, compliance requirements etc that you should be aware of. These constraints don’t disappear because a solution is more user-centered.

The more useful question becomes:

Given the constraints we have, what parts of the experience are most important to protect?

That shift changes your relationship with the team and that is often where seniority starts to show.

5. AI is making this even more obvious

Get better at judgement, not just craft

As design tools become faster and more capable, execution itself is becoming less of a differentiator.

If everyone can generate concepts faster, create prototypes faster, synthesize research faster, and explore more directions in less time, then the value of the designer begins to shift.

Knowing:

• Which problem deserves attention.

• Whether the team’s assumptions are sound.

• When something is ready to test.

• Which research matters.

• When the team is moving quickly toward the wrong solution.

AI can accelerate output but it cannot remove the need for someone to decide whether that output makes sense in the context of users, the product, the business, and the team building it.

Resource Corner

• Figma — State of the Designer 2026

• Figma — What do developers want from designers

• Nielsen Norman Group — UX Stakeholder Engagement 101

• Nielsen Norman Group — UX Maturity Model and Four Factors in UX Maturity

A parting shot….

Becoming a stronger designer isn’t only about improving what happens inside the design file.

It’s also about getting better at everything that happens outside of it.

Share

__ The UXU Team

Think about an app you genuinely love. Not one you use because you have to. One you are actually fond of.

Now think about the why. It probably works well, but “works well” is not why you love it. Plenty of products work well and inspire nothing. What you love is how it makes you feel. Calm. Capable. Delighted. Understood. Maybe it made you smile once when you did not expect to.

That feeling, not the feature list, is what turned a tool you use into a product you love.

For years, the field optimized hard for the functional stuff, metrics, speed, usability, and something quietly got lost along the way. Interfaces became clean, efficient, and emotionally flat. In 2026, the pendulum is swinging back, and emotional design is at the center of it.

This issue is about the difference between products people use and products people love, and how to design for the second one.

In this issue, we’ll cover:

• Why interfaces got emotionally flat

• The 3 levels every product is felt on

• What emotional design actually is (and is not)

• Designing feeling into real products

• Why this matters more in the age of AI

• More resources on Emotional design

Why interfaces got emotionally flat

For years, product design got better at what it could measure: usability, conversion, speed, and efficiency.

The problem is something like emotion is much harder to put on a dashboard.

You can track whether someone completed a task but it is harder to measure whether the experience felt warm, memorable, playful, or reassuring. So those qualities slowly became secondary.

The result has been a generation of products that work beautifully but often feel the same: clean, efficient, and emotionally forgettable.

Now the pendulum is swinging back and teams are rediscovering that usability and personality are not opposites. The best products can be clear, functional, and still feel like they have a pulse.

The three levels every product is felt on

Don Norman’s Emotional Design gives us a useful way to understand why some products simply work, while others actually stay with us. He describes three levels of emotional experience:

1️⃣ Visceral: the immediate gut reaction
This is what happens before we have even properly used the product. The visual style, motion, responsiveness, and overall polish create an instant feeling: this looks good, this feels good, I want to explore it.

2️⃣ Behavioral: the feeling of using it
This is the emotion created by the experience itself. Does the product feel intuitive? Does it respond the way you expect? Does completing a task feel effortless or frustrating? Good usability creates a quiet sense of confidence and control.

3️⃣ Reflective: what the product comes to mean
This is the deeper layer: the identity, memories, and meaning we attach to a product over time. It is why people become loyal to certain tools or brands, even when plenty of alternatives exist.

The insight for 2026 is that these three layers map almost perfectly onto where interfaces are heading, and the best products are starting to trigger all three intentionally rather than accidentally.

Quick pause. This one is especially fitting.

🎯 UXCON26 · One Day · With The Author of Emotional Design

On October 8, 2026, Norman headlines UXCON26, still publishing and still challenging this field at 88. If emotional design resonates with you, this is the rare chance to hear the thinking behind it from the source, in one room, alongside practitioners from Netflix, The New York Times, Target, UserTesting, and Skylight, hosted by Jeremy Miller of the Beyond UX Design podcast.

Three keynotes. Two panels. One day that reconnects you to why this work matters.

Join Don Norman at UXCON26

What emotional design actually is (and is not)

Emotional design is often mistaken for adding more personality to an interface: a mascot here, some confetti there, maybe a playful animation after a task is complete.

But that is only surface-level.

At its core, emotional design is about intentionally shaping how a product makes someone feel. Does it make them feel confident? Reassured? Energized? Understood? Those feelings can become just as important as whether the product technically works.

That is why the strongest experiences do more than solve a problem. They create a sense of connection and give the product a character people can recognize and remember.

We are already seeing this show up in more expressive interfaces: typography with personality, motion that helps explain what is happening, distinctive visual systems, and interactions that feel considered rather than templated.

But there is an important line to protect.

Emotion should work in service of the user, not against them. The same techniques that create delight can also create pressure, urgency, or manipulation. Done well, emotional design strengthens the experience. Done poorly, it is simply a friendlier-looking dark pattern.

Designing feeling into real products

Emotional design becomes real through the small decisions people encounter while using a product.

🔵 Focus on the moments people actually remember
Not every screen needs personality. Put more care into moments with emotional weight: onboarding, success, empty states, errors, and goodbyes. A thoughtful message at the right moment often matters more than adding delight everywhere.

🔵 Give the product a recognizable character
The strongest products tend to have a consistent voice and way of behaving. That character might be calm and reassuring, playful and energetic, or direct and competent. What matters is that it feels intentional and consistent across the experience.

🔵 Use motion with a purpose
Good motion should help communicate what is happening, reduce uncertainty, or add emphasis. The goal is not animation for animation’s sake, but movement that makes the experience clearer and more satisfying.

🔵 Treat failure as a design moment
People often remember how a product treated them when something went wrong. Clear explanations, helpful next steps, and empathetic language can turn frustration into trust.

🔵 Let AI collaborate, not take over
As AI becomes more embedded in products, good experiences will increasingly be the ones that check intent before acting. Asking, confirming, and giving users control can make an intelligent product feel respectful rather than intrusive.

Why this matters more in the age of AI

AI is making functional design easier to produce. Clean layouts, usable flows, polished copy, and competent interfaces can now be generated faster than ever.

That means “it works” is becoming less of a differentiator.

What becomes more valuable is what is harder to automate: understanding the people behind the interaction. Their anxieties, expectations, motivations, and the feeling they should leave with.

In a sea of increasingly similar AI-generated experiences, products with warmth, character, and a clear point of view are more likely to stand out and be remembered.

AI can help produce the interface. But deciding how an experience should feel, why that feeling matters, and what it should mean to the person using it still requires deep human understanding.

That is what makes emotional design less of a decorative skill and more of a competitive one.

📦 Resource Corner

Emotional Design by Don Norman
The foundational read on the three levels of emotional response and how emotion shapes product experiences.

Designing for Emotion by Aarron Walter
A practical guide to adding personality, warmth, and emotional connection to digital products.

The Most Popular Experience Design Trends of 2026 by Joe Smiley (UX Collective)
A useful look at why emotional design is resurfacing and how it connects to current interface trends.

What’s Next: 7 UI Design Trends of 2026 (Tubik)
Explores the return of visual character, expressive interfaces, and “clarity with signature.”

Hooked by Nir Eyal
A look at the psychology behind product habits and emotional connection, best read with an ethical lens.

💭 Final Thought

Clean, usable, efficient products still matter. But people are not efficiency machines. They remember how a product made them feel, whether it gave them confidence, reduced friction, felt thoughtful, or simply had a little character.

That is where the opportunity is now: pairing the rigor of good UX with the emotional craft that makes an experience memorable.

Make it work. Then make it feel like something.

--- The UXU Team

We’ve been building UXCON26 around one question:

What conversations do UX professionals need to be having right now?

On October 7–8, we’re bringing those conversations to Silver Spring, through practical workshops, candid leadership discussions, cross-functional perspectives, career conversations, and plenty of opportunities to connect with the people shaping the future of UX.

And now, the full program is taking shape.

Two days. A lot to take back to work.

October 7 — Expert Workshops

We’re starting UXCON26 with a dedicated workshop day for people who want to go beyond inspiration and actually build new skills.

11:00 AM – 1:00 PM EST
Build an AI Strategy for Faster and Deeper Insights with Leo Hoar

Explore how to think more strategically about AI in the research process — and how to use it to accelerate work without sacrificing the depth and judgment great research requires.

2:00 PM – 6:00 PM EST
Building with AI Beyond the Conversation with Jake Dibatista

Move beyond simply chatting with AI and explore what it means to actually build with it.

Great news: If you have an On-Site + Expert Workshop Pass, you can attend both workshops.

Get Your On-Site + Workshop Ticket

October 8 — The Main Conference

We then bring the whole UX community together.

The day starts with coffee, conversations and networking before moving into a lineup built around leadership, careers, collaboration and the future of our industry.

Opening Keynote: Becoming the leader your organization needs

Calvin Robertson opens the speaker program with:

“Becoming the Leader They’ve Been Waiting For: Leading Change When Design Isn’t Enough.”

Because doing great UX work is only part of the job. Creating change often requires influence, relationships and leadership far beyond the design file.

Podcast-Style Convo: A conversation with Don Norman

We’re especially excited to welcome Don Norman for a podcast-style conversation with Yao Adantor.

Rather than another traditional keynote, this will be a deeper conversation around design, the industry and the ideas shaping where UX goes next.

And later in the afternoon, Don returns for something even more interactive:

Don Norman Q&A

An entire hour dedicated to an open Q&A with Don and the UXCON community.

Bring your questions.

What does building a UX career look like now?

Our Cross-Sectional Career Panel brings together UX professionals with experience across organizations including Netflix, Amazon, Skylight and UXR Institute.

Instead of presenting one prescribed path into or through UX, we’ll explore the different ways careers actually develop, the decisions, pivots and opportunities that rarely fit neatly into a career roadmap.

Questions Are How We Find Each Other

Amanda Gelb, Founder & Principal at Aha, takes the stage for a mini-keynote on why better questions lead to better conversations.

Drawing from nearly two decades of design research and 145 dinners with strangers, Amanda explores why the most useful answers often come not from the questions we planned — but from what we ask next.

Later, our Industry Panel brings together voices from organizations including The New York Times, Target, User Interviews and more to examine what is happening across the wider UX and product landscape.

These are conversations designed to help you understand not only where UX is today, but where your own place within it could be heading.

Reserve Your Spot

We’re leaving room for connection.

UXCON26 isn’t designed to be eight hours of sitting quietly in a chair.

Throughout the day, you’ll have opportunities to meet other researchers, designers, product professionals and UX leaders during breaks, lunch and networking sessions.

And once the formal program ends?

Live Music & Networking & Happy Hour

Sometimes the conversation you have after the talk is just as valuable as the talk itself.

An Offer on Your UXCON26 ticket!!!

To celebrate the UXCON26 program reveal, we’re giving you 72 hours to save $$$ on your UXCON26 ticket.

Get your on-site pass for $225 instead of $265.

Offer ends Friday, August 21 at 11:59 PM ET.

Save $$ on Your UXCON26 Ticket

Thinking about bringing your team?

UXCON26 isn’t only for individual attendees.

If your UX, research, design or product team is navigating questions around AI, career development, cross-functional collaboration, leadership or the changing role of UX, this year’s program gives you plenty to experience, and unpack together afterward.

Group ticket options are available for organizations looking to bring multiple team members to UXCON26.

Bring your team, learn together, meet other professionals across the industry, and leave with conversations you can continue back at work.

Talk to Us For Group Rates →

This is the room we’re building.

A room where you can hear from Don Norman.

A room where you can learn how other UX professionals are navigating AI, leadership, career growth and organizational influence.

A room where researchers, designers, product people and industry leaders can actually meet each other — not through another LinkedIn connection request, but face-to-face.

And on October 8, we want you in it.

If you’ve been waiting to decide whether to attend, the program is now one more reason to say yes.

GET YOUR UXCON26 TICKET →

See you in Silver Spring.

The UXCON26 Team

It’s tempting to assume the difference is stronger research, a more polished prototype, or a better presentation.

Often, it isn’t.

The difference is that they understand who actually influences the decision, what those people care about, and where support or resistance is likely to come from before the meeting even begins.

No matter how human-centered your process is, your work still has to survive the organization around it.

And that requires a different kind of UX skill.

The work before the UX work

UX professionals spend a lot of time learning how to understand users.

We map journeys. We conduct interviews. We identify pain points. We test prototypes. We advocate for the people using the product.

But as you move into leadership, there is another system you have to learn to understand:

Your organization.

Nielsen Norman Group has written about the power dynamics UX teams face, noting that decisions about what gets built and funded are often controlled by product, engineering, or other leaders rather than UX itself.

That means a brilliant solution can still die because:

Finance thinks it is too expensive.

Engineering sees six months of additional complexity.

Product is under pressure to ship this quarter.

Marketing has already promised something different.

An executive simply isn’t convinced this problem deserves attention.

None of these people necessarily disagree with UX.

They are looking at the same decision through different incentives, risks, and responsibilities.

That is why UX leadership increasingly requires more than technical mastery.

It requires relationship mapping.

The Strategic Relationship Map

Stakeholder mapping itself isn’t new. A common approach plots stakeholders according to their power and interest. Nielsen Norman Group recommends going further by also considering a stakeholder’s attitude toward UX, because a highly influential UX skeptic demands a very different strategy from an enthusiastic supporter.

For UX leaders, we can simplify that into a useful diagnostic:

Plot people across two dimensions:

How much influence do they have?

and

How supportive are they of UX?

You end up with four broad groups:

High influence + High UX support

Your Champions

These are the people who already believe in the work and have enough organizational influence to help move it forward.

Don’t simply keep them informed.

Give them evidence they can carry into rooms where you aren’t present.

High influence + Low UX support

Your Critical Relationships

This may be the most important quadrant.

Resist the temptation to label these people “difficult stakeholders.”

Instead, get curious.

• What pressure are they under?

• What has made them skeptical?

• What would they need to see before supporting the work?

Turning one influential skeptic into an informed ally can be more valuable than winning another ten people who already agree with you.

Low influence + High UX support

Your Amplifiers

These people may not control budgets or roadmaps, but they can spread ideas, provide intelligence, build momentum, and strengthen your case.

They are often underestimated.

Low influence + Low UX support

Monitor

You probably don’t need to spend significant political capital here today.

But stakeholder positions change. Teams reorganize. People get promoted. Priorities shift.

Your relationship map should move with them.

Tip: NN/g similarly recommends revisiting stakeholder maps because changes in leadership, priorities, interest, and attitudes can materially change the landscape surrounding UX work.

Then ask the question we often forget:

What keeps this person up at night?

This is where the map becomes powerful.

When we say someone has a “hidden agenda,” it doesn’t necessarily mean something sinister.

Usually, it means there are priorities influencing their decision that haven’t been said out loud.

• Your VP of Product may be thinking about adoption.

• Your Engineering Director may be worried about technical debt.

• Your CFO may be watching cost.

• Your Growth Lead may have a conversion target.

• Your executive sponsor may have promised the board a launch before the end of the quarter.

If you walk into the room talking only about “what users told us,” you may be solving only one part of the decision.

Then connect the user problem to that reality.

Not by watering down the research but by translating it.

That is influence.

And……..

Creating relationships is one of the reasons we’re excited about UXCON26.

This year’s conversation goes beyond what any one UX discipline can accomplish on its own. Researchers, designers, product teams, engineers, strategists, and leaders increasingly have to figure out how to build together.

As we put it at UXCON26:

UX has never been a solo act. It’s a team sport.

Your next breakthrough might come from:

Understanding Product differently.

Finally getting Engineering involved earlier.

Having a conversation with a leader whose priorities you hadn’t understood.

Simply meeting someone who has figured out how to navigate the same organizational challenge you’re facing.

Come for the ideas | Come for the conversations |Come meet the people shaping what UX becomes next.

Get your UXCON26 ticket →

Use the map before the project starts

Imagine kicking off a major redesign.

Before opening Figma, building a research plan, or scheduling your first usability test, create your relationship map.

Ask:

• Who can approve this?

• Who can quietly kill it?

• Who can unblock it when things get difficult?

• Whose KPI might this project threaten?

• Who needs to see evidence early rather than at the final presentation?

• Who will advocate for the user when UX isn’t in the room?

Suddenly, stakeholder management stops being something you scramble to do when there is resistance. It becomes part of your strategy from day 1, and perhaps most importantly, you can begin predicting where friction will emerge before the project reaches that point.

The Final Note.

UX professionals already know how to understand people whose perspectives differ from their own. We do it with users every day.

Relationship mapping simply asks us to bring some of that same curiosity to the people inside our organizations.

That change in posture is small but the effect on your influence can be enormous.

Resource Corner

• Nielsen Norman Group, Stakeholder Analysis for UX Projects

• Nielsen Norman Group, UXers Need to Think Like Product Leaders

• Nielsen Norman Group, UX Stakeholder Engagement 101

• Harvard Business Review, You Can’t Sit Out Office Politics

__ The UXU Team

Every trend report this year is telling some version of the same story: the industry is recalibrating away from visual theatrics and toward clarity. Designers are pulling back on decorative flourishes and reducing cognitive load, choosing calmer micro-interactions over gamification and treating simplicity as the actual innovation.

It shows up in survey data too. Recent polling of UX practitioners found that while AI dominates what designers say will shape 2026, the excitement has a sharp caveat attached: most of them also report that stakeholders want to chase AI trends without a clear reason why, which is exactly the kind of pressure that produces noisy, over-engineered interfaces.

In other words, the tools got louder. The best practitioners are getting quieter on purpose.

Two forces are pushing this at once: user fatigue with over-decorated, AI-stuffed interfaces, and regulation — accessibility requirements like the EU’s Accessibility Act are shifting compliance-driven UX from “nice to have” to mandatory, which structurally rewards clarity over flash.

What “calm UX” actually means in practice

• Fewer decision points per screen. Every optional choice is a tax on attention — audit flows for steps that exist because they’re easy to build, not because users need them.

• Transparent AI, with an exit. If a system personalizes or acts on a user’s behalf, it should say so — and give a fast, obvious way to correct or reset it when it gets things wrong. Trust erodes the moment a “smart” feature feels like a trap.

• Accessibility as the default state, not a pass you run at the end. Teams building this way from the start are the ones least disrupted by tightening ADA and EAA enforcement.

Three things to try this week

Here’s the thing; this whole trend is really just the industry rediscovering an idea that already has a name. Human-centered design. The term, and a huge share of the thinking behind everything above, traces back to one person: Don Norman. And he’s headlining UXCON26.

Don Norman, live in Silver Spring

Thursday, October 8, 2026 · Silver Spring Civic Center, MD

If today’s issue resonated, this is the whole conference. Norman will be unpacking human-centered design for the AI era. The same tension between “smarter” and “simpler” we just walked through, from the person who’s been arguing for it since before it was trendy.

Get Your Ticket

Resource Corner

→ Lyssna’s 2026 designer survey — the data behind the AI-fatigue finding above.

→ UX Design Institute’s trend guide — good detail on the compliance angle (EAA, ADA updates).

→ Envato on calm interfaces — the “end of visual theatrics” framing this issue borrows from.

__The UXU Team

Today, we’re excited to announce Dovetail as our Gold Sponsor for UXCON26. 🎉

If you work in UX research, product, design, or customer experience, there’s a good chance Dovetail is already a familiar name.

Dovetail has built its platform around something we care deeply about at UXCON: helping teams get closer to the people they’re building for.

It brings research, customer feedback, support conversations, sales calls, and other customer signals together so teams can turn all of that information into insights they can actually use.

And that feels especially fitting for UXCON26.

Grab Your UXCON26 Ticket

Because this year, we’re talking about what happens beyond the UX team.

Great products rarely come from one brilliant designer or one perfectly executed research study.

They happen when researchers, designers, product managers, engineers, leaders, and the wider organization can understand the same customer, work from the same evidence, challenge each other’s assumptions, and make better decisions together.

That’s the conversation at the heart of UXCON26.

And it’s why having Dovetail join us as a Gold Sponsor feels like such a natural fit.

UX has changed. The way we work has to change with it.

Research is no longer only about running interviews and producing a report.

Design is no longer only about what happens inside Figma.

And building customer-centered products can’t sit with one department.

Teams today are dealing with more customer data, more tools, faster product cycles, and now AI changing how research, analysis, design, and product development happen.

These are exactly the kinds of conversations we want to have when hundreds of people from across UX, product, research, design, engineering, and leadership come together this October.

And we’d love for you to be in that room.

UXCON26 is happening:

📅 Thursday, October 8, 2026
📍 Silver Spring Civic Building at Veterans Plaza, Maryland
⏰ 9:00 AM – 5:00 PM EST

This isn’t a day of sitting quietly through presentation after presentation.

It’s a day to hear from people doing the work, meet people tackling problems similar to yours, challenge how you currently think about UX, discover new approaches and tools, and have the conversations that are much harder to have through a screen.

Whether you’re a researcher, designer, product manager, engineer, UX leader—or simply someone responsible for making products better for the people using them—you’ll find people you can learn from at UXCON26.

Reserve Your Spot

Come meet the UX community this October.

Dovetail joining us as a Gold Sponsor is another exciting step toward making UXCON26 our biggest gathering yet.

But ultimately, the companies on the sponsor wall aren’t what make UXCON special.

The people in the room do.

The unexpected conversation during a coffee break.

The person you meet who has been wrestling with the exact same problem.

The speaker who completely changes how you think about your work.

The introduction that turns into a collaboration, opportunity, friendship, or next career move.

That’s what we’re building toward on October 8.

And if you’ve been thinking about joining us this year, we’d love to see you there.

→ GET YOUR UXCON26 TICKET

__The UXCON Team

Something is shifting in 2026, and it is worth paying attention to.

This issue is about that shift, why it is happening, and what it means for how you design.

In this issue we’ll cover:

• Why the attention economy hit its limit

• What calm technology actually is

• From the attention economy to the intention economy

• What this looks like in real design decisions

• The business case for respecting attention

• Resource Corner

Why the attention economy hit its limit

The attention economy did not fail because it stopped working mechanically. Streaks still drive engagement. Notifications still pull people back. It hit its limit because people noticed, and started to resent it.

The core problem is saturation. Users in 2026 are overwhelmed by overstimulation. Every app is fighting for a slice of a finite, shrinking pool of attention, and the cumulative effect is fatigue. When every product treats a person’s focus as something to extract, the person’s overall experience of their digital life becomes exhausting, and they start looking for the products that do not do this.

There is a cultural current underneath it too.

Accenture identified a phenomenon called “social rewilding,” where people are deliberately disconnecting to prioritize real experiences over digital ones. This is not a fringe wellness trend. It is a mainstream reaction to years of digital overstimulation, and it changes the calculus for every product.

This year, designers are rewarded for judgment rather than novelty, for clarity rather than spectacle. A few extra clicks or one more attention-grab that used to seem clever now simply loses people.

What calm technology actually is

Calm technology is emerging as a deliberate response to digital saturation. The idea is simple to state and hard to practice: design tools that respect our limited attention instead of constantly soliciting it.

The philosophy is not new, it traces back to work at Xerox PARC decades ago, but 2026 is when it stopped being theory and became a competitive advantage. A calm technology approach helps conserve a user’s mental energy and, counterintuitively, creates a more enjoyable experience precisely because it asks less of them.

In practice, calm technology translates into concrete choices. E.g:

• A drastic reduction in notifications.

• More silence, more stillness in the interface.

• Minimalism centered on essential function rather than decoration.

The interface does its job and then gets out of the way, instead of continually tapping the user on the shoulder.

As a result, good UX becomes felt, not seen. A calm product is not one a person raves about for its flashy interface. It is one they use, accomplish what they came for, and leave without friction or residue. The absence of noise is the feature. That is a genuinely different definition of success than the one the field operated on for the last decade, and it requires designers to resist the instinct to add.

What shift are we seeing as a result……

The field is moving from an attention economy to an intention economy.

In the attention economy, the product’s job was to capture your focus and direct it, usually toward more time in the app. In the intention economy, the product’s job is to understand what you actually want to accomplish and help you do it, ideally with as little friction and time as possible. The measure of success flips. Time-in-app used to be the win. Now, for a growing category of products, getting you what you need quickly and letting you go is the win.

This shift is accelerated by agentic UX, where a user delegates a task to an AI rather than navigating to do it themselves. Instead of scrolling through a travel site for an hour, a person hands an agent the mission of organizing a trip. The user’s intention, not their sustained attention, becomes the thing the product is built around. Design is no longer an end in itself but a lever serving user intention.

The question stops being “how do we keep them here longer” and becomes “how do we help them accomplish their actual goal and get on with their life.”

What this looks like in real design decisions

This is not abstract philosophy. It shows up in specific, everyday choices.

🔵 Notifications become intentional, not reflexive
The default of notifying users about everything is being replaced by notifying them only about what genuinely matters to them, when it matters.

🔵 Interfaces respect attention by default
Users now expect control, and interfaces that respect attention perform better. Giving people control over what demands their focus, and defaulting to less rather than more, is becoming an expectation.

🔵 Dark patterns are disappearing on purpose
As users grow more aware of manipulative tactics, designers are intentionally avoiding dark patterns as part of ethical, sustainable design. The attention-extraction toolkit, fake urgency, confirmshaming, roach-motel flows, is not just legally risky now.

🔵 Clarity beats spectacle
The move is toward cognitive clarity over sensory richness. Removing visual clutter, simplifying flows, limiting theatrics. The question shifts from “how do we make this more exciting” to “will this reduce effort.”

Quick pause. This belongs in the room.

🎯 UXCON26 · One Day · The Whole Community

Shifts like this one, from capturing attention to respecting it, from screens to intention, are exactly the conversations the field needs to have out loud, together.

On October 8, 2026, the UX community comes together for a full day built around where this work is really heading. Headlining is Don Norman, who coined the term user experience and at 88 is still challenging this field to design more honestly and more humanely. Alongside him are practitioners from Netflix, The New York Times, Target, UserTesting, and Skylight, hosted by Jeremy Miller of the Beyond UX Design podcast.

Three keynotes. Two panels. One room. The conversations that stay with you.

Secure your UXCON26 ticket →

📦 Resource Corner

Calm Technology by Amber Case
The definitive resource on designing technology that respects attention, from the person who brought the concept into modern practice. The principles are short, memorable, and directly applicable. Start here.

Designing Calm Technology by Amber Case (O’Reilly)
The full book version, with practical patterns for building products that inform without overwhelming. Essential for anyone trying to move from attention-grabbing to attention-respecting design.

UX Design Trends 2026 (UX Design Institute)
Strong overview of the calm, sustainable, and human-centered shift, including the W3C Web Sustainability Guidelines and how they connect to lighter, more respectful design.

Digital Minimalism by Cal Newport
Not a design book, but the clearest articulation of why people are seeking relief from attention-hungry technology. Understanding the user mindset behind “social rewilding” makes you better at designing for it.

The Sustainable Web Manifesto
A short, practical statement of principles for building digital products that are lighter, more honest, and more resilient. Useful for connecting calm design to sustainability in concrete terms.

💭 Final Thought

We spent a decade learning to capture attention. The more interesting challenge, and the one that defines good design now, is learning to deserve it.

Design for the person’s intention, not their attention. Everything good follows from that.

--- The UXU Team

In 2026, most of that production line has an AI agent standing somewhere inside it. The question our community keeps asking us isn’t “should we use AI in research” anymore?” It’s “which parts of the process can an agent actually own, and which parts still need us?”

From Static Maps to Living Systems

The most visible shift is speed. Journey mapping platforms now let researchers describe a scenario or upload raw material ( interview transcripts, survey exports, support logs), and receive a working draft map in minutes, grounded in that actual data rather than assumption. Some tools go further, connecting journey maps and personas directly to external AI agents so the map becomes a live component in a broader workflow rather than a one-time deliverable.

70–90%
Estimated reduction in manual analysis time when AI drafts journey maps from research data, according to ZipTie’s 2026 framework for AI-era journey mapping.

The more interesting shift for design research workflows specifically is that agents are moving beyond “summarize my interviews” into orchestration. Picture an agent that drafts screener criteria, recruits participants, runs unmoderated tasks, checks the resulting sample against a segmentation model, and flags coverage gaps on its own — with a researcher steering direction and making final calls rather than executing every step.

Product analytics platforms have followed a similar path, adding anomaly detection that catches UX regressions or unexpected user paths before they surface as support tickets, now paired with likely root causes linked back to qualitative evidence.

That’s a meaningful change in what a researcher’s day looks like. Less time on logistics and first-pass synthesis, more time on judgment calls: is this segmentation model still right, is this “anomaly” actually meaningful, does this root cause hold up against what we heard in the room.

The Twist Nobody Put on a Journey Map Template

“Are there any models for mapping journeys for non-human actors?”

That’s the question product teams are increasingly asking, and the honest answer is that early models exist but they break most of the assumptions baked into a traditional eight-stage journey map when applied to non-human actors.

AI agents now interact with products directly, through APIs, MCP servers, browser automation, which means your product has two users to design for: the human, and the agent acting on the human’s behalf. The term for this is Agent Experience, or AX, coined by Netlify CEO Mathias Biilmann in early 2025.

The catch: an empathy map doesn’t transfer. An agent doesn’t get frustrated — it returns an error code, retries, or fails silently. As a result, teams may need two parallel artifacts going forward:

• A human-side journey map capturing emotional and behavioral signals, and

• An agent-side map capturing task signals pulled from API, MCP, and integration logs, both feeding the same product decisions.

If your organization builds anything with an API surface, this is worth putting on your 2027 roadmap conversation now, not later.

What This Means for the Role, Not Just the Artifact

Nielsen Norman Group’s 2026 State of UX report is fairly direct about where this leaves practitioners: AI can improve the “jagged” edges of research work and may hit watershed moments for certain activities the way it has for programming, but human direction, curation, and verification remain essential for turning insights into products people actually want. The report’s broader framing is that anyone treating UX as a checklist of deliverables is genuinely exposed — standardized design output is becoming easy to automate. What isn’t easy to automate is curated taste, research-informed contextual understanding, and careful judgment.

Where the Line Actually Sits Right Now

• Let agents own: first-draft synthesis, screener logistics, participant recruitment, coverage checks against segmentation models, anomaly flagging in behavioral data.

• Keep for yourself: problem framing, deciding which anomalies actually matter, validating AI-drafted personas or maps against real transcripts, and any judgment call that determines what the team builds next.

• Watch closely: whether your product has an API/agent surface worth mapping separately from your human journey — Agent Experience is early, but it’s not hypothetical anymore.

• Don’t skip: tracing AI-generated insights back to source data before they go into a deck. “Plausible but shallow” is the exact failure mode practitioners are already reporting.

The teams getting the most out of AI in research right now aren’t the ones with the most tools. They’re the ones who’ve decided, deliberately, where the human checkpoint lives.

UXCON Summer Tech Happy Hour

This month on Aug 20th, join us for a FREE, no-pressure evening to connect with the people shaping UX, product, design, and tech across the DMV at The Urban Winery in Silver Spring, MD.

No panels. No pitch decks. Just good conversation with people who get it.

Why?

✺ Meet practitioners, hiring managers, and collaborators from across the community
✺ Walk away with real leads, referrals, and new connections
✺ Enter to win one of two free UXCON26 tickets
✺ Unlock an exclusive UXCON26 discount, available only to those attending the Happy Hour.

Reserve Your Spot

Resource Corner

1. Levdikova, T. (2026). AI Mapping in UXPressia: Visualize Your Customers’ Journeys. UXPressia Blog. uxpressia.com/blog/ai-mapping

2. ZipTie.dev (2026). How to Map the AI User Journey: A 6-Stage Framework for 2026. ziptie.dev/blog/how-to-map-the-ai-user-journey

3. UXmatters (2026). The Future of UX Research: Navigating AI-Powered Tools and Methods. uxmatters.com

4. O’Sullivan, K. (2026). Your User Journey Map is a Beautiful Lie. Userpilot Blog. userpilot.com/blog/user-journey-map

5. Nielsen Norman Group (2026). State of UX 2026: Design Deeper to Differentiate. nngroup.com/articles/state-of-ux-2026

The UXU Team__

We wanted to build something different.

☆ UXCON26 Tech Happy Hour ☆

Date: Thursday, August 20
Time: 6:00 PM to 9:00 PM EDT
Venue: The Urban Winery of Silver Spring, Silver Spring, MD

This is a FREE, no-pressure evening to connect with the people shaping UX, product, design, and tech across the DMV. No panels. No pitch decks. Just good conversation with people who get it.

Grab a FREE Ticket

Why you should be in the room:

✺ Meet practitioners, hiring managers, and collaborators from across the community
✺ Walk away with real leads, referrals, and new connections
✺ Enter to win one of two free UXCON26 tickets
✺ Unlock an exclusive UXCON26 discount, available only to attendees in person

Whether you’re looking for your next role, new clients, referrals, or just good people to add to your circle, this is the room to be in. Admission is FREE. Drinks and food are on you.

Reserve Your Spot

Come for happy hour. Leave with a fuller network, sharper leads, and maybe a free UXCON26 ticket in hand.

See you there.

__The UXU Team

The data says something uncomfortable. When the Interaction Design Foundation asked hiring managers worldwide to name the top three skills they look for in a UX candidate, roughly 73% chose communication and problem-solving. Proficiency in design tools, the thing so many practitioners spend their energy on, was chosen by only 13%.

Read that gap again. The skills you were told to master are the ones hiring managers care about least. The skills that actually determine who gets hired, who advances, and who stalls are the ones almost nobody deliberately trains for. This issue is about those skills, why they matter more every year, and how to actually get better at them.

In this issue:

• Why tools stopped being the differentiator

• Communication is the whole job in disguise

• The skill that separates juniors from seniors

• Listening: the underrated half of research

• How to actually build these

• Resource Corner

Why tools stopped being the differentiator

There was a time when tool proficiency genuinely set people apart. Knowing Figma well, or Sketch before it, was a real advantage because not everyone had it.

That time is over. Tool fluency has become table stakes, the baseline everyone is assumed to have, not the thing that distinguishes you. And AI has accelerated this dramatically. When AI can generate a wireframe, draft copy, and produce a prototype, the value of being fast in a tool drops. The value of knowing what to build, why, and how to bring people along rises.

This is why the framing among people who hire is shifting. It is not enough to just make things intuitive anymore. With AI, strategy, and stakeholder battles entering the picture, what matters is being able to say, in effect, “yes, I can handle Figma, and I can also handle the room.” The room is the harder part. The room is where careers are actually decided.

The practitioners who struggle most are often the most technically skilled ones who assumed the craft would speak for itself. It does not speak. Someone has to speak for it, and that someone is you, using skills that no tool tutorial ever taught.

Quick pause. This belongs in the room.

🎯 UXCON26 · One Day · The Whole Community

Questions like this one, what it actually takes to make AI trustworthy through design, are exactly the conversations the field needs to have out loud, together.

On October 8, 2026, the UX community comes together for a full day built around where this work is really heading. Headlining is Don Norman, the person who coined the term user experience, at 88 still publishing and still pushing this field to be braver than it is comfortable being. Alongside him are practitioners from Netflix, The New York Times, Target, UserTesting, and Skylight, hosted by Jeremy Miller of the Beyond UX Design podcast.

The conversations that stay with you long after the day ends. You wouldn’t want to miss this.

Secure Your Spot!

Communication is the whole job in disguise

When people hear “communication skills,” they think of presenting well. That is a small slice of it. In UX, communication is woven into nearly everything you do, which is exactly why it matters so much.

Consider where communication actually shows up in the work: building rapport with participants so they give you honest, useful insights in research. Pitching ideas to business stakeholders who do not speak design. Collaborating with engineers to bring designs to life without losing intent in translation. Selling the value of UX itself to management. Facilitating brainstorms that actually go somewhere. Nearly every high-value UX activity depends on communication as the delivery mechanism.

Here is the failure mode, described bluntly by one industry writer: most designers communicate like they are translating ancient hieroglyphics, using jargon that would make a consultant blush and presenting work like they are defending a PhD thesis. The user need was real. The solution was good. But it died in the gap between the work and the ability to explain it in language a non-designer could hold onto.

A useful fix is the “story sandwich.” Structure any explanation of your work as Problem (why we are here), Solution (what we built), Impact (why it matters). Three parts, in plain language. And a test worth using: practice explaining your designs to non-designer friends first. If they get it, stakeholders will too. If they do not, you are not ready to present.

The reframe that matters: a technically average designer who can tell the story behind their choices and defend them will always have more impact than a brilliant one who cannot. That is not cynical. That is how influence works in every organization.

The skill that separates juniors from seniors

If you want to know what actually distinguishes a senior UX practitioner from a junior one, it is rarely craft. Both can often produce similar quality work. The difference is the ability to navigate the business environment around the work.

These soft skills are what separate junior designers from seniors in the role. A junior does the work and hands it over. A senior does the work and manages the room around it: aligns stakeholders, defends decisions with evidence rather than opinion, handles objections without getting defensive, and keeps a project moving through the organizational friction that would otherwise stall it.

Part of this is emotional intelligence, the ability to step outside your own bias, put yourself in the user’s shoes, and genuinely feel their frustration. That empathy is the intellectual core of user-centered design, and it extends to the people you work with, not just the people you design for. Reading a room, sensing when a stakeholder is unconvinced, knowing when to push and when to listen, these are senior-level skills, and they are entirely human.

The other part is the ability to sell a vision. You are constantly pitching to people who do not speak design, which means you need to tell a compelling story about the user’s journey that connects to what those people actually care about. A senior practitioner does not present features. They tell the story of a user, a problem, and an outcome the business recognizes as valuable.

None of this shows up in a tool. All of it shows up in a promotion conversation.

Listening: the underrated half of research

Communication gets talked about as an output skill, how well you speak and present. But the most valuable communication skill in UX is an input skill, and it is badly underrated: active listening.

You will spend enormous amounts of time gathering information, from users, from stakeholders, from teammates. How well you actually hear them determines the quality of everything downstream. In research especially, your attentiveness determines how well you understand user needs, feedback, and insights, all of which drive whether the product you build is any good.

Here is the trap: people assume listening is passive and automatic, that there is nothing difficult about it. That is false. Real active listening requires deliberate, conscious effort and sustained focus. It means fully concentrating on what someone is saying instead of waiting for your turn to talk, resisting the urge to fill silences, and staying curious about answers that do not match what you expected.

The payoff is direct. In research, the difference between a participant who gives you surface answers and one who tells you what they actually think is usually the researcher’s ability to build rapport and listen without leading. In stakeholder work, addressing someone’s real concern requires first genuinely hearing what it is, rather than the objection you assumed they had.

The best practitioners talk less than you would expect. They ask a good question, then get out of the way and actually hear the answer.

How to actually build these

Soft skills feel vague, which makes them feel unlearnable. They are not. They are learned through deliberate practice, just differently than tools.

✅ Practice explaining your work to non-designers
The single highest-leverage habit. Take any project and explain it to someone outside the field until they understand it. The friction you hit is exactly the friction stakeholders feel. Fix it there, in low stakes, before it costs you in a real meeting.

✅ Use structure to make communication reliable
You do not have to be naturally charismatic. Use frameworks. The story sandwich (Problem, Solution, Impact) turns a rambling explanation into a clear one every time. Structure is what makes good communication repeatable rather than dependent on mood.

✅ Treat every meeting as listening practice
In your next stakeholder or research conversation, deliberately talk less. Ask a question, then let the silence sit. Notice how much more you learn. Active listening improves fastest when you consciously practice restraint.

✅ Learn to disagree without defending
When someone pushes back on your work, practice responding with a question (”what’s driving that concern?”) instead of a defense. This one shift, from defending to understanding, is what separates practitioners who build trust from those who create friction.

✅ Find a mentor and become one
These skills transfer through people, not manuals. Seek someone who navigates organizations well and watch how they do it. Then mentor someone junior, because teaching a skill is how you actually understand it. Both accelerate your growth in ways no course can.

📦 Resource Corner

Key Soft Skills to Succeed as a UX Designer (Interaction Design Foundation)
The source of the 73% versus 13% data, with a strong breakdown of why communication underpins nearly every UX activity. Includes a great video from a Head of Product Design on why your ideas need you to speak for them.

Articulating Design Decisions by Tom Greever
The definitive book on communicating design work to stakeholders who do not speak design. Directly addresses the gap between doing good work and getting it approved. If you read one thing on this, read this.

How to Improve Communication Skills as a UX Designer (UX Playbook)
Ten practical, specific steps for handling feedback, presenting ideas, and holding your ground in sprint planning. Actionable rather than abstract.

Just Listen by Mark Goulston
The best book on active listening, written by a psychiatrist. Not a UX book, but the single most useful thing you can read to improve the input side of your communication, which research depends on entirely.

Storytelling for Designers (Nielsen Norman Group)
Practical guidance on using narrative to make your work land with stakeholders. Storytelling is the format that turns a good design decision into one people remember and support.

💭 Final Thought

There is a quiet unfairness in how this field is taught. Newcomers are handed tool tutorials and technique guides, given the clear impression that mastering the craft is the path forward. Then they get into the work and discover that the craft was the easy part, and the actual determinant of their career is a set of skills nobody put on the syllabus.

But there is freedom in knowing this early. The skills that matter most, communicating clearly, listening deeply, telling the story of your work, navigating the people around it, are all learnable. They are not innate gifts reserved for naturally charismatic people. They are practiced, refined through real interactions, and improved deliberately over time, exactly like any craft skill.

The practitioners who pull ahead are not the ones with the deepest tool knowledge. Tools change every year anyway. They are the ones who can take good work and make a room believe in it, who can hear what a user actually means, who can turn a design decision into a story a stakeholder remembers.

You already have the hard skills, or you can get them. Now build the ones that actually decide how far they take you.

Start with the next conversation you have.

--- The UXU Team

→ What is actually changing in the UX field right now and why it feels bigger than usual
→ The one day this year the community comes together to face it honestly
→ Who is in the room and why this lineup is different
→ How to get your ticket

Every few years something changes in this field that is not just a trend.

Not a new tool. Not a methodology debate. Not another article about whether UX is dying or evolving or being absorbed into something else. Something structural. Something that changes what the work actually is, what it requires from the people doing it, and what it means to be genuinely good at it.

That is what is happening right now.

AI is not coming for UX. It is already inside it. Research processes are changing. Design workflows are changing. The way organizations think about who they need on their teams and what those people should be able to do is changing faster than most job descriptions have caught up with. And underneath all of it, a lot of practitioners in this community are sitting with a version of the same question.

What does my career look like from here?

Not in a panicked way. In a serious, I need to actually think about this way. The kind of question that deserves a real answer from people who are operating at the highest level of the field right now, not a thread, not a webinar, not another piece of content to consume and forget.

A real conversation. In a real room. With the right people.

That is UXCON26.

October 8, 2026 · One Day · One Community

This is the day the UX community comes together to have the conversations that actually move things forward. The kind you think about on the drive home. The kind that change how you show up to work on Monday and keep changing how you show up six months later.

The People In The Room

Don Norman

coined the term user experience. He wrote the book sitting on nearly every designer’s shelf. He helped found the world’s first Department of Cognitive Science, became Vice President of Advanced Technology at Apple, and co-founded the Nielsen Norman Group, the firm that shaped how the entire industry thinks about human-centered design. At 88 he is still publishing, still challenging, and still asking this field to be braver than it is comfortable being.

Hearing Don Norman speak in 2026 is not a conference checkbox. It is a once in a career opportunity.

Alongside him:

Niyati Gupta has spent a decade leading design at Google, WhatsApp, and Netflix. Her talk, The Invisible Work of UX, pulls back the curtain on the facilitation, the framing, and the organizational influence that separates good designers from indispensable ones.

Calvin Robertson has built and led design teams at the Federal Reserve Bank, Lowe’s, Best Buy, and Corning. His session on overflowing leadership is about what it looks like when design thinking and genuine care for people drive outcomes at every level of an organization.

Amanda Gelb, founder of Aha Studio, designs high-impact workshops that spark genuine insight and move people toward real action. Her keynote is the kind of thing you find yourself quoting in meetings for months afterward.

Raven Adaramola is a Senior Product Designer at The New York Times, where millions of people open the Games app every single day to play Wordle, Connections, and The Crossword. She designs that experience.

Twisha Shah Brandenburg leads design and product at Target at the intersection of UX, strategy, engineering constraints, and organizational systems, where experience quality gets decided long before anything ships.

Zach Thomas leads cross-functional teams at Skylight modernizing mission-critical federal systems for the DHS, the US Air Force, and the CDC through human-centered design, the kind of work where getting it wrong has real consequences.

Leo Hoar founded the UXR Institute after seeing a gap in advanced, career-focused education for UX researchers. He filled it himself.

Basel Fakhoury co-founded User Interviews, one of the most widely used research recruitment platforms in the industry, now acquired by UserTesting where he serves as SVP.

Don't miss out - Secure your spot

Your Host: Jeremy Miller

Jeremy Miller has been in design since the early 2000s. Through his podcast Beyond UX Design he 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.

He co-founded Edge Kase Design Co. in 2024 and has spent years mentoring practitioners at every stage of their careers. He will be guiding the entire day at UXCON26 and there is no one better suited for it.

UXCON26 is not a content marathon. It 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.

The room is almost full. This is your moment to be in it.

Secure Your Spot!

📚 Resource Corner

→ Beyond UX Design Podcast with Jeremy Miller · The show built around the skills that actually determine how long a UX career lasts
→ Design for a Better World by Don Norman · His most recent book and his most urgent argument for why this work matters
→ Making an Impact Substack by Twisha Shah Brandenburg · Practical thinking on design leadership and organizational influence from one of UXCON26’s speakers

Final Thought

The field is changing. The community is gathering. October 8 is where you show up for both.

The UXU Team

That race is quietly being won, and it is revealing the next problem, which is bigger and more interesting for anyone in UX.

A system can be brilliant and still go unused if people do not trust it. And trust is not built in the model. It is built in the interface, in the moments where a person decides whether to rely on what the AI just told them or quietly abandon it. As one industry analysis put it, if 2023 to 2025 were about proving AI could work, 2026 is about proving it can be trusted. That makes trust a UX problem, and it puts this field in charge of one of the most consequential questions in tech right now.

In this issue:

• Why intelligence stopped being the bottleneck

• The black box problem and why users are done with it

• What explainable design actually looks like

• The transparency paradox nobody warns you about

• Control as the foundation of trust

• Resource Corner

but first…..

UXCON26 Tech Happy Hour - Free to Attend

Thursday, August 20 | 6:00–9:00 PM EDT
The Urban Winery of Silver Spring, MD

Take a night off from the job search, the client hunt, and the portfolio grind. Join us for a relaxed evening of drinks, conversation, and real connection with the people shaping UX, product, design, and tech across the DMV.

Why show up:
✺ Meet practitioners, hiring managers, and collaborators in one room
✺ Walk away with real leads, referrals, and new contacts
✺ Enter to win one of two free UXCON26 tickets
✺ Unlock an exclusive in-person discount on UXCON26, available only at this event

Come for happy hour. Leave with a fuller network

Secure your spot!

Why intelligence stopped being the bottleneck

There is a striking finding worth sitting with. Research shows that experienced developers using AI coding tools actually slow down, even while they believe they are moving faster. The problem is not the intelligence or capability of the tools. It is context, verification, and misplaced confidence.

That gap, between how capable a system is and whether people can actually rely on it, is the whole story of AI UX in 2026. The models got good. What did not automatically come with them is the design that lets a person understand, question, and trust what the system is doing.

The framing that is taking hold across the field is that UX has become the control surface for AI behavior. Tone-aware interfaces, failsafe patterns, and explainable actions position UX, not engineering, as the discipline that governs whether AI can be used safely and confidently. This is a genuine expansion of what UX is responsible for. The interface is no longer just how a person operates a tool. It is how they decide whether to believe it.

And the stakes are concrete. Research across financial services consistently shows that a lack of explanation in critical moments is one of the strongest drivers of user frustration and churn, especially in high-stakes scenarios like payments or onboarding. The issue is rarely the decision the AI made. It is the absence of a meaningful explanation for it.

Quick pause. This belongs in the room.

🎯 UXCON26 · One Day · The Whole Community

Questions like this one, what it actually takes to make AI trustworthy through design, are exactly the conversations the field needs to have out loud, together.

On October 8, 2026, the UX community comes together for a full day built around where this work is really heading. Headlining is Don Norman, the person who coined the term user experience, at 88 still publishing and still pushing this field to be braver than it is comfortable being. Alongside him are practitioners from Netflix, The New York Times, Target, UserTesting, and Skylight, hosted by Jeremy Miller of the Beyond UX Design podcast.

The conversations that stay with you long after the day ends. You wouldn’t want to miss this.

Secure Your Spot!

The black box problem and why users are done with it

For years, AI systems operated as black boxes. Something went in, an answer came out, and the reasoning in between was invisible. Users were expected to simply accept the output.

That era is ending, and users are the ones ending it. People in 2026 increasingly demand to know why an AI made a decision on their behalf. The opaque black box is no longer acceptable, and the reason is simple: trust comes through understanding. You cannot trust what you cannot understand, and you will not rely on a system that makes consequential decisions without telling you why.

This is intuitive if you think about your own behavior. An AI recommends a product, flags a transaction as fraud, rejects an application, or reorders your interface, and your immediate reaction is a question: why? When the system answers that question well, trust builds. When it stays silent, suspicion grows, and suspicion is what makes people abandon a product or switch to a competitor.

There is a defensive benefit too. Clear explanation is a weapon against misinformation and against the quiet erosion of confidence that happens when a system feels arbitrary. A person who understands why they are seeing something is far less likely to feel manipulated by it.

What explainable design actually looks like

Here is the good news: explainability does not require exposing model architecture or probability scores. Users do not need any of that. They need a clear, human answer to a simple question.

Often, a single sentence is enough. “We suggest this because you liked that” can defuse mistrust entirely. The pattern is straightforward: connect the output to a cause the user can recognize. Show the reasoning in plain language, at the moment it matters, without drowning them in detail.

A few patterns that are emerging as standards:

🔵 The “why am I seeing this” layer. A small, accessible explanation attached to any AI-driven decision or recommendation. Not a wall of text. One clear reason, available when the user wants it.

🔵 Mutual verification. Before executing something consequential, a simple “Did I get that right?” confirmation. This turns a one-way command into a conversation and gives the user a moment of control before the system acts.

🔵 Confidence signaling. Showing when the system is certain and when it is guessing. A system that admits uncertainty is trusted more than one that states everything with equal, unearned confidence. Sounding sure when you are not is exactly how trust breaks.

🔵 Traceable reasoning. For higher-stakes decisions, showing the cause-and-effect chain: what inputs led to this output. When users can see that reasoning, trust increases significantly. This does not mean technical depth. It means a legible path from input to result.

The guiding principle across all of these, and one worth writing on a wall: do not simplify complexity. Make complexity understandable. Those are different jobs. Hiding complexity leaves users in the dark. Making it understandable respects both their intelligence and their need to trust the system.

The transparency paradox nobody warns you about

Here is where it gets genuinely hard, and where good UX judgment separates from box-checking.

Regulation increasingly requires transparency, and the well-meaning response is to add more of it. Everywhere. Cookie banners, data-processing permissions, AI disclosures, consent toggles, terms and conditions. Each element is individually compliant. Together, they create cognitive overload.

The result is the opposite of what transparency was supposed to achieve. Users get pushed through dense screens of legal language and endless toggles, and instead of informed consent, you get mechanical behavior: scroll, accept, continue. Nobody read anything. Nobody understood anything. The transparency was technically present and functionally useless.

This is the paradox. More transparency does not equal more trust. Piling on disclosures produces the same glazed-over dismissal as hiding everything did. The interface has to simultaneously reduce friction and increase genuine accountability, which is one of the hardest design problems in the field right now.

The way through is not more explanation. It is better-placed explanation. Answer the specific question the user has, at the specific moment they have it, in language they actually process. A single clear explanation at the point of a real decision beats ten dense disclosure screens nobody reads. This is UX craft applied to trust: knowing what to surface, when, and how much, so understanding actually happens instead of just being technically offered.

Control as the foundation of trust

Explanation answers “why did it do that.” Control answers “what can I do about it.” Both are required, and control is the one teams most often forget.

People trust systems they can steer. The design principles emerging around this are concrete:

▸ Always offer an exit. Any AI action should be cancelable or reversible. A person who knows they can undo something engages far more freely than one who fears an irreversible mistake.

▸ Let people correct the system. A way to tweak an AI result and see how it adjusts turns a frustrating black box into a collaborator. The frustration users report most often is systems that respond but do not seem to listen.

▸ Offer a sandbox. Letting people test an AI’s proposal without real consequences builds confidence before commitment. They learn what the system does in a space where being wrong costs nothing.

▸ Make adaptation visible and optional. When a system personalizes or adapts, tell the user it is happening and let them turn it off. “This adapts based on your activity, and here is how to change it” is the difference between helpful and unsettling.

The through-line is agency. Trust is not blind faith in the system. It is informed reliance, the confidence that comes from understanding what the system does and knowing you remain in control of it. That combination, understanding plus control, is what UX is now responsible for delivering.

📦 Resource Corner

Explainable AI UI Design (XAI) (Eleken)
The clearest practical guide on why explainability is a UX problem, not just a technical one, with emerging design patterns and real examples. Start here if this topic is new to you.

Designing Trust in AI Products (Standard Beagle)
Strong on the three levels of transparency, algorithmic, interaction, and social, and how each contributes to what users perceive as honesty. Grounded in real product work.

UX for AI Compliance and Regulatory UX (Markswebb)
The best resource on the transparency paradox, how to explain AI decisions and gather consent without overwhelming users. Essential if you work on anything regulated.

Trust Is the New Benchmark for AI (CMSWire)
A sharp overview of why UX, not IT, is becoming the discipline that governs safe AI autonomy. Good for understanding the strategic shift and where UX gains influence.

People + AI Guidebook (Google PAIR)
The foundational, free resource on designing human-centered AI. Deep, practical guidance on explainability, trust, and feedback that remains one of the best references in the field.

💭 Final Thought

There is something worth appreciating in this shift. For years, UX had to argue for its own relevance in the AI conversation, often reduced to making the model’s output look nice after the important decisions were made elsewhere.

That has flipped. Trust is now the deciding factor in whether AI products succeed, and trust is built almost entirely through the things UX has always been about: understanding what a person needs, anticipating their questions, respecting their agency, and making the complex feel clear. The most powerful model in the world fails if people do not trust it enough to rely on it, and whether they trust it is a design outcome.

That is a real responsibility, and it is a genuine opportunity. The practitioners who learn to design for trust, explanation that lands, transparency that does not overwhelm, and control that feels real, are going to be central to how AI actually gets adopted, not decorative to it.

The question users are asking is “why should I trust this?”

Answering it well is the job now. And it has always been exactly the kind of thing UX does best.

--- The UXU Team

Buried in the role-by-role breakdown is a number every UX professional should sit with: Design (UX/UI) sits at just 14% Level 3–4 adoption - behind IT Admin (24%), Executive/C-suite (23%), and Product Management (15%). We’re not leading this shift. We’re trailing the roles closest to infrastructure and decision-making.

Here’s what the data says, and what to actually do with it.

By the numbers

• Design (UX/UI) at AI maturity Level 3–4 - 14%

• Customer experience as a top AI investment reason (Level 3–4 orgs) - 37% (+8pp)

• Owner/CEO respondents at Level 3–4 vs. individual contributors - 39% vs. 6%

• Decision makers who say investment outpaces employee readiness (Level 4) - 68%

• “Automating repetitive tasks” as an AI workflow, Level 1–2 → Level 3–4+ - 18pp

1. UX owns the exact metric mature orgs now chase

At Level 1 and 2, the business case for AI is cost and productivity. At Level 3 and 4, customer experience becomes the fastest-rising motivation for investment. That’s a UX conversation, not an engineering one, Create but it will go to whoever shows up with the framing and the metrics first.

Career move: Stop pitching AI projects as “efficiency wins.” Reframe your UX/AI work in terms of customer experience outcomes and new capability creation, the two reasons rising fastest among the most mature organizations. That’s the language leadership is already starting to reward.

Before we continue…..

BECOME A UXCON26 VOLUNTEER

🚨 UXCON26 is powered by more than speakers and sessions.

It's powered by the people behind the scenes.

We're looking for passionate volunteers who want to experience one of the biggest UX events from the inside. Whether you're growing your network, building real event experience, or looking to contribute to the UX community, this is your chance.

Learn. Connect. Make an impact.

If you've ever wanted to be part of something bigger than yourself, this is your moment.

📅 October 8, 2026
📍 Silver Spring Civic Center
⏰ 9:00 AM – 5:00 PM

Applications are now open. Join the team that makes UXCON26 unforgettable.

JOIN THE TEAM

back to where we stopped…….

2. Seniority - not tool skill - is the strongest signal of AI maturity

Owner/CEO respondents are more than 6x more likely than individual contributors to be operating at Level 3 or 4. This holds across every region and industry in the dataset. The gap isn’t about who knows the tools best - ICs are often the heaviest daily users. It’s about who has the authority to embed AI into a workflow, not just use it inside one.

Career move: If you’re an IC, your path to visible impact isn’t “use more AI tools” — it’s proposing a workflow-level change and getting a decision-maker to sponsor it. Attach yourself to governance conversations (AI policy, tool standardization, measurement frameworks) where UX has real standing to contribute.

3. The work is shifting from craft tasks to “systems work”

As organizations mature, individual tasks like writing, researching, and brainstorming actually see AI usage decline in relative share. What rises sharply: automating repetitive workflows (+18pp), routing work across tools (+15pp), and generating technical outputs (+12pp). Mature orgs haven’t replaced individual craft — they’ve layered systems thinking on top of it.

Career move: The differentiated skill isn’t “I can prompt an AI to draft copy” — everyone can do that now. It’s designing the workflow: how research findings route into design decisions, how AI-assisted outputs get reviewed, where the handoffs are. That’s a UX systems-design skill, and it’s rare.

4. “Too many AI tools” is now the fastest-growing complaint — and a UX problem in disguise

Among the most mature organizations, “too many AI tools” jumped +14pp as a top adoption challenge - the single largest increase of any listed friction point. Fragmented, poorly integrated tools are exactly the kind of experience problem UX research and IA methods are built to diagnose.

Career move: Position yourself as the person who audits and rationalizes the AI tool stack, not just the person who designs the next feature. Internal tool experience audits are an underexploited niche right now, and almost no one outside UX is positioned to do them well.

5. Mid-market is where the action is - not enterprise

Mid-market companies (500–999 employees) lead Level 3–4 adoption at 17%, while enterprise (5,000+) trails at just 7%. Scale brings more structure, but also more barriers — enterprise UX roles may see slower AI-driven change than mid-market ones.

Career move: If you’re job hunting or freelancing and want AI-forward UX work, mid-market companies (roughly 500–1,000 employees) are statistically your best bet right now, not the household-name enterprises.

This week’s action items

• Reframe one current AI-adjacent project around customer experience or capability impact, not efficiency.

• Identify one workflow (not one task) you could redesign with AI - and who needs to sponsor it.

• Ask your org: how many AI tools are we actually running, and does anyone own that inventory?

• If you’re job-seeking, filter your search toward mid-market companies (500–1,000 employees).

Resource corner

→ Full report: Notion, The Great Renovation: Inside the AI Transformation (2026), fielded via Qualtrics, N=6,118 across 10 markets.

→ Notion’s AI Transformation Model:

The UXU Team

→ What is actually happening to UX careers right now and why it feels different this time
→ Why most advice is not helping
→ A four-hour working session built for exactly this moment
→ How to get your spot before it fills

Something shifted in the last two years and most people felt it before they could name it.

The applications are going out. The responses are not coming back. Practitioners with real experience, strong portfolios, and genuine skill are sitting with the same quiet panic: what changed and why is the old playbook not working anymore?

It is not your portfolio. It is not your case studies. It is not your years of experience.

It is that the market started asking a different question while most practitioners were still answering the old one.

The question used to be: can you do the work?

The question now is: can you position yourself inside an economy where AI is already part of the process, where roles are being redefined faster than job descriptions can keep up, and where the practitioners getting hired are the ones who know how to communicate their value in a language the new market actually understands?

That is a different question. And most people have not been given the tools to answer it.

Why Most Advice Is Making It Worse

You have read the articles. You have watched the videos. You have updated your LinkedIn headline based on something you saw in a thread and waited to see if it made a difference.

It probably did not. Not because the advice was wrong. Because advice is not practice. Reading about how to reposition yourself is not the same as actually doing it, on your real resume, with real tools, in a room where someone who has hired people through this economy can tell you in real time what is landing and what is not.

The practitioners who are breaking through right now are not the ones who found the right article. They are the ones who did the work. Specifically. Intentionally. With the right people in the room.

That room exists on July 23.

HAPPENING TOMORROW

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

4 hours. Your real resume. Your real pitch. Your real positioning. Rebuilt in real time using AI tools that are already reshaping how hiring works, led by three founders who have hired, been hired, pivoted, 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 coming to give a talk. They are coming to sit with you and work on the thing that actually matters right now: how you show up to a market that has already moved on and make sure it cannot afford to move on without you.

You will not leave with notes to review later. You will leave with something finished. A sharper read on where your skills belong in this economy. Language that lands in interviews and networking conversations. And one specific next step you chose before you walked out the door.

No jargon. No theory. No slides you forget by Thursday. Just a room full of practitioners who are serious about what comes next, doing the work together.

RSVP HERE!

Spots are limited. This one fills fast and there is no virtual option.

RSVP HERE!

What You Walk Away With

✅ A finished output 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

📚 Resource Corner

→ 10 Best AI Resume Tailoring Tools in 2026 · Which tools actually pass ATS screening and which are noise
→ The 6 Best AI Resume Builders in 2026 · Free and paid options worth exploring before July 23
→ 4 AI Tools Design Job Seekers Need in 2026 · Built specifically for practitioners navigating the AI job market right now

Final Thought

The market is not waiting for you to feel ready. Tommorrow is how you get there.

The UXU Team

Two people do genuinely similar work. Same years in, same quality of output, both running research, both shipping design, both sitting in the same kinds of meetings. One of them makes $108,000. The other makes closer to $148,000. Neither is more talented. The difference is not effort or skill. It is that one of them understands how the market names and prices what they do, and the other does not.

The 2026 salary data makes this gap impossible to ignore, and it also makes it fixable. This issue is about understanding where the money actually sits in UX right now, and how to make sure your work is positioned to be paid for what it is worth.

In this issue:

• The title trap that anchors people to the wrong number

• Why research is not the low-paid path anymore

• The skills that genuinely move your salary

• Where the highest ceilings are hiding

• How your employer shapes your pay more than you think

• Resource Corner

The title trap that anchors people to the wrong number

The most expensive mistake in UX compensation is treating your title as a label instead of a price tag.

To people outside the field, “UX designer,” “UX researcher,” and “product designer” sound like the same job with different words. They are not, and the market pays them very differently. Across those three titles sits a combined salary gap of about $40,000, with the US range running from $77,000 to $175,000 depending on which one you land under.

The word doing the heaviest lifting right now is “product designer.” At most tech companies, that title has come to mean someone who owns the full arc of a problem, from research through to shipped interface. Because it signals ownership rather than execution of one slice, it carries the highest median of the common titles, around $118,000, and the gap widens at senior levels, where product designers clear $176,000 against roughly $150,000 for senior UX designers.

The trap is subtle. If your title says “UX designer” but you are actually doing research, strategy, and end-to-end design, you are likely anchored to a lower band than your work justifies. Recruiters see this constantly: a company searches “UX designer salary,” uses the median, and budgets for a role that is genuinely worth $30,000 more. The fix is not to inflate your title dishonestly. It is to make sure the title you claim reflects the fullest accurate description of what you actually own.

Quick pause. This one is directly relevant.

3 DAYS TO GO

🎯 Upskill AI Workshop · July 23, 2026 · Silver Spring

We made it easier to join.

We’ve reduced the workshop fee to just $49.99 because practical AI skills shouldn’t be out of reach for the people who need them most.

The clearest rising salary premium in UX right now belongs to practitioners who can genuinely fold AI into their workflow, not just prompt for a draft here and there. That is a 10–15% premium tied to a skill many people in the field have not actually built yet.

This workshop is a hands-on, four-hour session built for exactly that gap. No theory, no trend lists. Real work moving you from occasional AI use into workflow-level fluency across research synthesis, journey mapping, and design systems, with feedback from people who do this for a living.

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

Save Your Seat

Why research is not the low-paid path anymore

A stubborn myth in UX is that moving toward research means moving down in pay. In 2026, that is simply wrong, and believing it is expensive.

UX researchers earn a median around $105,000, competitive with generalist designers, and specialized researchers climb well past that, into the $130,000 range. More importantly, the direction is upward. The layoffs of 2023 cut a lot of dedicated research functions, and companies are now discovering the cost of that: product teams making worse decisions without anyone rigorously understanding the user. Some are rehiring researchers outright. Others are folding research into the design role and paying more for the combination.

Either way, the research premium is climbing. Designers who bring formal research skills, real usability testing, interviews, and structured analysis, earn 10 to 15% more than those who do not. This is one of the clearest and most durable premiums in the current market, and it is one many practitioners actively hide by burying their research work under a generalist framing.

If you have genuine research capability, it should be central to how you present yourself, not a footnote. Whether you position as a researcher or a designer who does rigorous research, making that skill visible is one of the most reliable ways to move your band.

The skills that genuinely move your salary

Here is a hard truth about tools: everyone has Figma now. Expert-level Figma is expected, not rewarded. It is the price of entry, not a differentiator. The skills that actually shift your number in 2026 are the ones that connect design outward, to code, to data, and to AI.

The premiums are specific and worth knowing:

▸ Front-end development (HTML, CSS, JavaScript, Webflow) adds the most, roughly 15 to 25%, because it collapses the gap between design and what actually ships.

▸ AI integration into your real workflow, not just prompting for drafts, carries a 10 to 15% premium, and it is rising fast because so few practitioners have genuinely built it into how they work.

▸ Data analysis, the ability to read behavioral data and translate it into design decisions, adds another 10 to 15% and compounds directly with research skills.

The mistake most people make is spreading thin across all of these, ending up with surface familiarity in each and a premium in none. The better strategy is to pick one that sits adjacent to your existing strength and go deep enough to name it on your resume with real evidence behind it. One demonstrable premium skill beats a scattered list every time.

Where the highest ceilings are hiding

If you want a specialization with genuine room to grow, one of the strongest in 2026 is also one of the least visible: design systems.

Design systems engineers build the shared infrastructure that lets an entire organization ship consistently, the component libraries, the tokens, the documentation, the bridge between design and engineering. The work requires both design sensibility and real technical depth, which makes qualified people rare, and rare is what the market pays for. The ceiling reflects it: Head of Design Systems roles run $160,000 to $200,000 and beyond, because at scale a design system is treated as strategic infrastructure, not a support function.

The appeal here is not just the number. It is that this lane has far less supply-side competition than visual or generalist design, where thousands of similar portfolios compete for the same roles. If you find yourself drawn to the systematic, technical side of the work more than the individual screen, this is an underexploited path with a high ceiling. You can start where you are, by owning a piece of your current team’s system, and build genuine expertise from there.

How your employer shapes your pay more than you think

Two practitioners with identical skills and titles can still end up far apart based on a single factor most people underweight when job hunting: where they work.

Industry alone can shift the same role by $20,000 to $40,000. Technology and SaaS pay the most, with senior product designers regularly clearing $150,000. Fintech pays strongly because the products are complex and compliance-heavy. Healthcare and medtech are growing fast and increasingly well-compensated. Agencies tend to pay lower base salaries but offer broader project exposure, which has its own value early in a career.

The deeper factor is design maturity. At companies where design genuinely drives decisions, UX practitioners earn 85 to 95% of what software engineers make at the same level. At companies where design is a supporting function that makes things look nice after the decisions are made, that gap widens sharply, and so does the ceiling on how far you can grow.

This is why a slightly lower offer at a design-mature organization often beats a higher one where design is decoration. Not just for pay growth, but for whether the work is any good and whether you will still want to be there in two years. The question worth asking in every interview: who does design report to, and at what point in a project does design get involved?

📦 Resource Corner

UX Designer Salary Guide 2026 (KORE1)
Written by a recruiter who hears the budget number before the candidate does. The most honest breakdown of how title and scope create the $25,000 to $40,000 gaps in this field. Read it before any negotiation.

UX Salary by Specialisation (UX Designer Salary)
Independent, current data on how each specialization pays, from UI to research to design systems, with the reasoning behind every gap and a calculator to benchmark yourself.

The 2026 UX Salary Report (User Interviews and Levels.fyi)
Nearly 20,000 real salary records across designer, researcher, and research-ops roles. The most rigorous dataset available for understanding where you actually stand.

UX/UI Designer Salary 2026 (Webflow)
The clearest breakdown of which specific skills carry which premiums, with real percentages. Practical for deciding what to learn next.

The UX Job Market in 2026 (UX Design Institute)
Which roles and skills are in highest demand, backed by the 2026 Figma design-leader survey. Useful for positioning yourself where the market is actually moving.

💭 Final Thought

The uncomfortable lesson in all of this is that being good at the work and being paid for the work are two different skills, and the field trains people well in the first while barely mentioning the second.

The healthcare researcher who started at $148,000 instead of $120,000 did not become more capable in the span of a few conversations. Someone simply reframed her work in the language the market already rewards. The value was always there. What changed was whether it was visible.

That is the real takeaway. The market in 2026 is paying genuine premiums for research rigor, technical fluency, AI integration, and systems thinking. If you have any of those and they are hidden inside a vague title or a generalist framing, you are leaving money on the table that is already yours to claim.

Know what your work is actually worth. Then make sure the words you use for it, everywhere from your resume to your own head, finally agree.

--- The UXU Team

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