The short version
- New hires do not ask the same question twice. They guess, and you find out in review three days later.
- The rationing is social, not informational: asking twice feels like evidence they were not paying attention.
- Ramp time is therefore set by how cheaply a question can be asked, including the second and third time.
- Make the low-status questions free to ask, and the guessing stops.
Ask a new engineer in month two what slowed them down and they will not say the documentation. They will describe a specific afternoon where they were unsure about something, did not want to ask again, made a reasonable assumption, and had to redo two days of work.
"They don't ask, they guess, and we find out in review."
The question budget nobody tells them about
Every new joiner operates an internal budget. They believe, usually correctly, that asking too many questions signals that they are not picking things up, and that asking the same question twice is worse than asking a new one. So they spend the budget on what feels most important and guess at the rest.
Two specific categories get rationed hardest. Questions they have already asked once, because repeating one feels like an admission. And questions that seem too basic, where asking risks looking as though they lack fundamentals the role assumed.
Both categories are precisely the ones where guessing is most expensive, because a basic misunderstanding propagates through everything built on top of it.
What guessing costs
| Path | Cost to the new hire | Cost to the team |
|---|---|---|
| Asks the question | A small social cost, in their perception | Two minutes, plus the asker's recovery |
| Guesses right | None | None |
| Guesses wrong | Two days of work, and confidence | Review time, rework, a delayed ticket |
The third row dwarfs the first, and the new hire cannot see that, because they only experience the social cost directly. From where they sit, asking has a visible price and guessing has an invisible risk, which is why the behaviour is so consistent across people and companies.
Make asking free
You cannot talk someone out of the question budget. "Ask me anything, no question is too basic" is said by every manager in every first week and it does not change the arithmetic, because the joiner can see that each question costs a busy person's attention.
What does change it is making some questions genuinely free. With StandIn, each person on the team confirms a ninety-second brief at the end of the day, and while they are off, their StandIn answers questions from it in their words, with a source under every answer, and never guesses. The new hire can ask their StandIn instead of interrupting them: the same question three times if they need to, at 22:00 if that is when they are working, with no social cost and no waiting.
The questions that then reach a human are the ones the record could not settle, which are also the ones most worth a colleague's time. And the joiner learns the area faster, because they are not rationing. See StandIn for the first 30 days.
Four things a manager can do in week one
- Ask a basic question yourself, in public. One visible instance of a senior person asking something simple does more than any invitation.
- Give the buddy protected hours. Two hours a day, on their calendar, so the joiner knows there is a slot rather than needing to judge whether now is a bad time.
- Tell them the guessing rule explicitly. "If you are unsure and cannot get an answer, write down the assumption you made in the pull request." That turns an invisible guess into a visible one.
- Review the first ticket on the assumption, not the code. Ask what they were unsure about. It surfaces the rationing immediately.
Common Questions
How do you reduce new-hire ramp time?
Reduce the cost of asking questions, especially repeated and basic ones. Ramp time is mostly determined by how quickly uncertainty gets resolved, and new hires systematically under-ask because they perceive a social price.
Why do new hires not ask questions?
Because they believe repeated or basic questions signal that they are not learning fast enough. It is a rational read of most workplaces, and telling them otherwise rarely changes the behaviour on its own.
How do we find out what they are guessing about?
Ask them to note assumptions in the pull request, and in review ask what they were unsure about before discussing the code. Both make the invisible guesses visible at the cheapest possible moment.
Does a longer onboarding document help?
Rarely. The questions that slow new joiners are specific and contextual, and a longer document has a lower chance of containing any given one while taking longer to search.
Log off like you mean it.
Your StandIn answers the questions that come up while you're out, from what you actually wrote down, so the return pile stays small.