The 3-Word Test: How to Spot a Broken Process in 30 Seconds

It starts with a question. "Where's the contract?" "Where's the pricing for that job?" "Where's the client history?" Three words. Every single time, they mean the same thing: a process is broken. Not a person. A process. And the fastest way to find every broken process in your business is to listen for those three words for one day.

The 3-Word Test

Here's the rule: if anyone on your team has to ask "where's the X?" — where's the signed contract, where's the email thread, where's the current pricing sheet — that piece of information should already be exactly where they need it. The fact that they have to stop, search, ask, or wait means the system failed.

Not the person. The system.

We've walked through service businesses where the average employee asks "where's the X?" six to eight times a day. Each time, they lose three to five minutes finding the answer. Sometimes more. That doesn't sound like much until you do the math:

Eight questions a day times five minutes each equals 40 minutes per person. Five team members adds up to over three hours a day. That's 66 hours a month. Roughly a week and a half of someone's time — spent asking where something is.

That's not work. That's waste.

Why 'Where's the X?' Is Always a Systems Problem

When you hear the 3-word question, the instinct is to blame the person. "Sarah should know where that file is." "Carlos should have that pricing memorized." But that's wrong. Sarah and Carlos aren't the problem. The system that makes them go find information is the problem.

Good people working around bad processes is the most expensive hidden cost in a service business. Your best employees spend a chunk of every day being your integration layer — the manual bridge between the CRM, the scheduling tool, the email inbox, and the spreadsheet. They're not doing the work you hired them for. They're doing the work your software stack should be doing.

Every "where's the X?" is a tax on your team's time. And because it's small and scattered across the day, nobody adds it up. That's why it keeps happening.

We covered this idea before in a post about the hidden 15% of capacity your team already owns — the capacity you're leaving on the table because nobody's measured the cumulative cost of these small interruptions. The 3-word test is how you find them.

The 5 Most Common 'Where's' in Service Businesses

After running process audits with dozens of service businesses, these five come up more than any other.

"Where's the client history?"

Your client calls. Your account manager opens the CRM — that's one screen. Then they open the email thread from last week — that's another. Then they check the notes app where someone jotted down the client's preference. By the time they piece together the full picture, the client has been on hold for two minutes. It happens a dozen times a day.

The fix: One source of truth where every client interaction lives — calls, emails, notes, contracts. Not a CRM that holds contacts while emails live somewhere else.

"Where's the current pricing?"

Your estimator needs to quote a job. They find a PDF from three months ago. Is it still accurate? They're not sure. They walk over to ask the owner. The owner is on the phone. They wait. The quote goes out late again.

The fix: Live pricing that updates in one place and propagates everywhere. No spreadsheets. No PDFs. No "let me check with the owner."

"Where's the job status?"

A client emails asking for an update. Your ops manager opens the scheduling app. The last note is from Tuesday. Three days ago. They don't know the current status. They forward the email to the field team and wait for a reply.

The fix: Status updates that post automatically when a job moves through its stages. The answer is written down before the client asks.

"Where's the signed contract?"

Sales closes a deal. The signed PDF goes into someone's email folder. Two weeks later, ops needs it to schedule the job. Nobody can find it. Someone spends 20 minutes digging through inboxes.

The fix: Contracts land in a single, searchable repository the moment they're signed. No downloads. No file cabinets. No "who has the PDF?"

"Where's the follow-up task?"

A lead called yesterday. The sales rep promised a quote by end of day. It didn't happen. Nobody followed up. A week later, the lead went with someone else. The best lead you'll ever get is the one that called you first. Letting it go cold is the most expensive "where's" on this list.

The fix: Tasks that create themselves when a trigger happens. A quote promised becomes a quote due. A lead that doesn't reply triggers a follow-up reminder. No sticky notes required.

What to Do When You Spot One

The 3-word test is a diagnostic, not a solution. Once you find a "where's the X?" moment, the temptation is to add another tool to fix it. Don't. That's exactly the tool sprawl problem we've seen cost businesses more than they save — we wrote about it in detail here, breaking down the math of eight disconnected tools. Adding another one just creates another place where things get lost.

Instead, do three things:

Trace the data. Where does the information originate? Where does it need to end up? What bridges does your team build between those two points every day?

Pick one system. A single vertical system — website, content, SEO, leads, CRM, and analytics in one place — eliminates the bridges entirely. The information lives where the work happens.

Write it down before you automate it. The fastest way to fail at automation is to automate a broken process. Fix the process first. Then let the system run it.

Start With One Question

You don't need a consultant for this. You don't need a budget. You just need to listen for three words for one day.

Tomorrow, pay attention to every time someone on your team asks "where's the X?" Write it down. Count it. Then ask yourself: what would it take so nobody ever has to ask that question again?

That's where the work starts. That's the conversation we have with every client on the first call. We map where your business is losing hours — not based on a generic checklist, but on the actual friction your team experiences every day. Then we architect a system that eliminates it.

If you're reading this and thinking about your own "where's" moments, that's the signal. Book a call at recursive-solutions.com. It's a working conversation, not a sales pitch. We'll run the 3-word test on your actual operations and show you what's costing you time.

FAQ

What is the 3-word test for broken processes?

The 3-word test is a simple diagnostic tool for service business owners. If anyone on your team asks "where's the X?" — where's the contract, pricing, or client history — that information should already be where they need it. The question reveals a process failure, not a people problem.

How much time do service businesses lose to information searching?

Based on our work with dozens of service businesses, employees ask "where's the X?" six to eight times per day. At three to five minutes per search, that's 30 to 40 minutes per person per day. For a team of five, that adds up to over 66 hours of wasted time every month.

What's the most common broken process in service businesses?

Client history access is the most common — your team needs to see past interactions, contracts, and notes in one place, but the data lives in three different tools. The second most common is pricing stored in outdated PDFs and spreadsheets that nobody can verify.

Should I buy a new tool when I find a broken process?

No. Adding another tool to fix a broken process usually makes it worse — you create another place where information can get lost. Instead, trace where the data originates and where it needs to go, then pick one system that handles both.

How do I start fixing broken processes in my business?

Start with the 3-word test. Listen for "where's the X?" for one day, write down every instance, and count the cost. Then document the process before trying to automate it. Automating a broken process just makes the broken process run faster.

What's the first step in the Recursive Solutions approach?

The first step is Map — a working conversation where we trace your actual operations and find the specific places where your business is losing hours. No generic pitch, no assumptions. Just a clear picture of the friction your team experiences.