People Rarely Resist the Tool. They Resist What It Might Mean.
When a creative team pushes back against AI, the obvious explanation is resistance to change. That is usually too convenient.
A designer may be wondering whether fewer designers will be needed. A writer may wonder whether years spent developing a voice can be replaced by a prompt. A creative director may worry that speed will become more important than judgement. Someone who has spent a decade becoming excellent at their craft can reasonably ask what excellence means when a machine can produce ten versions before lunch.
1Â Those questions cannot be solved with a training session. People need clarity about how the organisation sees their role changing. If leadership cannot explain what becomes more valuable because of AI, the team will fill the silence with its own assumptions.
Start With the Work, Not the Technology
The worst AI transition begins with a tool.
Here is the new platform. Here is the prompt library. Here are five workflows. Please start experimenting.
The better starting point is the work itself. Where does the team lose time? Which tasks are repetitive? Where do people spend energy producing variations instead of making decisions? Which parts of the process require taste, context, empathy, judgement, or collaboration?
AI becomes much easier to discuss when it is connected to an actual problem. The conversation changes from “Are we becoming an AI company?” to “Can this help us spend less time doing this particular thing and more time doing the part of the work that requires us?”
That distinction gives people something concrete to evaluate.
Give People Permission to Experiment Before Demanding Adoption
An AI transition creates enough uncertainty without adding a performance review to it.
If every experiment is expected to produce immediate efficiency, people stop experimenting. They learn the safest possible workflow, use the tool exactly as instructed, and call it adoption.
Give the team a defined space to play. Let a designer test image generation on an internal concept. Let a writer compare first drafts with and without AI assistance. Let a strategist use AI to challenge assumptions rather than produce the final recommendation. Then discuss what happened.
Some experiments will be useful. Some will be terrible. That is part of the process. A bad output is not a failed employee. It is information about where the tool does not belong.
Protect the Parts of Creative Work That Should Stay Human
Not every task should be automated simply because it can be.
2Â A creative team does more than produce assets. It interprets culture. It understands audiences. It makes choices when the brief is incomplete. It knows when something technically correct feels completely wrong. Those abilities become more important as generative tools make production cheaper and faster.
A useful transition therefore separates production from judgement. AI may generate ten concepts. Someone still has to decide which concept deserves another hour. AI may produce a first draft. Someone still has to know whether the argument is honest. AI may analyse patterns. Someone still has to decide whether the pattern actually matters.
The point is not to keep humans away from AI. It is to make sure humans remain responsible for the decisions that give the work meaning.
Let the Team Help Define the New Creative Workflow
People support change more readily when they can influence what the change becomes.
Instead of announcing a finished AI workflow, build it with the team. Ask where AI is useful, where it creates risk, what should require human review, and which tasks nobody wants automated in the first place.
This also reveals expertise that leadership may not see. The person who quietly understands production bottlenecks may design the best automation. The junior designer experimenting with new tools may discover a workflow the senior team would never have considered.
AI transitions are often described as top-down transformations. Creative teams usually work better when they feel like participants in the redesign.
Measure Better Work, Not Just Faster Work
Speed is the easiest AI metric and probably the least interesting one.
If a team produces twice as many concepts but spends twice as long choosing between them, the organisation has not necessarily improved. If writing gets faster but editing becomes harder, the time has simply moved. If production costs fall while the work becomes indistinguishable from everyone else’s, the savings may be expensive in disguise.
Measure what actually matters. Quality. Decision time. Creative range. Client outcomes. Team learning. The number of useful ideas that survive beyond the first draft.
A good AI transition should make the team more capable, not merely more productive.

Share your thoughts