Note · 9 Jan 2026

Sparse events in B2B scorecards

Some products produce twelve meaningful actions a month. Daily averages on that dictionary are a kind of fiction: most days are zero, a few days are work, and the mean looks like a pulse that never existed.

In the Sparse-Event Scoring programme we move the unit of time to match the job. For a reporting tool that might be a billing cycle. For a compliance app it might be a filing window. The score then asks whether the expected jobs happened inside the window, not whether Tuesday looked lively.

Thin dictionaries tempt teams to inflate them. Hover events, tooltip views, and “session start” get promoted so the chart has ink. That ink is a tax on honesty. We would rather keep twelve events and a wide window than two hundred events that nobody can name in a meeting.

Identity still matters. If the same person works on web and mobile, and you score both as separate lives, sparsity gets worse. Join what you can join. Do not invent a user for every device just to feed a daily chart.

The uncomfortable outcome: some weeks the score will not update. Executives who grew up on consumer dashboards find that silence rude. Teach them the window. If they still need a ticker, they are asking for a different product than the one you sell.