Where a Quarter of Your Workweek Goes Before You Make a Single Decision

I once timed it. Between Monday morning and Thursday afternoon, before I made a single decision that actually mattered, I'd spent the equivalent of a full working day just finding things. The number. The doc. The person who knew why we changed the target in March. None of it was hard. None of it was the work. It was the searching that happens before the work is even possible.

That's the part nobody puts on a calendar. We blame meetings — and some meetings deserve it — but the meeting isn't where the time goes. The time goes into everything that has to happen before the meeting can produce anything: assembling the inputs, reconciling the versions, tracking down the one person who remembers the context. The research backs up the instinct. Employees spend roughly a quarter of the workweek searching for information, according to McKinsey — about 1.8 hours a day, every day. For senior operators who sit at the intersection of every function, it runs higher.

Here are the six places that quarter actually disappears.

The Direct Answer

Executives and knowledge teams spend roughly a quarter of the workweek — more than a full day — just searching for the numbers, documents, and people needed before a decision can be made. The most expensive instance is the context-gathering before recurring reviews, when one person stitches data from a dozen tools into something the leadership team can act on. The fix is structural: connect the systems where work happens so the information assembles itself.

1. Hunting the number that lives in four places and agrees in none

The Q2 pipeline number is in Salesforce. It's also in the BI dashboard, where it's $40K higher because the refresh ran at a different hour. It's in last week's deck, where it's already stale. And it's in the spreadsheet your RevOps lead keeps locally because they don't trust any of the other three.

So before you can say anything about pipeline, you spend forty minutes deciding which version is true. Not analyzing it. Just locating the real one. I used to keep a private mental ledger of which source to trust for which metric — pipeline from the spreadsheet, headcount from the HRIS export, NPS from the deck two weeks ago because the dashboard one looked wrong. That ledger lived in my head, which meant I was the only person who could assemble a clean view. That's not expertise. That's a single point of failure wearing a trench coat.

2. Pinging three people to find the one who actually knows

You need to know why the EMEA launch slipped. You ask the PM. The PM points you to the eng lead. The eng lead says it was a legal review and you should talk to the GC. The GC was out that week and says ask the PM. By the time you reconstruct the actual reason, twenty minutes are gone and you've interrupted four people's afternoons to recover a fact that someone, somewhere, already wrote down.

This is the human routing table, and in most companies the Chief of Staff is the routing table. You know who knows things. That knowledge feels valuable — until you realize it mostly means people route their searches through you, which makes you the bottleneck for context that should never have required a person in the first place.

3. Figuring out which version of the doc is actually final

The file is called Q3_Planning_v3_FINAL_final_USE_THIS. There is, somewhere, a v4. You are almost sure the comment you need was in a different copy entirely.

The cost here isn't the reading. It's the verification — the low, constant hum of doubt about whether the thing in front of you is current. You make a decision based on a doc, and a quiet part of your brain keeps asking whether you're looking at the version that already got overruled. When the source of truth is a filename convention and a prayer, every document review starts with a search for the document that counts. Connect the work to a single live source and that whole verification tax disappears — there's only one version, and it's the one that's true right now.

4. Re-reading old threads to reconstruct a decision you already made

We decided this. I know we decided this. The problem is that we decided it in a Slack thread, during a meeting whose notes nobody finished, and the actual ruling is buried in message forty-one of a sixty-message exchange that also contains two jokes and a lunch order.

Decisions don't persist on their own. They scatter across the channels where they happened, and three weeks later someone reopens the question — not out of malice, but because there's no durable record of what we landed on and why. So you go spelunking through old threads to prove a decision was made, which is a genuinely absurd use of a senior operator's afternoon. This is exactly the gap Rhythms' Reviews feature was built to close: decisions get captured where they're made and carried into the next review automatically, so "didn't we already decide this?" stops being a research project.

5. Rebuilding the same update for the third audience this week

The same status — the EMEA launch, the pipeline gap, the hiring freeze — gets rewritten for the board pre-read on Monday, the staff meeting on Wednesday, and the cross-functional Slack update on Thursday. Same facts. Three formats. Each one assembled by hand from the same scattered sources, because the inputs never sit in one place long enough to be reused.

I used to joke that my real job title was Status Update Aggregator. The work wasn't deciding what to say. It was finding the raw material, again, to say it in a slightly different shape. The retrieval doesn't get cheaper because you've done it before. It resets every time the audience changes.

6. Assembling the pre-read before every recurring review — the most expensive search of all

Every other place on this list is a one-off. This one is a standing weekly appointment with all of them at once.

Before the executive operating review, before the customer health review, before the pipeline review, someone gathers everything: the numbers from place one, the context from place two, the right version from place three, the decisions from place four, repackaged like place five — and turns it into a pre-read the leadership team can actually use. In most companies that someone is a single person spending a meaningful chunk of their week as a human integration layer. By our estimate at Rhythms, up to 70% of management time gets consumed by this kind of "work about work," and review prep is where it's most concentrated and most visible.

It's also the most fixable. When the pre-read assembles itself from live data across every connected tool — which is what Rhythms' Reviews and Playbooks do, pulling from Salesforce, Jira, Slack, HubSpot, and the rest — the search doesn't get faster. It stops happening. The document that used to cost four hours of retrieval exists before anyone asks for it, grounded in the current numbers, with last week's decisions already carried forward. The person who used to build it walks into the room ready to use their judgment instead of having spent it all on assembly.

What changes when the pre-read already exists

The thing I didn't expect was how much of my sense of being good at my job was tangled up in being the person who could find anything. When the searching stopped, there was a strange beat of "then what am I for?" The answer turned out to be the actual work — the judgment, the thinking the company needed from me and rarely got, because I was spending a quarter of every week as the company's search engine. And there's a quieter cost to that: in the survey John Doerr cites in Measure What Matters, only 7% of employees say they fully understand their company's strategy and what's expected of them. It's hard to fault them when a quarter of the week goes to finding things — the understanding is exactly what gets crowded out.

So if you want a number for your next leadership conversation, use the quarter of the week. Then ask the harder question: which of these six places is your team's most expensive, and is anyone actually paid to fix it — or is it just absorbed by the one person who's good at finding things?

Try it free at rhythms.ai.

Frequently Asked Questions

How much time do employees waste looking for information at work?

Roughly a quarter of the workweek. McKinsey research puts it at about 1.8 hours a day spent searching for and gathering information — more than one full working day every week before any real work gets done. For senior operators who sit across every function, the share is usually higher, because they're the ones other people search through.

What is the coordination tax?

The coordination tax is the cumulative time spent aligning people, schedules, and information across teams — chasing numbers, reconciling versions, reconstructing decisions — rather than doing the work itself. It rarely shows up on any budget line, which is exactly why it grows unchecked. Most of it is information retrieval that precedes a decision, not the decision itself.

Why does adding more tools make this worse instead of better?

Each new tool adds another place information lives and another surface to check. Without a connective layer that pulls them together, more tools mean more searching and more "which version is current?" — so teams end up with more data and slower decisions.

How do you actually reduce time lost to information retrieval?

Stop relying on people to gather context by hand before every meeting. Connect the systems where work already happens so updates, metrics, and decisions assemble automatically, and the pre-read exists before anyone asks for it. The fix is structural — organization doesn't solve a problem caused by data living in twelve places.