The hidden payroll: what 'finding out' costs a mid-market company every week

Consider an employee trying to restore a process after its usual operator has left. The time spent rediscovering the method is a cost to investigate.

We call it the hidden payroll: the collective time people spend rediscovering knowledge the company failed to capture where they can find it.

It does not show up as a line item because it is distributed across regular salaries. But it is real, it is recurring, and it compounds.

Imagine an invoice incident where three finance colleagues each spend four hours investigating a changed supplier format. That is twelve person-hours, not four.

Two months later, the same supplier changes the format again. The person who found the workaround is on vacation. Nobody remembers what was done last time. Three different people in three different departments each try to figure it out. One of them calls the supplier. The supplier sends a PDF that explains the change. It was always there.

The cost of that episode is not the invoice delay. The cost is the twelve hours of senior finance time spent discovering what a five-minute phone call could have answered. And the cost is that next time, it will happen again.

The hidden payroll has a shape you can recognize. It is not dramatic. It does not announce itself with system outages or compliance failures. It shows up as the small delays, the duplicated effort, the questions that should not need asking, the solutions that get rediscovered every quarter by different people who do not know they are repeating work that was already done.

There are four places it lives.

The first is institutional memory that walks out the door. Your best operator knows which clients need special handling, which systems have undocumented quirks, which vendor relationships require a specific approach. They know this because they have been here five years and they paid attention. When they leave, that knowledge leaves with them. The company does not lose a person. It loses a library.

The second is workarounds that become the real process. The system was supposed to work one way. It does not. Someone found a path around the problem. That path is not documented. It is not in any training. It lives in someone's head and in the informal conversations that happen when a new person asks how to do something. The workaround is the process. The documented process is fiction.

The third is repeated discovery. The same question gets answered by different people in different ways because there is no single place where the answer lives. The company pays for the answer multiple times. Each payment looks like normal work. The total is not normal.

The fourth is the decision delay. Someone needs to make a call. They do not have the context. They ask around. People forward emails. Someone finds a document from 2023. It is mostly right. They decide with incomplete information. The decision is slower than it needs to be, and it is worse than it could have been.

A bounded calculation you can check

Assume 25 people each spend 20 minutes per working day on the same category of repeated information search. At five days and €50 per hour of loaded employment cost: 25 × (20 ÷ 60) × 5 = 41.67 person-hours/week; 41.67 × €50 = €2,083.33/week of allocated cost. These are explicit example inputs, not a measured company result.

If a tested change releases 30% of that category, the scenario yields 12.5 hours/week, valued at €625/week. Over an assumed 46 working weeks, that is 575 hours or €28,750 of gross capacity. It is not automatically cash saved.

Measure the applicable population, necessary search time and actual released share. Exclude overlapping categories, then deduct implementation and running costs when assessing a net return. Do not apply a knowledge-worker average to every employee.

The reflexive response is a knowledge management platform. Buy a tool. Migrate the documents. Train the teams. Tag everything. Build a taxonomy. Create governance. Appoint an owner.

A platform addresses storage and access, but the repeated question may come from missing ownership, outdated information or an undocumented decision. Identify the cause before selecting a tool.

The real problem is flow. Information moves through conversations, decisions, exceptions, and workarounds. A platform cannot capture it until the company understands how knowledge travels through daily operations.

A platform without a map of how knowledge flows is a library with no cataloging system and no librarian. It becomes a graveyard of outdated documents that nobody trusts, which makes the hidden payroll worse because people now have to search two places instead of one.

The sequence that actually works starts with a question most companies do not ask: what are our people spending time discovering that we should already know?

Ask what the company already knows and keeps paying to rediscover before discussing tools or platforms.

In the War Map diagnostic, this is one of the first things we map. Not the technology. The knowledge flow. Where does information enter the company. Where does it get processed. Where does it get stuck. Where does it leave. Which decisions require context that lives in someone's head. Which processes depend on undocumented workarounds. Which questions get asked repeatedly because there is no single answer.

The output maps where the hidden payroll is heaviest and what each area needs: better documentation, a workflow change, a controlled agent, or a decision leadership has avoided.

Solve IT routes each qualified case before prescribing an engagement. Diffuse problems may need a War Map; already-defined workflows may go directly to a bounded Feasibility Sprint. Scope, timing, price, and risk controls are agreed for the actual case.

Doing nothing carries a weekly cost. Salaries produce less because people spend their time finding out instead of doing.

There is a version of your company where the person who figured out the invoice workaround wrote down what they did. Where the next person with the same problem found the answer in two minutes. Where the decision that took three days of email threads took three hours because the context was already assembled. Where someone leaving meant a handoff, not a knowledge gap.

That version is not a technology problem. It is an understanding problem. And understanding comes before building, not after.

The hidden payroll does not go away because you buy a platform. It goes away because you decide that what your company knows is an asset worth mapping, and that mapping starts with asking what your people are paying to discover on their own.

Compare this capacity model with buying AI from an operational baseline before turning hours into a budget decision.