Why remote hires fail in the second month

The first month of a remote hire is designed. Someone made a checklist, cleared a calendar, and told the team a new person was starting. The second month has none of that, and it is where most engagements quietly go wrong.

This is not exactly a remote problem. Remote only makes it harder to see. Nobody walks past the desk and notices that the person has been stuck since Tuesday.

What the first month hides

Month one runs on three things, and all three expire at about the same time.

Attention. The manager has blocked time, the team is curious, and questions get answered within the hour. Nobody has to decide whether an interruption is worth it, because everything is an interruption in week one.

A checklist. Access, tools, introductions, a first small task. The work is defined by someone else, so ambiguity has not arrived yet.

Forgiveness. Everything is read generously. A slow week is called onboarding, and a misread instruction is called a time zone gap.

Around day thirty, all three run out. The calendar goes back to normal, the checklist is finished, and the generous reading becomes an ordinary one.

What actually breaks

The questions stop

A senior person who has been in the role a month feels they should not be asking basic questions any more. So they stop. They make a reasonable guess instead, and the guess is usually fine, and occasionally it is not.

The first wrong guess is invisible to you. The second one builds on the first. By the time it surfaces it looks like a judgment problem, when it started as a question nobody had a good moment to ask.

The work turns ambiguous

Month one work is defined. Month two work is the real job: a queue with no owner, a report nobody trusts, a process that three people describe differently.

Senior people are hired precisely to handle that. But handling it means knowing which version of the mess you want fixed, and that knowledge is yours, not theirs.

The manager takes their calendar back

This is the honest one. The weekly slot gets moved, then moved again, then becomes “message me if you need anything”. From ten time zones away, that sentence reads as: do not message me.

Silence tells you nothing

Here is the part worth keeping. A senior professional who is doing well and one who is badly stuck look identical from your side. Both are quiet.

Blocked people go quiet because raising the block feels like admitting they could not solve it. Busy people go quiet because they are busy. You cannot tell the two apart by message volume, so stop reading it that way.

What you can read is specificity. Someone doing well describes what they did in detail, names the tradeoff they made, and asks a narrow question. Someone stuck describes activity in general terms and asks nothing.

Watch for the second pattern between week three and week six. That is the window where a fixable misunderstanding turns into a settled one.

What a check-in is actually for

A check-in is not a performance review, a status meeting, or a progress report. It is a scheduled excuse to raise the thing that is not worth an unscheduled message.

That is the whole mechanism. Most of what goes wrong in month two is individually too small to interrupt anyone about. A recurring slot removes the decision about whether it is worth interrupting.

Which is why the slot has to be protected. A check-in that moves twice teaches the person that small problems are unwelcome, and that they were right not to raise them.

Why day 7, 30, 60 and 90

We check in at day 7, 30, 60 and 90, then monthly after that. The spacing is not arbitrary.

Day 7 catches access, context and the first misunderstanding, while all three are still quick to fix. Day 30 catches the handover from checklist work to real work. Day 60 is the important one, because it is the first check after the attention ran out.

Day 90 is a different conversation. By then you both know whether this works. The question changes from how it is going to what the next quarter is for.

Ask both sides, separately

We talk to the manager and to the professional in separate conversations, and we ask them the same things. The gap between the two answers is the useful output.

A manager who says things are fine and a professional who says they are waiting on three decisions is not a disagreement. It is a manager who has not noticed, which is a quick fix if you catch it in week five.

The questions that produce that gap are plain ones:

• What did you actually spend your week on?
• What is waiting on someone else right now?
• What did you decide alone that you would rather have asked about?
• What would make next week better than this one?

Nothing about how things feel. Feelings produce agreement and no information.

What to do with what you hear

Fix it in the week, not the quarter. Almost everything a month-two check-in produces is small. An access request nobody granted, a meeting the person should not attend, a report they have been building that nobody reads.

Small things only stay small for a while. A missing tool is a five-minute fix in week five and an argument about output in week twelve.

And say what you decided. If the answer is no, say no. A senior person can work with a clear no, and cannot work with a question that was heard and then never mentioned again.

The one-question version

If you want a single question to ask yourself at the end of month two, ask this. Do I know what this person spent last week on, in specifics, without asking them to write it up?

If the answer is no, month two is doing what month two does. That is fixable this week, and it gets harder to fix every week after.