Week one is not a test of how quickly you can improve things. It is the week in which the team decides what kind of manager they have, and almost every mistake that gets made in it is made out of a sincere desire to be useful.
The five things to do
1. Say what the first month is for
The single cheapest thing on this list. Two sentences to the whole team: you are spending the first few weeks understanding how the work actually runs, you will report back by a named date, and until then you are changing very little.
A team that gets a new manager spends the first two weeks speculating about what is about to change. Naming your intention removes that, and naming a date means you can be held to it — which is the point. Write the date down.
2. Meet everyone, one at a time
Forty-five minutes each, inside two weeks, in private. Not a group session, not a corridor conversation, and not batched to save time.
The order you see people in is read as a ranking, so decide it deliberately: either go alphabetically and say that is what you are doing, or start with whoever is most likely to be worried — the person who applied for your job, or the one who has been told they are a problem.
Ask fewer questions than you planned and follow up properly on the ones you do ask. Six questions with real follow-ups beats sixteen at speed. A few that earn their place in almost any first conversation:
- What does a good week look like for you? What does a bad one look like?
- What is slowing you down that you have stopped mentioning?
- What do you think I am going to change, and what are you hoping I do not?
- What should I not do in my first month?
- What did I not ask about that I should have?
That last one is worth asking every single time, and it is the one people remember.
3. Ask your own manager two questions
Of the conversations in week one this is the easiest to leave out, and the one most likely to prevent a surprise at day ninety.
- What does success look like at ninety days, specifically? If you get adjectives, keep asking. “Settled in” is not a criterion, and you cannot be measured fairly against something nobody wrote down.
- What am I allowed to change without asking you? Spend, headcount, process, anything visible outside the team. In writing if you can get it.
Two more, if the conversation allows: how do you want to hear bad news and how fast, and is there anything about a member of my team I should know that is not in a system.
4. Fix one small thing
Something boring and specific — an access request, a license, a broken report. The point is not the fix. The point is that somebody told you a problem and a thing happened, in week one, which is the fastest way to establish that talking to you is worth the effort.
5. Write it down, in two lists
Facts and quotes in one, your interpretations in the other. Write them up after each conversation rather than during it — typing while somebody describes a problem with their last manager changes what they are willing to describe.
Keeping the two lists apart matters because they age differently. In six weeks you will find that some of the second list was wrong and all of the first list is still useful.
The five things not to do
- Do not announce a vision. You do not have one — you have an impression formed in three days, and announcing it commits you to defending a position you will want to change by week six.
- Do not restructure anything. Not roles, not ownership, not who sits where. A reorganization is the most expensive possible way to discover that the org chart was not the problem, and the person you moved pays for the lesson.
- Do not touch the calendar yet. Audit it in week two — list every recurring meeting and what it is for — but change nothing until week five, and not until you have attended each one at least three times. A meeting you have been to twice is a meeting you do not understand, and the ones that look most pointless from outside are occasionally load-bearing in ways nobody has written down.
- Do not compare this team to your last one out loud. Ever, and especially not favorably. It tells everyone the standard lives somewhere else, with people they will never meet.
- Do not accept anyone’s summary of anyone else. Someone will usually tell you within days who the problem is. Treat it as an allegation to verify, not a conclusion to act on — if there were a record, you would have been given the record.
What week one actually feels like
Unproductive, and slightly fraudulent. You will end most days having produced nothing you can point at, in a job you were given because you produce things. Several people will ask you questions you cannot answer.
That is the week working correctly. Its output is not a decision or a plan. It is a set of relationships in which people are willing to tell you things, and a rough map of how the work actually moves — and there is no way to acquire either of those faster.
One thing to do before your impressions harden
Write down what surprised you this week. In three months you will have normalized all of it, and that list is the only record you will ever have of how this team looks to somebody arriving fresh. It is also, more often than not, where your first genuinely good change comes from.
Where the questions came from
The questions above are a small extract. The First-Week Listening Questions guide is free and ungated — fifteen questions across the three conversations you cannot postpone, each with what it is really asking, what a useful answer sounds like, and the follow-up, plus the fourteen-day report-back that decides whether the whole exercise built trust or spent it.
The full method — including the arithmetic that works out whether your week has room in it for the job at all — is The New Manager’s First 90 Days Playbook.
