Picture this: on Friday you merged your last pull request as a developer. On Monday you walk into the team room as the new team lead, and seven people look at you, waiting for some kind of direction. Nobody gives you a README for that moment. In my view, it is one of the hardest role changes in our industry, and what helps most is surprisingly unglamorous: a simple plan for the first three months.
I wrote a detailed guide with question lists and a copyable template in my article 90-day plan for new managers. Here is the condensed idea and the parts I find most important.
Why plan your own start at all?
The concept goes back to Michael D. Watkins and his book "The First 90 Days". One idea from it stuck with me: the breakeven point, the moment when you give the organization more than your onboarding costs it. A plan gets you there faster because it protects you from two opposite mistakes. One is blind activism, where you start changing things before you understand why they are the way they are. The other is endless waiting for things to "settle".
Just as important: the plan is not a contract and not a Gantt chart. I treat it as a working hypothesis that I revisit every couple of weeks. If a production incident takes over your first month, you simply move the phases. The point is to decide deliberately instead of drifting.
Three phases, three guiding questions
I split the 90 days into three rough blocks, each with one question that helps when priorities collide:
- Understand (days 1–30): How does this team work today, and why? Your most useful tool here is listening. Hold a longer one-on-one with every person, take notes per person, and have an explicit conversation with your own manager about what success in six months looks like and where you may decide on your own. Avoid rebuilding processes you don't understand yet.
- Early wins (days 31–60): Where can I make a visible difference with little effort? Condense your notes into a handful of neutral observations, reflect them back to the team, and let the team confirm or correct them. Then pick a small problem together, one the team named itself.
- Set direction (days 61–90): Where do we want to be in six months? Write a short vision, align it with your manager first, then discuss it with the team, and start handing over responsibility.
What I would emphasize differently
Watkins talks about early wins as something the new leader achieves. I see it a bit differently: the best early win is a win for the team that you enable. A flaky test that has annoyed everyone for months, or a meeting nobody needs anymore. Small things, but they show that problems in this team now actually get solved.
A vision also does not need to be a polished statement. Half a page is enough if it answers what the team is there for, how you will notice improvement, and what you deliberately leave out. That last part is the one people skip, and without it a vision is just a wish list.
The trap I see most often
If you are promoted from within your own team, the biggest temptation is to stay the technical hero. Code gives quick feedback, leadership doesn't. But every task you pull to yourself is a learning opportunity someone on the team misses, and you end up blocking decisions the team should make. Google's Project Oxygen research lists technical skills among the traits of good managers, but "is a good coach" sits at the top. I find that order telling.
Two related traps: relationships with former peers change whether you like it or not (naming that openly helps a lot), and many new leads try to solve everything alone instead of finding a sparring partner outside the team.
What the full article covers
- Concrete question lists for the first one-on-ones and for the conversation with your own manager
- Criteria for choosing a good early win and how to make working agreements visible
- How to ask for feedback on your start in a small team
- A week-by-week template for your own 90-day plan, ready to copy
You'll find all of it in the original article: 90-day plan for new managers: guide and template.
📖 This is the condensed version. The full article on sascha-ms.de goes deeper – with all code samples, diagrams and a short knowledge check.
👉 Next step: Preparing a first one-on-one? My question cheat sheet puts the best questions on one printable page.
📬 Stay updated: New articles on serverless, AI and leading tech teams via RSS, browser push or the weekly newsletter (in German).
Originally published on sascha-ms.de. More articles on serverless, AI in everyday development and leading tech teams: sascha-ms.de/en

