Why Performance Dips When a Manager Changes — and What the Dip Actually Reveals
Why does performance dip when a new manager takes over?
Because in most operations, the departing manager was carrying a meaningful part of the operating model in their head, and nothing about the role required them to make it transferable. The successor arrives with a title, a team, and a set of objectives, and then reconstructs the daily routine from their own instincts — while the team simultaneously re-learns how it is being managed.
This is not a claim that every dip has the same cause. Performance moves for many reasons, and a manager change is often coincident with other disruption rather than the source of it. The claim is narrower and more useful: when a transition produces a sustained dip, the most common structural explanation is that the role was never defined beyond its outputs.
The distinction that matters is between a role that is a seat in a system and a role that is the system. Both look the same on an organization chart. Both can produce acceptable results for years. They diverge exactly once — at the handoff — and by then the information that would have prevented the divergence is walking out of the building.
Does every dip after a manager change mean standard work was undefined?
No. Some settle-in period is genuine. A capable successor inheriting a well-defined operation still needs time, because relationships, credibility, and operational context do not transfer on the day the badge does. The team is also reading the new manager, which is its own adjustment.
The error is treating that concession as the end of the inquiry rather than the start of it. A settle-in period is a quantity. It has a depth, a duration, and a cost — in output, in rework, in the attention senior leadership spends absorbing the noise. Once it is treated as measurable, the question becomes whether any of it could have been mitigated, shortened, or made less consequential.
That question points directly at succession planning for the role, and it is the question the settle-in explanation is usually deployed to avoid. Saying a new manager needs time to settle is not an explanation of a dip. It is a description of one, narrated as though it were weather. Organizations that build transition planning into how they govern operational change treat it as a managed risk instead, because it is one of the few disruptions that can be seen coming.
Why do organizations not see the gap until the handoff?
Because high performance conceals it. A manager who runs the operation from memory and intuition, and who delivers, gives the organization no reason to examine how the results are produced. The effectiveness is the camouflage.
The confidence then compounds the exposure. When leadership rates a departing manager highly, the assumption is usually that the transition will be straightforward — this person is strong, they will train their replacement well, the handover is in good hands. But the capability that made them effective is the least documentable thing they have. Judgment about which operator to keep off a job during a bad week, an early feel for a supplier problem before it reaches the line, the sense of when a number is soft for a reason that will resolve itself: none of that is on a page, and much of it the manager cannot fully articulate on request.
So the organizations most exposed to a hard transition are frequently the ones that feel most secure going into it. The stronger the individual, the more the operation has quietly reorganized itself around them, and the less of that reorganization is visible to anyone above.
When is a manager running on memory and intuition acceptable?
Often. A manager and their team can produce entirely sufficient results with very little of the operating model written down, and an organization that perceives that management as sufficient is not making an error. Output is the test they are applying, and the output is fine.
The liability is not the intuition. It is that the organization has no read on whether the performance it is seeing is standardized or personal, and therefore no read on what a transition would cost. Sufficient results look identical from the outside in both cases. The organization is not carrying a performance problem — it is carrying an unmeasured one.
This is why the fix is not a blanket documentation mandate applied to every manager. It is a decision about which roles the organization needs visibility into, based on what a bad transition in that seat would actually cost. Written definition is the most durable form of that visibility, because it is the only form that can be referenced once the person is gone. But it is not the only form — shadowing, deliberate mentorship, and paired working genuinely transfer standard work, and they do so in a way documentation alone never quite manages. They are simply fragile, because the transfer mechanism leaves when the person does. The trade-off is worth making explicitly rather than by default, usually as part of how operational discipline gets built into how the work runs.
How do you make manager standard work visible without documenting everything?
Start with the organization’s own articulated objectives and use them as the frame, then work outward through the surfaces where the manager’s routine is already partly externalized. The goal is not a complete transcript of what a manager does. It is enough definition that the role can be held by someone else.
The sequence in practice:
Organizational objectives and metrics first. If the business has articulated KPIs, objectives, or goals, use them as the interrogation frame with the current manager. These are our measures — how does your department support each of them, and what specifically do you do in service of each? The routine gets assembled from the answers.
Team-level objectives next. Much of what a manager does supports outcomes that never roll up to a company metric. Ask the manager directly what their team is actually optimizing for.
Team analytics and internal knowledge. Who does what, who is unusually good at which work, where the load concentrates. This is often where the tacit judgment first becomes speakable.
Existing systems. A competence or skills matrix, defined processes and procedures, and the performance evaluations the manager is presumably already conducting. Each of these is a surface where judgment has already been partly written down, so harvest from them rather than interviewing the intuition out of someone cold.
Judgment governs the whole exercise. The organization’s objectives are a starting frame, not a boundary, and they are not automatically sufficient to give the standard work its shape — that sufficiency has to be assessed rather than assumed. If the objectives turn out to be too thin to structure the conversation, that is itself the finding, and it is a finding about the organization rather than the manager. Firms working through this generally discover it is a process design problem before it is a documentation problem.
Who is accountable for defining manager standard work?
The work is shared; the outcome is not. Managers, the organization, and senior leadership each own a distinct part, and the accountability terminates at the top rather than dissolving across the layers.
The manager owns real ground. Defining the team’s routines and objectives, and from those the data collected, the performance evaluated, and the processes applied. They also own being able to articulate that clearly and consistently — which is the part that determines whether any of it is transferable or whether it stays resident in one person.
The organization owns strategic alignment. Manager standard work has to sit inside a wider context, and if the business has not articulated what it is optimizing for, the manager is being asked to derive a routine from nothing. An organization can be ineffective at its half of this, which is why responsibility cannot simply be handed up the chain and left there.
Senior leadership owns the outcome, and this is where the comfortable reading has to be closed off. A leader who reads "systemic" and concludes the problem belongs to no one in particular has just described the failure being named. A system is precisely the thing senior leadership cannot delegate ownership of — there is no layer above it to absorb the consequence. Building that ownership into a structured improvement framework is what stops it from becoming everyone’s responsibility and therefore nobody’s.
Do management system requirements address leader standard work?
Indirectly, and by implication rather than prescription. Every formal management system reduces to the same core: a process approach that delivers consistent outputs within a discipline. Quality systems aim that at meeting customer requirements; environmental systems at controlling environmental risk; occupational health and safety systems at controlling harm. Processes underpin all of them, and leadership is responsible for the system, which is composed of processes.
Leader standard work is therefore not adjacent to that requirement. It is the process approach applied to the act of managing. But no auditor will raise a finding because manager routines were not defined — that would be prescriptive, and these frameworks deliberately are not. What an auditor can do is look at results across a period of change. If a manager was swapped in the last year and performance moved, that is a thread worth pulling, and it can lead somewhere. The obligation lands through outcomes, not through a checklist, which is why organizations satisfying a quality management system on paper can still be carrying this exposure in full.
The practical framing is better than the compliance one anyway. Any significant change in an operation should trigger the same question: what does this change affect, and what needs to happen to control the risk it introduces. A manager transition is a change. It is one of the few that can be anticipated, and one of the least often treated as a controlled one. The requirements themselves point at interpretation — the organization determines which processes it needs and ensures leadership is installed to deliver them. Defining manager standard work is that interpretation, done in operational language.
Frequently asked questions
How much of a manager’s role should actually be written down?
Enough that someone else could hold the seat without reconstructing it from scratch. That usually means the routine (what gets looked at, on what cadence, producing what), the objectives the team is serving, and the decisions the manager makes that others do not. It does not mean a transcript of the working week. Over-documentation produces a binder nobody opens, which fails in the same way as no documentation: it is not usable at the moment of transfer.
What is the difference between a job description and manager standard work?
A job description states scope and accountability. Manager standard work states the recurring activity that produces it — what the manager reviews, how often, and what comes out of it. Most organizations have the first and not the second, which is why a successor can be told exactly what they are responsible for and still have no idea what to do on Monday morning.
How do you assess transition risk before a manager actually leaves?
Ask in more than one direction. Leadership above the role can say whether defined manager routines are an expectation anywhere in the business, which establishes the ceiling. The manager can describe their own standard work, and the texture of that answer is informative regardless of what it contains. And the surrounding artifacts — competence matrices, process definitions, performance evaluation records — show how much has already been externalized. Where the exposure is material, this is often handled as part of broader process optimization rather than as a standalone exercise.
Does this apply to promotions from within?
Yes, and internal promotions often mask the problem more effectively than external hires. The successor already knows the operation, so the early weeks look smooth and the organization concludes the transition went well. What surfaces later is that they are running the role from their own instincts too, and the routine has quietly changed without anyone deciding it should. The dip is shallower and the drift is harder to see.
Where to start
Pick the manager whose departure would hurt most and ask them to describe their standard work — what they look at, how often, and what it produces. Then ask their leadership whether the answer matches what the business needs from that role. The gap between those two answers is the transition risk, and it is available to you now rather than at the exit interview.
