Key Principle
Steps 6-8 translate deep customer understanding into a product concept and measurable value claim. The Full Life Cycle Use Case (Step 6) maps the entire customer journey across 10 stages — not just product usage. The High-Level Product Specification (Step 7) defines the product visually, with a Feature-Function-Benefit brochure that forces customer-facing language. The Quantified Value Proposition (Step 8) converts the product's strongest benefit into a measurable delta aligned with the Persona's top priority.
Together, these three steps operationalize the formula Innovation = Invention x Commercialization. A product that works brilliantly (invention) but has invisible discovery, painful acquisition, or absent support paths (failed commercialization) still fails. The FLCUC is a commercialization diagnostic; the brochure translates invention into customer language; the QVP proves the value in units the Persona already cares about.
Why This Matters
Entrepreneurs naturally focus on product usage (Stage 6 of the FLCUC) and ignore the surrounding stages where adoption barriers hide — discovery, acquisition, payment, support, repurchase. Problems in these stages surface only when order volume declines, by which point the cost of correction has compounded. (Step 6)
Product specification before customer understanding causes disconnection from actual needs. The framework deliberately delays product definition until Step 7, after five steps of customer definition and one step of journey mapping. Building before the product definition stabilizes incurs unnecessary cost and creates sunk-cost attachment that resists iteration. (Step 7)
A value proposition that highlights the product's strongest benefit rather than the Persona's top priority fails to create purchase urgency. The proposal "gets lost in their pile of less-than-urgent things to do." Customers do not re-rank their priorities to accommodate your product. (Step 8)
Good Examples
Meater — Cattle Biosensor (Step 8). Persona's top priority = money. As-is state: $63K disease loss per 1,000 head. Possible state: $36K. QVP = $27 per calf saved. Purely quantitative because the priority is monetary. Conservative numbers "verified with numerous ranchers" made the claim harder to attack, accelerating customer engagement.
inTouch — Prenatal Monitoring (Step 8). Persona's top priority = emotional reassurance. QVP framed as "facilitating intimacy and providing reassurance" — qualitative, not dollar-denominated. Demonstrates that the QVP unit tracks the Persona's priority, not a default financial metric. Forcing dollar values onto emotional priorities produces numbers the Persona does not recognize or trust.
Lifetime Supply (Step 7). Original model: one-time perpetual-supply payment targeting well-to-do young males. Primary research revealed convenience (especially mobile reordering) was the core attraction. Model pivoted to subscription with annual renewal. Further conversations shifted the beachhead from young professionals to parents of college students (financial means + emotional motivation). The brochure was the vehicle that made each pivot testable rather than speculative.
Counterpoints
Entrepreneur Bias in Journey Mapping (Step 6). Entrepreneur constructs FLCUC through own eyes, overestimates enthusiasm and ease of adoption, omits that the Persona has competing priorities and is risk-averse toward new vendors. Countermeasure: primary market research at every stage. See the product through the Persona's eyes, not your own.
Premature Building (Step 7). Building at this stage creates attachment that resists iteration and pulls the team toward technology particulars and away from customer-centered refinement. "When there are too many oscillations in the system and the product hasn't reached steady state, efficient development cannot take place." Each oscillation in product definition invalidates prior development work.
High-Fidelity Distraction (Step 7). Detailed visual mockups (colors, polish) distract customers from evaluating features, functions, and benefits. Lower-fidelity wireframes keep feedback focused on workflow and functional value. High fidelity causes the customer to react to aesthetics, producing feedback about design preferences rather than value delivery.
Key Quotes
"A traditional use case covers only product usage. The Full Life Cycle Use Case extends across the entire customer journey — awareness through repurchase — because adoption barriers hide in the stages entrepreneurs ignore." (Step 6)
"Each feature must be mapped through a chain: Feature > Function > Benefit. This forces outward (customer-facing) thinking. Without this chain, teams default to inward (technology-facing) thinking — listing what the product does rather than why the customer should care." (Step 7)
"The brochure operationalizes Innovation = Invention x Commercialization — it translates technology capabilities (invention) into customer-facing value language (commercialization)." (Step 7)
"If the product also addresses the top priority, reframe around that dimension. The value proposition must match what the Persona already considers urgent, not what the entrepreneur considers impressive." (Step 8)
"Without a concrete as-is baseline, the 'possible' state is a claim without context. Customers can't evaluate a benefit they can't compare to their current reality." (Step 8)
Rules of Thumb
10 stages of the Full Life Cycle Use Case. Need recognition, Discovery, Analysis, Acquisition, Installation, Usage, Value determination, Payment, Support, Repurchase/advocacy. Start mapping from Stage 6 (Usage) — teams know this best — then extend forward and backward. (Step 6)
Integration over replacement. Customers generally satisfied with their workflow will not overhaul it. Map the existing workflow first, then show how your product integrates rather than replaces wholesale. (Step 6)
Visual format is mandatory. The FLCUC must be diagrammed (flowcharts, visual maps) to surface sequential dependencies and gaps that prose obscures. (Step 6)
Two-sided markets need two use cases. Each side gets its own Full Life Cycle Use Case with the Persona woven into every stage in rich detail. (Step 6)
Product spec = visual representation + brochure. Software: storyboards showing logical screen-to-screen flow. Hardware: diagrams. The brochure maps Feature > Function > Benefit for each capability. Both serve as learning tools, not sales tools. (Step 7)
Share the spec for feedback, not validation. If the team treats the spec as a pitch, they defend it instead of listening. If they treat it as a hypothesis, they extract signal. (Step 7)
Do not include pricing in the high-level spec. Customers who disagree with prices withhold feedback on the core concept. Premature pricing anchors attention on a secondary variable, reducing signal quality. (Step 7)
QVP construction: three moves. (1) Map the as-is state using the FLCUC in units the customer already tracks. (2) Map the possible state under conservative, evidence-backed assumptions. (3) Calculate the delta in the Persona's priority units. That number is the QVP. (Step 8)
Align to priority, not to strength. The QVP must express the delta in the Persona's top priority, not whichever benefit the product delivers most impressively. Three benefit categories: Better (quality/capability), Faster (time), Cheaper (cost). (Step 8)
Underpromise, overdeliver. A startup has no track record to buffer a miss. One overpromise can destroy the reference-customer relationship the entire beachhead strategy depends on. (Step 8)
One-page visual for the QVP. The QVP must travel without the founder in the room. A dense spreadsheet dies on arrival; a one-page diagram lets the Persona share it with internal stakeholders who gate the purchase decision. (Step 8)
QVP feeds downstream economics. The Quantified Value Proposition feeds Business Model (Step 15) and Pricing Framework (Step 16). Rigor here compounds; sloppiness propagates errors into revenue architecture. (Step 8)
Related References
- The 24-Step Framework — Core Philosophy — The 24-step framework and core philosophy
- Market Segmentation and Beachhead Selection — Steps 1-2: Market segmentation and beachhead selection
- End User Profile, TAM, and Persona — Steps 3-5: End user profile, TAM, and Persona