Aglet

Prioritize a Missing Versus Zero Fix

Flattening missing values into zero can change rates, trends, and operational choices while leaving the visible layout intact. Prioritize the work by the decision at risk, the number of measures sharing the display rule, and the evidence behind each state. Keep a label clarification separate from an arithmetic change.

Decide where the work belongs

  1. Show the decision consequence

    Use a fixture where a blank and an explicit zero lead to different trend or threshold readings. Name the report question and affected audience. Record observed rows and values instead of estimating impact across unmeasured reports or assuming every blank is an error.

  2. Compare correction choices

    Evaluate preserving blanks, displaying an explicit no-data label, and imputing zero only under a documented rule. For each option, list chart behavior, table and export effects, historical comparability, and owner approval. Keep an unresolved-definition path when the source state is ambiguous.

  3. Set a bounded queue action

    Choose a measure definition, display change, or source clarification as the next action. Attach the state fixture, affected surfaces, evidence threshold, and revisit trigger. Leave unrelated missing-field or chart-scale questions as separate work so the queue stays legible.

What to carry forward

Prioritization is complete when one value-state action has a named decision, owner, evidence threshold, and revisit trigger. Escalate a shared display change only when blank, zero, and unavailable semantics are documented; otherwise queue definition work before changing readers' interpretation.

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