Map the hops before you add another latency chart
A polished board on unnamed spans only accelerates the wrong debate.
Teams under pressure often skip hop naming and jump to a new dashboard. Weeks later, two groups argue over different numbers for the same user action because three spans still describe one path.
Prefer intent verbs over UI widgets. Keep vendor and region out of the span name and in properties. Write allowed keys the same day the span is born—or the stream becomes a free-form dump.
In Path Telemetry Mapping we spend early days on the decision map, not on chart cosmetics. Diagnostics get sharper only after the catalogue stops arguing with itself.