Persona Fanout Journey
One query. Different buyers. Different questions.
Start with a broad request, add what the buyer actually said, and watch it fan out by scenario and by every stage of the journey, from first intent to living with the thing afterwards. It works for any purchase. Every generated question can explain which inputs produced it and how to check it before anyone writes to it.
3 ready-made domains · 4 scenarios each · 5 stages · 80 questions per domain · illustrative hypotheses, not measured demand
4 scenarios · 5 stages · 80 questions · 0 gaps marked
Follow the lit path. Pick a scenario, then a stage. Open a question to see why it exists.4 shown / 80 total
01 Starting query
Starting intent
I want to buy a car
One broad request. Many possible contexts.
02 Clarify context
What do we need to know?
Explicit answers, not inferred traits. Click one to see what it changes, right here.
03 Persona scenarios
04 Buying stage
05 Fan-out questions
Illustrative hypotheses, not measured demand
Family-fit buyer → Compare → 4 questionsStated need: rear-facing child-seat space and room for a stroller
What this is: a planning model built from explicit, editable inputs. What it is not: measured search demand, observed customer behaviour, or an AI engine's internal queries. Edits save only in this browser.
The whole journey, not just the transaction
Most journey models stop at the purchase, which is why most content does too. The fifth stage is where renewal, churn, support demand and the next purchase are decided, and it has the least competition for the answers. The journey also loops: an ownership question is often the next discovery.
| Stage | Goal | Question types (P376) | Formats that tend to answer them | How to validate |
|---|---|---|---|---|
| 01Discover | Understand the need | Definition · Requirements · Price · How-to | Needs checklist · Requirements guide · Budget explainer · Getting-started guide | Validate with customer interviews and first-party research questions. |
| 02Explore | Build a shortlist | Shortlist · Availability · Price · How-to | Shortlist tool · Where-to-try guide · Price-band guide · Category guide | Validate against your own query logs, site search and customer interviews. |
| 03Compare | Evaluate trade-offs | Comparison · Price · Requirements · Definition | Comparison page · Total-cost worksheet · Evidence checklist · Trade-off guide | Validate with comparison questions from customer research and sales conversations. |
| 04Decide | Resolve buying friction | Process · Price · Availability · Troubleshooting | Pre-purchase checklist · Complete-cost breakdown · Availability and terms page · Risk checklist | Validate with the questions sales and support hear in the final week before purchase. |
| 05Own | Use, maintain, renew or replace | How-to · Troubleshooting · Process · Price | Setup guide · Troubleshooting guide · Ownership tracker · Renew-or-replace guide | Validate with support tickets, onboarding drop-off and renewal conversations. |
What the tool asks before it fans out
Six explicit inputs, the same for any purchase. Each one is an answer a person gives, never a trait read off a demographic, and each carries a note on what it may not imply.
- Budget cap
- A cap the buyer states. It does not establish income or what they can afford.
- Primary need
- The one thing the purchase must do. The evaluation criterion everything else serves.
- Hard constraint
- A must-have or a must-not, written as a thing rather than a sentence. Narrows the option set before comparison starts.
- Timing
- How soon, as a time. Changes which stage the buyer is really in.
- Location
- Only used where an answer is local: where to see, try or buy.
- Experience
- Context, not a preference. It changes what needs explaining, never what they want.
Worked example: family-fit buyer, buying a car
Starting query “I want to buy a car”. Stated need: rear-facing child-seat space and room for a stroller. Budget cap: $55,000. Constraint: three rows or a very large second row. Timing: within 3 months. Every question below is generated from those inputs and nothing else.
01Discover
Understand the need
- What does a car have to do well to deliver rear-facing child-seat space and room for a stroller? · Needs checklist
- Given three rows or a very large second row, which car requirements are essential and which are only nice to have? · Requirements guide
- Beyond the headline price, what does $55,000 for a car need to cover to get rear-facing child-seat space and room for a stroller? · Budget explainer
- How should I start researching a car when three rows or a very large second row is non-negotiable? · Getting-started guide
02Explore
Build a shortlist
- Which car options are worth shortlisting for rear-facing child-seat space and room for a stroller? · Shortlist tool
- Where in my area can I see or try car options, given three rows or a very large second row? · Where-to-try guide
- Which car options fit within $55,000 without giving up rear-facing child-seat space and room for a stroller? · Price-band guide
- How do I tell car options apart when three rows or a very large second row is what matters most? · Category guide
03Compare
Evaluate trade-offs
- How do my shortlisted car options compare on rear-facing child-seat space and room for a stroller? · Comparison page
- How do costs over time compare across the shortlist against $55,000, given three rows or a very large second row? · Total-cost worksheet
- What evidence should I request to confirm three rows or a very large second row for each car option? · Evidence checklist
- Which trade-offs between car options actually affect rear-facing child-seat space and room for a stroller, and which are noise? · Trade-off guide
04Decide
Resolve buying friction
- What must I confirm before committing to a car, given three rows or a very large second row? · Pre-purchase checklist
- What is the complete cost of the car I have chosen, relative to $55,000, once everything needed for rear-facing child-seat space and room for a stroller is included? · Complete-cost breakdown
- What do I need to confirm to complete the purchase within 3 months, starting with three rows or a very large second row? · Availability and terms page
- What could go wrong after buying this car for rear-facing child-seat space and room for a stroller, and what protects me? · Risk checklist
05Own
Use, maintain, renew or replace
- How should I set up my car so I get rear-facing child-seat space and room for a stroller from day one? · Setup guide
- What usually gets in the way of rear-facing child-seat space and room for a stroller once I own the car, and how do I fix it? · Troubleshooting guide
- What should I track to know the car still holds up given three rows or a very large second row? · Ownership tracker
- What should trigger replacing this car: rear-facing child-seat space and room for a stroller no longer met, or costs beyond $55,000? · Renew-or-replace guide
Questions people ask about this tool
- What does the Persona Fanout Journey do?
- It takes one broad starting query, asks what would need to be known before it could be answered, and fans it out into persona scenarios and buying stages. Each scenario at each stage produces four questions of different types, following the framework's P376 question types, and every question shows which explicit inputs produced it, what content format tends to answer it, and how to validate it. In the matrix you mark each question have or gap and export the gaps.
- Does it work for anything other than cars?
- Yes. The templates are written against inputs any purchase has, a budget cap, a primary need, a hard constraint, timing, location and experience, rather than against a domain. Buying a car, a phone and choosing a phone plan ship as presets, and the product label can be set to anything.
- Are these real search queries?
- No. They are illustrative hypotheses generated from templates and the scenario's stated inputs. Nothing here is measured search demand, observed customer behaviour or an AI engine's internal queries. Validate them against your own query logs, site search and customer conversations before writing to them.
- Why does experience not change the question?
- Experience is kept as context, the way age was in the original demo: it changes what needs explaining, never what someone wants. A first-time buyer and an experienced one with the same budget and need get the same question. Inferring a preference from a trait like that is how personas become fiction.
- How is this different from the Audience Personas tool?
- Audience Personas is built only on published research and grades every trait measured, derived or inferred against a named study. This is a planning model: its scenarios are explicit inputs a team types in, not survey results. The two are linked and deliberately kept apart.
Related
- Persona Builder: compose a persona from the framework and open it here
- Audience Personas: build any audience and see where it is, graded by evidence
- Every figure and source behind the measured personas
- The brightonSEO talk this method comes from
- A worked persona, graded trait by trait
Last updated 2026-09-24.