Communication

How to announce an AI programme without scaring your own staff

Staff hear efficiency language as a sentence about their own future, whether leadership intends it or not.

The situation in the room

A town hall presents a new AI programme through productivity, efficiency, and competitive pressure. By the afternoon, employees are updating resumes and managers are answering rumours.

The announcement was written for a board audience. It never answered what staff needed to know about their roles, timing, support, and the limits of what leadership knew. The work looked active from the outside. Inside the organization, the unanswered decision was still controlling what happened next.

What the situation is telling you

People fill vague language with the worst available story. Honest uncertainty with a date is more credible than polished reassurance without specifics.

That distinction matters because organizations often respond to the visible symptom. They buy another capability, add another review, or ask employees to try harder. The underlying distribution of authority, knowledge, and responsibility stays unchanged.

The sharp version is this: activity is not alignment. A credible programme connects the business outcome, the rules, and the people expected to carry the change.

Why the usual response fails

Silence about jobs does not sound neutral to the people doing them.

When leadership leaves that decision implicit, each function fills the gap with its own incentives. Technology sees deployment, finance sees cost, legal sees exposure, communications sees a message, and frontline teams see new accountability without new authority.

Silence about jobs does not sound neutral to the people doing them.

The decision behind the work

Lead with what changes for people, who is affected, what stays the same, what remains unknown, and when the next answer will come. Put the business case second.

Write the answer so that a person outside the project can use it. Name the owner, the boundary, the evidence, and the moment the decision gets reviewed again. If the answer depends on knowing who was in a particular meeting, it is not yet an operating decision.

This is where strategy earns its name. It reduces the number of choices people have to remake in private and gives the organization a stable reference point when the next tool, vendor, or urgent request arrives.

What good practice looks like

Communicate on a cadence. Short updates with no change can preserve more trust than one large announcement followed by silence.

Good practice is visible in ordinary work. People know what they may do, what they must check, who can decide, and where an exception goes. Leaders hear the same account from different teams because the framework is shared rather than remembered differently.

The aim is not perfect control. The aim is a system that notices when reality changes and knows who has to respond. That creates movement without pretending uncertainty has disappeared.

Make the answer operational

Start with the smallest version of the decision that still changes behaviour. Put it in plain language and test it with the people who will use it under pressure. Ask them what they would do, what they would record, and who they would call when the ordinary case stops being ordinary. Their hesitation will show where the instruction is still abstract.

Then connect the decision to the systems around it. A rule without training becomes a document people forget. Training without authority becomes advice people cannot follow. Authority without review becomes a permanent answer to a changing question. The three have to move together, with one person accountable for keeping them connected.

Review the result through actual work rather than confidence surveys alone. Look at a sample of decisions, outputs, exceptions, and escalations. Ask whether the intended boundary held and whether people found a hidden route around it. When the evidence changes, revise the operating choice openly and record why. That is not inconsistency. It is governance doing its job.

What to do on Monday

1. Ask an employee outside leadership to read the draft. Keep the action small enough to complete, specific enough to observe, and connected to a named decision rather than a general ambition.

2. Move people impact ahead of efficiency language. Keep the action small enough to complete, specific enough to observe, and connected to a named decision rather than a general ambition.

3. Schedule the next three updates before the first one goes out. Keep the action small enough to complete, specific enough to observe, and connected to a named decision rather than a general ambition.

Begin where decisions happen

Start with the room.

Book an executive session