A position on product design
Design is not UI.
Prompt is not strategy.
UI is what a product looks like. Design is the judgment about what it should be, and why.
AI has changed how we build. It accelerates prototyping, explores variations instantly, and handles repetitive work that once consumed entire days. It is genuinely useful.
Something important is getting lost in the excitement.
Scroll to see why the difference matters.
•10 min read
What AI does brilliantly
- •Creates visual options in seconds
- •Explores design variations at scale
- •Handles repetitive tasks
- •Speeds up the path from idea to screen
- •Lowers the cost of trying ten ideas instead of one
These tools are part of how we work now. They have made our cycles shorter and our exploration wider.
What follows is a closer look at the decisions these tools cannot make for you, and why that matters for your product.
This is the biggest shift in design tools since the move to the browser. The teams that win still do their own thinking. They use AI to act on it faster.
UI is the visible surface of decisions made one and two layers above it.
The core misunderstanding
Common beliefs
Design = screens
Visual outputs as the goal
UX = UI
Mixing up experience with interface
Strategy = good prompts
Letting tools do the thinking
AI output = correct output
Accepting suggestions without question
Reality
Design = decision-making
Choosing what to build and why, based on evidence
UX = systems and behavior
Seen in what users actually do
Strategy = trade-offs and intent
Weighing evidence with purpose
AI output = a guess
Something to test against real data
Fluent output reads as correct output. The more confident a result looks, the less anyone checks it, which is exactly when judgment matters most.
The first list can be automated. The second is where products are won or lost.
UX is not UI.
Understanding the distinction
UI · User Interface
UI is an output: a surface, a skin. It's what users see and touch. It can be templated, generated, and styled from existing patterns.
Buttons, colors, layouts, typography, spacing, icons.
UX · User Experience
UX is a system of decisions. The logic beneath the surface. It determines what exists, why it exists, and how it behaves when things go wrong.
Information architecture, user flows, error handling, edge cases, mental models, cognitive load.
A polished interface routinely hides a broken experience. The surface tells you nothing about the structure beneath.
When organizations mix up UI with UX, they focus on appearance while the underlying experience suffers. Users feel this immediately, even when they can't explain it.
Consistency is more than matching visuals. It means the same logic and the same care show up everywhere users touch your product.
You can automate UI.
You cannot automate the judgment that decides what to build.
The design process
Research
Gathering data about the problem space
↓Synthesis
Finding patterns in evidence
↓Decisions
Choosing directions informed by data
↓Validation
Testing assumptions with real users
↓Outcomes
Measuring impact against success criteria
Each stage requires human judgment backed by data. AI can help with the outputs at any stage. The decisions between stages are still human work.
A prompt can produce any of the dots. Strategy is knowing which one is worth picking.
Prompting is execution.
Strategy is intent.
Understanding the difference
A prompt is an instruction. Strategy is knowing which instructions are worth giving in the first place.
AI-first teams often confuse better prompts with better thinking. But a more sophisticated prompt cannot compensate for unclear goals, untested assumptions, or missing data about user behavior.
A better prompt cannot fix a missing strategy.
Prompts do not define goals.
They execute within given constraints.
Prompts do not weigh trade-offs.
They optimize for specified outputs.
Prompts do not know your users.
They pattern-match from training data, not lived experience.
Prompts do not maintain consistency.
Tools can store context, but they do not carry the intent behind your product from one decision to the next.
Strategy requires understanding what success looks like before you begin. No prompt can provide that for you.
Decide sits upstream of everything. The other stages execute against it.
What strategy actually decides.
The calls a prompt cannot make for you
Strategy is not a longer prompt or a smarter model. It is a small set of decisions made before any work begins.
These decisions are mostly subtraction. They narrow the field so the team can move with intent. Prompts can only add.
What problem is worth solving this quarter.
Out of every possible direction, you pick one. That choice is upstream of every prompt anyone will ever write.
Which users to disappoint on purpose.
You cannot serve everyone equally. Choosing who matters most is a judgment call, not an output.
What to cut so the rest can be great.
Most product work is subtraction. AI is built to add. The two pull in opposite directions.
How success will be measured before work begins.
If you cannot say what good looks like up front, no amount of execution will tell you when you have arrived.
AI has no accountability.
Designers do.
The accountability gap
When a product fails, when users churn, when support costs spike, when the market rejects your solution, someone needs to diagnose why.
That diagnosis falls to people with product judgment. They've seen patterns across products, felt the weight of failed launches, and learned what the data means in context.
Strategic judgment is earned, not installed.
Polished execution used to set teams apart. AI made it cheap overnight. What's left to defend is the judgment behind the decision: which problem to solve, who to disappoint, and what "good" looks like before the work begins.
A more capable model does not close this gap. However good the output gets, judgment still carries accountability, and accountability has to belong to someone.
Accountability cannot be automated. Someone still has to answer for the decision when it lands in front of users.
Bad design decisions compound.
Understanding design debt
Design debt works like technical debt. Every shortcut, every "we'll fix it later," every decision made without data adds up over time.
The cost shows up in the metrics: support tickets pile up, churn increases quietly, time-on-task grows, satisfaction drops. Teams spend their time on rework instead of building anything new.
Most users never mention the inconsistency. One day they just stop showing up.
Consistency takes clear human intent across every interaction. Only people who understand the whole can make the parts work together.
How design debt accumulates
Each row above was a decision that felt fast at the time. The bars show the running total: without strategy, most of the work ends up as rework instead of shipped value.
Same team, same calendar. The work that thinks first compounds; the work that ships first repeats.
The cost of skipping strategy.
Two timelines, same six months
Without strategy
- −First version ships in days.
- −Second version is a rebuild, not a refinement.
- −Support tickets cluster around flows nobody validated.
- −Churn rises quietly while the team ships features.
With strategy
- +First version ships a little later.
- +Each release builds on the last instead of replacing it.
- +Support volume stays flat as the product grows.
- +Retention compounds because the foundation holds.
Speed without strategy is just faster rework. The team that thinks first ships less, sooner, and keeps shipping.
If you design products for a living, none of this is news. You've felt the tension between what you know the product needs and what the timeline allows, between evidence and assumption, between craft and expedience. The hard part is talking about these problems with people who haven't felt them.
Shifting the conversation.
From aesthetics to outcomes
Evidence over opinion.
Usability recordings of real users struggling with "simple" flows accomplish what no slide deck can. When design decisions are backed by measurable impact on conversion, satisfaction, and time-to-task, the conversation shifts from taste to evidence. Fixing usability in production costs far more than getting it right in design. The exact number is hard to pin down, but the direction is not.
Partner, not order-taker.
Product managers own the why: business goals, customer problems, what to build. Designers own the how: interface, interactions, user journey. When UX is involved in discovery rather than just execution, the inputs improve. Better inputs, better outputs.
Edge cases are where products break.
Stakeholders focus on the happy path. Designers specialize in what happens when things go wrong. When a stakeholder hands you a finished solution, bring back two or three alternatives that solve the same problem. It changes the relationship. Edge cases ignored today become support tickets filed tomorrow.
Internal voices are not enough.
Examples of design paying off at other companies carry weight that no internal pitch can. Competitors with better UX did not arrive there by accident. A design system gives everyone a shared language, so the same debate does not have to happen twice.
Phrases that shift the conversation
When design keeps moving the numbers, stakeholders stop prescribing solutions and start relying on expertise.
What this site is (and isn't)
This is not a case against AI.
AI is evolving fast, and we welcome it. These tools make our work smoother: faster prototyping, wider exploration, fewer boring tasks eating up our days.
We're making the case for involving people with real product judgment, not anyone whose claim to design ends at access to the tools. Tenure is not the line. Strategic thinking is.
This is pro-expertise.
Years of practice, failed experiments, shipped results, and deep user understanding cannot be prompted. Confusing tool access with real expertise is where products go wrong.
This site is:
- +Pro intelligent use of tools
- +Pro data-informed decision-making
- +Pro design as a measurable discipline
- +Pro accountability in product decisions
This site is not:
- −Anti-automation
- −Anti-efficiency
- −Anti-progress
AI amplifies thinking. It cannot supply it.
AI accelerates Evidence and Execution. Goals, Decisions, and Measurement stay with you.
Where AI actually belongs in the strategy loop.
A simple map
Strategy is a loop, not a step. AI is excellent at one stage and useful in another. The other three are still yours.
01
Goals
Your call
Deciding what to pursue and what to ignore.
02
Evidence
AI helps
Synthesis, summarization, pattern surfacing on data humans collected.
03
Decisions
Your call
Weighing trade-offs against context AI cannot see.
04
Execution
AI excels
Producing artifacts, variations, prototypes, and first drafts at speed.
05
Measurement
Your call
Judging whether the outcome served the goal you set.
When teams let AI drift into Goals, Decisions, or Measurement, the loop breaks. The product starts optimizing for what is easy to generate instead of what is worth building.
The trap is that this drift feels like progress. Every stage you automate removes friction today, so the speed is real. But the friction you removed was judgment, and its absence compounds: the product gets quicker to produce and slower to trust.
The stages do not defend themselves. A team can keep Goals, Decisions, and Measurement on the chart and still stop doing the work inside them. The goal defaults to whatever is easiest to generate, the decision shrinks to an approval, and the measure becomes whether it shipped. Every box stays filled while the loop goes hollow.
What that same drift does to the person doing the work is a different argument. We make it in the companion piece to this essay, It's OK to be human.
In closing
Design is how strategy becomes reality.
Every product is the sum of decisions made visible to a user. Some were made consciously, by people who understood the trade-offs. Others were made by default, by tools, by rushing, by not asking questions.
Users experience both. They just can't tell you which is which.
Experience still matters.
AI is a valuable tool and we use it daily. Judgment is not a tool. It is earned over years of shipping work and watching how it lands.
If you keep having this argument at work, share this page and let it make the case for you.
The companion piece
It's OK to be humanThis essay takes the work's side of the argument: what gets built and who decides. The companion takes the person's side: what AI means for you, not just your product. If that is the question on your mind, read it next.
Further reading
- Des Traynor: Product Strategy Means Saying No on why real product strategy is turning down good ideas, again and again.
- Jared Spool: Design is the Rendering of Intent on design as intent made real: whoever makes the decisions is doing the design.
- Roger Martin: Strategy & Artificial Intelligence on why AI returns the average of the past while strategy bets on an exception.
- Julie Zhuo: When AI Has Better Taste Than You on why choosing what to optimize for stays with the designer, however good the tools get.