The Pilot Trap: Comms With AI in the Transform Phase

Almost every communications team that has tried AI has a pilot that worked.

Someone, usually one capable and curious person, built something. An agent that drafts the monthly newsletter. A workflow that turns a report into a week of social content in an afternoon. A monitoring brief that used to take half a day and now takes twenty minutes. It worked. People were impressed. There was a meeting where someone said, 'We should do more of this.

And then, often, nothing. Six months later, the pilot is still a pilot, or it has quietly stopped, because the person who built it got busy, or moved on, or simply could not carry it alone. The capability never spread. The impressive thing became a story that the team tells about that time they tried AI.

This is the pilot trap, and it is the most common way AI fails in communications. Not with a dramatic mistake. With a slow fade. The tools were never the hard part. The hard part is building an organisation that can hold the new way of working after the novelty wears off, and that is the Transform phase of the Comms With AI Operating System.

If you have followed the series this far, you have seen the four phases that produce and protect the work: Strategise, Create, Govern, and Monitor. The overview introduced all five, and the full series is here. This final article is about the phase that decides whether any of it lasts.

The Transformation Problem

Here is the distinction the pilot trap turns on. A pilot that depends on one enthusiastic person is not a capability. It is a hobby that happens to be useful. The moment that person is unavailable, the capability is unavailable, and an organisation cannot plan around a hobby.

Transform is the work of converting hobbies into capabilities. And the reason it is hard, the reason teams skip it, is that it is not technical work. Deploying an agent is comparatively easy. Changing how an organisation operates is not, because it touches the things organisations find genuinely difficult: roles, skills, incentives, ownership, and culture.

Consider what actually has to change for AI-assisted communications to become normal rather than novel. Job descriptions have to acknowledge it, or it stays off-the-record. People need new skills, and not the ones usually advertised. Someone has to own the decision to adopt, maintain, and retire tools, or the organisation accumulates a drawer of half-used subscriptions. There has to be a shared standard for what good AI-assisted work looks like, or every person applies their own. And the culture has to make it safe to say a workflow is not working, or problems go quiet instead of getting fixed.

None of that is a tooling problem. All of it is a leadership and organisational problem. That is why Transform is the phase where the AI does the least, and the phase that most determines whether the other four were worth the effort.

What the Transform Phase Covers

Transform is the capability layer of the Operating System. It holds the work of building an organisation that can sustain and improve agent-driven communications over time:

• AI readiness assessment: an honest diagnostic of where the team stands across all five phases
• Workflow redesign: rebuilding processes around what agents can now do, rather than bolting agents onto old processes
• Role evolution and team structure: how communications jobs change, and what the team needs to look like
• Training and upskilling: building the specific judgement that AI-assisted work requires
• Tool evaluation and selection: choosing, maintaining, and retiring tools deliberately
• Change management: leading people through the shift, not just announcing it
• Operating model design: deciding where agents live, who maintains them, and how the whole system is governed

Unlike the other phases of the Operating System, the Transform library on Comms With AI is deliberately small: four templates covering the structured, diagnostic end of the phase. The AI Readiness Assessment, Comms Workflow Audit, Capability Gap Analysis and AI Tool Evaluation Framework will get you a long way into the analytical groundwork. The rest of the phase is deliberately not templated. A template structures a repeatable task, and change leadership is not a repeatable task. It is leadership, judgement, and change work, specific to each organisation, and it is served through training and hands-on consulting rather than through a worksheet.

The 20/80 Rule for Transform

Across the Operating System, the working rule is roughly 30% AI, 70% human. Transform sits at the human end of the range, at 20% AI, 80% human, the same balance as Strategise and the lowest agent share in the framework.

This ratio shifts across the five phases:

• Strategise: 20/80 – research and synthesis AI, judgement human
• Create: 35/65 – drafting AI, voice and nuance human
• Govern: 25/75 – systematic checking AI, reputational judgement human
• Monitor: 40/60 – pattern detection AI, interpretation human
• Transform: 20/80 – readiness assessment AI, change leadership human

There is a neat symmetry in the framework here. The two phases where AI does the least, Strategise and Transform, are the two that bookend the cycle: the thinking before the work, and the organisational learning after it. The phases in the middle, where work is produced and processed, are where agents carry more. AI is strongest in the doing and weakest at the edges, where judgement and leadership live. That is not a limitation to apologise for. It is the shape of the tool, and designing around it honestly is the whole point of the Operating System.

The 20% an agent contributes to Transform is real and worth having. It can run a structured readiness assessment, benchmark a team against a maturity model, map current workflows, model redesigned ones, and compare tools against defined criteria. That is genuine analytical help. But it cannot do the 80%, because the 80% is convincing people, navigating politics, building trust, holding a standard, and leading through the discomfort of changing how work is done. No agent leads change. People do, or it does not happen.

Where Agents Change Transformation Work

Four applications are worth examining, though the honest framing for this phase is different from the others. In Strategise, Create, Govern, and Monitor, the agent does a meaningful share of the work. In Transform, the agent informs the work, and a human does almost all of it.

1. AI readiness assessment

The most useful starting application. An agent-supported diagnostic works systematically through the five phases of the Operating System and builds an honest picture of where a team stands: where it is genuinely capable, where it is improvising, where it has tools without process or process without tools, and where the gaps are most expensive.

The value is in the structure and the honesty. Teams assessing their own AI maturity tend to anchor on their best example, the one impressive pilot, and assume it represents the whole. A structured assessment pushes past the showcase and looks at the routine. The output is not a verdict. It is a map of where to spend effort first, which is the most useful thing to have at the start of any transformation.

This site's own origin is a relevant example of readiness in action. The build of the Comms With AI resource using Claude Code was, in part, a practical readiness exercise: finding out by doing what was actually possible, where the limits were, and what skills the work demanded.

2. Workflow redesign

The instinct when adopting agents is to bolt them onto the existing process. The team keeps its current workflow and inserts an agent at one step. This produces a modest gain and misses most of the value.

Real workflow redesign asks a harder question: if we were designing this process now, knowing what agents can do, what would it look like? An agent is useful for mapping the current workflow in detail and modelling redesigned versions, but the redesign decisions, what to keep, what to cut, what to resequence, are human and often political, because workflows encode who does what and changing them changes that.

3. Tool evaluation and selection

Communications teams accumulate tools the way garages accumulate tins of paint. A structured evaluation, comparing tools against the team's actual needs rather than their marketing, is work an agent can scaffold well.

Applied / Comms With AI has effectively been running this discipline in public since it started, through its tool review methodology and the reviews built on it, and the AI Tool Evaluation Framework template turns that method into something your team can run itself. The lesson from that work is consistent. The right tool is the one that fits the team's real workflow and skill level, not the one with the most features or the loudest launch. Transform is where a team decides to choose tools that way on purpose, and decides who owns the choice.

4. Skills mapping and role evolution

This is the application that matters most, because it is about people, and people are what make a capability last.

An agent can help map a team's current skills against the skills agent-assisted communications requires, and the gap is usually not where people expect. The scarce skill is not prompt-writing. It is judgement: knowing when to trust an agent's output and when to distrust it, when a draft is genuinely good and when it is merely fluent, when to push back. That judgement is built through guided practice, not a training course, and designing that practice is human work.

Underneath the skills question is a deeper one about what the job becomes. This site has written before about the shift from content creator to system builder: the communications professional moving from producing every piece by hand toward designing, briefing, and supervising the systems that produce them. That is the central role change of the Transform phase. It is not a smaller job. The craft simply relocates, from the output to the system that generates the output, and from doing the work to being accountable for the work an agent did. A team that does not name and support that shift will find its best people either quietly resisting it or quietly leaving.

A Test Your Organisation Should Pass

Run your organisation against the following five questions. They distinguish a real AI capability from a collection of clever pilots waiting to fade.

1. If your most AI-fluent person left tomorrow, would the capability survive?

If the answer is no, you have a person, not a capability. That is the single most important question in the phase, and for most teams the answer is uncomfortable.

2. Is AI use written into how you describe roles, or is it off-the-record?

If agent-assisted work is something people do but no job description mentions, it is unsupported by definition. What is not named is not resourced, not developed, and not defended.

3. Does your team share a standard for what good AI-assisted work looks like?

Without a shared standard, every person applies their own, quality varies invisibly, and the Govern phase has nothing consistent to govern against. The standard does not need to be elaborate. It needs to exist and be agreed.

4. Who owns the decision to adopt, change, or retire a tool?

If the answer is "nobody, really", the team will drift into tool sprawl, paying for things it half-uses and never deciding to stop. Ownership of the toolset is a named job or it is a mess.

5. Is there a real route for the team to say a workflow is not working, and be heard?

If raising a problem feels like criticising the AI strategy, problems will go quiet rather than get fixed. A capability that cannot hear bad news cannot improve, and a capability that cannot improve will not last.

If your organisation passes all five, you have built something durable. If it fails any of them, that is the Transform work still to do, and it is the work that protects everything the other four phases produced.

Where To Start

If Transform is the phase your team has skipped, which is the single most common gap in the whole Operating System, because it is the least visible and the least exciting, three starting points will move you furthest.

Start with a readiness assessment. Before redesigning anything, get a clear, structured, unflattering picture of where the team genuinely stands across all five phases. The AI Readiness Assessment template gives you the structure to do it in a working session rather than a quarter – or you can directly take our free online assessment tool. Effort spent in the wrong phase is effort wasted, and most teams do not actually know where their gaps are until they look properly.

Make one role's AI responsibilities explicit. Pick a role and write agent supervision, workflow ownership, or quality-standard accountability into it formally. One properly named responsibility does more for durability than five informal enthusiasms, because it converts a hobby into a job.

Build a shared quality standard before you scale. Agree, as a team, what good AI-assisted work looks like, and write it down. Scaling without a shared standard does not multiply quality. It multiplies inconsistency, and it leaves Govern with nothing stable to check against.

The Transform templates cover the diagnostic groundwork: readiness, workflows, capability gaps, tool evaluation. The change work they point to cannot be templated, because it is not a repeatable task. It is leadership work, specific to each organisation, and it is the work that decides whether an AI initiative becomes part of how the team operates or a story about something it once tried.

Closing the Loop: The Series in One Idea

Six articles, five phases, one argument.

The argument was never that AI writes communications. It is that AI is a workflow engine, and that communications work, being high-volume, structured, repetitive, and high-stakes, is unusually well-suited to being run as a set of designed workflows rather than a stream of improvisation.

The Comms With AI Operating System is the map of those workflows: Strategise to think clearly before the work, Create to produce at the volume modern communications demands, Govern to protect the organisation from what it publishes, Monitor to read the environment and shorten the lag, and Transform to build the organisation that can hold all of it.

The phases form a cycle, not a checklist, and Transform is where the cycle closes. The organisational learning of Transform feeds straight back into Strategise. A team that has been through the full loop once re-enters it sharper: clearer about where agents help, more honest about where they do not, and better at the judgement that the whole system still rests on. The AI/human ratio across the phases, from 20/80 in the thinking work to 40/60 in the monitoring, was the recurring reminder of that point. The human share never disappears. It concentrates on the decisions where experience is load-bearing, and it stays the majority of the work everywhere.

If there is one honest line to end the series on, it is this. The teams that win with AI in communications are not the ones with the most tools or the fastest output. They are the ones that treated this as a redesign of how the work is done, did the unglamorous Transform work of making it stick, and kept human judgement firmly in charge of the things that matter. That has been the whole series, and it remains the whole point.

Join the Discussion

Two live sessions this summer pick up exactly where this article leaves off.

On Wednesday 1 July I am hosting the next live Applied / Comms With AI Leader Interview, The Two Clocks: Elif Güvençer on repositioning comms for the AI era. Elif's framework names the tension at the heart of the Transform phase: one clock is the daily work, made faster; the other is the slower, structural job of redefining what the comms function is for. It is free, online (12:00 BST) and recorded. Register here; if you cannot make the slot, sign up anyway and we will send the recording and write-up.

And if training is the Transform work your team needs, in July I am running two live online AI courses with Big Fish Training, with individual places open for the first time: AI for Account Executives on Tuesday 7 July and AI for Account Managers & Directors on Wednesday 8 July, both 9.30am–1pm, £249 + VAT per place. Practical, hands-on, and built around real comms workflows. Full details and booking are with Big Fish.

What Comes Next

This is the final article in the AI Agent series, but it is not the end of the work. Applied / Comms With AI continues to document AI-assisted communications in practice: the experiments, the tool reviews, the interviews with practitioners doing this for real, and the honest accounts of what works and what does not. If the series was useful, the full archive is here, and the Operating System templates on Comms With AI are free to use across all five phases.

If your team is working on Transform, or on any phase of the Operating System, and you want to compare approaches, I am always happy to hear from fellow practitioners.

About

Applied / Comms With AI is the practical guide for communications leaders navigating AI, grounded in hands-on experimentation, workflow transformation and real-world implementation. Read the full AI Agent series here. Comms With AI is the companion template and resource library for communications professionals using AI; it holds the Operating System and its templates across all five phases, with the deeper Transform change work served through training and consulting, because organisational change is not a repeatable task. Both sit alongside Faur, a communications consultancy pioneering practical AI expertise for organisations ready to implement at scale. The Transform phase is where Faur does its deepest work: readiness assessments, workflow redesign, team training and the full Operating System diagnostic. If your organisation needs hands-on help making AI-assisted communications stick, get in touch at michael@faur.site or connect with me on LinkedIn.

This article concludes the AI Agent series published on Applied / Comms With AI. The series maps to the Comms With AI Operating System: Strategise, Create, Govern, Monitor, Transform.