A Neglected Fact: The Output Trap of Annual Planning
In Taiwan's startup scene, the most common year-end ritual is founders passionately debating next year's goals: expand the market, grow revenue, launch a new product. Twelve months later, how many of these goals actually get executed? Research firm Gartner published a 2020 survey showing that only 23% of organizations manage to complete more than 70% of their annual strategic objectives. This number exposes a brutal reality: for most people, annual plans ultimately become wish lists rather than execution blueprints.
The problem isn't that the goals themselves are poorly set—it's the absence of a quantifiable execution-tracking mechanism. When "achieve by year-end" becomes the only checkpoint, the twelve months in between turn into a vague wasteland. Researchers call this "execution decay in long-term goals"—the further the deadline, the more execution discipline erodes, and by the year-end review, you suddenly realize your output was seriously lacking.
This pattern harms founders not just through low output, but also through damaged morale and wasted resources. When a year ends and you discover your effort didn't match the results, next year's planning tends to swing between being overly conservative or excessively optimistic.
Root Cause: Why Your Execution Rate Never Picks Up
Digging deeper into this phenomenon reveals three structural problems. The first is "cycle mismatch"—goal-setting on an annual basis fundamentally conflicts with how the human brain processes time. Psychological research shows that our perception of future events decays as the distance increases; commitments beyond three months see significant weakening in neural connections. This means annual goals are automatically downgraded by the brain at the cognitive level.
Second is the "missing granularity." When most founders set goals at the beginning of the year, they tend to use abstract descriptions like "improve user experience" or "expand distribution channels." These goals may point in the right direction, but they lack concrete weekly measurable indicators. When a week ends with no quantifiable output, neither the team nor the individual can tell whether they're on the right track.
The third problem is even more fundamental: "feedback delay." Annual goals have far too long a feedback cycle, resulting in a learning curve that's too flat. When you discover in Q3 that your strategic direction was wrong, you've already wasted six months of time and resources. This is exactly why agile methodology rose to prominence in software development—it compresses the feedback cycle from months to days, allowing errors to be corrected before they cause major damage.
The Key Insight of the 12W System: Weekly Output Matters More Than Annual Output
The reason 12W delivers significant results lies at its core: it forces you to define and track Output every week, rather than focusing solely on Input. "I completed three feature developments this week" versus "I hope to launch a new system by year-end"—these two statements may seem related, but they represent fundamentally different mindsets. The former focuses on deliverable value; the latter is easily deceived by the feeling of being busy, obscuring actual results.
A real case illustrates this difference. One startup completed only two major feature developments in the twelve months before adopting the 12W system. The team felt busy, but from an outside view, their product iteration speed lagged far behind competitors. After implementing the twelve-week sprint framework, the team began setting clear weekly feature delivery targets and conducting output reviews every Friday. In the first 12W cycle, the team not only caught up to their previous twelve months' progress but also completed an additional feature module originally scheduled for the next quarter.
This contrast isn't an isolated case. British business mindset expert Charles Hummel pointed out in his research that the root cause of organizational inefficiency is often not a lack of resources or capability, but a lack of "urgency." When goals are set on an annual basis, no single day feels particularly urgent; but when goals are broken into twelve three-week cycles, the pressure of "must complete this week" naturally emerges, and execution rates improve dramatically.
Immediate Actionable Adjustment: The Weekly Output List
To turn these insights into actual action, I recommend a simple but strict tool: the Weekly Output List. Unlike a typical to-do list, this list only includes outputs that, once completed, will drive your core goals forward—not routine tasks or communications work.
Here's the specific approach: every Sunday evening, spend fifteen minutes listing no more than five key outputs for the upcoming week. These outputs must meet three conditions: first, they can be objectively verified as complete; second, their completion produces visible progress toward the core goal; third, they can be finished within an estimated forty working hours. On Friday, review this list, calculate the completion rate, and record the reasons.
The value of this exercise isn't in improving the number itself, but in building a kind of "output awareness." When you know you'll review this week's output over the weekend, your daily work choices unconsciously rearrange themselves around the core goal. Conference calls, email replies, routine reports—these necessary but output-less tasks will still take up time, but you won't let them steal the hours meant for key deliverables.
"Most people don't lack ability; they lack a framework that makes output visible. When weekly results become concrete numbers, the direction for improvement naturally emerges."—Deep Work, Cal Newport, 2016