Use case 03

Make tribal knowledge a company asset

Owners rarely ask for automation first. They ask to see how their own company runs.

Aperture is an AI-native operations tool. We map how the work actually runs first, then deploy agents inside the files the work already lives in. That first step captures operational know-how from the work itself and turns undocumented steps, decisions, handoffs, and exceptions into a living workflow map the company can retain and reuse.

At one consumer goods company, a single analyst tracks inventory across every warehouse, every day, down to when each item needs replenishment. The company's entire inventory picture lives in one file that analyst maintains.

It is excellent work. It is also a single point of failure.

Every company has its own version of that file. Capturing tribal knowledge before it walks out is an owner-level problem: until it is captured, the company does not own how its own work runs.

What operational knowledge does an org chart miss?

The org chart shows who reports to whom. It cannot show how an order becomes cash, how a complaint becomes a refund, or why month-end close takes nine days.

That knowledge exists, but it is fragmented, tribal, and often stale.

It is fragmented because each team sees only its part of the flow. It is tribal because it lives in people's heads and habits. And it is stale because the documents that do exist began drifting the day they were written.

The result is a strange asymmetry: an owner can see the company's cash position to the won, yet cannot see how the work that produces that cash actually runs.

What happens when tribal knowledge leaves the company?

Knowledge held this way walks out the door regularly. When the analyst with the inventory file resigns, the company loses more than one employee. It loses the memory of how a core process works, then spends months rebuilding it.

Every departure like this is an unrecorded write-off. It never appears in the P&L, but the loss is real. Panopto's workplace research found that 42% of institutional knowledge rests solely with individual employees. The quiet costs arrive first: slower onboarding, inconsistent output, and key person risk that surfaces in any diligence process. Inside consumer goods companies, those costs add up to what one executive called operational debt.

Why do most attempts to capture tribal knowledge fail?

Most capture projects follow the same advice: interview the experts, write the SOPs, store them in a knowledge base. It fails for two reasons.

First, interviews record the work as people believe it runs, not as it actually runs. The gap between what people believe they do and what they actually do is exactly where the important knowledge hides: the exceptions, the workarounds, the judgment calls.

Second, static documents decay. The process keeps moving after the project ends, nobody maintains the binder, and within a few quarters the SOPs describe a company that no longer exists, the same way plans drift from reality.

Why should visibility come before automation?

When owners come to us, automation is rarely their first request. They ask for visibility: show me how this company actually operates.

That order is right. Automating a process you cannot see is how companies end up with tools no one adopts. Visibility gives every later decision a foundation in evidence, including the decision about which automations are worth building. That sequencing question is the subject of the transformation stack.

How do you capture tribal knowledge and keep it?

The method that works records the work itself instead of asking people about it.

1. Record how the work actually runs, from the real systems and screens, not from memory.
2. Turn the recording into a workflow map the company owns: who does what, in which systems, with which handoffs and exceptions. This is what Aperture builds, and it becomes the ground truth of how the company runs.
3. Keep it living. The map updates as the work changes, so it never goes stale the way documents do.

At that point, the knowledge stops being tribal. It survives departures and helps new hires get up to speed. Its value compounds because every future decision, system implementation, and AI rollout can inherit the map instead of starting again with interviews.

The company's operating knowledge becomes what it should have been all along: an asset the company owns, not a set of habits it rents from the people who happen to hold them.

If part of your company's memory currently lives in one person's spreadsheet, we can show you what it looks like as a company asset. Talk to the founders.

← All posts