The first week is the only one where doing very little is the correct strategy, and it is the week almost every new manager spends trying to prove they deserve the job. The instinct is understandable. It is also how people spend month two undoing what they did in week one.
Here is what the five days are actually for.
Day one: say less than you want to
You will be asked, formally or not, to say a few words about how you intend to run things. Keep it short and keep it free of promises. Anything you commit to on day one is a commitment made with no information, and people will remember it precisely because it was your first statement.
Three sentences are enough: you are here, you intend to spend the first weeks understanding how the team works before changing anything, and you will be speaking with each of them individually this week. That last one is the only promise worth making, because you can keep it.
Avoid the open door speech. Everyone says it, nobody believes it, and it costs you credibility you have not earned yet.
Day two: get the expectations above you in writing
Before you work out what your team should be doing, find out what you will be judged on. Ask your own manager directly: in six months, what does a good outcome from this team look like, and what would make you consider this a bad quarter.
Write the answer down and send it back in an email confirming your understanding. That is not bureaucracy. It is the difference between managing toward a target and managing toward your own guess about a target, and the guess is wrong more often than anyone expects.
Ask two more things while you are there: what is already known to be broken here, and who outside the team you need to be on good terms with.
Days two to four: one conversation with each person
Thirty minutes each, individually, before the end of the week. Not a performance discussion and not a welcome chat. You are trying to learn what each person actually does, what they are stuck on, and what they think is broken.
Ask more than you tell. The ratio should be uncomfortable. A first-time manager who spends these meetings explaining their philosophy has wasted the only moment when people will tell them the truth cheaply, because you are still new enough to be told things without it counting as a complaint.
Questions that work, and the ones that do not, are covered in your first one-on-one with each team member.
Day five: write down what you think you have seen
At the end of the week, record your first impressions. Who seems strong, who seems disengaged, what looks inefficient, what seems to be the real bottleneck.
Do not act on any of it. The point of writing it down is that in four weeks you will read it again, and a good third of it will be wrong. The person who seemed disengaged was covering for somebody. The inefficient process exists because of a client requirement nobody mentioned. Knowing exactly which of your instincts misfired is the most valuable thing you take out of month one, and you cannot get it from memory.
What to avoid, specifically
- Changing a process. Whatever looks stupid probably exists because something worse happened once. Find out what before you remove it.
- Promising anything to your team. Headcount, tools, budget, flexibility. You do not yet know what you can deliver, and an unkept first promise is expensive for a long time.
- Criticizing your predecessor. Half the room liked them. All of the room will note that you talk about absent people.
- Doing the work yourself. You will be faster at it than anyone. That is exactly why it is a trap.
- Picking a favorite. Somebody will be helpful and pleasant in week one. It is often the person with the most to manage upward.
The one exception
If something is actively on fire, a deadline in days, a client about to leave, a person about to resign, you act. Wait and see is a default, not a rule. The test is whether the cost of waiting four weeks is real and measurable, or whether it just offends your sense of how things should be run.
Frequently asked questions
What should I say to my team on my first day as a manager?
Very little. Say that you will spend the first weeks understanding how the team works before changing anything, and that you will meet each person individually that week. That last promise is the only one worth making, because you can keep it.
Should I meet every team member in my first week?
Yes, thirty minutes each, one at a time. You are trying to learn what each person actually does, what slows them down and what they think is broken. Ask far more than you tell.
What should a new manager avoid in the first week?
Changing processes, promising things to the team, criticizing your predecessor, doing the work yourself and picking a favorite. Each one feels reasonable in the moment and costs you for months.
How do I find out what my boss expects from me?
Ask directly what a good outcome from your team looks like in six months and what would make it a bad quarter. Then confirm the answer back in writing, so you are managing toward a target and not toward a guess.
Next: the full ninety-day structure, and where week one fits into it. If the week leaves you wondering whether you deserve the job, read imposter syndrome in your first management job.