Why New Joiners Go Quiet In Week Three

Week one, the new person asks a lot of questions. Week two, fewer. Week three, almost none, and their work slows down at the same time. Nobody raises it, because quiet looks like settling in.

New joiners go quiet in week three because the permission to be new has expired in their head while their actual understanding is still full of holes. The welcome meetings are over, the obvious questions are used up, and the remaining questions feel too basic to ask after two weeks. The fix is scheduling: put specific things in the calendar for that week so they do not have to ask.

What is happening in their head

By day fifteen a new person has usually done three things. They have met everyone. They have finished whatever starter task they were given, ideally something real they shipped in the first week. And they have built a private list of things they still do not understand.

That list is the problem. Each item on it felt fine to ask about on day two. On day fifteen, asking feels like admitting you were not paying attention. So the list stays private and grows.

Meanwhile their manager sees somebody who has stopped asking questions and reads it as progress. Both sides are wrong about the other, and neither is going to say so.

The three questions they are sitting on

The unasked questions are surprisingly consistent across teams and roles.

• Who actually decides things. They know the org chart. They do not know who to convince. This one is almost never written down anywhere, except at a kickoff that names who can say no.
• What good looks like here. Is this level of detail expected? Is it normal to ship on a Friday? Is this a place where you ask forgiveness or permission?
• Whether the thing they are confused about is them or the system. Half the time the process really is confusing and everyone works around it. A new person has no way to tell the difference, so they assume it is them.

None of these come up in a status meeting. They have to be pulled out.

Put four things in the week three calendar

Do not rely on an open door. Book these before the person starts.

• A no agenda thirty minutes with the manager, framed as "bring the things you have been meaning to ask". Say the framing out loud. It gives back permission to be new.
• One session with somebody outside their immediate team. A second angle on how the place works, from a person they do not report to.
• A piece of work slightly above their comfort level, with a named person to help. Growth restarts the questions.
• A review of something they built in week one or two. Real feedback on real output tells them what good looks like better than any description.

Four calendar entries. Maybe three hours in total.

Make the basic questions cheap to ask

The deeper fix is making it normal to ask an obvious question at any point, not just in the first fortnight.

A few things that help:

• Keep a written page of the answers people actually ask for, including the embarrassing ones. Who approves expenses. What the release day is. What the acronyms mean.
• Have someone senior ask a basic question in public occasionally. It resets what is acceptable faster than any policy.
• Keep decisions and the reasons for them on the same board as the work, so a new person can read backwards instead of asking. When project records and people records sit together, as they do in SicherOne, a new joiner can see who owns what and who was away when something slipped, without having to ask a colleague to explain the history. That only holds while the board is true, so it is worth checking it against the signs a board has become fiction.

The signal to watch

You cannot measure this well, and you should be suspicious of anyone who says otherwise. But there is one reliable signal: the rate of questions.

If a new person's questions drop off sharply between week two and week three, that is not usually mastery. Mastery takes longer than that. It is more often the point where they decided to stop asking.

Ask them directly. "What have you been wondering about that you have not asked?" is a slightly awkward question that works almost every time, because it tells them you already know the list exists.