Your AI tools are ready. Your design org isn’t.
Design organizations have adopted a remarkable number of tools in a short window — Figma, FigJam, DevMode, and now AI layers on top of all of it. The tools work. That’s not the problem.
The problem is that nobody owns what happens next.
AI adoption isn’t a tools problem. It’s an ops problem.
There’s a pattern I keep seeing: leadership approves the budget, individuals start experimenting, and within 90 days the org has fragmented into a dozen parallel workflows that don’t talk to each other. One or two enthusiasts are burning out trying to carry everyone else toward the goal post. Everyone else is either quietly falling behind or quietly waiting to be shown the way.
This isn’t an AI-specific failure. It’s the same challenge DesignOps has always addressed — just with a new surface area and a much shorter adoption curve compressing the timeline.
What “ready” actually requires
Sustainable AI adoption happens across three layers:
-
- Layer 1: The Tool — where nearly all budget concentrates. The licenses, the subscriptions, the pilots.
- Layer 2: The Workflow — how the tools actually integrate with how people work day to day.
- Layer 3: The System — the infrastructure for capturing what works, sharing it, governing it, and iterating on it over time.
Most organizations invest heavily in Layer 1, lightly in Layer 2, and do nothing about Layer 3. Then they wonder why adoption stalls six months after launch.
The shared vocabulary problem
One of the earliest symptoms of missing infrastructure is vocabulary fragmentation. Teams develop local language for the same concepts. New hires have no map. Knowledge stays locked in individual heads — and leaves the org entirely when those people move on.
Shared vocabulary is what makes it possible for a new hire to be productive in 15–30 days instead of six months. It’s not glamorous work. It doesn’t make the demo reel. But it’s the foundation everything else is built on, and it’s the cheapest, highest-leverage investment you can make before building any other system.
The governance gap nobody wants to talk about
AI tools introduce new questions that most design orgs haven’t formally answered yet: What’s confidential? What’s a quality standard for AI-assisted work? Who gets attribution? What are we not using these tools for, and why?
Without explicit answers — in writing, owned by someone — teams will answer these questions differently. And inconsistency at that level compounds fast.
DesignOps is the function that builds the guardrails
I’ve started calling the accumulated risk of inadequate adoption practice AI Adoption Debt. Like technical debt, it’s not visible until it’s expensive. Unlike technical debt, most orgs don’t even have a name for it yet — which means they’re not tracking it, not measuring it, and not paying it down.
DesignOps is the function positioned to own this work. Not because it’s glamorous — it isn’t — but because DesignOps already owns the operational infrastructure of the design org. AI adoption is just the newest domain in that scope.
Who owns this?
Right now, in most organizations: nobody. The enthusiasts do their best. The stragglers fall further behind. Leadership looks at tool adoption metrics and sees green.
What’s needed is an explicit owner — someone with design knowledge, organizational authority, and an operational orientation. Not the most excited person. The most equipped person.
Three concrete starting points for org and design leaders
-
- Audit your current AI adoption honestly. Where is it happening? By whom? What’s been shared beyond the team that built it? The gaps will be obvious once you look.
- Assign ownership thoughtfully and explicitly. Enthusiast ownership is not organizational ownership. This work needs someone with the authority to set standards and the skill to build systems.
- Start with vocabulary before building systems. A shared glossary is not a small thing. It’s the connective tissue that makes everything else transferable.
The tools are ready
They’ve been ready. The question was never whether the tools would work. The question is whether your organization is built to absorb what they make possible — and whether you’re willing to do the unglamorous ops work that separates sustainable adoption from AI Adoption Debt.
Originally published on LinkedIn on May 5, 2026.