Why Talent Isn’t Enough: The 7 Momentum Attributes

Every fitness app on Earth wants to reduce heart attacks. None of them can measure heart attacks.

That gap between what a product wants to do and what it can actually count is where most strategy dashboards quietly fail. The team picks a metric they can track. The aspirational metric they actually care about gets quietly demoted. The measurable proxy on the dashboard becomes the new mission by default. Eighteen months later, the dashboard is green and the original mission is dead.

The fix is a small, technical-sounding distinction that almost nobody draws cleanly. Quantifiable does not mean measurable. Once you separate the two, you can build a chain from the goal you can’t track down to the behavior you can, and stop pretending the two are the same number.

⚡ Speed Run Notes

• Quantifiable means a real number exists in the world. Measurable means you can actually obtain it. Most teams collapse the two and end up tracking what they can see instead of what they care about.
• The Proxy Chain has four levels: Aspirational Top Metric → Measurable Proxy → Desired Actions → Core Drive Design. Each level constrains the one below it.
• The aspirational metric is your compass. The proxy metric is your dashboard. You need both. Keep one without the other and you either drift off-mission or lose the will to ship.
• Motivation itself is never directly measurable. It lives in the black box. What you can measure is the desired actions motivation produces and the proxies that correlate with the outcome you want.
• “Data-driven” without a Proxy Chain is the leading cause of Black Hat metric drift. Teams optimize for what they can see (clicks, sessions, time-on-page) instead of what they meant to deliver.

Table of Contents

Author Credibility: Yu-kai Chou

Yu-kai Chou is an S-Tier Behavioral Designer and the creator of the Octalysis Framework, the gamification design system now applied to products and experiences reaching over 1.5 billion users. His book Actionable Gamification is one of the most-cited works in the field, and he has been ranked the #1 Gamification Guru in the World.

He has advised MrBeast, LEGO, Microsoft, Porsche, Tesla, Stanford, Harvard, and governments including Ukraine on turning behavioral psychology into product mechanics that actually change user behavior.

Verify: Wikipedia · Google Scholar · Wikidata · LinkedIn

Why I’m the one writing this

I designed the Strategy Dashboard as the foundational tool for any serious gamification project. Sixteen years of running Octalysis Level 2 sessions with companies like LEGO, Microsoft, Porsche, and Coca-Cola taught me that the single most expensive mistake organizations make is not in the design phase — it’s in the metric phase, before the design even starts. Pick the wrong metric and the most beautiful design in the world will optimize you off a cliff.

What follows is the lens I now use in the first hour of every consulting engagement. It’s small. It’s almost embarrassingly simple. And it has prevented more wasted product investment than anything else I teach.

Quantifiable Does Not Mean Measurable

Here is the distinction. Hold it carefully because almost everyone collapses it.

A metric is quantifiable if a real, factual number exists in the world. Right now, somewhere, there is a true count of how many heart attacks happened on Earth this week. That number exists. It is quantifiable.

A metric is measurable if you can actually obtain that number for your own decisions. A fitness app cannot. The data does not flow to them. Hospitals don’t share it. Medical records aren’t connected to the wearable. The number is real, but the app cannot put it on a dashboard.

Quantifiable describes the world. Measurable describes your access. They are not the same word, and the difference is where strategy gets built or broken.

I see teams collapse them constantly. They write down “increase customer happiness” and then act surprised when nobody can produce a number for it. Or they go the other way: they write down “DAU” because it’s measurable, then stop asking whether DAU even tracks the thing they wanted in the first place. Both moves end in the same place. The dashboard reports something. The strategy reports nothing.

The Proxy Chain: Four Levels From Aspiration to Action

The fix is to refuse the binary. You do not have to choose between the unmeasurable thing you care about and the measurable thing you can see. You build a chain from one to the other and use both.

The chain has four levels:

Level 1 — The Aspirational Top Metric. The thing you actually want to be true in the world if your product succeeds. Often unmeasurable. That is fine. Its job is to be the compass, not the dashboard. “Reduce heart attacks per week worldwide.” “Help one million people start a creative practice.” “Make commercial real estate transactions more honest.” These are not numbers your team will ever see on a Looker board. They keep the ship pointed.

If a teammate asks, “why are we doing this work?” the aspirational metric is the answer.

Level 2 — The Measurable Proxy. The closest measurable thing that should correlate strongly with the aspirational metric being fulfilled. “Percentage of users completing daily physical activity goals.” “Number of users who post their first creative work in week one.” “Disclosure score on closed transactions.” This is the dashboard you check on Monday. It is not the goal — it is the best signal you can get without a magic wand.

If you fulfill the proxy, the aspirational metric is most likely fulfilled too. That last clause is doing a lot of work, and we’ll come back to it.

Level 3 — The Desired Actions. The specific behaviors a single user has to perform for the proxy to move. Open the app. Log a workout. Hit ten thousand steps. Complete a streak day. Each desired action is concrete enough that an engineer could write the event handler for it.

If the proxy is the dashboard, the desired actions are the buttons that make the dashboard light up.

Level 4 — The Core Drive Design. The motivational architecture that gets users to perform those desired actions repeatedly and willingly. Which of the eight Core Drives are you activating? Are you stacking Core Drive 2 (CD2) (progress) with Core Drive 6 (CD6) (scarcity)? Building Core Drive 5 (CD5) (social influence) into the loop with friend visibility? This is where the actual gamification design work happens, and it is the deepest level of the chain.

The whole point of the four-level structure is that each level constrains the one below it. Your aspirational metric tells you which proxy to pick. The proxy then tells you which desired actions count. From there, the desired actions tell you which Core Drives to design for. Without the chain, your design floats free and you end up shipping motivational mechanics that make people clicky without making them healthier, wealthier, or wiser, or whatever you said you were trying to do.

Note on terminology: In the Octalysis Framework, human motivation is broken down into 8 Core Drives (CDs). We use shorthand like CD2 for Core Drive 2 to refer to these specific motivational levers.

Walking the Chain: The Heart Attack Example

Let’s walk a fitness app through the chain so the structure is concrete.

Aspirational metric. Reduce heart attacks per week worldwide. Real number. Unmeasurable by the app. Keeps everyone on the team aligned on why the product exists. When somebody pitches a new feature, you check it against the aspirational metric: would a world with this feature have fewer heart attacks? If the answer is “no, but it’ll boost session time,” you have just caught a metric drift attempt.

Measurable proxy. Percentage of users completing their daily physical activity goal. The link to heart attacks is robustly supported by exercise-and-cardiovascular research; it isn’t a perfect one-to-one, but a population that hits its activity goal is reliably a healthier population than one that doesn’t. The app can absolutely track this. It’s the dashboard.

Desired actions. A user opens the app at least once today. They log their workout, or the wearable does it for them. They hit ten thousand steps, or whatever the personalized target is. They close the activity ring. Each of these actions, performed at scale, moves the proxy.

Core Drive design. CD2 (progress rings, badges, milestones), CD6 (don’t break the streak, today’s window closes at midnight), CD5 (your friends are also closing their rings). Stack them deliberately, audit for Black Hat overuse, and you have a system that produces the desired actions consistently.

Now the chain is whole. The CEO can defend the work to the board (“we’re trying to reduce heart attacks”). A product manager can pick features against the proxy (“does this lift our daily-goal-completion percentage?”). Designers can choose mechanics against the desired actions (“does this nudge get more streak days?”). Engineers can ship the right event handlers. Every level is doing its job, and nothing is floating.

Motivation Is in the Black Box

Here is a related and important point that the Proxy Chain forces you to confront.

Motivation itself has no measurement device. There is no sensor you can strap to a user that tells you, in real time, how motivated they are. Motivation lives in the black box of the human mind. We can poke at it with surveys, infer it from physiological signals, model it with Octalysis, but we cannot directly measure it.

What we can measure is the output of motivation: the desired actions a motivated person performs. Did they open the app? Did they finish the workout? Did they invite a friend? Those are the visible behaviors that motivation, properly designed for, produces.

This is why the Strategy Dashboard’s Business Metrics column has to come before the Core Drive design column. If you cannot articulate what behaviors you want and how they roll up to a measurable proxy, your motivational architecture is design-without-feedback. It might be brilliant. You will never know.

I’ve watched product teams skip this step a hundred times. They build a beautiful Octalysis chart, ship a feature stack, and then spend three months trying to figure out whether the system is “working” because nobody decided in advance what working would look like. The Proxy Chain forces that decision into the design phase, where it costs nothing to make and saves everything later.

Why Data-Driven Design Drifts Toward Black Hat

One more reason this matters. “Data-driven design” is now table stakes. Every product team is data-driven. The phrase is so universal it has lost meaning.

What “data-driven” actually does, without a Proxy Chain to anchor it, is silently drag your design toward whichever metrics happen to be easy to measure. Clicks. Sessions. Time on page. Scroll depth. Daily active users. These are all measurable. None of them are the thing you care about.

Worse, the easiest metrics to measure tend to correlate with Black Hat motivation: manufactured urgency, manipulated FOMO, attention-traps that drain the user without giving them anything back. A team that optimizes for time-on-page, with no aspirational anchor, will inevitably ship features that hold users hostage. The dashboard goes up. The user gets resentful. And the product wins the quarter while losing the decade.

The Proxy Chain is the structural defense against this drift. Sitting at the top, the aspirational metric is the question every measurable optimization has to answer to: “Yes, this lifts time-on-page, but does it move us toward fewer heart attacks?” If the answer is no, you have caught the drift before it ships. That moment is worth more than any A/B test result.

This is also where the relationship to Yu-kai’s broader Octalysis principle becomes visible: motivation is a limited quantity. Every interaction a user has with your product spends some of their motivation energy. Every scroll, every click, every dialog box withdraws a little. If the experience never replenishes through progress, surprise, social affirmation, or expression — the user runs out of motivation and drops out. A proxy that ignores this is measuring a treadmill that is about to stop. Run it through the chain and the drift becomes visible: rising sessions but falling completion is not a “feature is working” signal. It is a “users are running out of energy” signal.

A Diagnostic for Your Current Dashboard

Try this on your current product or feature. Five questions, in order.

1. What is the aspirational top metric? If you cannot answer this in one sentence without using your product’s name, you don’t have one. You have a product, not a mission. Stop and write it down.

2. Is your current KPI the aspirational metric or a proxy for it? If you cannot answer cleanly, you’ve collapsed the two. The most common form of collapse: a team uses DAU as both compass and dashboard. DAU is fine as a proxy, but it has nothing to say about whether your aspirational mission is being fulfilled. Mistaking it for the goal is how products get optimized into engagement traps.

3. Does your proxy correlate strongly with your aspirational metric? Most proxies are weaker than teams want to admit. “Time on page” is a weak proxy for “user got value.” “Email opens” is a weak proxy for “subscriber is engaged.” Strong proxies are ones where, if a population fulfills the proxy, the aspirational outcome is almost guaranteed. Test the link before you build the dashboard around it.

4. Are your desired actions specifically what would move the proxy? Or are they activities that feel productive but don’t actually roll up? It is shockingly common to find teams measuring proxy A while the design is funneling users toward desired actions that move proxy B.

5. Does your Core Drive design map cleanly to those desired actions? If you’ve stacked CD2 + CD6 to drive a behavior the proxy doesn’t actually need, you have built a beautiful slot machine for a goal nobody wanted. Audit and re-stack.

Most teams that run this diagnostic find at least one broken link. Fixing it is usually a half-day exercise that saves a quarter of wasted engineering work.

Five Ways to Use the Proxy Chain This Quarter

1. Run it backwards on a feature you’re about to ship. Pick the next feature on your roadmap. Trace it: which desired action does it enable, which proxy does that action move, which aspirational metric does that proxy correlate with? If any link is missing, the feature is doing something other than what your strategy claims it’s doing.

2. Add an aspirational column to your team’s KPI doc. If your KPI doc only contains measurable proxies, your team is one quarter of pressure away from optimizing into Black Hat. Inserting the aspirational column above the proxy column is a one-day documentation change that pays for itself the first time someone tries to ship a dark pattern in the name of “the metric.”

3. Use the chain in user research debriefs. When users tell you a feature isn’t working for them, ask: are they failing at the desired action, or is the desired action failing to produce the proxy outcome they expected? Half of “the feature is broken” feedback is actually “the feature works but it’s pointed at the wrong proxy.”

4. Defend against metric weaponization in stakeholder meetings. When an executive asks why a measurable number is flat, the Proxy Chain lets you say: “It’s flat because it’s a proxy. The aspirational metric, which is what we agreed we cared about, is moving in the right direction.” That is a defensible answer. “I don’t know but the dashboard says we’re up” is not.

5. Use it as a hiring filter for product roles. Ask candidates: “Tell me about a metric you tracked, and tell me what it was a proxy for.” A senior product person should be able to answer this in their sleep. A weaker hire will look at you confused, because they have only ever thought at the proxy layer. The Proxy Chain question is a fast read on someone’s strategic depth.

Compass and Dashboard Are Not the Same Thing

If you take one image from this post, take this one. A compass tells you which direction to walk. The dashboard tells you whether you are walking. Confuse the two and you’ll either march into the ocean with a beautiful dashboard, or stand still on a mountain because you can’t see the dashboard from here.

Most teams ship a dashboard and call it a strategy. The teams that build durable products carry both. The aspirational metric stays at the top of every doc, every kickoff, every launch review. Your measurable proxy gets watched daily. Desired actions get shipped weekly. Core Drive design gets refined quarterly. Each level is doing the job that level is for, and none of them is being asked to do a job it can’t.

For the deeper system this lives inside, the canonical reference is the Strategy Dashboard, where the Business Metrics column is one of five that work together to keep a gamification design honest. The full motivational architecture lives in the Octalysis Framework, and the long-form treatment of why Black Hat metric drift is so common is laid out in Actionable Gamification.

Quantifiable does not mean measurable. Build the chain. Carry both.

Frequently Asked Questions

What is the difference between quantifiable and measurable?

Quantifiable means a real, factual number exists somewhere in the world. Measurable means you, specifically, can obtain and use that number for decisions. Heart attacks per week worldwide is quantifiable but not measurable by a fitness app. Daily-goal-completion percentage is both. Most strategy mistakes start by collapsing the two words into one.

What is the Proxy Chain?

The Proxy Chain is a four-level structure that bridges an unmeasurable aspirational metric down to designable user behavior. The levels are: Aspirational Top Metric (compass, often unmeasurable), Measurable Proxy (dashboard, what you actually track), Desired Actions (specific behaviors that move the proxy), and Core Drive Design (motivational architecture that produces those behaviors).

Why can’t I just use the proxy as my goal?

Because proxies drift. Without an aspirational anchor sitting above the proxy, every quarterly pressure to “move the metric” pulls your design toward whatever lifts the proxy fastest, including dark patterns that hurt the underlying mission. The aspirational metric is the structural defense against that drift.

How do I pick a strong proxy?

A strong proxy is one where, if a user population fulfills the proxy, the aspirational metric is almost certainly fulfilled too. Test the correlation explicitly before committing. “Time on page” is a notoriously weak proxy for “user got value.” “Daily activity goal completion” is a strong proxy for “cardiovascular health is improving” because the underlying medical research supports the link.

Can motivation itself be measured?

Not directly. Motivation lives in the black box of the human mind. What you can measure is the output of motivation: the desired actions a motivated user performs and the proxies those actions roll up to. This is why the Strategy Dashboard’s Business Metrics column has to be defined before the Core Drive design column, not after.

WOULD YOU LIKE YU-KAI CHOU TO WORK WITH YOUR ORGANIZATION?