12-Week Year
Compress a year into twelve weeks and let urgency do the rest.
Table of Contents
History & Origins
The 12-Week Year was introduced by Brian Moran and Michael Lennington in their 2013 book of the same name. The authors drew on sports-periodisation (where athletes compress training into intense cycles) and execution psychology to argue that annual goals lose urgency because the deadline is too far away. By compressing a year's goals into 12 weeks, each week becomes the equivalent of a month, raising urgency and follow-through. The framework was adopted by sales teams, engineering organisations, and executive coaches as an execution-acceleration tool. It is particularly effective for B2B companies where annual planning cycles create a mid-year lull that lets strategic goals drift without consequence until it's too late to recover. Moran and Lennington developed the framework after observing that annual goals consistently underperformed, not because the goals were wrong but because the deadline was too distant to create daily urgency. By compressing the cycle to 12 weeks, every week matters, and under-performance shows up in days rather than quarters. The framework is complementary to OKRs (which define the outcomes) and to Time Blocking (which protects the deep work), and it is particularly valuable for goals that have been drifting in an annual cycle. Today, the 12-Week Year is used by sales teams (12-week revenue sprints), engineering teams (12-week delivery sprints), and executive teams (12-week strategic sprints), with the compression producing a measurable increase in execution velocity.
Core Concept
The 12-Week Year compresses annual goals into a 12-week sprint, treating each week as a month of execution. The framework argues that annual goals fail because the deadline is too distant to create urgency; by shortening the cycle, every week matters. Goals are broken into weekly milestones tracked against leading KPIs, so underperformance shows up in days, not quarters. At week 12, execution is scored, and the next 12-week cycle begins. The compression forces focus: you can't pursue everything in 12 weeks, so priorities become ruthlessly clear. The framework also includes a weekly accountability cadence, where progress is reviewed against the plan and course corrections happen mid-sprint rather than after a quiet quarter. The key insight is that urgency is a function of deadline proximity, not of importance: a 12-month deadline doesn't create daily urgency even for an important goal, while a 12-week deadline creates daily urgency for the same goal. The framework also argues that the 12-week cycle is long enough to produce meaningful results but short enough to maintain focus, and that the 5-day break between cycles (week 13) provides recovery and planning time. The compression also forces prioritisation: in 12 weeks, you can only pursue 2-3 goals, so the framework naturally produces focus, unlike an annual plan that tries to pursue 10 goals and delivers none.
B2B Application Guide
In B2B companies, the 12-Week Year compresses annual goals into a sprint that sharpens opex and resourcing decisions. Instead of a vague yearly budget, teams commit to weekly milestones tied to inventory turn, tech-debt reduction, or release cadence. Underperformance shows up in days, not quarters, so course corrections happen mid-sprint. The compressed cycle makes under-resourced goals visible early, so headcount and budget adjustments happen mid-sprint rather than after a quiet quarter. It also forces a tight, measurable commitment to a specific platform outcome, so opex goes to capability that lands inside the window rather than drifting into a multi-quarter rewrite that accrues tech debt without delivering value. For supply chain, a 12-week sprint targets inventory turn with weekly milestones on safety stock, supplier lead time, and stockout rate. For merchandising, a 12-week sprint targets gross margin with weekly milestones on private-label penetration, vendor terms, and markdown rate. For technology selection, a 12-week sprint targets platform reliability with weekly milestones on uptime, change-failure rate, and MTTR. For hiring, a 12-week sprint targets team capacity with weekly milestones on time-to-hire, offer acceptance, and ramp time. For vendor management, a 12-week sprint targets vendor performance with weekly milestones on on-time delivery, defect rate, and contract compliance. The framework also disciplines budgeting: opex is committed to the 12-week sprint, not to an annual baseline, so budget follows the sprint's goals rather than inertia.
Step-by-Step Implementation
Step 1: Choose 2-3 goals. Select the goals that, if achieved in 12 weeks, would make the biggest difference. Don't choose more than 3; the compression requires focus. Step 2: Break each goal into weekly milestones. For each goal, define what must be true at the end of each week to stay on track. Step 3: Define leading KPIs. For each goal, identify the leading indicator (the metric that predicts the goal will be achieved) and track it weekly. Step 4: Block the time. Use Time Blocking to reserve deep-work blocks for the sprint goals, so reactive work doesn't consume the week. Step 5: Review weekly. At the end of each week, review the milestones and KPIs against the plan. If behind, course-correct immediately. Step 6: Score at week 12. Score the execution (0-100%) for each goal, and identify what worked and what didn't. Step 7: Take week 13 off. Use the 5-day break for recovery and planning, so the next sprint starts fresh. Step 8: Plan the next 12-week cycle. Based on the previous cycle's scores, set the next 2-3 goals and weekly milestones. Step 9: Carry forward unfinished goals. Goals that didn't reach 100% roll into the next cycle, with the learnings from the previous cycle.
Common Pitfalls & How to Avoid Them
Pitfall 1: Too many goals. The sprint has 5+ goals, and focus is diffused. Avoid by limiting to 2-3 goals per 12-week cycle. Pitfall 2: No weekly milestones. The goal is set but not broken into weekly milestones, so progress isn't visible until week 12. Avoid by defining weekly milestones for each goal. Pitfall 3: No leading KPIs. The goal is tracked by a lagging indicator (revenue) rather than a leading indicator (pipeline), so under-performance is discovered too late. Avoid by defining leading KPIs that predict the goal. Pitfall 4: Not blocking the time. The sprint goals are set, but reactive work fills the week, and the goals drift. Avoid by Time Blocking the deep-work blocks for the sprint. Pitfall 5: Not reviewing weekly. The sprint is set and forgotten, and under-performance is discovered at week 12. Avoid by a weekly review against the milestones and KPIs. Pitfall 6: Not taking week 13 off. The team jumps straight into the next sprint, and burnout erodes execution. Avoid by taking the 5-day break for recovery and planning.
Extended Real-World Example
A B2B ecommerce team ran a 12-week sprint to lift retention by 8%. The goal was broken into weekly milestones: weeks 1-3 (segment the lapsed cohort), weeks 4-6 (build the win-back automation), weeks 7-9 (launch and measure), weeks 10-12 (optimise and score). Each week was tracked against CRM repeat-rate data. By week 8, the win-back automation was live and repeat rate had moved 5 points. The compressed cycle made the pace visible and kept the team focused on the single goal rather than diffusing across the annual plan. At week 12, execution was scored (retention +6.5%, short of the 8% target), and the unfinished work rolled into the next 12-week cycle with a clear baseline. Over four 12-week cycles, the retention sprint produced compounding results. Cycle 1: Retention +6.5% (target +8%). The win-back automation was built and launched, but the segmentation was too broad (all lapsed customers, not just high-value). Score: 81%. Cycle 2: Retention +7.2% (target +8%). The segmentation was refined to high-value lapsed customers, and the win-back offers were personalised. Score: 90%. Cycle 3: Retention +8.4% (target +8%). The win-back automation was extended to include a 3-touch sequence (email, SMS, account-manager call), and the repeat rate crossed the target. Score: 105%. Cycle 4: Retention +9.1% (target +8%). The win-back automation was optimised with ML-driven offer selection, and the retention lift exceeded the target. Score: 114%. The weekly milestones made under-performance visible early: in cycle 1, week 4, the segmentation milestone was behind (only 40% of the lapsed cohort was segmented), and the team redirected capacity from a non-sprint project to the segmentation, which was complete by week 5. The leading KPI (segmentation completion) predicted the lagging KPI (repeat rate), so the team knew by week 4 that the cycle was at risk, and course-corrected immediately. The 12-week compression also forced prioritisation: the team had 4 other initiatives on the annual plan, but only the retention sprint was pursued in cycles 1-4, and the other initiatives were deferred to later cycles. The result: retention lifted 9.1% in four 12-week cycles (48 weeks), compared to 3.2% in the previous 48 weeks under an annual plan. The compression produced a 2.8x improvement in execution velocity, because every week mattered and under-performance was caught in days rather than quarters. The week 13 breaks were taken consistently, and the team entered each cycle fresh, with the previous cycle's learnings carried forward.
Measuring Success
12-Week Year success is measured by the execution score (the percentage of the goal achieved at week 12) and the weekly milestone hit rate (the percentage of weekly milestones completed on time). The key indicators are: execution score (should trend toward 80-100% as the team learns to estimate and execute), weekly milestone hit rate (should trend toward 80%+ as the team learns to plan accurately), and course-correction frequency (how often the team redirected mid-sprint, which should be non-zero, showing the framework is being used actively). In practice, these are tracked by the weekly review and the week-12 scoring. The ultimate test is whether the compressed cycle is producing faster results than the annual cycle: is the team achieving more in 12 weeks than it did in a quarter under the annual plan? If the execution scores are consistently below 60%, the goals may be too ambitious, the weekly milestones may be too granular, or the team may not be blocking the time. If the scores are consistently 100%+, the goals may be sandbagged. A healthy 12-Week Year practice produces execution scores in the 70-100% range, with weekly milestone hit rates above 80%, and with course corrections happening mid-sprint rather than at week 12.
Framework Visualizations
Data-driven graphics showing how 12-Week Year is applied to real B2B data.
Explore Further
Explore the Full Portfolio
This is the complete portfolio of Sufi Khan Sulaiman, a technology leader specialising in B2B commerce and digital automation. Start from the Home page for the overview, then move through two decades of career experience across FLIR Systems, Lorex Technology, and 1c Platform, and the full catalogue of project case studies spanning headless commerce migrations, AI recommendation engines, and multi-channel fulfilment systems.
The skills and certifications page maps the technical and leadership capabilities behind the work, while the articles and the knowledge base break down the thinking into actionable frameworks. For hands-on learning, the tutorials and applications sections cover practical builds from front-end fundamentals to full-stack web apps.
For consulting engagement, the expertise page outlines service offerings, the ecommerce hub covers platform architecture and automation strategy, and the ecommerce guide (PDF) is a downloadable 55-page field manual. When you are ready to talk, the contact page is the direct line.