When I started leading a team, the thing nobody warned me about was the change in what I was allowed to be good at. As a researcher, my job was to be right. As the person running the group, being right is worth very little if nobody tells you what is actually happening, and the fastest way to stop being told things is to arrive with opinions.
That is the real trap of a new leadership role. Most people who get one are there because they were good at the previous job, and the previous job rewarded fast, visible competence. So they show up, assess in a fortnight, and start changing things — reorganising, replacing processes, resetting priorities. Then they are surprised when information stops flowing and the team that seemed enthusiastic in the interview is performing worse than before they arrived.
The problem is usually not the changes. It is the order they arrive in. A Center for Creative Leadership paper on executive integration puts the commonly cited failure rate for leaders in new roles at around 40% within the first 18 months, and those failures are mostly not about technical competence. They are about the transition being handled badly.
Before going further, a caveat the hundred-day genre usually skips. The framework comes from executive transitions: an outsider parachuted into a large organisation with a mandate and a board watching. If you have just been made tech lead of four people you have worked alongside for three years, most of it applies at a much smaller scale, and one part of it applies in reverse — you already know the real issues, and your problem is that your former peers are now recalibrating what they can say to you. Read accordingly. The number itself is arbitrary. Nothing happens on day 101.
The first month: your job is to find out what is actually true
The instinct is to establish authority early. Resist it, not out of humility but out of self-interest. Whatever you learn in the first month is the least filtered information you will ever get, because people have not yet worked out what you reward and what you punish. That window closes fast.
Have a one-to-one with everyone who reports to you inside the first two weeks. Not a performance review, not goal-setting. Ask what is working that they would not want changed. Ask what wastes their time. Ask what they would fix if the decision were theirs. Then, and this is the part that determines whether the exercise was worth anything, shut up and let the silence run. People need a few seconds longer than feels comfortable to decide whether to tell you the real answer.
These conversations do three things at once. They give you information no dashboard contains. They tell your team you regard them as a source of knowledge rather than a resource to allocate. And they reveal who the informal leaders are, which is frequently not the most senior name on the list.
Do not stop at direct reports. Talk to a sample of people two levels down. Talk to the leads of the teams that depend on yours and that yours depends on. Find whoever has been there longest; they know which initiatives already failed and why, and that history is almost never written down anywhere you can read it.
The goal at the end of the first month is modest and specific: you can name the three to five real problems, as opposed to the problems described to you when you were hired.
Weeks five to ten: a direction specific enough to argue with
After a month of listening you have a picture of the current state. The next job is synthesis: what does all that mean, what changes, what stays, and where are we going.
This is where a lot of new leaders produce a document full of words like alignment, high performance and customer focus, which cannot be disagreed with because they do not say anything. That is the failure mode to avoid, and it is seductive precisely because nobody will object to it.
A direction worth writing down answers concrete questions. What does success look like in twelve months, stated so that a sceptic could check? What are the two or three things we are prioritising, and — the part people skip — what are we explicitly dropping to make room? What changes about the day-to-day? What are we deliberately leaving alone?
Specificity matters because ambiguity is not neutral. People fill it with their worst guess, which is usually that their own work is the thing about to be cut. A concrete plan they disagree with is less destabilising than a vague one they cannot read. And disagreement is the point: you want the objections before you start executing, not six months in when someone says they always thought it would not work.
Put it in writing, walk through it live, take questions, then follow up individually with the people whose buy-in actually matters. Some of the pushback will be ordinary discomfort with change. Some of it will be someone telling you about a constraint you did not know existed. Separating the two is a large part of the job, and you will get it wrong sometimes.
Weeks eleven onward: early wins that are not performances
The quick-wins idea gets mangled constantly. The point is not to generate visible activity. It is to demonstrate, through something small and real, that the things you said you cared about are the things you actually do.
If you said the meeting load was wasting the team's time and two standing meetings are gone by week twelve, that counts. If you said the relationship with an adjacent team was broken and you have personally built a working channel with its lead, that counts. Both are unglamorous, both are checkable, and checkable is the whole value.
What does not count: announcing an initiative with no evidence it is moving, redrawing the org chart without a reason anyone finds convincing, or making people changes early. Personnel decisions in the first months are read as a statement about your values, whether you intend them that way or not. Sometimes one is genuinely unavoidable. If so, explain the reasoning to the team more fully than feels necessary, because in the absence of an explanation they will construct one.
The failure I would warn a new lead about
Isolation, and it happens by accident. You get pulled into meetings with your manager, your peers and your direct reports, and within a couple of months the only picture of the work you have is the one that survives being relayed twice. You start making decisions on filtered data. You get surprised by things the team saw coming weeks earlier and assumed you already knew.
The fix is structural rather than attitudinal, because being a nice, approachable person does not solve it. Keep some skip-level contact going permanently — less often than in the listening phase, but on the calendar, not dependent on you remembering. Make it normal enough that it is not an event when it happens. This is not about going around your reports; it is about not building a bubble that only shows you what everyone has already decided you want to hear.
One more thing, since the genre rarely admits it. You will be worse at this than you expect for a while, and the feedback loop is slow — months, not sprints. The compensation is that the quality of your attention to individual people is the one variable entirely within your control, and it matters more than any framework, hundred-day or otherwise.
Tags
Taresh Sharan
support@sharaninitiatives.com