Naming workflow steps so reports stay honest
If step three is called “Details” in three different product areas, your completion atlas becomes fiction. Names must map to a single user intent and a single success event.
Write definitions in plain language: “User submits shipping address that passes validation.” Avoid UI copy that changes every sprint.
Freeze definitions for a reporting quarter. When you rename or split a step, call it out in the next pack so trend lines stay trustworthy.
Share the glossary with support and analytics. Completion reporting fails when each team invents its own map of the same journey.