← Everyone's take

TAKES · Hugo answers

What should we track?

What should we track?“Fewer events, each with an owner, a schema and a test.”Hugo Demir, The Perfectionist

💡 WHY HUGO IS RIGHT

An event that drives a decision is production code: it can fire twice, never fire, or change meaning after a refactor. If the board deck depends on checkout_started, it deserves the same care as checkout itself: an owner, a schema, a test that fails when it breaks. Fifty trustworthy events are worth more than four hundred nobody can vouch for, and he would rather fix one now than explain a fake trend later.

✅ RIGHT WHEN

The numbers drive staffing, pricing or board decisions.

🚩 TOO FAR WHEN

Every new event waits on a test suite, so the experiment ships with no measurement at all.

See all 12Hugo's profile