How Many Hours a Week Does Your Team Lose Looking for Answers? (And What That Costs You)

The 9-Hour Leak Nobody Puts on the P&L

Pick any week and track where your team’s time actually goes. Not the time they spend doing the work — the time they spend finding how to do the work.

The number is bigger than most owners expect.

McKinsey’s Social Economy report — one of the most-cited studies on knowledge worker productivity — found that employees spend approximately 1.8 hours per day, or roughly 9 hours per week, searching for information. That’s close to 20% of the working week. The finding has been replicated in different forms across multiple analyst firms, and the range consistently lands between 15% and 25% of weekly work hours consumed by searching, asking questions, or waiting for answers.

Nine hours. Per person. Per week.

Now run the math on your own team.

What 9 Wasted Hours Per Employee Actually Costs

Take a conservative fully-loaded labor cost of $25 per hour. That includes wages, employer payroll taxes, benefits, and overhead. For many roles — office managers, operations coordinators, field supervisors — the real number is higher. But $25 is defensible and easy to work with.

One employee:

• 9 hours/week × $25/hr = $225/week in unproductive labor
• $225 × 50 working weeks = $11,250/year per person

A 10-person team:

• $11,250 × 10 = $112,500/year in time spent searching for answers

That number is not going to show up on your P&L as a line item. It hides inside salaries. It looks like normal payroll. But it’s real, and it’s recoverable.

If your average labor cost is $35/hr fully loaded — more realistic for a professional services firm or a technical team — the 10-person number climbs past $157,000 per year.

Where the Time Goes

The 9-hour estimate isn’t one big block of wasted time. It dissolves across the day in ways that are easy to dismiss individually:

• “Let me ask Sarah how we handle that” — 12 minutes gone
• Digging through email threads for the right invoice procedure — 8 minutes
• Calling the previous employee’s contact to find out what they used to do — never recovering that one
• Googling your own internal process because nobody wrote it down — 15 minutes
• Waiting for a manager to reply to a Slack message before continuing a task — 20 minutes just on that task

Each of those feels like a small friction. But small frictions compound. A 10-person team where everyone is losing an average of 90 minutes per day to this kind of information drag is functionally a 10-person team doing 8-person output.

The people who feel it most are often your best employees — the ones who care about getting things right and refuse to guess. They’re the ones tracking down the answer. Your lower performers? They often just guess and move on.

The Specific Problem: Nobody Documented the Answer

Every time someone on your team asks “how do we handle X,” two things are usually true:

1. Someone on the team already knows the answer.
2. That answer has never been written down in a place the asker can find it.

This isn’t a people problem. It’s a system problem. The knowledge exists — it’s just locked inside one person’s head, or buried in an email from 2022, or sitting in a PDF nobody named correctly.

The math problem you’re actually solving: how do you move institutional knowledge from a person’s head into a searchable, findable system so that the same question never requires a human interruption to answer twice?

That’s what process documentation does. Not the aspirational kind that lives in a binder on a shelf. The kind your team actually opens, trusts, and uses.

The Documentation Flip: What Happens When Answers Are Searchable

When a team has documented processes that are current, searchable, and consistently used, the information-search cost drops dramatically. The question shifts from “who do I ask?” to “where do I look?” — and the lookup takes two minutes instead of fifteen.

A reasonable operational target: less than 1 hour per week per person spent searching for internal process information.

Let’s re-run the math at that level:

One employee at <1 hr/week information search:

• 1 hour/week × $25/hr = $25/week
• $25 × 50 weeks = $1,250/year per person

A 10-person team:

• $1,250 × 10 = $12,500/year

The difference between a team with documented, searchable processes and a team without: $100,000 per year for every 10 employees, at conservative labor rates.

That’s not a documentation project. That’s a payroll line.

Why Most SMBs Don’t Fix This (And Why They Should)

The objection is always the same: “We don’t have time to document everything.”

That’s true. You don’t need to document everything. You need to document the processes that generate the most questions.

Spend 30 minutes mapping out the questions your team asks most frequently. In most 5–20 person businesses, the same 15–25 processes account for 80% of the recurring questions. Document those. Stop there. That’s the whole lever.

The second objection: “We wrote it down once and nobody used it.”

That’s a system problem, not a documentation problem. If your SOPs live in a Word doc in a folder nobody remembers, they’re not SOPs — they’re artifacts. The document has to be where people actually go when they have a question, not where you filed it after writing it.

Searchability is the functional requirement. If someone can type a keyword and find the right process in under 30 seconds, the documentation works. If they can’t, it doesn’t matter how thorough it is.

A Real-World Scenario: The Dental Practice

A 12-person dental practice. One doctor, a practice manager, three hygienists, two assistants, a front-desk coordinator, two billing staff, and a part-time marketing person.

Every new front-desk hire gets a training period. Most of it is the same questions: how do we handle insurance verification, what’s the protocol when a patient disputes a bill, who do I call for the HIPAA compliance question, what’s the cancellation policy and how do we document it.

The practice manager spent roughly 3–4 hours per week fielding those questions — not because the new hire was slow, but because nothing was written down. After documenting 18 core front-desk and billing processes in a searchable format, that dropped to under 45 minutes per week.

The practice manager’s time didn’t disappear. It got redirected to work that required a practice manager: scheduling, vendor negotiations, patient experience issues. That’s what recovering the time actually looks like in practice.

How to Start Without Building a Documentation Department

You don’t need a dedicated operations role to fix this. You need a starting point.

Step 1: Log every repeated question for one week. Every time someone asks how to do something that has a right answer, write it down. Don’t answer it differently each time — that’s a different problem. Just track what’s being asked.

Step 2: Rank by frequency. At the end of the week, you’ll have a list. The top 5–10 items are your first documentation sprint.

Step 3: Write the answer once, in the place people will look. The format matters less than the location. A numbered checklist is fine. A narrative is fine. What’s not fine is a document no one can find.

Step 4: Tell the team where to look. For the first few weeks, when someone asks you a question that’s now documented, don’t answer it — send them the link. That’s how you train the habit.

Step 5: Review quarterly. Processes change. If the documented process is wrong, trust in the system collapses. A 30-minute quarterly review of your top 10 processes keeps them accurate enough to be useful.

For a deeper look at building SOPs that actually stick, see How to Create SOPs for Your Business. For a comparison of tools that can host your processes in a searchable, role-assigned format, Best SOP Software in 2026 covers the major options across different team sizes and use cases.

The ROI Is Unconditional

Most investments in operations software or process improvement come with caveats: “it depends on adoption,” “results vary,” “assumes consistent usage.”

The math here is unconditional. If your team is currently spending 9 hours per week per person searching for information, and you get that to 2 hours per week per person, you’ve recovered 7 hours per person per week. At $25/hr, that’s $175/person/week, or $8,750/year per employee.

You don’t need a consultant to validate that number. You need to track it.

The only question worth asking: what’s the fully-loaded cost of a documentation system versus the labor cost you’re currently eating?

For most teams, the documentation investment is a rounding error compared to the ongoing cost of not having it. What’s the Process For is built specifically for SMBs that want documented, searchable, assignable processes without the per-user pricing that makes most tools impractical at team scale.

If you want to see whether it fits your situation, start a free trial. No credit card required.

---

The McKinsey “Social Economy” report finding on information search time (1.8 hours/day, ~20% of the working week) is from McKinsey Global Institute, July 2012. The original report is archived. The labor-cost math in this post uses $25/hr as a conservative floor for fully-loaded U.S. employee cost. Your actual numbers will vary based on role, industry, and region — but the direction of the arithmetic doesn’t change.