Set the adoption baseline before you commission another board
A polished adoption chart on untagged rollouts only accelerates the wrong debate.
Teams under pressure often skip shared cohort fields and jump to a new adoption board. Weeks later, programme and engineering argue over different “active” totals for the same cloud software because every surface still invents its own vocabulary.
Prefer shared rollout and tenure tags over UI widget names. Keep environment out of the event alias and in a property. Write allowed values the same day a new cloud surface ships—or the metric becomes a free-form dump.
In an Adoption Baseline Audit we spend early days on the inventory, not on chart cosmetics. Boards get sharper only after the baseline stops arguing with itself.