Journal
What dashboards hide about churn
A dashboard is a flattening machine. That is not an insult; it is the job. Churn, however, is not flat. It is a change in chosen behaviour, a change in definition, a change in who is in the denominator, or a push token that died while the tile stayed green. If you only watch the tile, you will manage the paint.
Definition drift is the quietest hide. Someone “cleans” a filter. QA devices drop out, or — more often — slide back in. A new platform identifier doubles a slice of users for a fortnight. The churn tile dips and a channel is blamed. In Cartography we ask operators to version the sentence that defines the curve, not just the SQL. If the sentence moved, the tile is a different painting.
Vanity packets hide the rest. A tooltip impression, a video autoplay, a settings heartbeat: all can be counted as life. Life is not the same as intention. The Dundee case on our letters page is a session_resume that treated a push-wake as a returning player. Their dashboard was confident. Their community was not.
What we want instead is a surface: more than one grain, a named valley, and a limitation written in the same pack as the number. That will look less like a product tour and more like an adult appendix. Boards survive appendixes. They do not survive a year of acting on a pretty hide.
If your current view cannot show a silent week, do not add another colour. Change the grain. The studio’s bias is paper first, vendor second — not because paper is romantic, but because paper cannot auto-smooth a lie.