Leading design in the AI-era

There’s a question I keep coming back to: where does a design leader actually have leverage in the organization in 2026?

It isn’t where the team sits or even what it ships. It’s which decisions become design’s to make - and which quietly drift toward Product Management or Engineering while no one’s looking.

Locus of Leverage

Design leadership already went through one major shift over the past decade, as execution moved from central design functions into embedded product squads. It’s shifting again, but the dynamic is harder to read. As AI compresses the day-to-day distance between roles, the boundaries between Design, Product, and Engineering have become porous. It’s getting increasingly hard to track which core responsibilities still belong to which team.

The operating model is where this plays out first. Embedded execution and a central practice aren’t opposing models - they’re answers to different problems. Embedded works for speed and product-context depth at the IC level. A central practice carries system-wide consistency, design system governance, AI policy, and the quality bar. The strongest setup is a hybrid: execution distributed, narrative and standards held centrally.

The pure embedded model also breaks on team math. When designers are significantly outnumbered by PMs - the common case in growing B2B SaaS - each designer carries multiple product areas. Regardless of philosophical preference, the model structurally tilts toward the central end of the spectrum.

Illusion of Full Automation

What sharpens the stakes today isn’t AI replacing designers - it’s AI creating an illusion of full automation across every adjacent role. Teams intoxicated by AI capabilities start to feel that missing UX skills can be compensated for by the right prompts, configurations, and tooling. Why waste time on an extra process when Claude Code can make it look beautiful in half an hour? The work looks democratized - and on the surface, it is. The deeper layer is different.

This is where design’s leverage stops being about artifacts and starts being about boundaries. Defining how the product behaves under real user conditions - how workflows are structured, where automation accelerates or creates friction, what users are expected to understand or trust, and where AI should act or defer - is fundamentally a UX concern.

That behavioral configuration layer is where design still has to hold ownership. The alternative is “vibe-designing” - teams improvising product behavior and interaction logic without a coherent system underneath, while identity, quality, and consistency quietly erode.

Accountability in Shared Workflows

For the team, the implication is a culture of shared workflows and explicit accountability. As workflows increasingly blur across roles, the key distinction is no longer task execution, but decision ownership. That accountability has to be specific. Not “design owns user experience” as a slogan, but a clear map of which configurations and quality bars are design’s to set. For the team members, this means growing toward multi-context fluency - across UX, business, and technical layers - faster than traditional career ladders ever assumed.

If these questions are part of your world too, drop me a line at victor.kaidan@gmail.com.