In Week 3 of 12W, I dropped a KPI (a new perspective)

Starting with the DAU 70% Data

At the Week 3 WAM meeting, the team reviewed the past 21 days of user engagement data, and an unsettling pattern emerged: the product's DAU/MAU ratio (Daily Active Users as a proportion of Monthly Active Users) sat at around 0.7, which on the surface suggested a highly sticky user base. However, drilling into the weekly retention curves revealed that 30% of new users never returned after their first week, and another 40% of "active users" only opened the app 2–3 times per month. The DAU number was propped up by a small group of power users, masking the fact that the majority of users were quietly churning.

Why We Picked the Wrong KPI from the Start

Choosing DAU as the core metric isn't an isolated case. According to Startup Genome's tracking report of over 3,200 startups (2022), roughly 68% of early-stage teams adopt Daily Active Users as their sole growth metric in their first quarter, without segmenting by product usage frequency or user lifecycle. The root of this bias: DAU is an intuitive, easy-to-narrate number — perfect for showing investors and partners something that "looks good."

But the way a product delivers core value determines what actually counts as a meaningful metric. For the product in this case, users only need to engage once a week to complete their core task. That means WAU (Weekly Active Users) not only maps more closely to the real usage pattern, it also reflects the product's cyclical value more honestly — without being diluted by power-user behavior. Staring at DAU led the team to pour resources into the wrong goal: boosting "daily opens," while the retention funnel that actually needed work got ignored.

Three Specific Lessons

Lesson one: KPI selection should start with confirming the frequency at which your product delivers value — not by copying market convention. Facebook uses DAU as its North Star because its core value is "continuous connection" — multiple uses per day is inherent to the product. But for a task-oriented utility, users engaging once a week is normal behavior. Measuring different products with the same yardstick is like using a thermometer to measure weight — no matter how good the number looks, it means nothing.

Lesson two: A metric's surface stability often masks structural problems. When DAU stays high but WAU growth stalls or declines, it means the product is riding on a small group of super users rather than continuously attracting new users to build scale. This structure doesn't reveal a crisis in the short to medium term, but the moment those super users churn, growth collapses off a cliff.

Lesson three, and the hardest one: dropping a metric the team has collectively signed off on requires enough data to make the case — and the emotional willingness to face the sunk-cost feeling of "all that work for nothing." Research shows that once a metric has been in place for a while, even when the data clearly shows it's failing, managers on average need an extra 2–3 weeks before officially announcing a switch — lagging far behind where the analysis points (Harvard Business Review, 2021, "Why Leaders Struggle to Abandon Failing Metrics").

Adjustments You Can Implement Right Now

The next step is concrete: set WAU as the primary tracking metric while keeping DAU as a supporting reference. This change doesn't require tearing down the existing data infrastructure — you just need to put WAU growth rate before DAU in the daily standup reporting order. Once WAU becomes the first number the team sees each day, resource allocation priorities naturally shift — from figuring out how to get users to "open daily" toward thinking about "how to make sure they remember to come back each week."

"The value of a metric isn't in how easy it is to measure — it's in whether it drives the right behavior. When you find yourself working hard to hit a number but have forgotten to ask what that number actually means, it's time to re-examine your North Star."