Building a process map — from the as-is, not the workshop

The most reliable process map isn’t built in a workshop — it’s pulled from the real as-is: from tickets, tools, handovers, system exports, and conversations. A workshop shows how the organization believes it works; a map pulled from the as-is shows how it actually does — including the edge cases and interfaces forgotten in the room, and re-pullable whenever something shifts.

A process map is meant to give an overview: which processes exist, how they connect, where the interfaces are. The classic route there is the workshop — people in a room, cards on the wall, a map as the result. The problem isn’t the workshop itself, but what it depicts: the shared picture in the room, not necessarily the lived workflow.

Why the workshop map diverges

In a workshop, people describe how they believe work is done — or how it should be. Both are useful, but neither is the as-is:

The edge cases are missing, because they’re obvious in daily work and forgotten in the workshop.
The informal shortcuts are missing, because no one puts them on the record officially.
The interfaces where things actually snag look smoother than they are.

The result looks tidy and still goes stale fast — for the same reasons as any process diagram after three months.

How do I build a process map from the real as-is?

The other route doesn’t start in the room, but with the traces real operations leave behind anyway:

Name the sources — tickets, tools, handovers, system exports, conversations. That’s where the real workflow lives.
Run the engine — Forge connects the individual processes into a consistent picture, including the interfaces and edge cases.
Map as an artifact — an overview that depicts the lived state, not the workshop ideal — and that can be re-pulled when something shifts.

This doesn’t make the workshop redundant — it makes it better: instead of drawing the map from zero, the team discusses a picture that’s already accurate. How this approach differs from classic process mining is in Process mining vs. engine.

The difference

A map is a tool for deciding. Decisions based on the target picture miss reality. A map from the as-is isn’t just more accurate — it stays that way, because it can grow back.

The most useful process map isn’t the prettiest, but the truest — and the most current.

To try it: Bring an area whose process landscape you want to understand into the demo call — we’ll pull the first map live from your real sources.