Field notes

Drawing waits without shaming teams

When a map paints a desk red, people brace. In Operations Route Studio we teach wait layers as weather, not verdicts — temporary conditions that change with staffing, tools, and demand.

Notebook with timeline sketches on a desk

Name the wait type

Soft waits (waiting for a person) and hard waits (waiting for a system) ask for different fixes. Mixing them into one “delay” bar makes everyone look equally responsible for problems they cannot touch.

Show samples, not eternal averages

A Tuesday morning sample next to a Friday afternoon sample tells a truer story than a quarterly average that erases the crunch everyone remembers.

Invite a co-author

Ask someone who works the route to annotate the draft before leadership sees it. Corrections land softer when the map already carries floor language.

← Back to blog