Process Archaeology
The diagnostic discipline practiced inside the Truth Audit. Layered, low-judgment excavation of the operational layers a business has accumulated, to find the real process underneath the documented one.
The discipline
Process Archaeology is the diagnostic method Vantelira uses inside the Truth Audit. Its job is to surface what the operation is actually doing — not what the org chart says it does, not what the SOP describes, not what leadership believes is happening. The real thing, layer by layer.
The metaphor is precise. Growing businesses don't write their operations — they accumulate them. Each layer was a sensible response to a real problem at the time: a workaround when a tool failed, a hand-off built around the one person who knew how to do it, a process change that never made it into the documentation. Years later, the operation is the sum of those layers, and nobody on the team can describe the whole thing in one breath.
Why "archaeology"
Three reasons:
- The work is layered. You don't find the real process in one place. You find it in fragments — a config someone set up in 2022, a Slack channel where exceptions get reported, a spreadsheet that the COO refreshes manually every Monday morning.
- The work is non-judgmental. Every layer was a rational response to a real constraint. The job is to understand each one, not to label it as wrong.
- The work is careful. You don't disturb the operation while you map it. Archaeologists don't bulldoze the site to find the foundation. Neither do we.
How it works in practice
Process Archaeology runs through three modes, often in parallel:
- Observation. Watching the operation run, not asking how it runs. Most of the gap between documented and real is invisible to the people doing the work — it's invisible because it's normal to them.
- Structured interviews. "Walk me through the last time you did this." Not "what's the process?" The first question gets you the truth. The second gets you the SOP.
- System trace. Following a single real transaction end-to-end through every system, every spreadsheet, every chat thread. What does the data actually look like by the time it gets to the destination? Where did it get reshaped along the way?
What it produces
The output is the spine of the Truth Audit deliverable: a written map of the real process, every workaround named, every undocumented handoff drawn. From that map, the three named money leaks fall out — they are almost always sitting in the layers that nobody had previously connected.
"We've never seen a clean operation we were called in to fix. That's the whole point." — Ysi Gonzalez, founder of Vantelira
The posture
Process Archaeology is non-judgmental by design. The chaos isn't the problem. The chaos is the data. The team that built those layers is also the team that kept the operation running through every stage of growth — and the work is built around that respect. The output names what's broken, but it does not blame the people who built it. That posture is what makes the Truth Audit safe to run.
Process Archaeology questions.
See what's really happening.
Process Archaeology runs inside the Truth Audit. Fourteen days, fixed price, refundable if we don't surface three money leaks.
Start Here