The Designer’s Mindset Is Now an AI Leadership Skill
As organizations race to deploy AI at scale, the hardest part is no longer the model or the infrastructure. It’s the human layer: reshaping workflows, governing adoption, and building teams that can actually move on AI. A new breed of leader—sometimes called an AI innovation lead, acceleration officer, or similar—has emerged to connect those dots. Their mandate sounds straightforward, but it’s notoriously difficult to execute.
Many of these leaders get trapped in what technical leader Kaitlyn Hova calls "performative progress": shipping tools to check a box without changing the underlying systems. The ones who succeed tend to share a common approach that has less to do with engineering and more to do with design. Based on conversations with leaders in these roles, a clear pattern emerges. They aren’t just thinking like technologists; they’re borrowing from the designer’s playbook to align teams, make better bets, and turn experimentation into lasting change.
Use the Material Before You Lead It
A core tenet of design is knowing your material—and that means using it intensively. For leaders whose job is acceleration, the instinct might be to stay at the strategic altitude and delegate hands-on work. But if you’re operating at 30,000 feet, you miss the daily trade-offs and tactics that determine whether a tool actually sticks.
The most effective AI leaders are building their own agents and prompting in every tool they can find, often outside of work. This isn’t just curiosity—it’s a safe way to push limits without compromising company systems. One leader profiled used AI to manage everything in their personal life, from planning family vacations to organizing volunteer work. That level of engagement builds the fluency required to lead a probabilistic shift. You cannot guide teams through uncertain, probabilistic tools if you haven’t watched those tools behave in the real world.
Read the Workflow, Not Just the Output
Using AI yourself is necessary, but understanding how the broader business is using it is equally critical. Leaders who stay focused on outputs often miss the real signal: what happens in the workflow itself. Pain points, friction, and breakthrough moments all live in the process, not the result.
Observation means paying attention to signals across the company—what excites teams, what frustrates them, and where they route around official tools. Slack threads, survey responses, and usage patterns tell the story. A new AI automation might work perfectly in a demo, yet adoption flatlines if it adds friction to an already complex process. Teams may start stitching together their own solutions rather than raising a flag. If you’re not watching that behavior directly, you’ll miss the evidence that the tool’s real flaw is its fit, not its capability.
Prototype to Build Alignment
Design balances observation with action. In fast-moving AI work, ideas rarely die for being bad—they die because teams can’t visualize them. Prototyping solves that problem. When leaders turn early concepts into tangible artifacts using tools like Figma Make, they give teams something concrete to react to, refine, and rally around.
These prototypes are more than just outputs. They serve as coordination and alignment tools. Teams visually see where a workflow breaks, what’s missing, and what’s worth pursuing. Visual roadmaps, mockups, diagrams, and demos do more than illustrate an end state—they map the path to get there. Several leaders report that moments of real clarity came from seeing these visuals together. And when you need to make the case for time, resources, or budget, having something real to point to is a persuasive advantage.
Make Critique a Habit
How teams refine ideas matters as much as the ideas themselves. Leaders shaping AI tools and workflows are adopting a classic design practice: critique. These aren’t just for designers—engineering crits help technical teams align early on complex problems.
In practice, that means creating intentional spaces—standing meetings or dedicated Slack channels—where teams evaluate what they’re building. Start by sharing a prototype, a workflow exploration, or an infrastructure question. Ask for feedback and set the tone by being receptive. Not everything needs to be actioned, only considered. Over time, the group develops a shared standard of what “good” looks like, which reduces bottlenecks and accelerates decisions without losing coherence. These sessions also bring to light information that only a few people have but everyone needs.
Treat Community as Infrastructure
AI transformation is not a one-time project with a finish line. The technology changes constantly, so learning must be continuous—and collective. Design has always operated this way, thriving on working in the open and building on shared ideas. Community spaces, whether internal groups or cross-industry Slack channels, let leaders see what’s working, what’s failing, and where the edge is moving next. Coming together with practitioners expands perspectives and creates momentum that individual effort rarely sustains.
The AI leadership playbook is still emerging. But the leaders who are making headway are grounded in design principles: using the tools firsthand, observing real workflows, prototyping for alignment, normalizing critique, and investing in shared learning. Design brings structure to AI’s complexity—turning an abstract, high-uncertainty initiative into a concrete, moving effort. The technology will continue to shift; the approach is what stays steady.
