Why New Hires Don't Ask Questions, and What Fixes It

It’s 4:10 pm on Tuesday and Anna has a customer call in eighteen hours. She has one question she cannot answer: why the Brightwater account has a 60-day renewal notice when every other account has just 30 days. Anna is 23, a customer success associate in her second week at her first full-time job. She types the question into ChatGPT first. It returns a polished paragraph about renewal terms in general and nothing about Brightwater. She opens Slack, writes to her manager, deletes the message, writes it again, and deletes it again.

Most new hires hold back questions because they think too many questions make them seem incompetent. Many also think that each question spends goodwill with a colleague they barely know. So, they ask the safest person instead of the right one, or skip the question altogether, and just guess the answer.

The advice new hires usually get is to ask more questions, and managers are told that a quiet new hire is a warning sign. Both treat silence as a failing of the new hire. Anna's afternoon, however, shows it as arithmetic.

A Ledger Nobody Gave Her

Anna keeps a count of her questions, though nobody asked her to. Her manager has answered six of her questions since Monday and her onboarding buddy four. The account notes name Imran, the senior associate who handled Brightwater last year, as the person who would know. She has not messaged him, because she has met him once and the question feels like one she should be able to answer herself. Each name carries a balance, that’s constantly running low. The post on why new employees don't know who to ask covers hires who cannot find the right person. Anna can. What stops her is the price of asking.

At 4:20 pm, she opens a direct message to Imran, types the question, and reads it as he might: a senior colleague, a near stranger, a question the account notes may already answer. She deletes it. Her manager said to hop on a call anytime, but a call costs more than a message, because it demands someone's full attention at once. By 4:40 pm, the safest option left is her buddy, who joined four months ago and has never worked with Brightwater. He guesses it was a negotiated exception and suggests she say so on the call. So, she goes into the call with a half-right answer.

Why Asking Costs More Than It Looks

Anna's instinct is correct. UC Irvine research finds that on an average it takes 23 minutes to regain full focus after an interruption, so every question she sends costs a colleague more than the minute it takes to answer.

That makes "just ask" poor advice. It tells a new hire to spend something she believes is scarce, with no information on how much she has left. People with a budget spend it on the safest option and save the hard questions, and the hard questions are usually about a specific account, system, or decision that only a few people can answer. The wider ramp-up cost is covered in our post on new hire time to productivity.

It Is Not a Generation Thing

Anna's habits are easy to file under a generational trait. She checks an AI tool before she asks a person, because a chatbot cannot judge her and doesn’t cost anybody a minute, and she (like most) prefers a message to a call. Close to half of Gen Z workers say they would rather ask ChatGPT than their boss, a figure covered in our post on why Gen Z prefers AI over managers for workplace questions.

Greg is 46 and joined the same week as Anna as a senior account manager with fifteen years of experience. He keeps the same tally in a notes app: the same names, the same reluctance to spend a favor on a colleague he has not met. He goes to his manager before a peer, because the manager is the safe option. The behavior seems to depend on how new a person is to the place, not how old they are, which is the a similar reason why nobody uses documentation. So, the AI tool is a reasonable first stop for new hires of any age. Here, it fails Anna because it cannot know what happened on the Brightwater account, and neither can anyone who was not there.

What Changes When the Answer Already Exists

Let’s run the afternoon again with a tiny difference. Three months earlier, a colleague asked Imran in a Slack thread why Brightwater has a 60-day notice, and he explained that the term was negotiated after the customer missed a renewal window in its first year. She saved the thread in Pravodha because it explained an account she also touched.

Pravodha keeps that thread attributed to Imran, searchable by topic, and marked as useful by the colleagues who found it valuable. At 4:10 pm, Anna searches "Brightwater renewal" instead of opening ChatGPT and finds Imran's explanation with his name on it. She walks into the call knowing why the term exists and when the notice window falls. Imran's profile is linked from the answer, and it shows an expertise badge for renewals as well as Brightwater, earned because colleagues found his answers on those topics useful. That tells Anna he is the right person and that others found his answers worth noting, making the message easier to send. Her one question for the day goes to him: whether the customer has asked to change the term. That question has to go to a person, and she can afford to ask it.

This works because someone saved the thread, and a badge shows recognition. A question nobody has answered in writing still goes to a person, which is the point. Anna spends her questions on what nobody wrote down, not on what someone already explained.

What Managers Can Do in Week Two

A manager cannot make asking feel free, but can lower its price.

• Replace "ask me anything" with a daily window, such as fifteen minutes at 3 p.m., so a question has a time and place to land.
• Give new hires a shared channel for first-month questions, so asking is normal, visible, and findable by the next hire.
• Answer the account histories before day one: for each account with unusual terms, write down why and who explained it.
• Name the colleague who knows each account's history, so a new hire never has to guess who is safe to ask.
• Say out loud that a question costs a colleague a few minutes, and that you have decided the cost is worth paying.

Capturing those answers without asking experts to write anything is covered in our blog post how to capture knowledge from Slack without adding work for experts.

Anna's afternoon had one question and a guess. In an ideal situation, that afternoon would have a quick search and a saved answer from Imran.

Pravodha is built around the capture model. It integrates with Slack, Microsoft Teams, and your email to preserve the institutional knowledge your team generates every day: attributing it to the people who created it, surfacing peer validation, and making it permanently searchable without adding any burden on the experts.