A Number You Don't Want to Face
When coaching startup teams, I see a recurring pattern: after the first week, the entrepreneur's WAM (Weekly Action Metric) shows "zero progress." It's not because of laziness, and it's not because the direction is wrong—it's because the goals set at the very beginning far exceeded what was realistically executable in the short term. Psychological research shows that when a goal's difficulty exceeds what a person perceives as achievable, the brain triggers a "psychological reactance" mechanism, pushing that goal out of conscious awareness. This isn't a willpower problem—it's a natural protective response from the cognitive system.
According to Locke and Latham's goal-setting theory, published in 2002, goal difficulty does improve performance, but this relationship has one critical prerequisite: the goal must possess "clarity" and "feedback." When an entrepreneur only sets one grand number—like "hit $100K in revenue in the first month"—but doesn't break it down into concrete daily or weekly actions, the goal itself becomes a source of psychological pressure rather than a driver of action.
Root Cause Analysis: Why Big Goals Create Helplessness
From a cognitive psychology standpoint, the human decision-making system has limited tolerance for "delayed feedback." When a goal takes weeks or months to show results, the brain tends to choose the "more immediate" reward path. This explains why many entrepreneurs will code for three hours late into the night while ignoring customer development—because "coding" delivers an immediate sense of productivity, while the feedback from "cold-calling potential customers" is unknown and distant.
Furthermore, setting oversized goals triggers the risk of "learned helplessness." Psychologist Seligman's classic 1967 experiment found that when animals (or humans) repeatedly experience outcomes they cannot control, they gradually stop trying. Apply this to the startup context: when an entrepreneur fails to hit their set numbers for consecutive weeks, they begin to question their own ability and direction, rather than examining the reasonableness of the goals themselves.
Another frequently overlooked factor is "the scarcity of attentional resources." Cognitive science research shows that human self-control and decision-making capacity are finite resources. When an entrepreneur has to repeatedly "resist" the anxiety generated by their goals throughout the day, that resistance itself drains willpower. This depletion tends to peak in the afternoon, causing the most important decisions and actions to be postponed indefinitely.
Real Lessons Learned: The True Value of WAM Lies in Granularity
After reviewing the WAM records of multiple Taiwanese startup teams, a pattern emerged: teams that executed consistently week after week never set goals on a timeline longer than three days. In other words, they transformed "what to achieve a month from now" into "what to do within the next three days." This finding aligns closely with the Sprint concept in Agile development: slice the long-term vision into digestible blocks, each with a clear definition of done and validation criteria.
Specifically, if an entrepreneur's goal for the week is "improve user retention," that's not an effective WAM entry. An effective entry would be: "this week, send out 20 user follow-up emails and record the response rate." The former is a wish; the latter is an action. The former triggers anxiety; the latter triggers execution. This isn't about lowering the bar—it's about making the bar measurable and adjustable.
Another important lesson: WAM targets should "trail" rather than "lead" current capacity. In other words, this week's goal should be 80% to 90% of last week's actual execution—not 100% of the ideal state. This approach may seem conservative, but it ensures a positive "achievement" signal every week, and positive feedback is the strongest driver of sustained action.
Adjustments You Can Make Right Now: Three Steps to Reset This Week's Goals
Step 1: Translate the original number-based goal into "concrete actions." For example, change "add 50 subscribers this week" to "publish product introduction posts on three relevant forums this week, and reply to at least five comments on each post." The former depends on external outcomes; the latter is fully under your own control.
Step 2: Set the "shortest verifiable cycle." Based on observation, for content entrepreneurship or software services, 48 hours is the most efficient verifiable unit. Within those 48 hours, there must be an action that can be "completed" and a metric that can be "observed." If a particular action takes more than 72 hours to yield any feedback, consider breaking it down further.
Step 3: Build in "failure expectations" and an "adjustment frequency." Every weekly goal should be set with a built-in assumption: "if this action doesn't work, I'll know within three days." This assumption isn't pessimism—it's the distilled wisdom of practical experience. Entrepreneurship is fundamentally a process of constant hypothesizing and validating. People who fear failure often die from not daring to act, not from the act itself.
"When setting goals, the real danger isn't that the goal is too small—it's that the goal is so large that the brain treats it as a threat rather than a challenge." (Extended interpretation based on Locke and Latham's Goal-Setting Theory)