The people who are actually your process

Truth Map showing a straight documented process line above three nodes and a dashed actual process line weaving down through three human roles - Interpreter, Gatekeeper, and Jack the Operator. Labelled as the human judgement layer not captured in documentation.

A client told me recently that their business could never be automated. Their reason: they email their customers for missing information, and what comes back is a photograph, or a scan, or handwriting on a napkin.

There's a person in that office whose job it is to look at the napkin, read it, and turn it into something the internal system can accept. That person doesn't appear anywhere in the process document. If you asked the head of operations to draw the workflow, you would not find them on the diagram. But if that person left tomorrow, the business would notice by lunchtime.

I call this person the Interpreter. They sit at the edge of the process where the world stops filling in forms. They appear wherever messy outside input has to be translated into something an internal system can accept.

They are not the only one.

The Gatekeeper approves things on mood and favour, not the published criteria. Everyone who works with them knows their tells: Fridays are worse, don't go through them if you have a shared history with the person asking, come back after coffee. They usually sit in a project office or an approvals role that looks administrative on the org chart, and they are quietly setting the terms of what gets done in a business unit twice their size.

Jack the Operator knows the undocumented field on the legacy system that has to be filled in before the record will save. Nobody wrote this down. If you ask Jack directly, he'll shrug - it's reflex to him, and he's forgotten that other people don't know it. The moment Jack retires, three teams downstream will start submitting broken records and nobody will understand why.

These are not quirks, this is the actual process.

The process document - the swimlane diagram, the SOP, the map on the wall, describes what is supposed to happen. What actually happens involves the Interpreter reading the napkin, the Gatekeeper waving something through because they like the person asking, and Jack pressing a button he has never spoken about. Between them, they carry the parts of the workflow the document doesn't cover: the ragged inputs, the exceptions, the judgement calls, the invisible corrections upstream that keep the quality metrics clean.

I have been in enough of these workflows now to say something plainly. The gap between the documented process and the real one is not a failure of documentation. It is not something a better template would fix. It is the accumulated work of the people who make the business function where the documented process doesn't quite reach.

The trouble is what happens when a new tool arrives.

A company buys a new system, a project management platform, an AI interview tool, an integrated CRM and the vendor's implementation plan is built off the documented process. That plan looks clean because the process it's based on looks clean. Nobody involved in the sale, the procurement decision, or the rollout knew about the napkin, or Jack's undocumented field, or the fact that the Gatekeeper is what stopped Marketing and Engineering going to war in 2023.

The new system lands, automates the documented process, and eats the corridor.

I ran a workflow map for a client recently whose team had just bought a widely used project platform. The team's lead had spent the previous three years managing a careful contact protocol with a small number of external stakeholders, she didn't email them cold, she didn't cc their manager, she waited until she had a specific reason and used a particular phrasing that had been earned over years. Nobody wrote this down. It sat inside her head as "how we handle them."

The new platform has an automated stakeholder-update feature. It's a good feature. It will send a competent, well-worded update at every project milestone. And it will destroy three years of that lead's carefully-held contact protocol inside a fortnight, and the team will not know why the relationship has cooled, and the platform will still look like it's working.

That is one finding, on one workflow, in one department. It's what a Ground Truth looks like.

Ground Truth is the work I do now. One department buys, one workflow is in scope, and I go and find where the documented process and the actual one have separated. I talk to the people doing the work, not the process owner reading me the document, the people doing it. And I ask them to walk me through the last time they did the thing, not a time it went right. I write up what I find as a set of findings: one page each, one place where documented and actual diverge, what depends on that divergence, who is carrying it, and what happens if the incoming system replaces it as documented.

The output is a Ground Truth Map: the shortlist of findings sitting under the change your client is about to make, and a decision for each - preserve the work in the new design, or accept the loss knowingly.

Most of what I find, once seen, still requires the human. That is not a comforting finding. It is an accurate one.

If you are inside a rollout right now and the shape of this piece feels uncomfortably familiar, that's the moment to talk. The Interpreter, the Gatekeeper, and Jack are the corridor between the boxes on your diagram. The corridor is where the work is actually done.

Ground Truth: https://www.gailweiner.com/ground-truth

This article was developed in collaboration with Claude (Opus 4.7) and GPT (5.6 Sol).

Gail Weiner is the founder of Simpatico Studios and a Trust Architect working with UK and EU organisations on the governance, ethics and epistemic reality of working with AI. Twenty-five years across technology, corporate leadership and entrepreneurship - from systems analyst to a seat at the executive table, before founding Simpatico Recruitment in 2014 and Simpatico Studios in its current form. She runs three business strands: Trust Architecture consulting (including the Ground Truth diagnostic and Floor Map scale-up product), an engineering capacity brokerage placing European development teams with UK and US companies, and Simpatico Publishing, an AI-native publishing operation. She has worked with Claude as a primary strategic partner since July 2023. Born in Johannesburg, twenty years in Cape Town, now based in Bristol. British citizen as of August 2026.

Find her work at gailweiner.com and on LinkedIn and Substack.

Follow her on X