Within the 12W ecosystem, we have the chance to observe startup teams at different stages up close. Each team walks into the accelerator carrying its own assumptions—some choose user growth as their core focus, others zero in on revenue performance. Those differences create a unique learning field where you can see the real-world outcomes of various strategic choices.
A Concrete Failure Worth Studying
In the accelerator environment, you can often see teams start to adjust their strategic direction around week three. One pattern in particular is worth digging into: many teams actively set and track specific KPIs in weeks one and two, but by week three, a portion of them hit a clear bottleneck.
According to a report published by Startup Genome in 2022, roughly 30% of startups go through at least one major strategic pivot within their first year—and one common cause is a gap between the metrics they set and the reality on the ground. This data echoes what we see inside the accelerator: chasing metrics is not the same as chasing value.
Within these cases, one pattern stands out: when a team over-focuses on a single metric, it often overlooks the other factors that support that metric. A team chasing registration numbers, for example, might find that while the number is climbing, user activity stays stuck at a worryingly low level.
This observation led us to a fundamental question: when we set a KPI, is it because it "should be tracked," or because it "truly reflects the value we create"?
What's Really Going On Underneath
The answer usually reveals deeper assumption errors. When setting KPIs, many startup teams unconsciously adopt industry-standard frameworks. They study competitors' products, read relevant reports, and then copy those "critical success metrics." This approach overlooks an important premise: every product delivers value in its own unique way, and that way isn't always captured by generic metrics.
The concept of "validated learning" emphasized in The Lean Startup becomes especially important here. Eric Ries points out that a startup team's primary task is to test its assumptions, not to blindly chase predetermined success indicators. When a team finds that a metric keeps deviating from expectations, it shouldn't simply double down on improving that number—it should step back and examine whether the underlying assumptions supporting the metric are actually correct.
Another common cause we observe in the accelerator is a timing mismatch. Teams at different stages should focus on different metrics. For a team still searching for product-market fit, over-focusing on revenue can be a distraction; for a team that has already found fit, not tracking monetization efficiency is another form of waste. This misalignment between stage and metric is often the root cause of teams getting stuck around week three.
There's also a psychological factor that can't be ignored: metrics themselves have a hypnotic effect. When the numbers trend positive, teams easily develop a sense of security, believing they're on the right track. But that security is sometimes false—the numbers might be growing for the wrong reasons, or it could simply be a temporary trend rather than real progress.
What We Actually Learned
The first important lesson from these observations: a KPI is not a navigation system, it's a review system. Most entrepreneurs treat metrics as a compass pointing the way forward, but in reality, the more accurate job of a metric is to tell you what happened over a past period—not where you should go next. Choosing a direction requires deep understanding of customers, product, and market, not a chase after numbers.
The second lesson: dropping a metric is never a sign of failure. Choosing to stop tracking a certain metric usually means the team has made an important strategic decision: it has decided to put its attention somewhere more meaningful. In The Hard Thing About Hard Things, Ben Horowitz shares many stories of difficult decisions, and a core theme is that strong leaders know when to hold firm and when to pivot decisively.
The third lesson involves the hierarchy of metrics. Research shows that high-performing teams typically build a three-layer metric framework: at the top is the North Star metric—that single metric that best represents the value the product creates for users; in the middle are supporting metrics—important but not endpoints in themselves; at the bottom are diagnostic metrics—detailed data used to understand why the upper-level metrics are moving. When a middle- or bottom-layer metric consistently underperforms, rather than constantly optimizing it, the team should ask whether this metric is really worth tracking in the first place.
The final lesson is about how a team allocates its energy. A startup team's attention is a limited resource. When a large share of attention is poured into tracking and improving a metric, other important work—like product iteration, customer interviews, team collaboration—often gets squeezed. Choosing to drop a seemingly important metric that actually consumes too many resources is a way of protecting the team's energy.
An Adjustment You Can Make Right Now
Based on these observations and lessons, we recommend that every startup team run a "metric audit" every two weeks. The exercise is very simple—it only requires answering three questions: First, does this metric directly reflect the value users get from our product? Second, if this metric suddenly disappeared, would we lose any important information? Third, is the cost of tracking this metric—including time and attention—proportional to the value it delivers?
If any of the answers during the audit come back unsatisfying, it's time to consider adjusting or dropping that metric. This adjustment doesn't have to wait until the end of the quarter or the next strategy meeting—it can be made immediately. In fact, the earlier you run this kind of audit, the better your odds of avoiding going too far in the wrong direction.
Inside the 12W ecosystem, we continue to see that teams willing to regularly review and adjust their metric frameworks tend to find the development path that fits them faster. Metrics are tools, not goals. Learning to drop the wrong metric at the right time is an important capability on the entrepreneurial journey.
Research by Anders Ericsson, author of Peak, points out that one of the key differences between experts and amateurs is that the former can consistently distinguish between "effective practice" and "surface-level effort." The same principle applies in entrepreneurship: distinguishing "meaningful tracking" from "false busyness" is a fundamental skill every founder has to build. Real efficiency isn't about tracking more metrics—it's about making sure that every number being tracked delivers genuine insight to the team.