First Months
Joining a team that is already in trouble
Arriving somewhere with a backlog, a departure and low morale is a specific situation with specific traps, and the ordinary onboarding advice does not fit it.
By Julien Perrot3 min read

You can usually tell within a fortnight
The signs are consistent enough to name. Several people left recently and were not replaced. Meetings are attended by fewer people than were invited. Nobody can tell you who owns a particular system, and the answer to most questions is that the person who knew has gone. There is a deadline nobody believes in, and a quiet tolerance for missing things that would elsewhere cause a fuss.
None of this was visible at interview, and the fact that it was not visible is itself worth noting. Struggling teams recruit; that is often why the vacancy existed. It does not mean you were deceived — the people interviewing you may have been describing the team they are trying to rebuild rather than the one that currently exists.
The trap is being handed everything at once
A team short of people will absorb whatever capacity arrives. Within weeks a new joiner can find themselves nominally responsible for three things they have not been taught, because there is nobody else and because saying yes felt like the only available answer. The pressure is not malicious. It is arithmetic.
What makes this dangerous is that the ordinary protections of a first month quietly disappear. There is no ramp-up, so there is no period where mistakes are expected. There is nobody with spare attention to check your work, so errors survive longer. And the reputation you build is formed under conditions that would stretch someone experienced, which is not a fair test and will not be described as one afterwards.
The useful discipline is to accept work one item at a time and to say out loud what each acceptance displaces. Not a refusal — a statement of consequence. If I take the weekly report on, the migration slips by about a week; is that the trade you want? Managers under pressure are often making these trades unconsciously, and making them explicit is genuinely helpful rather than obstructive.
Do not diagnose out loud in the first month
You will see what is wrong quickly, and some of what you see will be correct. Saying it early is still a mistake, because the people around you have almost certainly seen it too, have probably tried to fix it, and have reasons for the current state that you have not yet heard. A newcomer explaining the obvious problem to people who have been living inside it lands as contempt even when it is not.
Write the observations down privately with dates. Revisit them at month four. The ones that survive are worth raising, and by then you will be able to raise them as someone who has carried the consequences rather than as a visitor.
Find out whether anyone above knows
The single most useful thing to establish is whether the trouble is recognised further up. A team that is struggling with senior awareness and a plan is a different proposition from a team whose difficulties are invisible or actively denied. The first is hard work with an end date. The second tends to produce a slow rotation of people who arrive, exhaust themselves and leave.
You can ask about this without appearing to complain. Asking what the team is expected to deliver this year, and what has been agreed will not happen, is a normal question. If nothing has been agreed to drop, and the workload plainly exceeds the people available, you have learned something important about how realistic the surrounding management is.
The upside is real, and so is the exit
There is a genuine argument for these roles. Responsibility arrives years earlier than it otherwise would, you learn systems end to end because nobody is available to shield you, and visible improvement is easy to demonstrate when the starting point is low. People who spend two years in a struggling team frequently come out with a range of experience their peers do not have.
But the trade should be made knowingly and with a limit. Decide roughly how long you are prepared to give it and what would have to change for you to stay longer, then look at that honestly at the point you set. If the workload is affecting your sleep, your health or your relationships, that is not a career question and should not be handled as one; talk to a doctor or another qualified professional rather than waiting to see whether the next quarter is calmer.
Common questions
Should I have spotted this at interview?
Sometimes, but the signals are subtle and easy to miss. Repeated vagueness about why the role is open, interviewers who look tired, and an inability to describe what the team achieved last year are all worth noticing. None of them is conclusive, and plenty of good teams have a bad month during a hiring process.
Is it bad for my record to leave quickly?
A short stint draws a question rather than an automatic rejection, particularly when you can describe the situation calmly and without blaming individuals. What reads badly is a pattern of short stints, or an explanation that makes everyone in the previous organisation sound unreasonable.
Can one new person improve a struggling team?
Rarely on their own, and expecting to is the fastest route to burning out. What one person can reliably do is stop making the situation worse — finish what they start, keep records, and be honest about capacity — which sounds modest and is more than the average.
Deputy editor, After the First Job
Julien covers first months, managing up, money at work and the questions readers actually send in and would rather show the working than assert the conclusion.





