Practical Solutions
How can a new COO build support for change before announcing the plan?
The answer is to make the first commitment an intelligence commitment, not a communication commitment. Before a new COO announces a plan, they need enough evidence to know which parts of it will travel, which assumptions are weak, and whose interpretation of the change will shape the organisation’s response.
Illustrative business scenario—not a reported client result.
A newly appointed COO arrives with a credible brief: reduce delivery delays, simplify handovers and make performance more visible. Within ten days, the executive team expects an announcement. The draft plan is sensible. It is also built mainly from formal reporting, a board mandate and the views of the people who commissioned the role.
The plan is not the first commitment
A public plan does more than describe work. It tells people what the new COO thinks the organisation’s problem is, who has been listened to and whose knowledge is not yet visible. Once that signal has been sent, changing course can look like retreat rather than learning.
That is why the first fortnight is often more valuable as a period of structured inquiry than as a runway to a polished announcement. Research on organisational socialisation identifies role clarity, task mastery, social acceptance and perceived fit as important adjustment indicators. It also finds links between proactive information-seeking, support and those early indicators. 1 The research is not a test of senior-COO transition plans, so it cannot prove that one conversation sequence will produce a successful change. It does, however, support the modest proposition that acceptance and usable organisational intelligence matter when someone is new to a system.
Why the normal announcement fails
The usual fix is understandable: consult the hierarchy, refine the slides and communicate with confidence. It looks decisive and keeps the timetable moving.
It also tends to reproduce the official account of the organisation. That account may be useful, but it is rarely the whole operating picture. The person who knows why a handover stalls, which measure gets bypassed or where a prior change lost credibility may not be the most senior person in the room.
The existing Insight on stakeholder sequencing explains why a seniority-ordered meeting list can miss informal influence. This is a different question. Here, the COO is deciding what must be learned before the plan becomes a public commitment.
Use the first fortnight to test the map
The useful task is not an open-ended listening tour. It is a short, bounded test of the assumptions carrying the draft plan.
- Write the working hypothesis. State the proposed change in plain language, the operational problem it is meant to address and the two or three assumptions on which it depends. For example: delays are caused by unclear ownership, rather than by capacity or an approval rule.
- Hear from contrasting positions. Speak to people close to the work, a respected informal connector, a sceptical voice and a leader accountable for the outcome. Ask what would make the plan fail, what previous attempts missed and what evidence would change their own view.
- Separate observation from interpretation. Record concrete examples, not labels such as “resistant” or “not collaborative”. Then compare the accounts. The difference between accounts is often where the next question sits.
This is not a request for agreement. It is a way of finding material information before agreement is treated as the goal.
Make one bounded change before the larger announcement
A new COO still needs to show movement. The alternative to a full announcement is not silence. It is one change that is small enough to revise and useful enough to reveal something important.
In this scenario, the COO asks two functions to run a four-week handover review on one recurring delay. The group agrees a visible owner, a single escalation route and a short weekly check. The COO is explicit that the exercise tests the diagnosis; it does not settle the wider operating-model design.
That distinction matters. It gives people a way to contribute evidence without asking them to endorse a direction whose consequences they cannot yet see. It may also reveal that the delay comes from an approval bottleneck, a customer-information gap or a legitimate capacity constraint. Any of those findings would improve the eventual plan.
Measure whether the plan is getting better
The potential payoff is not instant buy-in. It is a better-founded first move and less avoidable rework after the announcement.
Track a small set of measures that distinguish activity from learning: the number of material assumptions revised; the range of functions and levels represented in the evidence; the time from contrary evidence to a documented decision; and whether the pilot clarifies ownership without creating new unmanaged work.
Released time should be treated as released capacity, not as cash saved. A four-week pilot cannot establish that a wider transformation will deliver a financial return. It can show whether the next decision is being made with a more accurate map.
The limits of this approach
Some decisions cannot wait for a fortnight of inquiry. A safety issue, contractual exposure or acute operational failure may require immediate action. In those circumstances, the new COO can still name what is temporary, what will be reviewed and what evidence could alter the next step.
This approach also does not replace organisational change expertise, employment processes or technical assurance. It is a decision discipline for the moment before a new leader turns a plausible plan into a public commitment.
Start with a clearer baseline
If you are entering a senior leadership role, the Leadership Transition Programme’s Free Assessment is the current no-cost starting point. It is presented by the site as a 15-minute baseline assessment with no commitment. The particular stakeholder landscape and transition pressures still need to be understood in their own context.