Most process maps are pictures. The business case that justifies changing the process lives somewhere else, in a spreadsheet built during the same engagement, and the two drift apart immediately. Somebody adds three steps to the map in week four, nobody updates the model, and by the time the recommendation is presented the numbers describe a process that no longer matches the diagram printed next to them.
Sapeum puts the numbers on the map. Each process defines its own fields, so a claims process and a hiring process can carry different metadata. Numeric fields declare units, bounds and a color, and render as a small bar on the step card. Two ship as defaults, effort and systems touched. Calculation fields compute from other fields through a sandboxed expression evaluator, and they are hierarchy-aware, which is the part that matters. A parent step totals its children, so the cost of a sub-process falls out of the map instead of being maintained by hand beside it.
One hour against three and a half. The bar makes the comparison before you have read either number.
Once the numbers are on the map, the styling can read them. A display rule names a field, a value to match, and what to change, with color, shape and outline set independently so that two rules compose rather than compete. The value can be an exact match, a numeric comparison, a contains test, or simply not empty at all. That last one earns its keep. A rule that colors every step with something written in its Problems field turns the map into a picture of where the process hurts, and nobody has to remember to apply it. Rules are stored at a scope you pick, so a convention set once for the whole team lands on every process in it.
One field, one condition, one color. Stored on the team, so it applies everywhere.
And here is that rule doing its work. Nobody colored these in by hand.
The pattern worth noticing: conditional formatting is not decoration, it is the cheapest analysis in the product. A map that answers "where is the bottleneck" by being looked at is a different conversation from a ranked table. The same fields export to a spreadsheet, one row per step with the hierarchy in columns, for the point in the engagement where finance wants a model rather than a diagram, and because the model is generated from the map the two cannot drift.
Sapeum lets your process map carry the numbers that justify changing it. Try Sapeum.
