The new manager's first month, and the questions nobody can answer

A new manager stepping into a role inherits three things: a team, a set of responsibilities, and a body of decisions already in motion — active exceptions, ongoing arrangements, judgement calls their predecessor made that are still shaping how the team operates. The first two get handed over reasonably well, usually through a formal process. The third almost never does, because there's rarely a formal process for handing over decisions rather than duties.

Why the gap is worse for managers than for individual contributors

An individual contributor inherits a role's tasks and processes. A manager inherits those, plus every judgement call embedded across their whole team's operations — pricing exceptions, staffing arrangements, informal agreements with other departments, unwritten priorities that shaped how the team allocated its time. A new manager who only receives a handover on formal responsibilities is missing the layer that actually explains why the team currently operates the way it does.

This produces a specific, recognisable pattern in a new manager's first month: they ask a reasonable question — why does this report get this priority, why is this arrangement structured this way — and get an answer that amounts to "that's just how it's been done," because the person who could explain it fully is either gone or was never asked to pass the reasoning along explicitly.

Where this creates the most friction

Questioning something that turns out to matter more than it looked. A new manager, trying to make an early positive impact, changes something that seemed inefficient — only to discover it existed for a good reason nobody explained, and now has to walk the change back, at some cost to their credibility with the team.

Inheriting relationships without their context. A new manager takes over interactions with other departments or external parties who have an established, informal understanding with the previous manager — an understanding the new manager has no way to know exists until they accidentally violate it — see the vendor relationship that lived in one person's phone.

Team members who assume the new manager already knows. Because the team has been operating under certain unwritten rules for a long time, they don't think to explain them — they simply expect the new manager to already understand context that was never actually documented anywhere, and only becomes visible when it's violated.

Why a standard handover checklist doesn't catch this

A typical management handover covers structure: org chart, budget, key metrics, direct reports. All useful, and all silent on the specific judgement calls currently shaping the team's day-to-day operation. This is the managerial version of the gap this entire cluster keeps returning to — a system of record for structure, with no equivalent for the reasoning underneath it — see what a system of record cannot do.

Building a better handover for incoming managers

Add a section specifically for "things that look odd but exist for a reason." Ask the outgoing manager, or a senior team member if there's no outgoing manager to ask, to list anything a newcomer might reasonably want to change, along with the reason it's currently the way it is.

Give the new manager permission to ask "why" without it reading as a challenge. A culture where a new manager's questions are treated as reasonable curiosity, rather than criticism of existing practice, gets faster and more complete answers than one where questioning the status quo feels risky.

Delay major changes until the reasoning behind existing arrangements has actually been checked. Not indefinitely — but a short deliberate pause before changing something inherited, specifically to ask why it exists, prevents most of the credibility-damaging reversals that come from acting too early on an incomplete picture.

Common questions

Why do new managers struggle more with this gap than individual contributors?

Because a manager inherits not just their own tasks, but every judgement call embedded across their whole team's operations — pricing exceptions, informal arrangements, unwritten priorities. A standard handover rarely covers this layer, leaving a new manager with structural information but no access to the reasoning that actually explains current practice.

What's a common mistake new managers make because of this gap?

Changing something that looks inefficient early on, without realising it exists for a specific reason, and then having to reverse the change once the reasoning surfaces — at some cost to their credibility with the team, who may have expected the new manager to already understand why things were done that way.

Why doesn't a standard management handover checklist solve this?

Because it typically covers structural information — org chart, budget, key metrics, reporting lines — and stays silent on the specific judgement calls currently shaping day-to-day operations. Structure transfers easily through a checklist; the reasoning behind non-obvious decisions usually doesn't.

How can a business improve handovers for incoming managers?

Add a specific section covering things that might look odd to a newcomer but exist for a documented reason, encourage new managers to ask "why" without it being read as criticism, and build in a short deliberate pause before major changes so the reasoning behind existing arrangements can be checked first.

Related: what a system of record cannot do · the vendor relationship that lived in one person's phone · succession planning for knowledge not just roles