Iteration and Postlaunch Learning
Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.
Workflow
- Restate the intended outcomes, guardrails, launch scope, population, and observation window.
- Collect product, operational, support, qualitative, accessibility, security, and business evidence with source dates.
- Compare observed behavior to baseline, target, expectation, and known confounders.
- Separate defects, usability friction, adoption barriers, operational issues, unexpected benefits, and unresolved signals.
- Assess whether changes are warranted now, require more evidence, or should be deferred.
- Prioritize iterations by user impact, risk, confidence, effort, reversibility, and learning value.
- Define the next experiment or change with success, failure, rollback, and review conditions.
Boundaries
- Do not call a release successful from deployment, traffic, or anecdotes alone.
- Do not conceal negative evidence or repeatedly move targets after observing results.
- Do not implement, deploy, or message users unless separately authorized.
Output
Return Intended outcomes, Observed evidence, Variance, Learning, Priorities, Next experiments, and Claim limits.
1---2name: iteration-postlaunch-learning3description: Plan and synthesize postlaunch learning from observed behavior, incidents, feedback, experiments, and outcome measures. Use after a release when the team must decide what to retain, change, investigate, or stop.4license: MIT5---67# Iteration and Postlaunch Learning89Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.1011## Workflow12131. Restate the intended outcomes, guardrails, launch scope, population, and observation window.142. Collect product, operational, support, qualitative, accessibility, security, and business evidence with source dates.153. Compare observed behavior to baseline, target, expectation, and known confounders.164. Separate defects, usability friction, adoption barriers, operational issues, unexpected benefits, and unresolved signals.175. Assess whether changes are warranted now, require more evidence, or should be deferred.186. Prioritize iterations by user impact, risk, confidence, effort, reversibility, and learning value.197. Define the next experiment or change with success, failure, rollback, and review conditions.2021## Boundaries2223- Do not call a release successful from deployment, traffic, or anecdotes alone.24- Do not conceal negative evidence or repeatedly move targets after observing results.25- Do not implement, deploy, or message users unless separately authorized.2627## Output2829Return Intended outcomes, Observed evidence, Variance, Learning, Priorities, Next experiments, and Claim limits.30
JovaniPink