Your first 30 days

The first month in a management role shapes how your team sees you for a long time. The goal is not to change everything. It is to listen, learn and build trust, while keeping the work moving.

Before day one

If possible, talk to your new manager about expectations:

• What does success look like in three and six months?
• What are the known problems with the team or its work?
• What decisions can you make alone, and which need discussion?

Also ask the previous manager, if there was one, for a handover: each person's goals, recent feedback, ongoing concerns and commitments made to the team.

Week one: meet everyone

Hold a first one on one with each person on your team. Keep it open and curious. Useful questions:

• What do you enjoy most about your work here? What do you enjoy least?
• What is one thing you would change about how the team works?
• How do you prefer to receive feedback?
• What do you hope to be doing in a year?
• What should I know about you that will help me support you?

Take notes and do not promise solutions on the spot. Listening carefully is the first signal that you are a manager worth trusting.

Weeks two to four: map the landscape

• Meet key partners: the product manager, designers, peer managers and the teams you depend on.
• Read the team's recent planning documents, incident reports and retrospectives.
• Observe the team's rituals before changing them.
• Make a list of themes you are hearing: problems mentioned by several people, strengths, open questions.

Small, visible wins

Look for one or two small problems you can fix quickly, such as a broken build pipeline that wastes everyone's time or an unclear on call schedule. Fixing them shows you listen and act, without making big changes before you understand the context.

Avoid these early mistakes

• Announcing a big reorganisation of how the team works in week one. You do not yet know why things are the way they are.
• Becoming the bottleneck. If every decision and review goes through you, the team slows down and you burn out.
• Disappearing into meetings. Stay present in the team's day to day work, even if you write less code.

Write a short summary

At the end of the month, write a one page summary of what you learned and what you plan to focus on next. Share it with your manager and, in an appropriate form, your team. It shows you listened and gives everyone a clear sense of direction.