Header
← Field Notes

The Deliverable Got Cheaper. The Judgment Didn't.

AI didn't automate the thinking. It automated the part that looked like thinking — and now the gap is showing.

  • UX Design
  • Artificial Intelligence
Read on LinkedIn
Nate Wearin

Nate Wearin

The Fuego Team

6.5.26

I've been running Fuego UX for six years now. Like a lot of you, I've spent the last year getting the same questions from everyone around me. Clients, prospects, my own team, people we're trying to hire, peers in the community. What does AI mean for our work. What's going to change. Are we going to be okay.

Here's where I've landed.

The old way of working is changing

For decades, the interfacewasthe product. The slide deckwasthe strategy. The dashboardwasthe data. The CRMwasthe customer relationship. The tool and the work were the same thing, and we stopped noticing they didn't have to be.

That's changing now.

As AI becomes a real part of how software works, the screen becomes just one way to look at something, not the thing itself. The deck becomes an output. The dashboard becomes a view. The real product is what sits underneath.

AI is showing what teams have been skipping

Most teams I talk to are moving faster than ever. But the people on the receiving end aren't feeling it.

That's not a technology problem. That's a people problem.

AI can write a persona, map a user journey, outline a service plan. That's useful. But it can also make a team feel like they've done the work when they haven't. The document looks like research. The prototype looks like design. The deck looks like strategy. If you skip the part where you actually understand people, AI won't save you. It just makes the gap harder to see.

What this means for each discipline

  • User Research

    AI will write the personas. It won't do the interviews. The people who go out, talk to real users, and bring back something genuine are going to be very hard to replace.

  • UX Design

    Building screens is no longer the hard part. The real job is understanding what a product is and how it should work across different situations. That's a thinking problem, not a visual one.

  • Product Strategy

    If the screen is just a view, someone has to figure out what's underneath it. The goals, the logic, the decisions that hold it all together. The deck is an output. The thinking is the product.

  • Branding & Service Design

    AI can make a lot of content fast. It can't decide what a brand actually means. Keeping a consistent voice and feel across AI-generated touchpoints is a human job. Agencies that do that well will be valuable.

  • Design Engineering

    The products being built now need people who understand both what users need and how the system behind it works. That mix is rare and it's getting more valuable.

How I'm thinking about this for our practice

Stop protecting the deliverable. Start owning the judgment. AI can speed up the work. But someone still has to decide what's worth building, whether it actually helped people, and what to do next. That part doesn't automate.

The teams that win won't be the ones that produce the most. They'll be the ones that learned the most and made something people actually trust.

Keep Reading

Need this kind of thinking on your team?

From research and strategy to design and development, we help teams create digital experiences grounded in real user needs.

Let's chat

Deliberately, over reps: study work you admire and articulate why it works, seek honest critique, ship real things and watch how people respond, and write your reasoning down so it becomes explicit. Taste isn't mystical — it's pattern recognition built from exposure and feedback. The faster you close the loop between decision and outcome, the faster it grows.

It's learned. What looks like innate taste is usually accumulated judgment — thousands of small comparisons about what works and what doesn't. AI can hand you a first draft instantly, but knowing what's missing is a trained skill, and it's the one that increasingly separates designers. That's the good news: it's buildable.

Do the thinking first, then bring in AI — draft your own direction, use AI to generate options and pressure-test it, and feel free to ignore most of what it returns. Outsourcing the judgment is where skills atrophy; outsourcing the grunt work is where they compound. Treat AI as a fast collaborator, not the decision-maker.

The judgment, not the artifact. You're paying for the research that reveals what to build, the strategy that decides what's worth building, and the experienced eye that knows whether the fast-generated version is actually right. Production got cheap; knowing what's worth producing didn't.