Name the fatigue without diagnosing employees as resistant. People may not oppose change, but they may be exhausted by competing demands, unfinished initiatives, and constantly changing direction.

Thank them specifically. “Thank you for your resilience” is vague. Name what they carried, absorbed or delivered.

Acknowledge what the organisation underestimated. This demonstrates that leadership has learned something rather than merely asking people to regroup.

Clarify what’s changed, and what hasn’t. People need some sense of continuity, not another wholesale reset.

Say what will stop, pause or receive less attention. A priority is only credible when something else is deprioritised.

Separate essential work from transformation work. Teams need to know how to balance running the business with changing it.

Explain the sequencing. Not everything needs to happen immediately. Show what comes first, what follows and why.

Define what good progress looks like by year-end. Give people a realistic finish line rather than another broad ambition.

Give managers a usable message. A senior leadership announcement isn’t enough. Managers will need to explain what the priorities mean for each team.

Create permission to surface conflicts. Employees should know where to escalate competing demands when local priorities conflict with the enterprise message.

Be precise about what is known, unknown and still being decided. Blurring those categories makes employees suspicious.

Explain what leadership is using to make decisions. People can tolerate uncertainty better when they understand the logic, evidence and principles behind decisions.

Avoid manufactured excitement. Employees can distinguish genuine conviction from a motivational performance.

Give people something firm to organise around. This might be customer commitments, financial priorities, operating principles or a small number of near-term outcomes.

Be honest about constraints. If resources are limited, say so. Otherwise, employees experience the gap between the message and reality as dishonesty.

Match ambition with capacity. Don’t ask for ‘extraordinary execution’ while refusing to acknowledge workload, staffing or capability limitations.

Clarify where extra effort may be required, and where it should not be. A general call to “step up” can subtly signal an expectation of indefinite overwork.

Make the exchange explicit. If the organisation is asking more of people, what will it provide in return: recognition, development, autonomy, financial reward, time back, better systems or clearer decisions?

Set clear performance expectations without turning the message into a threat. People should understand the standard, how it will be assessed and what support is available.

Give employees agency. Explain what teams and individuals can control, influence or improve despite the uncertainty.

Commit to communication milestones. Tell people when they will hear more, even if the answer is still incomplete.

Equip managers for difficult questions. Morale is more often shaped by the manager's conversation after the announcement than by the announcement itself.

Allow room for mixed emotions. Employees can be concerned about the conditions yet remain committed to the organisation. Leaders don’t need to demand optimism.

Celebrate credible progress, not symbolic wins. Morale improves when people can see evidence that effort is producing something worthwhile.

Protect trust by acknowledging trade-offs. Every decision benefits something and places pressure elsewhere. Mature communication makes that visible.

Lead with the business problem, not the AI.
Explain what improves, for whom and why it matters. ‘AI-powered’ is not a commercial outcome.

Define the value in measurable terms.
Specify whether the solution should reduce cost, increase revenue, save time, improve quality or lower risk, and then explain how this will be measured.

Show the full cost and path to value.
Include integration, data preparation, governance, training, adoption and ongoing usage costs, not only the licence fee.

Address risk before buyers raise it.
Be ready to explain security, privacy, accuracy, human oversight, legal exposure and accountability. Governance is increasingly part of the buying case, not a late-stage technical discussion.

Bring evidence that resembles their environment.
A dazzling demo is weaker than a relevant use case, a realistic baseline, a customer result or a structured trial with clear success measures.

The more serious the situation, the greater the temptation to soften it. Unfortunately, that’s also when employees listen most closely for evasiveness.

Steer clear of euphemisms such as ‘workforce optimisation’, ‘resource rebalancing’ and ‘role impacts’, etc. They force employees to decode what leadership is avoiding saying.

Vagueness creates an information vacuum that employees fill with rumours, unofficial fragments and worst-case interpretations.

Carefully qualified language can sound legally safe but be operationally useless. Instead of “Some roles may potentially be affected”, say what’s being considered, who may be affected and when decisions will be made.

Avoid passive voice, which can make leaders sound unwilling to take responsibility. “Changes have been made” avoids saying who made the decision, why and what will happen next.

Use AI to help shape difficult messages, but don’t let it blandify them. Keep your personality, be specific and make sure you’re still saying something meaningful.

Don’t bury the actual message beneath several paragraphs of strategic context. Say what’s happening upfront, then provide the explanation people need.

Direct language can still convey empathy, dignity and respect. Fuzzy or overly softened wording is less kind because it leaves people uncertain about what’s really happening.

Don’t use warmth as camouflage. Appreciation rings hollow when it isn’t accompanied by clear information or fair action.

Read what you’ve crafted aloud. Ask whether a real person would speak this way to another real person facing the consequences.