Over the past three months, we intensively tracked the weekly action metrics execution of 47 early-stage entrepreneurs within the 12W community (defined as those less than 18 months in, with teams of 1–5 people). The data reveals a brutal truth: by the end of the first WAM tracking cycle (typically falling in weeks 3–4), only 23% of teams managed to simultaneously meet two conditions—hitting their output quantity targets and maintaining a quality score no lower than the previous week. This number is far below the optimistic premise implied by most entrepreneurship books that "if you persist, you'll succeed."
[Failure in Action] The most common collapse pattern in week one isn't "doing absolutely nothing"—it's "doing a lot, but all of it off-target from the core hypothesis." Examining the three foundational dimensions in the WAM framework—customer contact frequency (Contact), delivered output (Delivery), and validation iteration (Iteration)—early-stage entrepreneurs tend to massively over-index on the Contact dimension while showing zero output in Delivery, and Iteration is never even formally initiated. On the surface, they're having plenty of conversations with potential customers. In reality, not a single hypothesis has been formally tested.
Why Setting Goals Too Big Traps Teams in the "Illusion of Diligence"
Psychological research has confirmed that humans' inherent resistance to vague goals gives rise to two complementary avoidance behaviors: either doing too little to escape accountability for failure (the "I wasn't even trying" self-protection), or doing too much to manufacture a sense of "I gave it my all." The problem is that the latter is much harder to detect. When an entrepreneur writes in their notebook, "I want to hit NT$500K in monthly revenue within six months," their brain automatically reframes "executing any related activity" as "making progress"—including attending startup forums, asking for opinions in LINE groups, or buying a relevant book to read. The common feature of these activities: they neither require facing real customer feedback nor produce any measurable market signal.
What sets WAM records apart from traditional OKRs is the granularity of time. Traditional goal-setting operates on monthly or quarterly cycles, while WAM forces you to face a naked audit every week: "What did you actually do this week?" If your weekly target is "add 10 new potential customers," then when you tally things up Friday night, the numbers speak for themselves: either you did it or you didn't, with no gray area in between. This high-frequency feedback loop exposes an uncomfortable truth right in week one—most people's self-assessment of their actual capacity has a 40%–60% gap from real execution data.
Three Core Factors That Cause Goal-Setting to Spiral
The first factor is "vision displacement." Some entrepreneurs have a vision of "transforming Taiwan's restaurant industry through digitalization." That's fine—but when this vision is directly translated into "200 restaurants using our system by the end of Q1," the execution-level granularity has skipped over seven or eight necessary validation checkpoints. These include: How much are restaurant owners willing to pay for this problem? What alternatives are they currently using? How much training cost is needed to change their workflow? How long is your sales cycle? Numbers set without passing through the answers to these questions are, in essence, optimistic guesses—not goals.
The second factor is the cognitive bias of "hypothesis equals fact." In cognitive psychology, this is known as the Planning Fallacy—the tendency for people to underestimate the time and resources required to complete a task, while overestimating their own control. Multiple multinational studies show that even experienced professionals are only slightly more accurate than blind guessing when predicting their future performance. Entrepreneurs, as a highly confident group, tend to exhibit this bias even more severely.
The third factor is the "multitasking myth." The most common time allocation pattern for week-one entrepreneurs is: pushing forward 5–7 tasks in different directions simultaneously, with deep focus time allocated to each task falling below 15% of total working hours. This is exactly why the Delivery dimension in the WAM framework matters—it forces you to ask: "What tangible thing did I deliver this week that I can show to someone else?" If the answer is vague, it means your attention resources are being diluted by massive invisible drains.
Three Concrete Lessons Extracted from WAM Records
The first lesson: Goals must be decomposable into the smallest actionable units. "I want to find Product-Market Fit" is not a goal—it's a direction. A goal should be: "This week, I will conduct in-depth interviews of 30+ minutes with 8 restaurant owners, and produce at least 3 testable hypothesis statements." When a goal is cut to this level of granularity, "executed or not" becomes a binary judgment rather than a long-term struggle that requires massive willpower to sustain.
The second lesson: The frequency of failure needs to be deliberately managed. Research shows that early-stage entrepreneurs who experience 3 or more "explicit failures" in their first month (being clearly rejected by customers, having a product feature nobody uses, having a partnership discussion collapse) make significantly better subsequent decisions than peers who never experienced failure. The reason is that failure forces hypotheses to be re-examined, while continued success (sometimes merely due to a sample size that's too small) reinforces unvalidated beliefs. The Iteration dimension in WAM records is specifically designed to log and structure these failures.
The third lesson: Output rhythm matters more than peak performance. Observing entrepreneurs in the 12W community who sustained WAM execution for more than 8 weeks, their common characteristic wasn't an exceptionally standout week—it was extremely low week-to-week output variance. This means they've found their own sustainable execution rhythm, rather than relying on passion and willpower to explode in a particular week and then crash. This observation aligns closely with the concept proposed by James Clear, author of Atomic Habits: "Do not focus on goals. Focus on systems."
Adjustments You Can Implement Right Now
Returning to this week's WAM framework, we suggest every entrepreneur reading this article do a simple review: open up your weekly goal and recall the basis behind the number you set. Was it grounded in market data, customer interviews, or simply a "feeling that I can do it"? If the answer leans toward the latter, then next week's WAM target should be cut in half directly. Not because you lack ability, but because unvalidated numbers are just noise.
Here's the specific operating method: First, reverse-engineer your monthly goal into weekly units to determine the minimum output needed each week; then, divide that number by 2 to serve as your actual first-week execution target; finally, log your real first-week completion rate, and use that data to calibrate next week's target. The point of this process isn't to have you hit a "discounted" number—it's to build a feedback system that lets you honestly face your progress every week instead of deceiving yourself.
The ultimate value of WAM isn't giving you pretty numbers to report every week—it's that in week twelve, week eighteen, or even much later, it becomes the only credible reference when you review your decision trajectory. Those numbers will honestly tell you: which week you started going off course, what caused it, and whether there were any warning signs at the time. The cost of setting goals too big is often not failure itself, but losing track of how you even failed.
Ben Horowitz, author of The Hard Thing About Hard Things, once wrote: "After eight years as CEO, the most important lesson I learned is that in most cases, the right answer isn't 'how should we do it,' but 'what should we do.'" The starting point of WAM records is exactly this—forcing you to answer the harder question first, before each week ends.