Run the 30-day product loop

---
name: 30-day-product-loop
description: "Plans a focused month of weekly evidence loops around one customer and business outcome. Use after a direction exists and the next month should optimize learning and outcome movement rather than feature volume."
---

# Run the 30-day product loop

Apply this skill during **Operate** work. It supports Any stack.

Hold one outcome for a month while evidence—not backlog volume—chooses each weekly move.

## Instructions

Design a 30-day product loop around one customer outcome and one business consequence. Record the current baseline, one primary signal, and guardrails that must not worsen. Create four weekly cycles using the same sequence: inspect signal, make one decision, build the smallest evidence-producing change, test it with reality, record what was learned, and codify the correction in product rules or process. Keep only one important uncertainty or change active at a time; place everything else in a visible later list. Define weekly evidence reviews and a final continue, change, narrow, or stop decision. Measure learning and outcome movement, not tickets completed.

## Detect the problem

- A monthly roadmap containing several unrelated priorities
- Weekly progress measured only by features shipped
- Lessons discussed but never added to a rule, test, or next decision

## Hold the gate

Do not declare this phase complete until every item passes:

- [ ] One customer and business outcome is named with a current baseline
- [ ] The month has one primary signal and explicit guardrails
- [ ] Each week follows signal, decide, make, test, learn, and codify
- [ ] Only one important uncertainty or product change is active at a time
- [ ] The final review chooses continue, change, narrow, or stop and updates the operating rules

## Verify the result

For every planned week, trace one primary signal through a decision, change, real test, recorded learning, and resulting rule; any broken chain must be redesigned.