The question tax is what a new hire's questions cost the people who answer them. Every question costs twice: once for the person asking, once for the person who stops to answer. When a new hire joins, the answering falls to managers and the teammates who have been around longest, one interruption at a time.

What is the question tax?

A new hire is on payroll from day one. For a few months, most of that buys questions.

Who owns the Acme account? Why do we discount like that? Is staging supposed to be down? None of these are bad questions. Each one is a small invoice, sent to whoever happens to know.

The person asking pays in waiting. The person answering pays in whatever they were doing. A five-minute answer is rarely five minutes. It's five minutes, plus the time it takes to remember what the spreadsheet was for.

That's the tax. It isn't a sign of a bad team or a slow hire. It applies to any team where the context lives in Slack threads and in people's heads, and it's collected in the same place every time: the calendar of the person who knows the most.

How much time do teammates spend on repeat answers?

APQC measured both sides of the transaction. Knowledge workers spend, on average, 1.7 hours a week seeking out the right people to answer questions and provide expertise. They spend another 1.7 hours a week providing duplicate information or repeating the same answers or updates (APQC, 2022).

Those are averages across knowledge workers in an ordinary week. They are not a measurement of a team with a new hire on it. Nobody has published that number. Anyone who has sat next to a new hire has a private estimate.

Three things make the new-hire version worse than the average:

  1. The questions go up the org chart. "Why did we decide this?" can only be answered by someone who was there. That is usually the manager or the most senior person on the team.
  2. The questions repeat. Each new hire asks the same things, in a slightly different order, of the same few people.
  3. The answers evaporate. They're given out loud or in a direct message. The next hire can't find them, so the next hire asks.

To put a price on it for your own team, the onboarding cost calculator has a line for teammate hours. Every default is labeled as an assumption, so replace them with yours.

Why don't managers just write it down?

They were supposed to. So was everyone.

It isn't laziness. Writing the context for one role takes hours. The team it describes changes monthly. The hire starts Monday. And the manager is doing all of this in the same quarter they're short one person, which is why they're hiring.

The People team can't do it for them. They own onboarding, and they built the checklist and the 30-60-90 template. What they can't write is why the billing service works the way it does, or which customer was promised what. The role-specific part was always going to come from managers.

So the document doesn't get written. The answers get given out loud, one at a time, and the manager becomes the documentation.

Why a bigger FAQ doesn't fix it

The usual fix is a longer FAQ, a tidier wiki, or a chatbot on top of both. All three assume the new hire knows what to ask.

They don't. A new hire in week one doesn't know that pricing changed last spring, so they don't ask why. They don't know one account has a custom contract, so they find out on a call, from the customer.

An FAQ holds the questions someone thought to write down. The expensive ones are the questions nobody knew to ask, and those arrive later, as mistakes, and then as questions anyway.

Keep the FAQ. Keep the wiki. They're useful once someone knows what exists. What a new hire needs before that is the story, in order, without having to ask for it. The longer versions of this argument: Firstweek vs. an AI chatbot and Firstweek vs. your company wiki.

What to do before day one

Five things a new hire should have in writing before they start. A manager can draft this list by hand today. It covers most of what the questions are about.

  1. Owners. Who owns each account, system, process and decision the new hire will touch. Names, not team names.
  2. Why-decisions. The three or four decisions that explain how the team works now, with the reasoning from the time.
  3. Open work. What's in flight, what's late, and what they're inheriting mid-stream.
  4. Customers. Which ones matter to this role, what was promised, and what went wrong before.
  5. Who to ask about what. A short map from topic to person, so each question goes to the right desk once.

Almost all of it is already written down: in Slack, in Jira, in Confluence, in the CRM. It has never been assembled. Assembling it by hand takes the hours managers don't have, which is where this post started.

Firstweek does the assembling. It reads the tools you already use through read-only connections and writes one cited onboarding artifact for each new hire. Every claim links to the thread, page or record it came from, and the hiring manager approves it before day one.

It doesn't end questions. The ones about judgment still need a person, and should. What it changes is who has to carry the rest: the things already written down get handed over in writing. Here is a sample artifact, written for a fictional company's new hire.

FAQ

What is the question tax?

It's the cost of a new hire's questions to the people who answer them. Every question costs twice: once for the person asking, once for the person who stops to answer.

How can managers spend less time answering repeat questions from new hires?

Put the predictable answers in writing before day one: who owns what, why key decisions were made, what work is open, which customers matter and who to ask about what. Most repeat questions fall into those five groups.

Won't a chatbot or an FAQ answer these questions?

Only the ones a new hire thinks to ask. In week one they don't know what exists, so the costly questions never get typed.

Does Firstweek eliminate new-hire questions?

No. It writes down the context that already exists in your tools, cited and approved by the hiring manager. Questions that need judgment still go to a person.

Sources: APQC, KM Makes Knowledge Workers More Productive and Less Stressed Out (2022), listed with its link on the onboarding statistics page.

Run it on your next hire. 30 days. Then we talk. Start a pilot or see a sample artifact. How it works for scaling teams.