Hero's Journey: Set-up, Conflict, Resolution
The Hero's Journey, as taught here, helps you tell a transformation story as Set-up, Conflict, and Resolution so the audience can see the ordinary world, the ordeal, and the changed return. Joseph Campbell described a longer monomyth. This page does not run that full stage list. It is not a promise…
Framework Card
- Name:
- Hero's Journey
- Goal:
- Tell a transformation story as Set-up, Conflict, and Resolution so the audience can see the ordinary world, the ordeal, and the changed return.
- Flow:
- Set-up → Conflict → Resolution
- Best For:
- Origin stories that skip the struggle; Change narratives that need a human arc; Keynotes that currently read as a feature list
Why it matters
Origin stories often skip the middle. The founder was curious. Then the product existed. Listeners cannot tell what it cost, so they cannot tell what changed. The other failure mode is the opposite: a long complaint with no return, so the room only hears that things were hard.
Change programs have the same hole. Leaders announce the new operating model as if the team had already arrived. People still live in the old world. Without an ordeal and a return, the talk is a slogan.
This three-stage shape is a way to keep both ends honest. It does not make the story more mythic than the facts.
What it is
This page uses three beats:
| Stage | Job |
|---|---|
| Set-up | Ordinary world, who the hero is, what they want, why the familiar state cannot last |
| Conflict | The ordeal that costs something: failed attempts, resistance, a real constraint |
| Resolution | Return changed: new capacity, new rule, or a takeaway the audience can use |
Campbell mapped departure, initiation, and return across many stages. Business teaching often compresses that into three acts. The letters "hero" and "journey" are teaching shorthand. The method is: starting state, costly middle, changed end.
This is not Freytag's seven-beat rise and fall (no required named climax box). It is not Pixar's "Once upon a time / Because of that" chain. It is not StoryBrand, where the customer is the hero and the brand is the guide.
The hero here is the character whose change the story tracks: a person, a team, or an audience stand-in. Do not quietly swap in the company as savior unless that is actually the story.
How it works
A useful pass uses events you can stand behind.
1. Set-up
Name the ordinary world in a few lines. Who wanted what. What made staying put costly enough to move. Do not write a childhood memoir.
2. Conflict
Show the ordeal. Cost can be time, money, trust, or a failed attempt. If nothing was at risk, you do not have Conflict yet. Do not invent a villain.
3. Resolution
Show the changed state. A lesson is allowed if it follows from the ordeal. "We learned a lot" with no new behavior is not Resolution.
Keep one hero. Mixing three protagonists in one journey usually means you have three stories.
How it compares
When another lens fits better, or when you need a complementary view, these frameworks do different jobs. They are not interchangeable labels for the same question.
| Framework | What it helps you see | How it differs from this page |
|---|---|---|
| Freytag's Pyramid | Rise, peak, and fall across seven teaching beats | Dramatic rhythm. This page is three-beat transformation. |
| Pixar Storytelling Formula | Once upon a time / Because of that | Causal sentences, not ordeal-and-return as named stages |
| StoryBrand | Customer as hero, brand as guide | Marketing roles. This page tracks one character's change. |
| Self-Us-Now | Speaker identity, shared identity, present ask | A speech opener, not a full journey |
The Hero's Journey on this page is the lens for ordinary world, ordeal, and changed return. Other methods help when the question is Freytag rhythm, Pixar causality, or StoryBrand roles.
When to Use This Framework
- A brand origin that currently reads as a resume. Dates and logos are present. The struggle is missing or theatrical.
- Change communication that announces the destination only. People need to hear what the crossing cost and what is now true.
- A keynote that is still a feature list. The speaker has a human turn (a failed launch, a team that almost quit) and has not placed it.
Example
A concrete example makes the structure easier to reuse when you are under uncertainty.
Example: A reorg told as a transformation, not a slide of boxes
A VP must explain why a product org moved from feature teams to four outcome squads. The current draft is an org chart.
- Set-up: Feature teams shipped on time and still missed the metric they were hired to move. Owners were unclear at the seam between teams.
- Conflict: The first two quarters of the new squads were slower. Two senior ICs left. A launch slipped. Leadership had to defend the change in public.
- Resolution: Each squad now owns a metric and a backlog. The VP names the rule that stays: no shared "platform team" dumping ground without a named customer.
Implication: Conflict is the slow quarters and the attrition, not a mythic dragon. Resolution is the new rule, not a claim that morale soared.
Example: A founder origin without a fake funding plot
A founder is asked for "the story" at a customer dinner. The real path: they were an ops lead, built an internal tool, other teams copied it, they left to productize it. There was no dramatic investor rejection.
- Set-up: Spreadsheets broke every month-end. The internal tool was a night project.
- Conflict: Support load from other teams collided with the day job. Legal would not let a free internal tool keep spreading. They had to choose stay or leave.
- Resolution: They left, licensed the approach, and the takeaway is "we productized a tool we already knew how to support," not "we were destined."
Implication: Inventing three rejected seed rounds would be a method failure. The ordeal is the collision of day job and demand, which is enough.
Takeaway
What this Hero's Journey can help with
- Ordering a change story so ordinary world, ordeal, and return are all visible
- Stopping a highlight reel that skips cost
- Stopping a complaint that never returns
- Keeping one protagonist in view
What this Hero's Journey cannot replace
- Freytag's Pyramid. Seven-beat dramatic rhythm with a named climax. Different grain.
- Pixar Storytelling Formula. Causal sentence chain. Different scaffold.
- StoryBrand. Customer as hero, brand as guide. Different roles.
- Campbell's full monomyth. This page is a three-beat teaching model.
- Missing facts. Invented adversity is not a journey. It is a fabrication.
Honest scope: this is a three-stage transformation story. It should not be sold as inspiration.
Frequently asked questions
No. Campbell's monomyth is longer. This page compresses the idea into Set-up, Conflict, and Resolution for talks and change stories.
The person or group whose transformation you are telling. In StoryBrand the customer is the hero and the brand is the guide. Do not mix those jobs by accident.
It has to cost something. A mild inconvenience is usually Set-up, not Conflict.
Only if you are actually telling a transformation. A feature walkthrough does not become a journey by adding the word hero.
No. That is a method failure. Shorten Conflict or pick a true ordeal from the case.