Want this content delivered right to your inbox?
How to structure sessions that move teams from AI resistance to alignment
Table of contents
How to structure sessions that move teams from AI resistance to alignment
Design thinking for AI adoption is a structured approach that applies the five-stage design thinking process (empathize, define, ideate, prototype, test) to the human and organizational challenges of integrating AI into how a team actually works. Unlike standard technology rollouts, which focus on implementation timelines and training plans, this approach starts with the people who need to change their behavior.
Why Design Thinking Works for AI Adoption
Most AI adoption efforts encounter a predictable wall. The technology works. The business case is clear. The leadership team is aligned. But the teams who need to change how they work are resistant, confused, or quietly finding workarounds. Technical rollouts treat this as a communication problem to be solved with announcements and training. Design thinking treats it as a design problem. The design thinking process asks facilitators to begin with empathy rather than implementation. That shift changes everything. Instead of rolling out AI and then managing the resistance that follows, facilitators surface what people actually worry about before resistance calcifies into habit. The result is an adoption plan shaped by real concerns, not assumptions built in a conference room. Three conditions make design thinking particularly well-suited for AI adoption:
- The stakes are high enough to warrant a structured process. AI adoption asks people to change core workflows, trust new tools, and accept uncertainty about what their roles will look like in 12 months. That kind of change does not respond well to quick workshops or memo-driven rollouts.
- The resistance is usually non-technical. The most common blockers are fear of job displacement, concern about AI errors affecting real decisions, and confusion about who is accountable when AI is involved. These are human and organizational questions, not software questions. Design thinking is built for human and organizational questions.
- The solution space is genuinely open. Not every team needs the same AI tools or the same integration depth. Design thinking protects that variation rather than forcing a single rollout plan onto every department.
The 5 Stages of Design Thinking for AI Adoption
The five stages of design thinking map directly to the phases of a well-run AI adoption workshop. Here is how each stage works in practice, and what distinguishes it from standard change management.
Stage 1: Empathize
The empathy stage is where most AI adoption efforts cut corners. It takes time, it surfaces uncomfortable concerns, and it can feel like delay when leadership is pressing for results. Facilitators who skip it spend the rest of the engagement managing resistance that could have been surfaced and addressed early. In an AI adoption context, the empathy stage involves structured listening with the teams who will actually use the AI tools. The goal is not consensus. It is understanding. What do people worry about? What do they hope for? Where do they see AI creating problems they do not currently have? Facilitation approaches that work well here include one-on-one interviews before the group session, anonymous pre-workshop surveys, and small-group discussions organized by role or department. The facilitator’s job in this stage is to listen and record without editing, reassuring, or correcting. In Voltage Control’s facilitation certification program, candidates consistently find that teams receiving AI tools with no empathy stage are far more likely to develop unofficial workarounds within 60 days. The workarounds are not evidence of bad behavior. They are evidence that the rollout did not account for how people actually work.
Stage 2: Define
The define stage turns what the empathy phase surfaced into a specific, actionable problem statement. For AI adoption, this means narrowing from a general concern like “people are worried about AI” to something specific enough to design against. A well-formed define statement for AI adoption sounds like this: “Our \[department\] team needs a way to \[use AI for a specific task\] without feeling like they’ve lost \[the specific thing they value\] in the process.” The brackets are where the empathy research fills in the specifics. Two failure modes are common in this stage:
- Too broad: “We need people to embrace AI.” This gives a design team nothing to work with.
- Too technology-focused: “We need to implement AI in the workflow.” This skips the human tension entirely.
A facilitator’s job is to push until the define statement names the specific tension the adoption needs to resolve. A good define statement is also testable: once the prototype runs, the team can assess whether it resolved the tension or not.
Stage 3: Ideate
The ideate stage generates possible approaches to the problem defined in stage 2\. For AI adoption, this usually means brainstorming how to integrate specific AI tools into specific workflows in ways that address the concerns surfaced during the empathy phase. Standard brainstorming (give everyone sticky notes, call time at five minutes) tends to produce ideas that sound good in the room but do not hold up when tested against real work. Three techniques work better for AI adoption ideation:
- Role-reversal prompting: Ask each team member to describe how AI could support the most frustrating part of a colleague’s job. This surfaces cross-role insights that individual brainstorming misses.
- Constraint stacking: Run ideation in rounds, adding a new constraint each round (for example: “what if the AI could only assist, never decide?” then “what if you had to explain every AI recommendation to a client?”). Constraints produce more creative, workable ideas than open sessions.
- Negative brainstorming: Before generating solutions, brainstorm what the worst possible AI rollout would look like. Reversing the list generates a practical checklist for avoiding known failure patterns.
Stage 4: Prototype
The prototype stage in AI adoption is not about building software. It is about designing a low-stakes test of the adoption approach before committing to a full rollout. The goal is to learn quickly and cheaply, not to be comprehensive. Prototypes for AI adoption take three main forms: Process prototype: A team runs one workflow with AI assistance for two weeks, with a structured debrief at the end. No new tools, no formal rollout, no performance metrics yet. Just an observed experiment with a defined learning question. Decision prototype: The team maps out where in their current process an AI tool would make a decision, inform a decision, or flag something for human review. This prototype is a diagram, not a working system. It surfaces role-boundary questions before the technology is live. Communication prototype: The team drafts how they would explain AI-assisted outputs to clients, stakeholders, or leadership. This prototype reveals whether the team actually trusts the AI enough to stand behind its outputs. Each form is appropriate for different resistance patterns. A facilitator who understands what the define stage surfaced can choose the right prototype type rather than defaulting to a process pilot every time.
Stage 5: Test
The test stage closes the design thinking loop: run the prototype, observe what happens, and feed those findings back into the process. For AI adoption, this requires three things to be defined before the test begins, not after.
A specific learning question. Not “did people like using the AI?” but “did using the AI reduce time to first draft?” or “did people feel more or less confident in their outputs when AI was involved?” Specific questions produce usable data. General questions produce impressions.
A comparison condition. Without a baseline, the test cannot tell you whether the change made things better. A rough baseline drawn from the empathy interviews is better than none at all.
A decision rule. What does the team do with the results? If the specific condition is met, move to a broader rollout. If not, return to ideate. Committing to the rule before the test prevents the results from being interpreted selectively after.
Common Pitfalls in Design Thinking for AI Adoption
Skipping the empathy stage when leadership is impatient
The most common failure pattern is compressing the empathy phase because leadership is ready to move. Facilitators who do this inherit the resistance they were hired to prevent. A two-hour empathy session before an AI rollout is far cheaper than a four-month adoption delay caused by teams that quietly built workarounds.
Letting the prototype become the rollout
Prototypes work because they are low-stakes. When a prototype starts to grow in scope, add users, or get tied to performance metrics before the learning question is answered, it stops functioning as a prototype. It becomes an early rollout with no learning structure. Facilitators need to hold the line on prototype scope explicitly, not assume the word “prototype” is self-enforcing.
Using design thinking as window dressing
Design thinking for AI adoption fails when leadership has already decided what the rollout looks like and is using the workshop process to generate buy-in rather than real input. Teams recognize this pattern quickly. The result tends to be deeper resistance than no workshop at all, because the process looked like engagement while functioning as information delivery. One test: if the empathy stage findings could actually change the implementation plan, the process is real. If they could not, it is theater.
A Step-by-Step Workshop Structure for AI Adoption
For a facilitator running a half-day session, here is a sequence that moves through the design thinking process at practical depth.
Hour 1: Empathy Send an anonymous pre-work survey 48 hours before the session asking three questions: what concern about AI do you most want addressed, what are you most hopeful about, and what would need to be true for this to go well? Open the session by surfacing the survey themes (anonymized). Run 30 minutes of small-group discussion in mixed-role groups of 3-4, with a structured prompt. Close with 15 minutes of whole-group synthesis: what themes surfaced, what surprised people.
Hour 2: Define The facilitator drafts three problem statements based on what the empathy phase surfaced. Groups vote and refine toward one. The final define statement is written visibly and posted for the rest of the session.
Hour 3: Ideate and Prototype Selection Two ideation rounds using constraint stacking. Dot voting on top ideas. The facilitator introduces three prototype options based on what emerged from the define stage. Groups select one and draft the prototype design in detail: what is being tested, how, and for how long.
Hour 4: Test Design and Next Steps Groups write the learning question for the prototype. Groups define the comparison condition and the decision rule. The facilitator captures the define statement, prototype design, and decision rule as a one-page summary before the session ends. This structure moves a team from surface-level concern to a concrete, agreed experiment in four hours. The prototype itself takes two to four weeks. The full design thinking cycle can run from first workshop to rollout decision in approximately five weeks.
Getting Started
Facilitators who want to apply design thinking to AI adoption do not need to run a full five-stage engagement on day one. The highest-leverage entry point is the empathy stage: before any implementation decisions are made, spend two hours with the teams closest to the AI tools and ask what they actually worry about. That data shapes everything that follows. It identifies whether resistance is primarily about job security, about trust in AI accuracy, about accountability, or about workflow disruption. Each of those patterns needs a different design approach. Without the empathy data, facilitators end up designing solutions to guesses. For facilitation teams that want structured support building this kind of process, Voltage Control works with organizations at every stage of AI adoption, from initial team assessments to full workshop design. Book a free intro call to talk through where your team is and what a design thinking approach might look like in your context.
