Measure sync health before you commission another status board
A polished lag chart on untagged conflict events only accelerates the wrong debate.
Teams under pressure often skip attribution fields and jump to a new sync status board. Weeks later, product and platform argue over different totals for the same release because every conflict still shares one opaque counter.
Prefer path and device tags over widget names. Keep environment out of the timer alias and in a property. Write allowed values the same day a new sync path ships—or the path becomes a free-form dump.
In a Sync Health Baseline we spend early days on the inventory, not on chart cosmetics. Boards get sharper only after the measurement map stops arguing with itself.