Map the delivery path before you commission another cycle-time board
A polished board on untagged handoffs only accelerates the wrong debate.
Teams under pressure often skip shared change ids and jump to a new cycle-time board. Weeks later, engineering and product argue over different lead-time totals for the same path because every stage still invents its own vocabulary.
Prefer shared change and stage tags over tool widget names. Keep environment out of the event alias and in a property. Write allowed values the same day a new pipeline ships—or the path becomes a free-form dump.
In a Throughput Baseline Audit we spend early days on the inventory, not on chart cosmetics. Boards get sharper only after the delivery map stops arguing with itself.