The Chief of Staff as Orchestrator of Change

The role, redefined

The Chief of Staff is too often read as a chief gatekeeper, a filter between the executive and the noise. That reading survives because most CoS roles were built for access control: who gets in the door, what reaches the calendar, what reaches the desk. I have held this role, and I have watched it defined this way, and I think that reading is now actively wrong.

The role the modern organisation actually needs is the opposite. Not a filter, but a conductor, the person who makes sure the strategy, the portfolio, the change programmes, and the operating model move as one system rather than five. A filter reduces noise. A conductor makes the whole system play in time. Those are different jobs, and the second one is the one that is increasingly missing.

I think of the Chief of Staff as orchestrator of change as the connective tissue between intent and execution. The executive sets intent. The portfolio funds it. The change programmes deliver it. The operating model holds it together. Almost nobody owns the holding-together, and that is the gap the modern CoS fills.

Why the old reading is now dangerous

The gatekeeper reading was fine when change was occasional. A year of steady-state operation, a quarter of transformation, back to steady state. The CoS filtered the steady state and protected the executive for the transformation quarter.

That model breaks when change is continuous, which is where most enterprises now are. John Kotter's argument in Leading Change was that change fails when it is treated as a discrete programme rather than a continuous capability.¹ We are now well past the point where transformation is a programme; it is the operating state. In that state, a gatekeeper CoS becomes a bottleneck; every decision routes through one throat, and the throat chokes. The conductor model scales; the gatekeeper model does not.

What the orchestrator actually does

I have come to four responsibilities that define the orchestrator role, and I test every CoS mandate against them.

• Holds the operating model. The CoS owns the map of how decisions get made, who owns what, and how work flows, and keeps it honest when reality drifts from the org chart. Skelton and Pais make the underlying point in Team Topologies: the org chart describes the intended flow of work, but the actual flow of work follows team interactions, and the two diverge fast.² The CoS is the person who knows where they have diverged and closes the gap.
• Aligns the portfolio to the strategy. Every funded initiative is checked against the strategy and against the other initiatives. Duplication and gaps surface here, not in delivery. This is where the CoS earns their keep; most portfolios I have audited contain at least two initiatives doing the same thing under different sponsors, and nobody notices until the CoS notices.
• Runs the cadence of change. Governance, portfolio reviews, and operating-model reviews share one rhythm, owned by the CoS, so intervention happens at the right time. Cadence is the cheapest lever a CoS has, and the most underused. Most organisations run governance, portfolio, and operations on three unrelated cycles, which is why intervention always arrives too late.
• Protects psychological safety for dissent. A transformation fails the moment bad news stops travelling up. The CoS is the channel that makes dissent safe and timely. Edmondson's research is unambiguous on this: psychological safety is what determines whether teams surface problems early, and surfacing early is what determines whether transformation succeeds.³ The CoS cannot manufacture safety alone, but they can model it, and they can protect the people who practise it.

The thing nobody tells you about the role

The part of the role I was least prepared for is how much of it is translation. The executive speaks strategy. The portfolio speaks value and risk. The delivery teams speak flow and blockers. These are three languages, and they do not translate automatically. Most of the value I have created as a CoS has come from being the person who can sit in all three rooms and carry the meaning across, turning a strategic intent into a portfolio filter, a portfolio filter into a team's definition of done, and a team's blocker into a decision the executive can actually make.

I think this is the real reason the conductor metaphor fits better than the gatekeeper one. A conductor does not play the instruments. A conductor makes sure every section knows where the beat is, and that the whole orchestra is in the same bar. That is the job.

Why this matters more now

As change programmes multiply and AI inserts itself into delivery, the cost of an un-orchestrated portfolio grows: duplicated funding, conflicting priorities, and decisions that are made and then unmade three levels down. I have seen this cost in real money: the same capability funded twice because two sponsors did not know about each other, the same change delivered three times because the cadence was not shared, the strategic priority re-litigated every quarter because nobody held the line between reviews.

The orchestrator is the role that turns a collection of transformations into a single transformation. Without it, an enterprise runs five transformations in parallel and calls it one. With it, the five become one system with one beat.

A good gatekeeper reduces noise. A good conductor makes the whole system play in time.

If I had to give one piece of advice to an executive hiring a Chief of Staff today, it would be this: hire for orchestration, not for access control. The access-control CoS is a holdover from a slower era. The orchestration CoS is the role your transformation actually needs.

¹ John Kotter, Leading Change (Harvard Business Review Press, 2012). ² Matthew Skelton & Manuel Pais, Team Topologies (IT Revolution, 2019). ³ Amy C. Edmondson, The Fearless Organization (Wiley, 2018).