Start with one sentence
The from-zero blueprint
Define who the work serves, what they receive, and the change you hope to support. Seven steps and a ten-question audit give the idea somewhere concrete to land.
- Leave with
- One clear promise
The free toolkit · No account needed
Define the work. Put it in front of a person. Record what happened. Choose what comes next.
Read the toolkit as Markdown →Your next useful move
Start by naming one person, the situation they face, and the complete thing you will deliver. The blueprint helps you turn the mission into a testable promise.
Leave with one sentence someone else can repeat.
Start with one sentence
Define who the work serves, what they receive, and the change you hope to support. Seven steps and a ten-question audit give the idea somewhere concrete to land.
One focused move each day
Deliver the smallest complete promise, record use and return, and make a decision. Keep private notes, export the whole sprint, or restore an earlier export.
Use the numbers you have
Separate reach, delivery, use, return, and evidenced change. Check your definitions and the strongest claim the evidence can support before publishing a number.
Finish with a decision
Put the promise, people, reporting window, findings, method, and limits in one report. Review missing context before sharing, and carry the checklist and warnings into your exports.
No account, payment, or background upload is required. Working drafts are separate and private to this browser. Keep an export before clearing browser storage.
Start with the blueprint if your promise is still unclear. Use the 30-day sprint when you are ready to deliver and observe. Use the scorecard when you have signals to classify, then the proof pack when you need to report a finding and decision.
The blueprint, sprint, impact scorecard, and proof pack are free to use without an account. The interactive tools keep working drafts in your browser and offer exports you can keep.
The tools keep separate drafts and never combine counts automatically. In the proof pack builder, Review scorecard snapshot lets you inspect a copy from this browser before explicitly replacing the current report. It carries the project, promise, planned change, separate counts, and evidence notes. Reporting dates, findings, limitations, and decisions still need your review. The original scorecard is unchanged.
Export the proof pack from the sprint, keep the JSON file, and open Restore a sprint file in the other browser. Review its project, completed days, and note count, then explicitly replace the current sprint. Older version-one SIX33 sprint exports are supported.
There is no automatic account sync. Export a JSON backup from the sprint, scorecard, or proof pack, then restore it in the same tool on another browser. Review the backup before explicitly replacing the current draft. Keep backups private: they are readable files, not encrypted.
A completed sprint is a record of work and evidence. An impact claim still needs a defined outcome, a stated method, a reporting window, and material limitations. Completing a checklist or exporting a report does not establish that a life changed.