The first week
What to Do When There Is Nothing to Do
Empty time in a first fortnight is normal, it is nobody's failure, and there are four things worth doing with it that do not require anybody's permission.
What the people on this page had to find out, and where from
Which of the two deploy guides is current
worked out6Decided by checking which matched the scripts
That nobody reads the team channel after 15:00
worked out7Learned from two unanswered afternoons
two things you had to know · nobody told you any of them · the median arrived in week 7 · all two you went and got
Two things nobody told anybody, learned by noticing. Both were visible in week one and neither was legible until much later.
When a new employee is learning an unfamiliar workflow, managers can read the implementation guide to understand where time is going before assuming that a slow start is an effort problem.
For additional context beyond this collection, see the material published by Payscale.
Four stretches of a first fortnight with no work in them
Three days waiting for repository access
11 hanswer: 3 minYou waited because you did not want to be the new person who complains. Granted in four minutes once asked a second time
An afternoon after finishing the induction modules
4 hanswer: 2 minYou waited because you assumed somebody would send something. Nobody was going to; nobody knew you had finished
Two days while your manager was away
9 hanswer: 5 minYou waited because it seemed unreasonable to bother anybody else. Two colleagues would have been glad to be asked
A morning before your first real task was agreed
3 hanswer: 6 minYou waited because you were waiting to be told. The task was waiting for you to choose it
four occasions · 27 hours spent stuck · 16 minutes of answers · the longest single wait was 11 hours
Twenty-seven hours of a first fortnight with nothing in them, and sixteen minutes of conversation would have filled all four. In every case somebody was waiting to be asked. One person's own first fortnight.
Large parts of a first fortnight have nothing in them. This is normal, it is not a sign that you were a mistake, and almost everybody joining remotely experiences it as though it were.
It happens because the work that would occupy you requires access you do not have, context you have not got, or a decision somebody has not made yet. None of that is anybody's failure, and all of it resolves.
Why it feels worse than it is
Three reasons, and naming them helps.
Nobody can see that you have nothing to do. In an office your empty desk would be visible; here your silence looks identical to concentration.
You have no basis for comparison. You do not know that the person who joined in June also spent most of their first week reading, because nobody says so.
And the obvious remedy — asking for work — feels like admitting you cannot find any, which is precisely backwards and is the single most common misreading of a first fortnight.
The four things worth doing
In rough order of value.
Read the team's recent history. A fortnight of the team's channels, the last twenty pull requests or documents, the last few decisions. The closest available substitute for overhearing, and nobody will ever suggest it to you.
Write down everything you do not understand. Covered in its own note. Empty time is exactly when this is possible.
Talk to people. Twenty minutes each with four or five colleagues, asked for directly. This is the single best use of a week with no access to anything, and the section on who is who is mostly about it.
Find something small and real. A typo in the documentation. A broken link. A setup instruction that does not work any more because you just followed it and it did not. These are genuine contributions, they require no permission, and they are how most people's first useful week actually happens.
The fourth one is the one that matters
You are, this week, the only person in the organisation who has recently followed the setup instructions. Everybody else did it years ago, from memory, with a colleague next to them.
So the instructions are wrong, and you are the only person who knows. Fixing them is small, real, useful, and visible — and it is the only task in your first fortnight for which being new is a qualification rather than a handicap.
Asking for work without it sounding like that
The form matters more than most people expect.
I have got through the induction material and I have read back through the team's last couple of weeks. I have got time — would it be more useful for me to pick up something small, or to spend it talking to people?
That is not "I have nothing to do". It reports what you have already done, offers two sensible options, and makes it easy for a busy manager to answer in one word.
What not to do with it
Do not spend it producing something unasked and large. A new person's two-day document on how everything should be reorganised is received as a problem, not a contribution, and the section on first work covers why.
Do not spend it in silence. Three days of nothing with nobody told is how week two becomes an awkward conversation.
And do not spend it studying. You cannot learn this job from documents, and the attempt converts empty time into anxious time without producing anything.
Saying it after a week, not after three
The window in which empty time is easy to raise is about a week.
In week one it is expected and nobody is surprised. In week two it is a reasonable question. By week four it has become something you have apparently been sitting on, and raising it then means explaining three weeks rather than one.
That ratchet is why the panel above runs to twenty-seven hours: not because anybody refused, but because each day of silence made the conversation slightly harder to start.
The practical rule is a date rather than a feeling. If you have had nothing substantial by the end of the first full week, say so on the Monday. The message in the note above takes forty seconds, and the version of it sent in week one is a different and much easier message than the same words in week four.
The three days that are fine
Not every gap needs raising. Two or three days of nothing in the first week is normal and self-correcting.
The thing that distinguishes a normal gap from a problem is whether anybody has said what happens next. Three days with no work and a manager who has said "next week we will get you onto the import" is a plan. Three days with no work and no statement at all is a silence, and silences do not end by themselves.
So the question to ask yourself is not how long it has been. It is whether anybody has told you what comes after.