Aglet

Prioritize a Report Ratio Denominator Fix

A denominator change can move a rate while every event row remains unchanged. Prioritize it by the decision that relies on the ratio, the breadth of shared use, and the confidence of the eligibility rule. Keep formula correction, label clarification, and data-definition work as distinct queue outcomes.

Decide where the work belongs

  1. Describe the decision risk

    Show the choice or threshold that changes under the competing denominators. Use a fixed numerator and two eligible populations to demonstrate the difference. Record actual rows and displayed wording instead of a guessed rate or a claim about general user impact.

  2. Compare intervention paths

    Evaluate revising the denominator, adding a named ratio variant, and exposing the eligible population beside the measure. For each path, list historical effects, filters, exports, fixtures, and owner approval. Include a defer path when eligibility depends on a policy still being decided.

  3. Choose a bounded queue action

    Select one next artifact: a metric definition, a formula change, a label revision, or a comparison fixture. State the evidence threshold and revisit trigger. Keep zero-denominator handling and rounding issues visible as separate questions when they are not the first divergence.

What to carry forward

Prioritization is complete when one denominator action has a named decision, owner, evidence threshold, and revisit trigger. Escalate a shared ratio change only after eligible population is agreed; otherwise queue definition work before changing a rate readers already compare.

Technical background: Metabase documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow