How to take over a team as a new manager
To take over a team as a new manager, spend the first month understanding its work, habits, and expectations before changing routines. Agree one useful experiment with the team, provide the support it needs, and review the result. Use the first 90 days to establish shared expectations and a reliable working rhythm.
- Use this when
- You are taking responsibility for a team whose working habits and unwritten expectations are still unfamiliar
- Built for
- New managers, newly promoted leaders, and experienced leaders joining an established team
- The outcome
- Build shared expectations before changing established routines.
MAKE THE PATTERN DISCUSSABLE
Learn the team before changing its rhythm.
A new manager can mistake an unfamiliar habit for a broken process or assume everyone shares their expectations. TeamDynamics gives you a starting picture of the team’s working behavior. Combine it with listening and real examples before choosing what to preserve or change.
THE PLAYBOOK
A first-90-days plan for a new team manager
Taking over an established team means joining a system that already has habits and expectations. Use a team profile and real work examples to understand what to preserve, where people need support, and which change is worth testing first.
Prepare for the conversation
Gather the team's existing profile and working agreements if available, along with its current priorities. If you are starting a Pro assessment, invite the full team and explain the purpose before asking for responses. Schedule introductory one-to-ones and a team discussion; a result becomes more useful when people can explain the experience behind it.
- 01
Days 1–30: listen and understand
Review the team profile, priorities, and existing agreements. In introductory one-to-ones, ask what helps people do good work and which recurring situation costs them effort. Use the manager coaching view to prepare questions, then let the person explain their experience.
- 02
Days 31–60: agree one experiment
Bring the team together with the Team Discussion Guide. Share what you have heard, check the interpretation, and choose one issue worth addressing. Write a working agreement with clear ownership, a sign of progress, and a review date.
- 03
Days 61–90: review and establish the rhythm
Discuss what happened in the next real examples of work. Keep or adjust the agreement and clarify the expectations you and the team now share. Build individual support and the next team experiment into existing one-to-ones and planning meetings.
A WORKED EXAMPLE · ILLUSTRATIVE
Clarify decision rights without slowing the team
A new manager expects project leads to decide independently. The team has been checking most choices with the previous manager, so routine work now stalls while everyone waits for a cue.
The working agreement
For the next month, project leads decide routine changes within their agreed scope and record the choice. Changes affecting another team's deadline or the shared budget come to the manager with a recommendation. Review one example of each at the weekly team meeting.
- Who owns it
- The manager makes the boundaries explicit; project leads own decisions within them.
- When to review
- Review the first month of examples at the 60-day checkpoint.
- A sign of progress
- Routine decisions move forward and people can identify which choices still need the manager.
THE RELEVANT DIMENSIONS
Put precise language around the work.
TeamDynamics describes four parts of team behavior. For this moment, these are especially useful places to begin.
How information moves
How information becomes insight
How a course of action is chosen
How the team works toward its goals
START THE CONVERSATION
Discussion prompts: New managers
- 01
Which team habit should I understand before trying to change anything?
- 02
Where are my expectations different from the team’s current defaults?
- 03
What one agreement would make the next month of work easier?
PUT IT INTO PRACTICE
Review what changed in the work.
By day 90, revisit the trial with the team. Ask which habits you understand better, whether your expectations were clear, and where the team needs a different agreement. Use the manager coaching view to prepare individual support conversations, balancing potential tension with shared blind spots. Keep what helps and carry the next small experiment into the team's normal planning cycle.
Common questions: New managers
Can I start before everyone has completed a team assessment?
Yes. Begin listening, review existing agreements, and use the sample reports to plan questions. Solo can provide a team estimate from your own perspective, but distinguish it from a Pro result that combines completed team responses. Check what any existing result represents before using it in a team conversation.
Should I change the team's habits to match my preferences?
Start with the work and the team's examples. Your preference is useful context, but it does not establish the best approach. Preserve habits that serve the team and test changes where a specific expectation or recurring problem calls for them.
KEEP EXPLORING
One framework, more team moments.
StormingIndividual coaching
Leave with a useful experiment and clear support from the manager.
StormingLeading change
A practical change agreement covering what stays, what shifts, and the next checkpoint.
NormingRoles and responsibilities
A usable ownership map with explicit handoffs, delegated authority, and escalation rules.
YOUR TEAM, MADE VISIBLE
Give this conversation a shared starting point.
Add the complete roster once. Everyone contributes to the team result and receives guidance they can use.