Turn an important priority into governed weekly execution.
The 12 Week Sprint creates focus, scorecards, commitments, and decision gates around one meaningful business outcome.
Choose this path only when the conditions are right.
Strong fit
- A defined objective can be completed or materially advanced in 12 weeks.
- The accountable owner and contributors are known.
- Success can be measured with leading and lagging indicators.
- The team will participate in a weekly execution rhythm.
Not the right fit
- The underlying problem is still unclear.
- The work requires a multi-discipline transformation rather than one operating cycle.
- No internal owner can be assigned.
- The organization will not maintain weekly commitments or evidence.
Defined outputs—not vague support.
- Sprint objective and success criteria
- 12-week goal and milestone structure
- Leading and lagging scorecard
- Weekly commitments and action records
- Decision gates, risk log, and blocker management
- Sprint closeout and next-cycle recommendation
A governed decision and implementation path.
Every stage has a purpose, an owner, and evidence of completion.
Set
Define the objective, baseline, success criteria, owners, and operating rules.
Plan
Translate the outcome into milestones, measures, and weekly commitments.
Run
Execute through a disciplined weekly review and Focus Queue.
Decide
Use decision gates to adjust scope, resources, and priorities.
Close
Evaluate results, capture learning, and determine the next cycle.
Expected operating cycle
12 weeks, with a formal setup, weekly sprint records, decision gates, and a structured closeout.
Progress must be visible.
- Weekly scorecard trend
- Commitment completion rate
- Decision and blocker history
- Final outcome compared with the approved baseline
Representative operating case
An owner had a revenue goal but no consistent execution rhythm. The Sprint converted the goal into weekly prospecting, follow-up, proposal, and visit measures; surfaced blockers early; and created a visible operating record for course correction. This is an illustrative engagement pattern.
Illustrative engagement patternEvery action enters a governed workflow.
Business Bottleneck Scorecard
Use the diagnostic when readiness, constraint, or program fit still requires evidence.
Make the decision with the important questions answered.
Can a Sprint include several goals?
The strongest Sprints center on one objective supported by a limited number of goals and measures.
What happens when a week is missed?
The scorecard makes the miss visible, the cause is reviewed, and the next commitment is adjusted without hiding the variance.
Is this only for revenue goals?
No. Sprints can address operations, leadership, finance, customer experience, or another measurable priority.
Do we need YSCO OS?
The Sprint is governed through YSCO OS so goals, scorecards, actions, blockers, and decisions remain connected.
What if the problem is broader than one Sprint?
YSCO will route the business to the Accelerator or Fractional COO path when the constraint requires broader operating change.
Route the business into the correct OS workflow.
Proceed with the fit path, begin with the diagnostic, or choose the alternative when the conditions are not yet right.
Execution proof comes from weekly scorecards, commitments, blocker history, and the final result against baseline.
Representative proof includes membership movement, campaign attribution, referral revenue, and governed weekly actions tied to one measurable objective.