Sprint OS

The Sprint OS grew out of two traditions colliding. The first is sprint planning from software development — fixed timeboxes, committed scope, a review at the end. The second is a decade of operations consulting for small businesses, where the same failure kept surfacing: good plans, no weekly reckoning. The Sprint OS is the system we built to fix that, and it is the methodology Pilot runs on. It is not 12 Week Year software; it is our own system, built from running real sprints.

The loop is deliberately small. A sprint is one focused ~12-week (90-day) execution cycle. Inside it you set one to three sprint goals, break each into weekly tactics, and score every week as completed tactics divided by planned tactics. The 85% weekly benchmark tells you whether the sprint is on track long before the deadline does, and a weekly accountability meeting — or a solo weekly review — closes the loop so the score is acted on, not just recorded.

The plan is: plan the sprint, execute the week, score it Friday. That cadence is what separates the Sprint OS from a planning document. Pilot is loosely inspired by the 12 Week Year but is its own methodology, and is not affiliated with or endorsed by Brian P. Moran, LLC or 12 Week Year®.