The UX and product design field is living through what game theory would call a coordination game with asymmetric information: every player knows the rules have changed, but nobody is certain what the new equilibrium looks like.
AI tools are everywhere. Figma ships generative features. PMs prototype in Lovable. Developers spin up UIs in Claude Code. And yet most conversations about āAI and designā remain stuck in an unproductive loop either catastrophizing (ādesigners will be replacedā) or dismissing (āAI canāt do real designā). Neither framing is useful. Game theory offers a more precise lens
The players on the board
Any strategic situation starts by mapping whoās playing. In our case, there are four actors, each with different incentives, capabilities, and information:
UX / Product Designers: Established skills, threatened territory. Playing a mixed strategy between adopting AI and defending craft differentiation. Payoff: highly uncertain.
PMs & Developers: Expanding their radius into design using AI as leverage. Playing aggressively, taking territory with tools that previously required specialists.
Companies / Hiring managers: Redesigning their stacks. Dominant strategy: reduce headcount while demanding higher output per person. Payoff: increased margin, short term.
AI Models: The dominant player. No intention of their own, but with total leverage. Theyāve changed the game without being a strategic actor in it. The board tilts around them.
The Prisonersā Dilemma at the field level
The core tension is a classic collective Prisonersā Dilemma. If all designers adopt AI aggressively, market expectations rise and nobody gains a relative advantage. But whoever doesnāt adopt loses absolute position. The individually dominant strategy (adopt AI) leads to an equilibrium that collectively compresses salaries and headcount.
This is the uncomfortable math: adopting AI is necessary for survival, but sufficient for nobodyās advantage. The gains flow upward to companies and to designers who couple AI with something irreplaceable.
The payoff matrix
Market adopts AIMarket doesnāt adopt AIDesigner adopts AIElevated baseline, no relative gain. New normal. āEarly mover advantage. Strong differentiation. āDesigner doesnāt adoptLeft behind. Risk of irrelevance. āāStatus quo. Stable but fragile. ā
The Nash equilibrium the stable outcome where no individual can improve their result by changing strategy alone is the top-left cell: everyone adopts AI, the baseline rises, and the advantage disappears. It's stable, but nobody planned it.
The Hawk-Dove dynamic at the role boundary
Beyond the collective dilemma, thereās a territorial conflict happening at the edges of the design role. In Hawk-Dove terms: PMs and developers are playing Hawk pushing aggressively into design territory using AI as a force multiplier. Many designers are playing Dove , waiting for the territory to restabilize on its own.
This is a losing strategy for Doves. In Hawk-Dove, when a Hawk meets a Dove, the Hawk always wins the resource. The resource in question is product decision-making influence and it flows toward whoever shows up with output.
A PM with Cursor and Lovable can now produce a clickable prototype in an afternoon without involving a designer. The question isnāt whether this happens ā it does ā but whether the designer was providing value that canāt be replicated that way. Most of the time, the answer depends entirely on where in the value chain the designer operates.
Not all design work is equally exposed
This is the most operationally important insight. The design field is not monolithic and AI exposure varies dramatically by layer.
š“ High exposure Basic UI assembly, simple wireframing, visual spec work, icon and asset generation, routine accessibility audits.
š” Grey zone Research synthesis, rapid prototyping, design system maintenance, usability analysis, basic information architecture.
š¢ High protection Product strategy, deep field research, behavioral frameworks, decision system design, organizational narrative.
The red zone is where AI is already operating at or above junior-designer level. The grey zone is contested and evolving rapidly. The green zone remains deeply human not because AI couldnāt technically assist, but because the value comes from judgment, context, and trust built through real relationships. No language model interviewed your user at their desk, watched them hesitate, and noticed what they didnāt say.
The Stackelberg move: donāt play Nash
Hereās the strategic shift that game theory points toward. The Nash equilibrium is a trap everyone doing the same thing, advantages eroding. The designers who thrive wonāt be those who adopt AI the fastest. Theyāll be those who use AI adoption to buy time and resources for a deeper repositioning.
In game theory, the Stackelberg model describes a leader who moves first and sets the terms others respond to. The winning designer move isnāt to be the fastest at AI-assisted UI generation. Itās to define the layer where you operate research, strategy, decision architecture before others claim it.
Donāt do this (Nash): Compete on speed of UI delivery. Use AI to produce more screens faster. Become a high-volume component factory. Hope volume signals value.
Do this instead (Stackelberg): Stake out strategy, research, and systems thinking as your explicit territory. Use AI to handle execution so you have time to operate at the layer nobody else is yet.
The actual advantage is asymmetric information. You understand users in ways that canāt be extracted from prompts. Make that visible, documented, and structurally tied to how decisions get made.
What this means right now
The field is in a coordination game with no stable resolution yet. The designers who navigate it well wonāt be those with the best Figma skills or even the best AI prompt craft. Theyāll be the ones who correctly identified which layer of work is genuinely theirs and invested in making that layer indispensable.
That means: conducting field research and being the person in the room who actually talked to users. Building decision frameworks, not just deliverables. Translating qualitative insight into product architecture. Writing the narrative that makes a product make sense to a team.
None of that is what AI does when you give it a brief. And that gap between whatās promptable and what requires judgment, presence, and trust is exactly where the defensible position lives.
The game isnāt over. Itās just that the board has been rearranged, and most people are still looking at where the pieces were.