103 Rules for First-Time Managers
Everything they should have told you before giving you a team.
You were good at the job, so they gave you a team, and nobody mentioned that the job had just changed completely.
Start with the job you've got. Each book takes a different part of working life, from your first team to the decisions that shape a whole organisation.
Everything they should have told you before giving you a team.
You were good at the job, so they gave you a team, and nobody mentioned that the job had just changed completely.
Because avoiding them is not a management strategy.
Sooner or later every manager has one: the colleague whose work keeps coming back wrong, the star who is brilliant at the job and exhausting to sit near, or two people who have stopped speaking and expect you to carry their messages. Waiting for it to sort itself out rarely works, and while you wait, the rest of the team is usually paying for it.
Less theatre. Better work.
Most teams have plenty of teamwork on display: a Monday stand-up, a charter from last year's away day, a dashboard on the big screen and a reply-all thread now on its thirty-first message. What they're often missing is anyone who could say who decides, what 'done' means or why the same argument with the same neighbouring team comes round every month.
Fewer gut feelings. Fewer expensive surprises.
Most hiring is done by busy people a few times a year, with a process inherited from whoever last had a vacancy. The advert describes an ideal candidate instead of a normal week, the interview rewards whoever is best at interviews, and the surprises turn up after the contract is signed, for the new starter as well as for you.
Get it finished. Not just nearly finished.
Plenty of projects reach 'nearly finished' on time. The expensive part is getting from there to an ordinary day when the result works and everyone knows who runs it. Sometimes that is the team who built it; either way, the budget, the patience and the original date tend to run out first.
You do not need to be the smartest person in the room.
You may have been promoted after doing strong technical work, and now the hardest problem on the team is how much of it depends on you: the designs waiting for your approval, the incidents that end with your phone ringing, and the system only you would dare to change.
Fix the system. Stop feeding the fire.
An operation can spend part of its day on work it created for itself: customers chasing things that should already have happened, cases reopened because they were closed too soon, jobs that were urgent only because someone upstream was late, and the daily rescue everybody has come to rely on. Because that work looks exactly like the real thing, it gets staffed and even praised, and the fire never quite goes out.
Build something people would actually miss.
Product teams are surrounded by encouraging evidence. Customers are polite in interviews, prototypes test well, launch traffic looks like success and an average can hide almost anyone who is struggling, so a product can collect a year of good news while nobody comes to depend on it.
The job changed. Nobody gave you the instructions.
You may have arrived through promotion, recruitment or founding the business. Now you're expected to help run all of it, with a budget round next month, a board paper due on Friday, managers doing the managing you used to do, and a job title that may or may not make you a director in law.
A launch email is not a transformation.
Imagine the system went live on time, the announcement was warmly received and the milestone turned green. Three months later the old spreadsheet is still doing the real work, one region has found its own way round the new process, and the programme report calls the whole thing a success.