Seven-Day Shipping Sprint
Reduce a project to one useful outcome and make it available to another person within seven days.
The constraint
At the end of seven days, one real person must be able to inspect, use, or respond to something that was not available on day one.
Day 1: Choose one outcome
Write: "After this sprint, a person can..." Remove every outcome joined by "and."
Day 2: Remove scope
List everything not required for that outcome. Delay accounts, dashboards, automation, polish, and extra channels unless the outcome depends on them.
Day 3: Build the complete thin path
Connect the beginning to the result with the simplest working implementation. It may be manual behind the scenes.
Day 4: Make failure visible
Test the path with imperfect input. Add enough explanation or error handling that another person can continue.
Day 5: Put it in front of one person
Observe without teaching the workflow. Record where the person hesitates, stops, or expects something different.
Day 6: Fix the first blocking problem
Choose the issue that prevents the intended outcome. Ignore cosmetic requests and unrelated possibilities.
Day 7: Ship and document
Publish the working URL, repository, document, or release. State what works, what does not, and what evidence you need next.
The sprint is successful when
- [ ] Another person can reach the intended outcome.
- [ ] The current limitation is visible.
- [ ] You recorded at least one observation from real use.
- [ ] The next decision depends on evidence, not launch excitement.