ENTREPRENEURSHIPWeeks to result

The Persona and Full Life Cycle Use Case

Transform an abstract target market into a concrete, real person whose prioritized needs and complete product journey drive every decision your team makes.

Problem it solves

business growth stalls

Best for

Founding teams who need to align on exactly who their customer is and how the product fits into that customer's real life and workflow

Not ideal for

Teams that already have extensive customer data and established product-market fit and are optimizing rather than discovering

Overview

Why this framework exists

This framework moves from the general End User Profile to a specific, real individual — the Persona — who becomes the definitive reference point for all product and business decisions. Unlike marketing composites, the Persona is a real person: someone you have met, interviewed, and observed in their actual environment. The framework then extends into a Full Life Cycle Use Case that maps the complete journey from the moment the Persona recognizes a need, through discovery, evaluation, acquisition, installation, daily use, value realization, payment, support, and repeat purchase or word of mouth. Together, the Persona and Use Case eliminate the guesswork that kills startups by replacing internal debate with observable, testable facts about one specific human being and their real-world context.

Core principles

6 total
  1. The Persona should be a real person, not a composite — there is only one right answer to any question about what this specific person wants
  2. The Persona's Purchasing Criteria in Prioritized Order is the most critical piece of information — it dictates every product and positioning decision
  3. You cannot believe everything the end user tells you — validate what they say by observing their actual behavior
  4. The Full Life Cycle Use Case must be seen through the customer's eyes, not the entrepreneur's
  5. Everyone on the team must be involved in creating the Persona to ensure alignment and shared understanding
  6. The Persona determines what to do and equally important, what not to do

Steps

5 steps
  1. Build the End User Profile
    Create a demographic and psychographic description of the typical end user in your beachhead market. Include gender, age range, income, location, motivations, fears, media habits, buying reasons, and what makes them identifiable. This provides the criteria for counting end users and calculating TAM.
    Pro tipLook beyond demographics to context and personality. Understanding that your target industrial designer sees themselves as an artist, not a businessperson, and wears all black with body piercings tells you more about product positioning than knowing their age range.
    WarningA profile that spans too wide a demographic (like 'males and females aged 17-40') provides no actionable focus. If your profile could describe vastly different people, you need to segment further.
  2. Choose and Profile the Persona
    Select one real end user from one potential customer who best exemplifies your End User Profile. Prepare a detailed fact sheet with their real name, photograph, life history, job details, specific salary, company context, and personality. Interview them to fill gaps. List their Purchasing Criteria in Prioritized Order — the thing that keeps them awake at night.
    Pro tipGo beyond what the Persona says — observe the details. Is their desk organized? Do they have a beeper? What kind of clothes do they wear? These details are often the most telling of all about their real priorities.
    WarningDo not spend too much time finding the perfect Persona. Make your best guess and get started — you can change it later as you gain more information.
  3. Make the Persona Visible and Central
    Display the Persona's picture and fact sheet prominently in your workspace. Reference the Persona by name in all product discussions. When team members disagree about features or priorities, return to the Persona for the definitive answer.
    Pro tipThe Persona should become like a family member. After years, you should be able to describe them from memory — their appearance, habits, frustrations, and dreams. That level of intimacy with your customer is a defining factor in success.
    WarningIf the Persona becomes a poster that people walk past without noticing, it has failed its purpose. The Persona must be a living reference that shapes daily decisions.
  4. Map the Full Life Cycle Use Case
    Document the complete journey in ten phases: (1) how the Persona determines they have a need, (2) how they find your product, (3) how they analyze it, (4) how they acquire it, (5) how they install it, (6) how they use it in detail, (7) how they determine value, (8) how they pay, (9) how they get support, and (10) how they buy more or spread awareness.
    Pro tipStart by mapping how the Persona uses the product once acquired — this is the easiest starting point. Then build out the front end (discovery and acquisition) and back end (support and word of mouth).
    WarningEntrepreneurs consistently overestimate customer enthusiasm, underestimate adoption barriers, and miss that the customer has many competing priorities. The Full Life Cycle Use Case exposes these blind spots before they become expensive failures.
  5. Validate with Primary Research
    Test the Full Life Cycle Use Case with real potential customers beyond the Persona. Present your visual use case diagram and gather feedback on whether each step reflects reality. Identify steps where friction, confusion, or resistance arise.
    Pro tipUse the validated use case as a basis for identifying your Next 10 Customers (Step 9). If the use case resonates consistently, you have strong evidence of product-market fit.
    WarningA use case that only works for your Persona and nobody else suggests your beachhead market may not be homogeneous enough. Revisit your segmentation.

Common mistakes

4 traps
Using a composite persona instead of a real person
Generic composites like 'Mary Marketing' leave room for debate and projection. A real person eliminates ambiguity — there is exactly one answer to what this person wants, fears, and values.
Listing features instead of the Persona's prioritized purchasing criteria
Products fail when they are built around feature lists rather than the ranked priorities that drive real purchasing decisions. The top priority is what keeps the Persona awake at night — your product must address it.
Mapping only product usage and ignoring acquisition and post-purchase
The traditional use case only shows how the customer uses the product. Missing the discovery, purchasing, and support phases means you will not notice critical problems until orders drop and you are scrambling.
Seeing the use case through the entrepreneur's eyes instead of the customer's
Entrepreneurs overestimate enthusiasm, underestimate friction, and forget that the customer has dozens of competing priorities. Always map the journey from the customer's perspective, validated by observation.

Origin story

How this framework came to be

Bill Aulet developed this approach at MIT after observing that founding teams constantly debated what customers wanted based on conflicting assumptions. By anchoring every discussion to a specific real person with a name, face, and documented priorities, teams found immediate alignment. The Full Life Cycle Use Case extends the traditional software use case concept to cover the entire customer journey, because Aulet found that entrepreneurs who only mapped product usage missed critical failure points in acquisition, payment, and support.

Source

Traced to primary
Source · BOOK
Disciplined Entrepreneurship
Bill Aulet · 2013
Open source →