Aglet

Prioritize Which Product Cost to Baseline

Teams can spend weeks measuring a number that never changes a product choice. Prioritize baselines that clarify a consequential problem, reveal a hidden burden, or create a fair comparison for a planned change. Keep measurement effort proportional to decision value.

Decide where the work belongs

  1. Compare consequence and use

    For each candidate cost, describe the user or operational outcome affected and the decision a baseline would unlock. Give weight to blocked work, repeated rework, access burden, and expensive uncertainty rather than to easy-to-count activity.

  2. Assess measurement quality

    Review data availability, sample fit, start and end definitions, missingness, and expected variation. Compare direct observation with self-report or proxy measures. A rough but relevant baseline may outrank a precise proxy that misses the real burden.

  3. Choose a measurement queue

    Select one baseline, owner, method, period, and review date. Defer candidates with a reason and trigger. Record what could make the measure unnecessary, such as a decision already being constrained by another known fact.

What to carry forward

The priority output is a baseline queue with consequence, decision value, measurement quality, effort, owner, and review trigger. Start where a fair starting point can change product choices. Avoid measuring activity that has no interpretable relationship to user outcome.

Technical background: GOV.UK user research guidance.

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