Measurement Card

A Measurement Card is a one-page form you fill in before reporting a number, pinning down exactly what it counts, on whom, over what period, and what it cannot prove.

It is Thursday, and someone says the new onboarding lifted activation 18 percent. You ask what counts as activation. One person says the user finished setup. Another says they came back on day seven. The dashboard uses a rule a contractor wrote in March that nobody has opened since. Now three people are arguing over a number none of them can define the same way twice, and a budget decision is sitting on top of it.

A Measurement Card is a single page with 10 slots that you fill in before anyone reports the number. The cue: a number is about to steer a decision, and the thing being counted is only a stand-in for what you actually care about. First, split the construct from the observable. Write that you care about a user getting real value, and that your visible proxy is a return login. Second, fix the measure, the population, and the time window. Third, write the scoring rule, what you do about missing data, the safeguards against gaming, and the limits you will not claim past. What changes is that the number means the same thing in July as it did in March, and disputes move to the card instead of the meeting. Skip it when you are browsing data and no decision hangs on the answer.