Your First Leadership Role at a Startup: The First 90 Days

Your First Leadership Role at a Startup: The First 90 Days

By Deep Work Club · Last updated: October 2026 · Reading time: 11 minutes

Your first leadership role at a startup rarely comes with preparation. Usually you are the person who delivered the most, and suddenly you are expected to lead a team that sat next to you yesterday. This article shows what really changes for a new manager in the first 90 days, gives you a 30/60/90-day plan as a table, lists the conversations to have early and describes the traps almost everyone falls into.

Key takeaways

  • "Never learned to lead" is the norm: In our work with leaders and people teams, a missing leadership toolkit is one of the topics that comes up most often. People get promoted for delivering, not for leading.

  • Your first leadership role is an identity shift, not a skills upgrade. Linda Hill (Harvard Business School) followed 19 new managers through their first year: moving from doing to enabling is a psychological transformation, not just new material to learn.

  • The best specialists often struggle most. The curse of knowledge (Camerer, Loewenstein & Weber, 1989) describes how experts cannot set aside what they know. They underestimate how hard things are for others.

  • The first 90 days can be planned: 30 days of listening, 30 days of creating clarity, 30 days of building rhythm and delegation.

  • Training works: According to Gallup (2025), most managers worldwide say they have never received any training. Those who do are half as likely to be actively disengaged.

What really changes in your first leadership role?

In your first leadership role, the way your success is measured changes: until now, what you delivered yourself counted; now what counts is what your team achieves without you. Doing becomes enabling. You work less on the task and more on clarity, priorities and people, and at first that work is hard to see and hard to measure.

Linda Hill, a professor at Harvard Business School, followed 19 people through their first year as managers for her book Becoming a Manager. Her finding: the move is a genuine transformation of professional identity and a process of learning from experience, not a checklist to work through. In her Harvard Business Review article "Becoming the Boss" (2007) she describes why new managers stumble at first: they expect formal authority and control. In reality they are caught in a web of dependencies on their team, their own boss and their peers. Authority has to be earned, and the goal is real commitment, not mere compliance.

That matches our work with leaders and people teams: hardly any topic comes up as often as a first leadership role without preparation. Mostly, people simply lack the toolkit: authority with older reports, difficult conversations, motivating, delegating. Many new managers describe it like this:

"You get thrown in at the deep end and have to piece everything together yourself."

The gap often only shows in the team's feedback: organising well is not the same as leading well, and the team usually notices the difference before the manager does.

People get promoted for organising and delivering. Hardly anyone gets trained to lead. In its State of the Global Workplace report 2025, Gallup writes that most managers worldwide say they have never received any training. At the same time, manager engagement fell from 30 to 27 percent, and by five percentage points among managers under 35.

Why is the switch so hard for the best performers?

The best specialists often find their first leadership role especially hard because their knowledge gets in the way. If you are very good at something, you forget what it feels like not to be. Behavioural economics calls this the curse of knowledge. The result: unclear handovers, expectations set too high and the reflex to just do it yourself.

The economists Colin Camerer, George Loewenstein and Martin Weber coined the term "curse of knowledge" in 1989 in the Journal of Political Economy. Their finding: better-informed people cannot ignore what they know, even when it would be in their own interest. More information is not always better.

Stanford researcher Pamela Hinds looked at how this shows up at work in 1999. In two studies, people with different levels of experience estimated how long novices would need for a complex task. The more expertise someone had, the worse the estimate, and it was almost always too short. Techniques meant to correct this barely helped. People with intermediate experience tended to estimate more realistically.

For your first leadership role, this means:

  • Your briefings are shorter than you think. What is obvious to you is missing context for others.

  • Your time estimates for others are too optimistic. Build in more buffer than feels right.

  • "It's faster if I do it myself" is true in the short term. In the long term it is the direct route to becoming the bottleneck.

A simple countermeasure: have people explain a task back to you before they start.

What does a 30/60/90-day plan for new managers look like?

A good 30/60/90-day plan for new managers has three phases: in the first 30 days you understand people and expectations, in days 31 to 60 you create clarity about roles and routines, and by day 90 you build a rhythm in which you hand work off instead of collecting it.

A widely used framework for this period comes from Michael Watkins' book The First 90 Days. For a first leadership role at a startup, it breaks down like this:

Phase

Focus

In practice

How you know it's working

Days 1–30

Listen and understand

A 1:1 with every person on the team. An expectations conversation with your own manager. A list of every task you still do yourself. No major restructuring yet.

You can say for each person what motivates them and what is holding them back right now.

Days 31–60

Create clarity

Write down expectations and responsibilities for each person. A fixed 1:1 rhythm and one team meeting per week. Hand off your first tasks deliberately. Give feedback early and in small doses.

Nobody has to guess how performance is measured.

Days 61–90

Rhythm and delegation

Set priorities for the next quarter with the team. Clarify who decides on important decisions. Have the first difficult conversation instead of postponing it. Ask for feedback on yourself.

The team makes decisions that used to land on your desk.

The plan is a frame, not a contract. Priorities shift fast at startups, but the order of understand, clarify, hand off still makes sense.

Which conversations should you have in your first weeks?

In your first weeks as a new manager, have five conversations: a 1:1 with every person on your team, an expectations conversation with your own manager, conversations with peers in adjacent teams, an open conversation with former colleagues about your new role and one with someone outside the company.

  1. A 1:1 with every person on the team. Questions, not announcements: What's going well? What annoys you? What should I definitely not change? How do you like to receive feedback?

  2. An expectations conversation with your manager. How will my success be measured in six months? What can I decide on my own, and what not? How often do we want to talk?

  3. Peers in adjacent teams. Hill describes management as a web of dependencies. That web gets built in the first weeks, not when things are on fire.

  4. Former colleagues. Address the new role openly instead of pretending nothing has changed. How to do that well is covered in From Peer to Manager.

  5. Someone outside the company. Many new managers have no one at their level internally. Often there is also no experienced person above them to learn from. Being alone in the role, without a sparring partner, is a pattern we see again and again in our work with leaders.

What if you manage people who are older or more experienced?

When you manage people who are older or more experienced than you, status incongruence arises: age and experience don't match the formal hierarchy. That is not a personal failure but a measurable tension. It shrinks when you explicitly acknowledge expertise, describe your role clearly and address negative reactions early.

In 2017, Florian Kunze and Jochen Menges studied 61 companies in Germany with almost 7,800 employees for the Journal of Organizational Behavior. The larger the age gap between younger supervisors and older subordinates, the more often employees experienced negative emotions such as anger or fear. The authors explain this with status incongruence and violated career norms: many people carry an unwritten picture of when someone is "allowed" to lead whom. Where these emotions were expressed openly, this went along with weaker company performance. The authors explicitly do not recommend suppressing feelings. Instead, they suggest companies put less weight on career timetables and hierarchical thinking.

What helps in practice:

  • Name the expertise. "You've known this topic longer than I have. I need your assessment; depending on the topic, I'll make the decision with you or on my own."

  • Describe your role, don't defend it. Your job is not to know more. Your job is to make sure good decisions get made and the team moves forward.

  • Address the tension early. A short "How do you feel about me being in this role now?" in the first 1:1 takes two minutes and saves months of silent friction.

If you were promoted from within your own team, closeness adds a second tension. More in From Peer to Manager.

What are the typical traps in a first leadership role?

The three typical traps in a first leadership role are: doing everything yourself because it's faster, wanting to stay everyone's friend instead of taking on the role, and feeling like you don't really belong. All three are normal. They only become dangerous when they quietly turn into habits.

Trap 1: Doing everything yourself

The curse of knowledge makes doing it yourself tempting. It feels productive, and in the short term it is. After a few months, though, you are the bottleneck every decision waits on, and your team learns nothing. How to hand off work step by step is covered in Delegation in Hypergrowth.

Trap 2: Wanting to stay friends

Nobody wants to be the bad guy. So expectations stay vague and critical feedback gets postponed. The result is rarely harmony, but a lack of clarity. Often there is a good intention behind it: not becoming the kind of manager you once suffered under yourself. But being a good manager means having the uncomfortable conversations too. How to do that is covered in the article on difficult conversations at work.

Trap 3: Feeling like an impostor

Impostor feelings and constant comparison come up again and again with new managers. On the outside things go well; on the inside everything gets questioned. The feeling does not disappear with the next promotion. More in the article on impostor syndrome as a leader.

If I were a first-time team lead: what would I do differently?

If I were a first-time team lead today, I would try to prove less and ask more. I would change very little in the first weeks, write down early what I want to hand off, and from day one look for people who are in the same role for the first time or were recently.

Point by point:

  • I would redefine my first goal. Not "show that I can do it" but "understand what my team needs."

  • I would put every task I still do myself on a list and next to each one a date by which it sits with someone else.

  • I would ask my own manager how they will know in six months that I'm doing well. And write it down.

  • I would give the first piece of critical feedback within the first 30 days, small and concrete, so it becomes normal rather than an event.

  • I would find a group where I can say honestly what isn't working. Leaders rarely look for theory; they look for the experience of people in the same situation. A question we hear again and again in our work with leaders: "How do others solve this, and what worked for them?"

Three things for this week

  1. Task list: Write down everything you did yourself this week. Mark what only you can do. Everything else is a candidate to hand off.

  2. One expectations question: Ask your own manager: "How will you know in six months that I'm doing this role well?"

  3. One explain-back round: At your next handover, have the person explain the task back in their own words. You'll see where your knowledge played a trick on you.

Frequently asked questions

What should I do in my first 90 days as a new manager? In the first 30 days, listen and clarify expectations; in days 31 to 60, define roles and routines; by day 90, build a steady rhythm and deliberately hand off tasks. Hold off on major restructuring until you know your team.

Why do I feel overwhelmed in my first leadership role? Because the measure of success changes: before, your own output counted; now your team's does. In our work with leaders and people teams, a missing leadership toolkit is one of the most common topics. Feeling overwhelmed at first is normal, not a sign of a wrong choice.

What is the curse of knowledge? A bias described by Camerer, Loewenstein and Weber in 1989: people who know more cannot set their knowledge aside and underestimate how hard something is for others. For managers it shows up in briefings that are too short and timelines that are too optimistic.

How do I manage employees who are older than me? Explicitly acknowledge their experience, describe your role as enabling rather than knowing better, and address tension early. Research by Kunze and Menges (2017) shows that large age gaps go along with more negative emotions in the workforce.

How much should I still do myself as a new manager? At first, more than you'd like, but with an expiry date. Write down what you still do yourself and set a date for each task by which it sits with someone else. If you keep doing everything yourself, you become the bottleneck.

In summary

Your first leadership role at a startup is not a bigger job but a different one. Doing becomes enabling, and strong specialists in particular trip over their own knowledge. A 30/60/90-day plan gives you something to hold on to: first understand, then clarify, then hand off. Add a few early conversations and an honest look at the three typical traps.

In short: you don't become a good manager because you know everything, but because your team moves forward without you.

The Leadership Circle offers exchange with others who are at the same point right now.

Don't want to figure this out alone? In the Leadership Circle, up to ten leaders from Berlin startups and scale-ups meet regularly to exchange experiences, facilitated by Lea Mersch. Book a free intro call

Sources

  • Camerer, C., Loewenstein, G., & Weber, M. (1989). The curse of knowledge in economic settings: An experimental analysis. Journal of Political Economy, 97(5), 1232–1254. doi:10.1086/261651

  • Hinds, P. J. (1999). The curse of expertise: The effects of expertise and debiasing methods on prediction of novice performance. Journal of Experimental Psychology: Applied, 5(2), 205–221. doi:10.1037/1076-898X.5.2.205

  • Hill, L. A. (2003). Becoming a Manager: How New Managers Master the Challenges of Leadership (2nd ed.). Harvard Business School Press. First edition 1992: Becoming a Manager: Mastery of a New Identity.

  • Hill, L. A. (2007). Becoming the boss. Harvard Business Review, January 2007.

  • Kunze, F., & Menges, J. I. (2017). Younger supervisors, older subordinates: An organizational-level study of age differences, emotions, and performance. Journal of Organizational Behavior, 38(4), 461–486. doi:10.1002/job.2129

  • Watkins, M. D. (2013). The First 90 Days, Updated and Expanded. Harvard Business Review Press. First edition 2003.

  • Gallup (2025). Global Employee Engagement Drops for Only the Second Time in 12 Years. Press release on the State of the Global Workplace report 2025, 23 April 2025. gallup.com