The 5Es Framework
A fixed five-phase lens — Entice, Enter, Engage, Exit, Extend — for evaluating an experience and making sure the neglected bookends get designed, not just the core.
Most teams pour everything into the middle of an experience and neglect how it begins and ends. The 5Es exists to stop that.
What it is
A fixed evaluation lens that forces attention onto the phases teams routinely skip.
The 5Es Framework applies five fixed phases to any experience: Entice, Enter, Engage, Exit, and Extend. The phases are always the same — what changes is what you find inside each one. The framework exists to solve a specific and near-universal problem: teams over-invest in the middle of an experience and under-invest in the bookends that begin and end it. The 5Es makes those bookends impossible to skip.
Its design is deliberately structural. Unlike a journey map, which shapes its stages to fit the specific experience being mapped, the 5Es applies the same five lenses every time. That consistency is the point: it prevents the team from creating a map that simply confirms where they already spend their time. Engage will almost always look strong. Entice, Exit, and Extend will almost always reveal neglected territory — and the framework forces you to look at them regardless.
The method was developed in the context of retail experience design and has since been applied across services, digital products, events, hospitality, and member-based organizations. It is not a narrative tool — it does not capture the emotional arc of a single person’s journey. It is an evaluation tool: a structured lens for assessing an experience phase by phase and identifying which phases have been designed and which have been assumed.
The five phases
Click a phase to see what to evaluate in it.
The bar chart shows where teams typically invest their design attention. The phases with amber markers are the bookends teams most often skip. The core is where almost all the attention goes.
When to deploy it
A diagnostic tool for experiences where the middle works and the edges do not.
Use the 5Es when
- →The core experience scores well but retention, return visits, or word-of-mouth are weak — the classic bookend-neglect pattern.
- →You want a fast, structured evaluation of an experience before deciding where to invest design effort.
- →You need a consistent lens that the whole team will apply the same way, regardless of where their instincts lead.
- →You suspect the team is pouring resources into Engage while Entice, Exit, and Extend have never been formally designed at all.
- →You need to evaluate multiple experiences or locations with a consistent benchmark rather than a bespoke journey map each time.
Do not lean on it when
- ×You need a deep narrative of a specific person's emotional journey through a specific experience. Use Journey Mapping, which shapes its stages to the experience and adds an emotion line.
- ×You need to diagnose an operational or backstage failure — why the service breaks rather than what the customer experiences. Use Service Blueprinting.
- ×The experience genuinely has no bookend phases — for instance, a single discrete transaction with no before or after. The 5Es will produce thin or empty phases.
- ×You need primary evidence rather than a structured evaluation. The 5Es organizes what you know; it does not replace going and finding out.
The honest limit: the 5Es tells you which phases are neglected, not why they are. Identifying that Exit is undesigned is a finding; understanding what to do about it requires research. Use the framework to direct attention, then follow that attention with real fieldwork.
How it works
Five moves, in order, with the bookends first.
Scope the experience.
Agree on what counts as the full experience you are evaluating. Where does it start — from the first moment of awareness, or from the moment of arrival? Where does it end — when the person leaves, or months later when they decide whether to return? Defining the edges before you begin prevents the team from unconsciously scoping out the bookends.
Evaluate Entice.
How do people become aware of and motivated to begin the experience? Is the promise clear and honest? Does it set the right expectation for what follows? Does it attract the right people? Teams often have very little evidence here because pre-arrival awareness leaves few measurable signals. Treat that absence of evidence as information.
Evaluate Enter.
What are the first moments like — from the instant of arrival through the beginning of full engagement? Does the opening reduce or increase anxiety? Is the transition smooth and welcoming, or confusing and intimidating? First impressions here color everything that follows, including the perception of Engage, regardless of how good Engage actually is.
Evaluate Engage.
How well is the core value being delivered? This is the phase teams know best and have already invested in most heavily. Evaluate it honestly, but spend proportionally less time here than on the bookends. The 5Es framework asks you to resist the gravitational pull toward the thing you already understand.
Evaluate Exit.
How does the experience conclude and the person leave? Is the ending graceful and intentional, or abrupt and forgotten? The ending disproportionately shapes what people remember — the peak-end effect. An undesigned exit is one of the most reliable causes of good experiences being remembered as mediocre ones.
Evaluate Extend.
What happens after the person leaves to sustain the relationship and earn a return? Is there anything — or does the relationship simply go dark? This is the most commonly neglected phase of all. Most teams have never designed it; they have only assumed it. The absence of an Extend phase is not a neutral state: it is the experience of abandonment.
Best practices
What good looks like — and what prevents it.
When it goes well
- ✓The bookend phases are populated with real evidence — interviews, observation, or logged data — rather than team assumption. The framework only reveals what you have actually looked at.
- ✓The Engage phase is covered quickly and allocated proportionally less workshop time than the bookends, because the team already knows it best.
- ✓The evaluation starts from scoped boundaries that include the earliest pre-arrival moment (Entice) and the latest post-departure moment (Extend).
- ✓Each phase produces a clear verdict: designed deliberately, addressed but not designed, or never touched. The goal is to find the never-touched phases.
- ✓The session produces specific interventions for the weakest bookend phases — concrete things to design or research — not just a finding that the bookends are weak.
The mistakes, and how to avoid them
Spending most of the session on Engage.
The pull toward the familiar is nearly gravitational. Set an explicit time budget per phase before the session begins, and enforce proportionally more time on the bookends. Engage can usually be covered in a fraction of the time because it is already well understood.
Scoping out the bookends at the start.
Teams often define the experience as starting at the front door and ending when the person leaves — accidentally removing Entice and Extend from scope before the evaluation begins. Scope the experience before the session and include the full bookend territory.
Running the 5Es without evidence for the bookends.
A 5Es session built from team knowledge will confirm what the team already believes — which is always that Engage is fine and the bookends are someone else's problem. Populate the bookends with primary evidence first: interviews, observation, or anything that brings the person's actual experience into the room.
Treating “we do not know” as a null finding.
A phase the team has no information about is not a blank — it is evidence of neglect. Mark it clearly. An Extend phase no one can describe is the most important finding of the session, not an absence of finding.
Stopping at the finding.
The 5Es produces a diagnostic. The diagnostic is not the output — specific design or research actions for each neglected phase are. End every session with named next steps for the bookends, not just a summary of which ones are weak.
Logistics
Setting up a session that actually finds the neglected phases.
A 5Es session is a half-day workshop. Its value is proportional to the quality of the evidence that enters the room. Evidence-free 5Es sessions reliably confirm what the team already believes — which is that the bookends are fine. Gather real evidence for the bookend phases before the session begins.
Do the bookend research first
Before the workshop, gather evidence specifically for Entice, Exit, and Extend: talk to people who chose not to come back, observe the arrival and departure moments, or analyze what happens in the days after an experience ends. This evidence is almost never already in the building.
Bring a cross-functional group
Marketing owns Entice. Operations owns Enter and Exit. Customer success owns Extend. None of them typically see the full picture together. Getting them in the same session is half the value — the evaluation surfaces the gaps between teams, not just the gaps in the experience.
Set time budgets per phase before you start
Announce and enforce phase time limits at the start: for example, 20 minutes each on Entice, Enter, Engage, Exit, and Extend. The team will overspend on Engage without explicit time pressure. A timer is not pedantic — it is the mechanism.
Treat silence as a finding
If the team has nothing to say about Exit or Extend — no evidence, no practices, no one responsible — write that down explicitly. “No one owns this phase and we have no evidence for it” is the most important finding of the session. It means the phase has never been designed.
End with specific actions, not summaries
Each bookend phase with a weak or absent verdict needs a named person and a named next step: who will research it, what they will do, and by when. A session that ends with “we need to work on Exit” has not finished. A session that ends with “[name] will observe three exit moments and interview two customers by [date]” has.
AI and this method
AI reinforces the bias the 5Es is designed to correct.
Toggle between modes to see what AI contributes to each phase — and where its confidence fails at exactly the phases that most need attention.
In-depth example
The same studio, evaluated two ways.
Altitude Fitness, a boutique cycling studio with three locations, has excellent class quality and strong retention among regulars — but fewer than 40% of first-time visitors return for a second class. Management has focused on instructors and programming: the Engage phase. The 5Es workshop is commissioned to find out what else is going on. The same studio, evaluated once with a traditional 5Es workshop grounded in primary research, and once with AI providing the analysis.
Scenario
Altitude Fitness — boutique cycling studio, three locations
The studio has excellent retention among riders who make it past their first three classes. The problem is that fewer than 40% of first-time visitors come back for a second class. Management has focused its energy on instructor quality and class programming — the Engage phase. The 5Es workshop is commissioned to find out what is actually driving the drop-off.
ENTICE
PROBLEM FOUNDThe studio’s Instagram is aspirational — serious athletes mid-sprint. First-timers see it and assume the classes are too advanced for them. The promise attracts experienced riders and deters everyone else. Three people in the workshop were almost put off by the feed before they ever booked.
ENTER
PROBLEM FOUNDThe check-in area is unmanned for the first five minutes of arrival. First-timers stand at the door, unsure whether to walk in, where to leave their bag, or whether their bike is set up correctly. Two workshop participants describe feeling embarrassed to ask — so they guessed. One set up her bike wrong and spent the first fifteen minutes in discomfort.
ENGAGE
WELL DESIGNEDInstructors are excellent. Energy is high. The class itself scores consistently well in post-visit surveys. This is where the studio’s investment has gone, and it shows. No significant problems found here.
EXIT
PROBLEM FOUNDWhen the class ends, the instructor immediately leaves to set up the next session. First-timers are left on their bikes with no closing moment — no cool-down ritual, no acknowledgement that they finished. Three participants said the experience “just stopped.” The last impression is awkward and uncelebrated.
EXTEND
NOT DESIGNEDAfter the first visit, nothing happens. No welcome message. No sequence that acknowledges the difficulty of the first class. No community touchpoint between classes. The studio has a strong community for regulars, but first-timers are invisible to it. This is the most neglected phase — it has simply never been designed.
What the workshop found
The drop-off problem is not in the class — it is in everything surrounding it. Four of the five phases had been neglected because the team had never formally looked at them. The workshop identified specific interventions for Enter, Exit, and Extend that cost almost nothing to implement: a greeter for the first five minutes, a 30-second closing acknowledgement by the instructor, and a three-email welcome sequence for first-timers. None of these required new programming or facilities investment.
Where it ends
Where the 5Es hands off to its neighbors.
The 5Es evaluates an experience through five fixed phases. Two neighboring methods extend it in different directions — one into a person’s emotional narrative, one into the operational machine behind the experience.
The 5Es applies five fixed, evenly-weighted phases to any experience: Entice, Enter, Engage, Exit, Extend. The phases are always the same; what changes is what you find in each one. The framework’s purpose is to force attention onto the bookends that teams routinely skip.
Frameworks
Where the 5Es shows up.
The 5Es is primarily a definition and discovery tool — it evaluates and diagnoses before the team invests in a design direction. It maps most naturally to the early stages of frameworks where the question is “which problem are we solving” rather than “how do we solve it.”
Related methods
What to combine with the 5Es.
Sources & further reading
The work behind this method.
The Experience Economy
B. Joseph Pine II and James H. Gilmore (1999)
The foundational argument that designed experiences — not goods or services — are the primary economic offering. The 5Es emerged from this tradition of treating experiences as designable, stageable entities with deliberate structure rather than accidental outcomes.
Outside In: The Power of Putting Customers at the Center of Your Business
Harley Manning and Kerry Bodine (2012)
A rigorous treatment of customer experience as a designed system, with extensive evidence for why experiences are remembered by their peaks and endings rather than their averages. The peak-end effect underlies the 5Es' emphasis on Exit as disproportionately important to what people remember.
This Is Service Design Doing
Marc Stickdorn, Markus Hormess, Adam Lawrence, and Jakob Schneider (2018)
The comprehensive service design toolkit, including the methods that complement the 5Es: journey mapping, service blueprinting, and research approaches for each phase of an experience. The methods in this book and the 5Es are designed to be used together.