
How Do You Design Epic Meaning Into a Meaningless Product?
An Octalysis Prime member asked me the hardest question about Core Drive 1 I’ve ever fielded.
“Yu-kai, how do you add Epic Meaning & Calling to selling your soul for money?”
He wasn’t joking. He was running a blockchain reseller program — a pure Core Drive 4 (Ownership & Possession), profit-driven offer. Nothing inherent about “mission.” Nothing to pretend was noble. He wanted to know whether CD1 was still designable, or whether he had to fake it.
My answer surprised him. Because designing Epic Meaning into a product that has none isn’t only possible. It is the entire discipline of Core Drive 1, and the process is cleaner and more repeatable than most people expect.
Speed Run Notes
- CD1 (Epic Meaning & Calling) is not a feature you find in your product. It is a feature you design into your product. The same way gamification makes boring work engaging, CD1 design makes a meaningless offer meaningful.
- The difference between weak CD1 and strong CD1 is whether the narrative shows up in your copy or in your game loop. Copy is claimed. Loops are structural.
- Every CD1 design starts with picking a universal theme (freedom, hope, empowerment, love, faith, justice) and building a bridge narrative from your product to that theme.
- The Chicago tunnel workers, in brutal, invisible, and lethal work, built CD1 for themselves with one sentence. If they can do it, your SaaS tool can.
- When your CD1 lives only in your tagline, you have marketing. When it lives in your mechanics, rituals, and feedback messages, you have design. Only one of those survives contact with a sophisticated user.
How to read the shorthand: CD1 = Core Drive 1 (Epic Meaning & Calling) in my Octalysis Framework. When I write CD2, CD4, etc. below, I mean Core Drives 2, 4, etc. — the eight core drives behind every behavior decision. Here is the full map if you want the whole framework before reading this piece.
Table of Contents
- The Question That Broke the CD1 Room
- Why Claiming Meaning and Designing Meaning Are Opposite Skills
- Step 1: Pick Your CD1 Theme (Not the Obvious One)
- Step 2: Build the Bridge Narrative
- Step 3: Bake CD1 Into the Game Loop (the Power Move)
- Step 4: Ship Feedback That Amplifies the Mission
- The Chicago Tunnel Workers Proof
- The Two Axes Behind Every CD1 Design
- The Brands That Already Proved This
- The CD1 Audit: Seven Questions
- What This Process Unlocks
About Yu-kai Chou
Why I’m the one writing this.

I created the Octalysis Framework in 2012, and I’ve spent the years since watching teams at LEGO, Microsoft, Porsche, Google, the Ukrainian government, and MrBeast’s ops crew try to implement Core Drive 1. I’ve also watched ten times that number of teams decide Core Drive 1 (Epic Meaning & Calling) “doesn’t apply to our product” and move on. They were wrong. Every time.
This piece is the step-by-step I wish existed in 2013. It came out of a live Octalysis Prime session where someone asked the most cynical version of the CD1 question possible — and the answer reframed the entire design problem for the whole room.
You can use this process on anything: a loyalty program, a subscription tool, a tax filing app, a crypto reseller, even the Chicago tunnel work. The process does not change. Only the bridge narrative does.
The Question That Broke the CD1 Room
My answer to the Octalysis Prime member was one sentence.
“Just like gamification makes non-engaging things engaging, Core Drive 1 (Epic Meaning & Calling) design makes meaningless things meaningful. That’s the whole point.”
This is the part most people miss. CD1 is not a diagnosis (“your product has meaning or it doesn’t”). It is a design discipline (“you construct meaning into the product”).
You don’t wait for the meaning fairy to bless your offering. You build the bridge yourself.
Apple didn’t discover it was selling rebellion. Steve Jobs decided Apple was selling rebellion and then built every ritual, every keynote, and every campaign around that narrative until it became self-fulfilling. “Think Different” was not descriptive. It was prescriptive. It told the company what to become.
The blockchain reseller can do the same thing. The crypto tool can do the same thing. Your B2B SaaS tool sitting on your roadmap right now can do the same thing. None of them have CD1 by default. All of them can have CD1 by design.
Why Claiming Meaning and Designing Meaning Are Opposite Skills
There’s a specific failure mode I see constantly: founders read about Epic Meaning & Calling, get excited, and rewrite their About page to say “We inspire hope.”
That is not Core Drive 1 (Epic Meaning & Calling) design. That is CD1 claiming. And they are opposite skills.
Claiming CD1 makes you sound like a mission-washed startup. Designing CD1 makes your users feel like they are doing something bigger than themselves every time they engage with your product.
Here’s the test I use on every client engagement.
First. If you deleted every sentence in your product that asserts meaning (“we help people,” “our mission is,” “together we…”), would CD1 still show up anywhere?
Second. Does a user encounter an activity, result, or feedback message that makes them feel they just contributed to something bigger?
Third. Would a stranger, watching a user interact with your product silently for ten minutes, detect the mission without being told what the mission is?
If the answer to all three is no, you have no CD1 design. You have CD1 copy. And copy is the weakest possible layer to put Core Drive 1 on.
The reason is simple. Copy is noise. Every product claims a mission now. When everyone claims a mission, the claim itself stops transmitting information. But when your product’s mechanics enact the mission, when the feedback loop makes the user witness their own contribution, CD1 becomes undeniable, because it’s being proven in real time, by the user’s own experience.
This is the structural principle behind every CD1 design decision that follows.
Step 1: Pick Your CD1 Theme (Not the Obvious One)
Core Drive 1 (Epic Meaning & Calling) themes are the universal human values that can anchor your bridge narrative. The six that work for almost any product:
- Freedom: financial, personal, data, time
- Hope: a better future against bad odds
- Empowerment: independence, self-authorship, capability
- Love and Connection: bringing people together
- Faith: belief in something bigger, purpose beyond proof
- Justice: righting a wrong, leveling an unfair playing field
Here’s the move most founders get wrong. They pick the obvious theme for their category and stop there.
A fintech app picks “financial freedom.” A meditation app picks “inner peace.” A project management tool picks “productivity.” Safe, predictable, and exactly why they can’t differentiate on CD1 — because six other products in the same category picked the same theme.
The art is picking a theme that isn’t obvious for your category but becomes obvious once you explain the bridge.
Nike sells athletic shoes. Everyone in that category picks “performance” or “achievement.” Nike picked “no excuses” — a theme from the moral and discipline space, not the athletic space. Once you hear “Just Do It,” the bridge collapses instantly: the shoes are the permission slip to stop making excuses. Now the shoes aren’t shoes. They’re a commitment device.
Avon sells cosmetics. Everyone in that category picks “beauty” or “self-confidence.” Avon picked “empowerment” — specifically, financial empowerment for women who couldn’t otherwise earn. Cosmetics weren’t cosmetics. They were a ladder. A mother who couldn’t finish college could still run a network and feed her kids. That is CD1 that a L’Oréal lipstick campaign can’t compete with, because L’Oréal is still playing in the category’s default theme.
When you’re picking your CD1 theme, don’t ask “what feels right for my category?” Ask “what theme would make me the only player in my category working on that mission?” The answer is almost always one step off-category. One bridge narrative away.
Step 2: Build the Bridge Narrative

A theme alone is a word. A bridge narrative is a paragraph that makes the theme click for your specific product.
This is the step where the design work actually happens. You’re writing one paragraph that takes your literal offering and shows, in plain language, why it connects to the universal human value you picked in Step 1.
Back to the crypto reseller. Here was the bridge we worked out in the Octalysis Prime session in real time:
“Financial freedom with all your data owned and controlled by questionable entities is not true freedom. It’s money made through slavery. We help you obtain financial freedom while having full control of all your data — achieving true freedom.”
Look at what this paragraph does in three sentences.
Sentence 1 attacks the default mission of the whole category (“financial freedom”) as insufficient. It creates a category-level problem the reader didn’t know they had.
Sentence 2 names the shadow side of the default mission. The language is deliberately sharp. “Slavery” is not a word you drop casually. It makes the gap feel urgent.
Sentence 3 gives the upgraded mission that repositions the product from “another crypto reseller” to “the one that delivers real freedom.” The product didn’t change. The bridge changed. And the bridge is what the user feels.
The bridge narrative is not marketing copy. It is the foundational document you’ll use to make every downstream design decision, from onboarding screens to milestone celebrations. If the bridge is weak, every mechanic built on it will be weak. So this paragraph deserves more iteration than most teams give it. I usually ask clients to rewrite theirs at least five times before we move to Step 3.
Step 3: Bake CD1 Into the Game Loop (the Power Move)
This is the step that separates weak Core Drive 1 (Epic Meaning & Calling) from strong CD1, and it’s where most teams stop short.
Weak CD1 puts the mission in the communication layer: homepage, tagline, newsletter footer.
Strong CD1 puts the mission in the mechanics layer. The user’s actions, inside the product, produce outcomes aligned with the mission.
One example to lock this in. Imagine a community platform that picked “hope” as its CD1 theme, with a bridge narrative about giving people who feel stuck a sense that a better future is possible.
Weak design: the homepage headline reads “A community that inspires hope.” A banner under the hero section says “Every day, our members lift each other up.” An email footer signs off “With hope, the team.”
Strong design: every time a member posts a story about how they got unstuck, the platform auto-generates a shareable card showing how many other members read their story and marked it as helpful. The member doesn’t just hear the platform is hopeful. They see themselves being a source of hope for strangers. Their post is hope made visible. The mechanic produces the mission.
In the strong version, if the team deleted the word “hope” from every piece of copy on the site, CD1 would still be screaming at you through the feedback loop. In the weak version, if you delete the word “hope,” the mission disappears with it.
For the crypto reseller, the parallel move is to design a dashboard where the user can see which specific pieces of their financial footprint are controlled by them versus still controlled by custodial entities. Every transaction they reclaim from a middleman is logged as a “freedom milestone.” The dashboard is not telling them they bought “true freedom.” It is showing them earning it, transaction by transaction.
When you bake CD1 into the game loop, the mission stops being a claim. It becomes a property of the system. A claim is something the user has to believe. A property is something they observe. Observation beats belief every time.
Step 4: Ship Feedback That Amplifies the Mission
Once the loop carries Core Drive 1 (Epic Meaning & Calling), you want the feedback layer to keep pointing at it. This is the final compound effect.
The four Octalysis phases, Discovery, Onboarding, Scaffolding, and Endgame, are all places where one mission-aligned feedback line does ten times the work of a clever copy line.
Discovery phase (first impression). A single line that positions the category problem, not the product feature. “Most fitness apps measure activity. We measure the moments you chose discipline over excuse.” The tagline already installs the “no excuses” theme before the user has tried anything.
Onboarding. A welcome sequence that asks the user to declare which version of themselves they are trying to become, and mirrors that declaration back to them in every subsequent interaction. The user now has their own stake in the mission, not the product’s stake.
Scaffolding (ongoing engagement). Mission-aligned milestones. Not “You completed 10 workouts” but “You chose the hard path 10 times this month.” Same data point. Different CD1 signal.
Endgame. Community-level mission metrics. “This month, the whole community chose discipline over excuse 340,000 times.” The user is now contributing to a collective result that feels bigger than them.
None of this requires a product pivot. It requires re-labeling, re-framing, and re-sequencing what the user already sees. That is what makes CD1 one of the highest-leverage Core Drives in the whole framework. The cost of upgrading it is cheap. The impact on long-term retention and word-of-mouth is enormous.
One warning. Every CD1 feedback line has to be earned. If your onboarding says the user is “choosing discipline over excuse” but the workouts are trivial and skippable, the user will feel manipulated and bounce harder than if you’d said nothing. CD1 is the most devastating Core Drive when it backfires. The mission has to track the reality. The reality has to track the mission. Otherwise you are running a shallow mission-washing play, and sophisticated users will catch you in the first session.
The Chicago Tunnel Workers Proof

Every time I teach this process, someone in the room pushes back.
“Yu-kai, fine, some products can design Core Drive 1 (Epic Meaning & Calling). But my product is actually boring. There’s nothing to build a bridge to. My work is meaningless.”
I tell them about the Chicago tunnel workers.
Under the city of Chicago, there’s an enormous tunnel system. Building and maintaining it requires people to go underground for months at a time, in dangerous conditions, with incident rates that have taken lives. In one orientation class of twelve workers, five died over the next several years of service. The work is physically brutal. The pay is decent, not great. And the public does not think about it at all. Most Chicagoans do not even know the tunnels exist.
By any conventional reading, it is the definition of meaningless labor. Invisible, punishing, replaceable.
Yet surviving workers I’ve spoken with speak about the job with something close to reverence. One said it this way: “We’re under the whole city, improving the lives of people above us, and they don’t even know we’re here.”
Look at what is happening in that sentence. The anonymity of the work isn’t a cost. It is the source of the meaning. Like Batman. Like the ending of The Dark Knight where Gotham never learns who saved them. The invisibility adds to the sacrifice, and the sacrifice adds to the dignity. These workers designed a bridge narrative for themselves out of the most unpromising material available. Hidden labor became heroic labor. And the narrative worked. They held the job for years and turned a lethal profession into a source of pride.
The Chicago tunnel workers are the final proof of the CD1 principle. There is no product, no job, no offering so mundane that CD1 cannot be designed for it. The design question is never “is there meaning here?” It is “what theme and bridge will make the meaning impossible to miss?”
If men who literally dug holes for a city that ignored them could build Epic Meaning out of a hard hat and a grave statistic, your SaaS tool can do it too.
The Two Axes Behind Every CD1 Design
One layer beneath the four steps, every Core Drive 1 (Epic Meaning & Calling) design sits at a coordinate on two axes. I teach this mental model in Octalysis Prime, and once you see it, the brand examples in the next section snap into place.
Axis 1: Real vs. Fictional. Real CD1 changes something in the world. Buy a pair of TOMS, a pair gets donated. Use Waze, your data updates the map for every other driver behind you. Fictional CD1 lives in a story. Trade Samurai turns forex into a quest where the trader balances the forces of greed and fear. Pokémon Go lets you defend a fictional gym on a real street corner. Both work. Real is harder to build but cheaper to defend. Fictional is faster to deploy but only holds if the storytelling is good enough.
Axis 2: Existing vs. Inspired. Existing CD1 is already structurally true of the product: the meaning is there before the marketing. Waze’s user-generated routing genuinely helps every other driver, with or without the tagline. Inspired CD1 is meaning the team designed and named, where none was structurally present before. Apple’s “rebellion” was inspired. Avon’s “any mother can become financially independent” started inspired and became existing once enough women were actually doing it. Most strong CD1 starts inspired and becomes existing as the user base catches up to the narrative.
Plot any product on the 2×2 and you can read its CD1 strategy off the grid. Waze sits firmly in Real + Existing, where it almost designs itself. Trade Samurai sits in Fictional + Inspired: pure storytelling layer. Apple sits in Real + Inspired — a manufactured rebellion that became real once enough rebels actually showed up. The blockchain reseller from the opening question? Begins life in Fictional + Inspired and earns the right to migrate toward Real + Existing only when the dashboard actually delivers on the freedom claim.
One more reinforcement most teams miss. CD1 is only as strong as the team’s belief in it, and belief is judged by sacrificial decisions. When LEGO had to choose between selling more Star Wars kits (their biggest revenue line) and keeping the brand’s creative-play mission credible, they brought in outside design help to fix the problem. That kind of move is the cheapest CD1 marketing money can buy, and the most expensive to fake. If your leadership won’t make a sacrificial decision in CD1’s name, the user will smell it within three sessions.
The Brands That Already Proved This
Here are four case studies I use in Octalysis workshops. Each one started with a mundane product category, picked an off-category theme, and designed a bridge narrative so well that the mission now carries the brand.
| Brand | Category Default | Core Drive 1 (Epic Meaning & Calling) Theme Picked | Bridge Narrative |
|---|---|---|---|
| Apple | Computing hardware | Rebellion / Individuality | “Think Different.” Tools for misfits, heretics, and round-peg-in-square-hole thinkers changing the world. |
| Nike | Athletic apparel | No Excuses | “Just Do It.” Belief in sacrifice, discipline, and total commitment regardless of circumstance. |
| Avon | Cosmetics | Financial Empowerment | Any woman can become financially independent through the network. The product is a ladder, not a lipstick. |
| CaixaBank | Retail lending | Dream Enablement | “We enable people’s dreams by allowing them to secure the things that change their lives.” Loans aren’t debt. They’re dream-unlocks. |
| Patagonia | Outdoor apparel | Environmental Stewardship | “We’re in business to save our home planet.” The jacket isn’t a jacket. It’s a vote — repaired, resold, and routed through 1% for the Planet to active environmental work. |
That last row is the 2020s extension of the same move. Patagonia took a category whose default theme was “adventure” or “performance” and walked one step out into environmental stewardship. The Worn Wear repair program, the 1% for the Planet pledge, and the 2022 ownership transfer to a non-profit trust mean the mission isn’t claimed in copy. It’s executed in the company’s mechanics. Same move as Avon. Same move as Nike. New decade. Same discipline.
Notice the pattern across all five. None of them picked the default theme for their category. Computing didn’t become “productivity.” Athletic apparel didn’t become “performance.” Cosmetics didn’t become “beauty.” Retail lending didn’t become “financial access.” Outdoor apparel didn’t become “performance.” Every single one jumped the category and picked a theme from an adjacent space, then built a bridge back. That is the move. That is what off-category theme selection looks like in practice.
If your theme sounds like what every other player in your space is already saying, you haven’t finished Step 1.
The CD1 Audit: Seven Questions
If you want to pressure-test your current Core Drive 1 (Epic Meaning & Calling) design, run this audit. I use it with clients during the first hour of every engagement. It exposes which companies have CD1 and which companies have copy.
- What is your CD1 theme? Can you name it in one word? (Freedom, hope, empowerment, love, faith, justice, or another.)
- Is that theme the default for your category, or did you pick an off-category theme and build a bridge back?
- What is your bridge narrative in one paragraph? Does it attack the category default and position your offer as the upgrade?
- If you deleted every mission claim from your website and product, would a stranger still detect the mission from the mechanics alone?
- Name one feature where the user’s action, inside the product, produces the mission as an observable outcome.
- Name one milestone feedback line in your current product that reinforces the CD1 theme rather than the task completion. If you can’t, you are on the claiming layer, not the design layer.
- What is the worst-case version of your mission backfiring on you if the reality does not keep up? Are you comfortable with that risk?
Most products fail the audit at question 4. That is useful. It tells you the specific gap between where your CD1 lives today and where it needs to live to do the work.
What This Process Unlocks
When a product has real Core Drive 1 (Epic Meaning & Calling) design, not just claimed CD1, three things change.
User retention goes up because the user is no longer loyal to a tool. They are loyal to a mission, and the tool happens to be the fastest way to be part of the mission.
Word-of-mouth goes up because users who are part of a mission recruit. Users who are loyal to a tool do not. Nobody forwards a SaaS invoice to their friends. They forward a reason to join a cause.
Pricing power goes up because mission-aligned users tolerate higher prices. The price isn’t a fee for a feature. It’s the membership dues for the club that cares about the thing they care about. Apple’s price premium over commodity PCs isn’t a feature gap. It is a CD1 premium.
And all of this is available to any product, at any stage, in any category. The only thing standing between most products and a real CD1 design is the founder deciding “our product doesn’t have a mission” and stopping there. The Chicago tunnel workers didn’t stop there. Avon didn’t. Nike didn’t. You don’t have to either.
If you want the deeper framework that sits behind all of this, the Octalysis Framework maps every motivational driver your product is activating or failing to activate, not just CD1. Most teams find they’re leaning on the same three Core Drives and leaving five on the table. That pattern shows up as flat engagement no matter how much copy they write. The full framework, plus the design process for each Core Drive, is in my book Actionable Gamification. Start there if you want to run this audit across all eight drives instead of just one. And if you’re trying to design a life that has the same CD1 depth we’re asking your products to have, 10,000 Hours of Play applies the same process to your career and personal game.
Your turn.
What product are you going to run the Step 1 through Step 4 process on this week? Pick one. Work the four steps in order. Write the bridge paragraph five times before you accept it. Then tell me what you found. Drop it in the comments below, or send it to me on LinkedIn.
