Name the span, not the screen
Teams often ask for a new chart before they agree on what a span means. Soft Sys Net engagements reverse that order: name the hop, name the failure mode, then decide which surface deserves a place in the weekly pack.
A useful naming rule: if two engineers argue about whether an attribute belongs on a span, it probably belongs in a glossary first — not on six different widgets.
Carry the glossary into the next release checklist. Screens change; shared names are what keep software system observability honest across deploys.