The unofficial process is the process

Most organizations run two versions of their important processes. One lives in the procedure document, the system configuration, and the flowchart from the last implementation. The other lives in a spreadsheet on someone's desktop, a checklist taped to a monitor, and a direct message that says "before you submit that, check with me." When the two disagree, the second one is usually the one getting the work done.

It is tempting to treat that second version as drift - people not following the process. Most of the time it is the opposite. The workaround exists because the official process left a gap, and someone closed it the only way they could. That is not disobedience. It is often the most honest documentation you have.

What the unofficial process looks like

• The side spreadsheet. A tracker kept next to the system of record because the system cannot show what people actually need to see, like what is waiting on whom.
• The private checklist. Steps someone learned the hard way and wrote down for themselves - often the very steps that prevent the expensive mistakes.
• The chat approval. A quick "OK to send?" in a direct message that never appears in the workflow, but that everyone knows is required.
• The re-keying step. Copying data from one place to another because two systems do not talk, usually with a small fix-up applied along the way.
• The unwritten checkpoint. Certain cases always go past one particular person first, because that person knows which ones tend to go wrong.

None of these show up on the process map. All of them are carrying load.

Why workarounds are signal, not noise

Each workaround answers a question the official process did not. Read them that way and they tell you a great deal:

• A side tracker tells you which status or handoff the system fails to make visible.
• A personal checklist tells you where the real risk sits, and which knowledge has never been captured.
• An off-system approval tells you where judgement is genuinely needed, and who is trusted to give it.
• A re-keying step tells you where data breaks between systems, and what cleanup is quietly happening in the middle.

Shutting these down without understanding them is how a "process improvement" makes things worse. You remove the patch, the original gap reopens, and the people who were quietly holding things together lose the tools they relied on.

How to find them

Unofficial processes rarely surface in a workshop, because people describe the process they are supposed to follow. They surface when you look at the work itself.

Follow a real case end to end

Pick a recent item and trace every place it went: every file opened, message sent, and tab switched along the way. The gaps between systems are where workarounds live.

Ask what people keep for themselves

"What do you keep open all day?" and "What would you hand a new hire on a sticky note?" reveal more than "walk me through the process."

Look for copies

Exports, duplicate trackers, and attachments saved to personal folders are signs the official record is not serving the people who use it.

Make it safe to show you

If people think a workaround will get them in trouble, they will hide it. Say up front that you are looking for the clever fixes, not grading compliance. The goal is to learn from the patch, not to punish whoever built it.

Design from how the work actually gets done

Once you can see the unofficial process, the design question changes. It is no longer "how do we get people to follow the process?" It becomes "what is the process, really, and how do we make it durable?"

• Keep what the workaround does, not how it does it. If the side spreadsheet exists to show who is waiting on what, the durable version needs that view - not necessarily a spreadsheet.
• Promote the hidden steps. If an off-system approval is genuinely needed, make it an explicit, recorded step with a clear owner.
• Retire the patch only after the gap is closed. Run the new version alongside the old one until people stop reaching for the workaround on their own.
• Watch for the next one. New workarounds will appear. Treat them as an early warning that something in the work has changed.

This is also where AI can earn its place - once the real process is understood. Reading, matching, and reconciling are often exactly the jobs people built side spreadsheets to handle. Automate the documented process instead of the real one, and the workaround simply moves somewhere else.

How Kultiv approaches it

Our process intelligence work starts with the work, not the diagram. We look at how cases actually move, ask about the trackers and checklists people depend on, and treat every workaround as a requirement to understand before anything changes. Then we design the durable version, with the hidden steps made explicit and traceable. Where it makes sense, we run it as a managed operation so it keeps pace as the work changes.

If you want to know how a process really runs, start with the spreadsheet nobody officially owns. It is usually the most accurate map you have.