Collaboration
Building a shared language for handoffs
If three teams use three names for the same wait, your efficiency map is already fractured.
Handoffs are where process efficiency mapping either becomes a shared instrument or a set of parallel dialects. Analytics cannot reconcile dialects after the fact; the vocabulary has to be negotiated while the map is drawn.
Name the artefact, not the mood
“Ready for finance” means little. “Invoice packet complete in shared folder X” can be checked. Prefer nouns you can point at: file, ticket state, signed form, pick list.
Agree the clock
One team starts the clock when they send; another when they open. Write the rule on the map in plain English. Business analytics then inherits a definition instead of inventing one in a dashboard filter.
Keep a glossary sticky
During studio critiques we keep a living glossary beside the diagram. When someone says “triage,” we ask whether they mean sort, or assess, or assign. The first time feels pedantic; the tenth time prevents a useless WIP chart.
Rehearse the handoff sentence
A useful test: can a sponsor say “the wait sits between assess and credit” and have both teams nod? If not, keep workshopping names before you scale the metrics. Shared language is not soft work — it is the load-bearing beam under process efficiency mapping.