The first ninety days are the only time not knowing is legitimate
A new manager arrives with two things: a title and a short-lived permission. The title is public, announced and signed. The permission is written down nowhere. Because they are new, they can ask questions, ask why a decision was made the way it was, ask for the most basic information a second time. Nobody reads this as a gap, because being new makes not knowing legitimate.
The permission feels open-ended, and it is not. Within a few months, without anyone saying so, the expectation shifts. The same question asked in month three draws a small pause; asked in month six, it reads not as curiosity but as a deficit. A new manager's most valuable asset in the first ninety days is not what they know but their right not to know. Most spend it without ever seeing it as an asset.
Why it does not look like a right
It stays invisible because the manager experiences it as a weakness. They usually reached the seat on the strength of what they knew: they mastered a field, solved problems faster than others, were the person in the meeting with the answer. Their identity is built on knowing. Being, for the first time, the one who does not know feels like a threat to that identity, and the manager removes it the fastest way available: by acting as if they know. The person who appointed them also chose them for what they knew, and showing a gap can feel like questioning that choice.
We wrote about why the first months after a promotion give misleading feedback in the skill that got you promoted. This piece looks at a different loss in the same period: the manager closing, by their own hand, a position they can never take back.
The pressure for a quick win spends the permission early
Almost every ninety-day plan asks for a quick win. The logic is easy to follow. The new manager should prove themselves early and show the team and senior leadership that something has started to move. The plan writes it as a goal and the manager reads it as a test. A test leaves no room for not knowing.
Where the permission goes
The permission rarely runs out in one large mistake. It goes in small, reasonable-looking steps:
- Announcing a restructure or a change of priorities in the first weeks, before knowing the team.
- Nodding through a topic in a meeting without understanding it, then researching it alone afterwards.
- Reversing a predecessor's decision without asking why it was made, because asking feels like accepting the inheritance.
All three look like decisiveness from outside, and sometimes they work. Each one makes it a little harder for the manager to say they do not know. The manager who made the first announcement is now a person with a plan, and a basic question from a person with a plan invites another: what was the plan based on. Every firm answer given early closes, for good, a question that could have been asked.
What the team reads
The team does not read these steps the way the manager imagines. It does not see someone who has the answers. It sees someone who does not need the questions. The consequence is quiet: people begin telling the manager not what they think but what they guess the manager wants to hear. The candid conversations of the first weeks were possible because the manager had not yet taken a side. Once the manager takes sides, they close.
The right not to know ends not with time but with the first firm answer.
The question not asked comes back as a surprise in month eight
The answers to questions not asked in the first ninety days do not disappear. They wait. They usually surface at a moment when the manager can no longer ask, as surprises: the most experienced person on the team has been thinking about leaving for months, a key client was relying on a verbal agreement with the predecessor, what senior leadership expects turns out to differ from what was discussed at hiring.
Most of this was in plain sight in month one. Someone knew, and was probably willing to say, if anyone had asked. The manager who learns it in month eight loses twice: once in dealing with the problem itself, and again in having to explain to themselves why they did not know sooner. Late information does not only bring a problem; it shakes the manager's trust in their own judgement.
Shame in hindsight
A sentence we hear often in coaching: if only I had asked in the first month. Behind it there is usually not a lack of information but shame. The manager had thought of asking and did not, because at the time the question felt like an admission of not being ready. Looking back, the cost of the question was small. The cost of not asking is paid months later, with interest.
This is also one root of the observation that the real test of a promotion arrives not in the first quarter but in the second year. What was not asked in the first ninety days returns, once the attention has moved on, as information the manager lacks.
Protecting the permission is a matter of record, not of plan
There is no way to extend the right not to know. It expires. There is a way to use it deliberately, and it runs through a small record kept beside the ninety-day plan. The plan writes down what the manager will do. The record writes down what they do not yet know.
A ledger with three columns
The record kept by the managers we work with on this usually holds three things:
- What they do not yet know, and who they could learn it from, with dates.
- Their first impressions, written in the first two weeks and kept unedited.
- The decisions they have deliberately deferred, and the information each one is waiting on.
The first column makes the questions visible; once a question is written down, not asking it becomes visible too. The second does a less obvious job. A new manager's first impressions are the only view not yet shaped by the organisation's habits. By month three most of them have begun to look normal. With the written version still there, the manager can tell what is genuinely normal from what they have merely got used to.
The language of deferral
The third column is the hardest, because in a manager deferral looks like indecision. A deferral that states its reason is not indecision. A manager who says the decision will come at the end of the month, after talking to three named people, is announcing a schedule, not an uncertainty. A deferred decision stated with its reason does not spend the right not to know; it turns it into a method. The team reads that not as weakness but as seriousness.
From the field
Managers moving into a new role usually come to us with their ninety-day plan. They describe how ambitious it is and which quick win they are aiming for. As the conversation goes on, it becomes clear that what they want to talk about is not the plan but the worry behind it: what happens if they cannot prove themselves fast enough.
The question we ask first
So in the first conversation we ask something before the plan: what they do not know right now, and why they hesitate to say so. The answer often begins with a long silence. Then the list arrives, and almost all of it is made of questions nobody would have found odd in the first weeks. The real work of the first ninety days is to ask those questions while the permission still holds.
From there we work out together who those questions go to, in what order and in what words. How we work begins with this question. Managing the team you used to belong to shows another side of the same transition, and our other pieces sit on the Perspective page.