Coffee mornings with team leaders are a practical change-management intervention when adoption depends on what happens inside teams. They create a live forum where team leaders hear the business case, test their understanding, ask questions, practise their role, and raise risks before those risks become resistance on the floor. This matters because change outcomes depend not only on project delivery, but on whether people adopt and use the new way of working; PMI explicitly warns that project outputs only create value when they are adopted and integrated into operations [PMI, 2013]. (pmi.org)

Team leaders are especially important because they translate enterprise messages into local meaning. Prosci describes people managers as communicators, liaisons, advocates, resistance managers, and coaches in change [Prosci, 2025]. Gallup’s workplace research similarly finds that managers account for at least 70% of the variance in employee engagement across business units, reinforcing why manager capability and confidence matter during change [Gallup, 2015]. (prosci.com)

A change coffee morning is a structured live engagement session for team leaders. It may feel informal, but it should have defined outcomes: aligned messages, clearer leadership expectations, surfaced concerns, practised conversations, and agreed next actions. ACMP’s standard defines stakeholder engagement as involving people affected by or able to influence change success, with attention to what stakeholders need to know and do [ACMP, 2025]. (acmpmexico.org)

Use coffee mornings when team leaders need to prepare before they brief their teams, when resistance is increasing, when impacts differ by team, or when the project is moving from design into readiness, deployment, or sustainment. They are less useful when key decisions are still too unclear to discuss honestly, or when leaders are invited only to “receive slides” with no chance to influence, question, or practise.

Before the session, gather the change case, impacted groups, timeline, adoption risks, known objections, decisions already made, decisions still open, and what team leaders are expected to do next. Prosci recommends that senior leaders carry organizational messages such as the business reasons for change, while immediate supervisors are preferred senders for personal impact messages [Prosci, 2025]. (prosci.com)

The change manager should prepare a short message pack, leader talking points, a frequently asked questions log, a risk-capture mechanism, and one or two realistic team scenarios. The sponsor should be ready to explain why the change is happening, why now, and the risk of not changing, because Prosci identifies these as the first questions change communications should address [Prosci, 2025]. McKinsey’s influence model also emphasizes understanding and conviction as one of four core conditions for behavior change [McKinsey, 2016]. (prosci.com)

Timing should match the project phase. In early design, use coffee mornings to sense impacts and test assumptions. Before go-live, use them to build readiness and rehearse team conversations. After go-live, use them to remove barriers, reinforce new behaviors, and capture lessons.

A company is introducing a new customer relationship management system across sales and service. Team leaders are worried that productivity will fall during the first month. The change manager runs three coffee mornings, grouped by function. The sponsor explains the customer and revenue rationale. The project lead demonstrates the new workflow. Team leaders then practise answering questions about workload, customer handoffs, and data quality.

During discussion, leaders identify that service teams need a different go-live checklist from sales. The change manager logs this as a readiness action, assigns an owner, and updates the training pack. Two weeks later, the next coffee morning reviews open risks, early adoption data, and recurring questions. This turns the session into a live adoption mechanism rather than a one-off communication event.

The first mistake is treating the coffee morning as a casual morale event. It can be warm and informal, but it still needs outcomes, actions, and follow-through. The second is overloading leaders with slides instead of helping them practise the conversations they must have. McKinsey’s model stresses skills, reinforcement, role modeling, and conviction, not communication alone [McKinsey, 2016]. (mckinsey.com)

Another mistake is inviting leaders too late. If team leaders first hear about the change at the same time as their teams, they cannot confidently translate the message. Finally, do not ask for feedback unless someone will review it, respond, and explain what changed or why it could not change.

Measure whether the action improves readiness and adoption, not whether people enjoyed the coffee. Useful indicators include attendance by priority leader groups, percentage of leaders who can explain the “why” and local impact, number and closure rate of captured actions, recurring questions by theme, leader confidence before and after the session, team briefing completion, training completion, go-live readiness, adoption of new process behaviors, and reduction in avoidable escalations. ACMP includes measurement, benefit realization, readiness, learning, and sustainability within change management practice, while PMI links two-way stakeholder communication and sensemaking to sustaining change [ACMP, 2025; PMI, 2013]. (acmpmexico.org)

60-minute coffee morning agenda

Opening script:
“Thank you for making time. This session is not a presentation to cascade. It is a working session to help you understand the change, test the message, raise what may get in the way, and prepare for the conversations your teams will need from you.”