On my first day in any new PM role, I've had the same two urges. Change something, quickly, so everyone can see why I was hired. And meet everybody, immediately, so nobody feels left out.
Both are wrong. It took me an embarrassing number of first days to work that out.
So this is the note I'd leave on my own desk, if I could get in early enough.
You don't have to justify the hire by Friday
The worry goes like this. They've brought in a project manager, which means somebody thinks something needs managing. If I haven't fixed a process, replaced a tool or redrawn a workflow by the end of week one, they'll wonder what I'm for.
Nobody is wondering that. They're wondering whether you're about to make their job harder.
A new PM who changes things in the first week is changing things they don't understand yet. The odd status column that looks pointless is there because of something that went wrong two years ago. The meeting everyone moans about is the only time two teams ever speak. You can't tell the dead weight from the load-bearing walls on day three, and the people who can are watching to see if you'll ask them first.
The pressure to prove yourself is real. It's also entirely yours. I've never once had a boss say, a week in, "I notice you haven't overhauled anything." I have had a developer say, months later, "I liked that you didn't come in swinging."
So write the ideas down. All of them. Keep the list somewhere private and look at it again in a month. Half will have been wrong, a few will have fixed themselves, and the two that survive will land far better coming from someone who's bothered to learn how the place works.
Don't say hi to everyone on day one
This one sounds rude, so stay with me.
The standard first day is a lap of the building. Twelve introductions, twelve handshakes or twelve video calls, and the same ninety seconds about yourself on repeat. Where you've worked. What you're here to do. A small joke that was quite good at 9.30.
By person six, you're a tribute act to yourself. You've heard your own patter five times and you're bored of it, which means they get the flat version. Worse, you've stopped listening properly, because you're busy remembering the last five names.
And person six might be the one who matters most. The quiet developer who knows where everything is buried. The account manager who'll either back you or work around you. They deserve the 9.30 version, with the good joke, and so does person eleven.
So spread it out. Two or three proper conversations a day for the first couple of weeks. Tell people that's the plan, so nobody thinks they've been skipped: "I'm getting round everyone properly over the next fortnight, and I'd rather do it well than fast." Nobody has ever been offended by that sentence.
You'll also learn more. In the first conversation you don't know what to ask. By the ninth, you're asking about the thing three other people have hinted at, and that's when the useful answers start.
What to do instead
Not nothing. Doing nothing looks exactly like being lost.
Ask people what they'd fix if they were you. They've usually been waiting years for someone to ask, and their answer tells you more than any handover document.
Find one small, boring irritation that's nobody's job, and quietly make it go away. A broken link in the template. A recurring invite with the wrong room. It's not change, it's housekeeping, and it tells people you notice things.
And read. The board, the old retros, the last three launch emails. Most of what you want to ask on day one is already written down somewhere, and turning up to a conversation having read it is the cheapest respect going.
The note on the desk
If I could only leave one line, it'd be this: they hired you for the year, not the week.
Slow down. Save the good joke for person six.
Keep reading


