Your Team Loses 10 Hours a Week to Information Problems. They Say They're "Too Busy" to Fix It. The Time Paradox That Keeps Customer Education Permanently on the Backlog.

February 12, 2026

Your Team Loses 10 Hours a Week to Information Problems. They Say They're "Too Busy" to Fix It.

The Time Paradox That Keeps Customer Education Permanently on the Backlog.

I've spent the last 39 posts diagnosing why customer education programs fail. I've documented the $1.8M annual cost of inaction accessibility.link.new-tab. I've built a 90-second business case framework accessibility.link.new-tab. I've mapped a 30-day pilot accessibility.link.new-tab and a Day 31 scaling playbook accessibility.link.new-tab.

And the most common response I get is: "We know we should do this. We just don't have time."

That response is the problem.

Not because they're wrong about being busy. They're right — they're drowning. But the reason they're drowning is the same reason they say they can't start: they don't have a system for answering questions at scale.

The Time Paradox: Too Busy to Stop Being Busy

APQC surveyed 982 full-time knowledge workers in 2021. The headline finding should make every CS leader pause:

Knowledge workers lose 25% of their work week — 10 hours out of 40 — to information problems.

Here's where those 10 hours go:

  • 2.8 hours/week searching for or requesting information that should be findable
  • 2.0 hours/week recreating information that already exists somewhere
  • 1.7 hours/week providing duplicate answers — answering the same question someone else already answered
  • 1.7 hours/week managing internal workplace communication about information

That's 10 hours. Every week. Per person. Lost to the absence of a system that makes knowledge findable.

Now ask a knowledge worker: "Do you have time to create a help article this week?"

The answer is no. Of course the answer is no. They just lost a quarter of their week to the problem that help article would solve.

The paradox: the busier you are, the more you need customer education. And the busier you are, the less likely you are to start.

This isn't laziness. It's a structural trap.

Your Calendar Proves You Have More Time Than You Think

"We don't have time" really means "we don't have uninterrupted time." There's a difference.

Atlassian surveyed 5,000 knowledge workers across 4 continents. The findings:

  • 72% of meetings are ineffective
  • 80% say they'd be more productive with fewer meetings
  • 62% attend meetings without stated goals
  • 80% believe most meetings could run in half the time
  • 51% work overtime several days per week because meetings consumed their productive hours

Microsoft's Work Trend Index found that employees are interrupted every 2 minutes during core work hours — 275 times per day. Gloria Mark's research at UC Irvine (peer-reviewed, replicated) shows it takes 23 minutes and 15 seconds to fully refocus after each significant interruption.

So when your support lead says she doesn't have time to write a tutorial, she's right — but not because the hours don't exist. It's because reactive work has consumed every block of focused time she might have used for proactive work.

The hours exist. They're just being spent answering the same questions one at a time instead of once.

The Math Nobody Does

Let's calculate what "answering the same question" actually costs.

A typical B2B SaaS company with 500 support tickets per month. Industry data says 40-60% are repetitive, known-answer questions (TSIA). Let's use 40% — the conservative end.

200 tickets per month × $25-$35 per ticket (SaaS Capital 2024) = $5,000-$7,000 per month.

That's $60,000-$84,000 per year spent answering questions you could answer once.

Now multiply across the broader team. Those 982 knowledge workers in the APQC study each spend 1.7 hours per week providing duplicate information. At a loaded cost of $36/hour (US average knowledge worker), that's $3,200 per employee per year just on the duplication — not counting the time searching for information that already exists.

For a 10-person team: $69,000 per year in duplicated effort.

The time to write a focused help article that answers one specific question? 1-3 hours (practitioner consensus for subject matter experts writing about what they already know).

One help article. $60,000 in annual ticket deflection potential. 1-3 hours to create.

The ROI of those 1-3 hours is so asymmetric it should be embarrassing that anyone says "we don't have time."

What Actually Happens When You Start

The objection assumes that "starting customer education" means a massive initiative. A 6-month project. A platform purchase. A content team hire.

It doesn't.

Here's what real teams experience when they start small:

  • An eCommerce brand launched a simple FAQ widget and saw a 38% drop in ticket volume within 30 days (eDesk case study)
  • Another company deflected 1,200 repetitive order-status questions in a single month by publishing tracking guides
  • swissQprint reported a 34% reduction in support tickets after launching their documentation portal (Zoomin/Screendesk)
  • 91% of customers say they'd use a knowledge base if it met their needs (Zendesk) — the demand already exists
  • Well-implemented knowledge bases can reduce support tickets by 60-80% over time (Pylon)

The timeline to measurable results? Not months. Days to weeks. You write five articles targeting your top five support tickets. You link them in your auto-replies and onboarding sequences. You measure ticket volume on those topics. Within 30 days, you have data.

This is exactly the approach from the 30-Day Pilot accessibility.link.new-tab. Five articles. 30 days. $5,400/year in conservative savings. No platform, no team, no strategy deck.

The Real Risk: What Happens When You Don't Start

"We don't have time" assumes that the status quo is free. It isn't.

The costs of not starting compound:

1. Support costs grow linearly with customers. Every new customer adds their share of repeat questions. Without self-service resources, your support headcount must grow proportionally. At 500 tickets/month and $25-35 each, adding 20% more customers means $12,000-$16,800/year in additional support cost — forever.

2. Knowledge concentration increases your bus factor. That one person who knows everything? They can't take vacation, can't get sick, can't get promoted. When they leave — and the average employee tenure is 4.1 years — new hires need 8-12 months to reach full productivity. Replacement costs: 50-200% of annual salary. All because the knowledge was in their head instead of in a system.

3. Invisible churn accelerates. 85% of customer churn is due to poor service, not price or product issues (Qualtrics). 67% of churn is preventable if the issue is resolved at first engagement. But only 1 in 26 unhappy customers will tell you — the other 25 just leave silently (TARP Research). Without education resources, every confused customer who can't find an answer is a silent churn signal you'll never see.

4. Context switching costs compound. HBR found knowledge workers toggle between apps and websites 1,200 times per day, spending 4 hours per week — 5 full working weeks per year — just reorienting after switches. Every time your SME stops their real work to answer a question that could be in a help article, they lose 23 minutes of refocus time (Gloria Mark, UC Irvine). That's not just the 5 minutes answering. It's the 28 minutes total.

You can't save your way out of a capacity problem by staying busy.

The 3-Hour Investment

Here's what "starting" actually requires:

Hour 1: Export your last 90 days of support tickets. Sort by topic. Identify the top 5 questions by frequency.

Hour 2: Write a thorough answer to question #1. Not a paragraph — a real answer with screenshots, examples, and context. The kind of answer you'd give if you could only answer this question once and it had to serve every future customer.

Hour 3: Publish it. Link it in your support auto-replies. Share it with your CS team. Set a calendar reminder for 30 days to check ticket volume on that topic.

That's it. Three hours. One article. And 30 days from now, you'll have data showing how many tickets it deflected.

If the answer is "none" — the article wasn't helpful enough. Rewrite it.

If the answer is "some" — you've proven the model. Write articles for questions #2 through #5.

If the answer is "a lot" — you've just built the business case for a customer education program using real data from your own company. No projections needed. No vendor demos. No committee approval.

This is the 90-Second Business Case accessibility.link.new-tab built from real results.

Why "We Don't Have Time" Is Actually "We Don't Have a System"

The time objection is a symptom, not a cause.

When you say "we don't have time to create education content," you're really saying:

  • We don't have a system for identifying which content would save the most time
  • We don't have a system for creating content without pulling SMEs away for weeks
  • We don't have a system for measuring whether content actually deflects tickets
  • We don't have a system for keeping content current as the product changes

This is the Content Creation Bottleneck accessibility.link.new-tab from post #333. It takes 49 hours to create 1 hour of traditional e-learning (Chapman Alliance, 250+ organizations). That's the enterprise approach. Of course nobody has time for that.

But a focused help article isn't e-learning. It's 1-3 hours of writing by someone who already knows the answer. The 49:1 ratio is for interactive modules with branching scenarios and video production. The ratio for "write a clear answer to a specific question" is closer to 3:1.

The system problem isn't time. It's that most platforms either:

  • Require technical skills to publish (Markdown, CMS templates, developer handoff)
  • Can't connect content to support metrics (so you can't prove it's working)
  • Live in a separate system from your support tools (so linking is manual)
  • Don't track what customers actually need (so you're guessing which articles to write)

The fix isn't "find more time." It's "find a system where creating and measuring content is fast enough that your busiest person can do it between meetings."

Three Diagnostic Questions

Bring these to your next QBR:

1. How many hours per week does your team spend answering the same questions? If you don't know, export 90 days of tickets and tag by topic. The APQC data says 25% of the work week. For support teams handling repetitive questions, it's likely higher.

2. What's your cost per support ticket, and how many are deflectable? $25-35 per SaaS ticket (SaaS Capital 2024). 40-60% are repetitive knowledge-gap questions (TSIA). Multiply. That's the annual budget you're spending on answers you could give once.

3. When was the last time you wrote a help article that directly answered your #1 support question? If the answer is "never" or "I can't remember," the time paradox is running. You're too busy answering questions to write the answer that stops the questions.

The Waiting Tax

Every week you wait costs the same as the week before. The questions don't stop. The tickets don't decrease. The SME doesn't get less busy.

But unlike most investments where ROI takes months to materialize, support deflection shows results in days. One article. One week. Measurable reduction.

You don't need a strategy. You don't need a platform. You don't need a content team.

You need 3 hours and the willingness to answer your #1 support question in writing instead of on a call.

The time exists. You're spending it on the problem right now. The question is whether you'll spend 3 of those hours building the solution.

---

We're building Omumu specifically to make the "3-hour investment" as friction-free as possible — identify the questions, create the content, measure the deflection, all in one place. If the time paradox resonates, join the waitlist accessibility.link.new-tab and tell us what your team's top 3 repeat questions are.

Sources: APQC 2021 (n=982 knowledge workers), Atlassian 2024 (n=5,000), Microsoft Work Trend Index 2024, Gloria Mark/UC Irvine (CHI 2008, peer-reviewed), HBR 2022 (n=137 employees/20 teams), Sophie Leroy/UW (Organizational Behavior and Human Decision Processes, 2009), TSIA Education Services, SaaS Capital 2024, Zendesk, Qualtrics, TARP Research, eDesk case studies, Zoomin/Screendesk, Pylon 2025, Chapman Alliance (250+ organizations).