t4-p3-03authored4–7h
One iteration driven by data
requires: t4-p3-02
Spec
Identify the worst-performing metric, form a hypothesis for why, ship one specific change targeting it - for example changing the prompt time or format if response rate is low - then measure again over a second usage period.
Why this matters
One change, then measure again. This is Track 1's paired-comparison discipline applied to a product decision, and it is the only way to distinguish a fix from a coincidence.
Verify
No result yet. Run `learn verify t4-p3-03` locally, or push to trigger CI.
artifact
unrun
judge
unrun
Rubric
# t4-p3-03 — One iteration driven by data
**Task:** Identify the worst-performing metric, form a hypothesis for why, ship one specific change targeting it - for example changing the prompt time or format if response rate is low - then measure again over a second usage period.
**Strong:** Directly answers every one of the review questions below in the affirmative, with specific evidence from the actual work, not a restatement of the task.
- Was exactly one thing changed?
- Is the second measurement reported honestly, including if it did not help?
**Passing but weak:** The deliverable exists and technically satisfies the spec, but is generic, restates the task instructions instead of engaging with them, or only partially addresses the review questions below.
**Fails:** The deliverable is missing, or engages with none of the review questions below - e.g. it describes what was built without explaining the reasoning the task actually asks for.