How Design Thinking Makes You a Better AI Leader

How Design Thinking Makes You a Better AI Leader

When I ask senior leaders what they think design thinking is, I usually get some version of: "Post-it notes, empathy maps, and prototyping." Which is roughly like describing surgery as "scalpels, gloves, and stitching."

Design thinking is a structured method for solving problems that are ambiguous, complex, and resistant to straightforward analysis. It starts with understanding before solving. It generates multiple options before committing to one. It tests assumptions cheaply before investing heavily. It treats failure as information rather than defeat.

These are, as it turns out, exactly the capabilities that effective AI leadership requires.

The Problem That Design Thinking Was Built For

Design thinking emerged from a specific type of challenge: "wicked problems" — problems that are hard to define, where the solution changes the nature of the problem, and where there's no objectively right answer.

Sound familiar?

AI adoption in large organizations is a wicked problem. The right AI strategy depends on variables that are changing faster than strategy cycles can keep up with. The solution — whatever AI capabilities you build and embed — will change how your organization works in ways that create new challenges. And there is no objectively right answer: the best AI approach for a pharmaceutical company in 2026 looks nothing like the best approach for a retail organization.

The analytical frameworks that work for well-defined problems — the ones that most leadership development programs are built around — don't work for wicked problems. Design thinking does.

Four Design Methods That Directly Apply to AI Leadership

Empathy before solutions. Design thinking starts with deep understanding of the people you're designing for — their actual experience, not your assumptions about it. AI leadership requires the same discipline: before designing AI adoption programs, training initiatives, or governance frameworks, you need to deeply understand how AI actually affects the people doing the work.

Most AI strategy is developed at a remove from actual use. Leaders hear aggregated reports, consultant summaries, and curated success stories. Design thinking insists on firsthand exposure: watching how your team actually uses AI, listening to what frustrates them, observing where the tools fail. That understanding radically changes what interventions you design.

Problem framing before problem solving. Design thinking's most counterintuitive principle is that the most important work happens before you start generating solutions. How you frame a problem determines which solutions are even visible. A poorly framed problem produces excellent solutions to the wrong question.

In AI leadership, this means resisting the pressure to jump to AI solutions before you've precisely defined the problem you're solving. "We need to use AI" is not a well-framed problem. "We need to reduce the time our senior analysts spend on data compilation so they can invest more time in interpretation" is.

Rapid prototyping and iteration. Design thinking treats early attempts as prototypes — learning vehicles rather than deliverables. This runs directly counter to the enterprise instinct to plan comprehensively, approve carefully, and deploy fully before learning.

AI adoption is ideally suited to rapid prototyping. The cost of trying something with AI is low. The cost of designing a comprehensive program around an assumption that turns out to be wrong is high. Design thinking leaders run small experiments, learn quickly, and iterate — rather than commissioning elaborate studies that produce recommendations six months later.

Diverge before you converge. Design thinking insists on generating many options before selecting one. This is deeply uncomfortable for leaders trained to be decisive — but it's essential for AI strategy, because the space of possible approaches is genuinely large and the right answer is not obvious in advance.

A leader who applies design thinking to AI strategy will, before committing to an approach, explicitly generate at least five different ways the organization could develop AI capability — and evaluate each seriously rather than anchoring on the first plausible option.

The CoCreate Intersection

This intersection of design thinking and AI leadership is not accidental for CoCreate. It's foundational to how we approach executive enablement.

The leaders we work with aren't primarily technology executives. They're design leaders, product leaders, and general managers who have built their judgment through years of navigating ambiguous problems with limited information. That judgment — developed through design thinking methods — is more transferable to AI leadership than almost any technical training.

What we add is the AI-specific context, tools, and practice that allows that judgment to operate in the new environment. The result is leaders who can apply sophisticated problem-framing, empathetic listening, and rapid iteration to the genuinely novel challenges that AI transformation presents.

That's not a coincidence. It's the design thinking approach — applied to the problem of organizational AI adoption.