The first week's WAM tracking record came out, and the numbers left everyone speechless. 72 weekly goals were set, but only 3 were actually completed, with an execution rate of less than 5%. This number reveals not a capability issue, but a systematic flaw. The cost of setting goals too large is not just this week's failure, but planting the seeds of collapse for the entire WAM system.
Failure is Not Accidental: The Systematic Problems Revealed by WAM Records
Examining this WAM record reveals a harsh fact: there is a systematic flaw in the goal-setting itself. The 72 goals covered seven major categories including product development, content creation, partnership negotiations, and learning plans, each one appearing necessary. However, when all goals are listed side by side, the criteria for judging priority disappear. Research shows that when people set goals, they tend to plan based on "what they want to achieve" rather than "what historical data shows they can achieve." This tendency leads to goal quantities far exceeding actual execution capacity boundaries.
Why Too Many Goals Inevitably Lead to Execution Collapse
Breaking down this failure case, the problem structure is clearly visible. The first reason is "baseline misplacement" — people reference not their historical performance, but how much they could complete in an ideal state. When listing the to-do list, the brain defaults to using estimates from the best-case scenario, while reality always includes interruptions, exhaustion, and unexpected events. According to Leo Babauta, author of "The Art of Action," most knowledge workers can actually execute deep work sessions for only 2 to 3 hours per day on average, with the remaining time being sliced up by meetings, messages, and trivial tasks.
The second reason is "lack of granularity". Many goals remain at the project level rather than the action level. "Complete user interviews" is not an action; it needs to be broken down into "invite 5 users", "prepare interview guide", "conduct the first interview", etc., multiple measurable steps. A vague goal equals no goal.
The third reason is "lack of energy management". A person's energy is not constant throughout the day, but the goal list does not reflect such fluctuations. Placing high‑cognitive‑load tasks in the afternoon often results in half‑finished work or delays.
Practical lessons learned: Reducing the number of goals improves execution rate
A list of 72 goals looks ambitious, but execution rate data tells the whole story. If the number of goals is reduced to 3 to 5, each with a clear action definition and completion criteria, the execution rate could rise from 5% to over 60%. This is not lowering standards, but more precisely allocating limited resources.
True prioritization is not about picking 3 out of 10 tasks to do, but having the courage to decisively discard the other 7. This "less is more" principle is not unfamiliar in the startup world. The Pareto principle points out that a minority of actions generate the majority of results, but the problem is that from the start those few actions were not accurately identified.
Another hidden benefit of reducing the number of goals is the protection of the motivation system. Psychological research indicates that goal achievement rate is a key variable in maintaining long-term motivation. Frequently completing a small number of goals enhances intrinsic motivation, while listing 72 items per week but only achieving 3 leads to learned helplessness. More dangerously, this failure pattern forms a negative cycle: failure leads to decreased motivation, decreased motivation leads to setting more goals next week to compensate, more goals lead to lower execution rate, and lower execution rate leads to deeper failure.
An adjustment you can implement immediately
Starting next week, forcibly limit the number of WAM goals: a maximum of 5 per week, with 3 being ideal. Each item must answer three questions: what to do (specific action), to what extent (measurable standard), and when to complete it (clear deadline). Move remaining goals into the "pending pool," not deleting them, just pausing them.
Second, establish the "one item per day" principle. Each day, choose the most important 1 thing from your weekly goals as the primary task for that day. Before this task is completed, do not handle other matters. This is not inefficiency, but focus.
Third, conduct a "completion review" every night. If no priority items were completed that day, this is a signal for adjustment, not an excuse to end the day.
Fourth, keep a failure list. This is not indulging helpless emotions, but objectively recording facts: this week 72 items were set, only 3 were achieved. The numbers speak for themselves, and this list will become the most honest reference material when planning for next week.
Finally, use data instead of feelings. Record the number of goals and completion rate each week, calculating the real execution rate, rather than judging based on subjective feelings. After 3 to 4 weeks of tracking, you will have your own baseline data, rather than relying on others' advice or intuition.
"Planning fallacy" was first proposed by Kahneman and his colleagues, describing how people systematically underestimate the time and resources needed to complete tasks. In "Thinking, Fast and Slow," Kahneman suggests using an "outside view"—referencing historical performance on similar tasks—rather than relying solely on internal estimates. The significance of reducing the number of goals lies in forcing yourself back to the outside view: using actual completion rates, rather than a wish list, to define next week's output boundaries.