AI just called design’s bluffAI tools are exposing how much of 'design work' was really just execution, not thinking.
- The argument: When AI can produce polished mockups instantly, design's value shifts from execution speed to judgment, taste, and problem framing.
- Why it stings: Many design orgs still measure output by artifacts produced — screens, flows, comps — which AI now automates trivially.
- What's next: Design leaders need to redefine what senior-level design work even means once the artifact-production bottleneck disappears.
For design
Worth auditing what your team's leveling and promo criteria actually reward — if it's still artifact output rather than judgment and framing, AI is about to make that measure meaningless.
Design system contracts: the component lives in neither Figma nor codeA component's real definition now lives in the contract between Figma and code, not either one alone.
- The idea: As tokens and code-generation blur the line, a component's true source of truth becomes the explicit contract connecting design and dev — not the Figma file or codebase alone.
- Why it matters: Teams still treating Figma as the single source of truth risk drift once AI coding tools start generating directly from prompts or specs.
- What to do: Design systems teams should document components as explicit contracts — props, states, tokens — that both AI tools and humans can read reliably.
For design
If your design system doesn't have machine-readable component contracts yet, this is the year to build them — they'll be the interface AI coding tools actually consume.
Design systems need evalsTeams have taught AI agents their design system but have no way to verify agents actually follow it.
- The gap: Companies feed design systems into AI coding agents, but there's no standard way to evaluate whether the generated output actually complies.
- Why it matters: Without evals, 'AI follows our design system' is a hope, not a verified fact — leading to silent, compounding drift.
- What's needed: DesignOps teams likely need to build their own eval suites — sample prompts plus expected component usage — as agentic coding scales.
For design
This is a concrete gap DesignOps can own directly: build a small eval set to benchmark any AI coding tool for design-system compliance before rolling it out broadly.
People will always need to trust the human behind any decision-makingWhen a manager leans on AI more than the team's own judgment, trust erodes fast.
- The scenario: A creative professional describes a manager who defers to AI outputs over the team's own recommendations.
- Why it matters: Trust in decisions still traces back to an accountable human — AI can't absorb blame or context the way a person can.
- The tension: As AI gets folded into decision-making, teams need clarity on when it's an input versus when it's effectively the decision-maker.
For design
If leadership is starting to treat AI outputs as tie-breakers over team recommendations, get ahead of it — propose a clear policy on when AI informs vs. decides before trust erodes silently.