The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
loading…
product, ux & customer framework
Map target customer, underserved needs, value proposition, feature set and UX.
quick answer
Product-Market Fit Pyramid is a pyramid / hierarchy for Product-market fit. It turns the decision into named fields, evidence, and a visible product-market fit pyramid worksheet / visual.
The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
Map target customer, underserved needs, value proposition, feature set and UX.
Use Product Strategy Stack when its output is closer to the conversation you need: Connect mission, strategy, goals, roadmap and tasks.
worked example
A filled example is easier to understand than a blank template. Use it to see the shape before applying the framework to your own case.
The pyramid builds product-market fit from a specific customer and underserved need up to value, features, and experience.
The pyramid builds product-market fit from a specific customer and underserved need up to value, features, and experience.
generate yours
Start Ask PL with the framework, required inputs, and your context. It will ask for missing details, render the pyramid / hierarchy, and explain what decision the output should change.
Apply Product-Market Fit Pyramid to my situation. Context: [Decision, audience, options, evidence, and constraints.] Use the Product-Market Fit Pyramid structure: - Levels from foundation to peak: - labels: Ask only for missing inputs that would change the output. Then render the pyramid / hierarchy and name the decision it should change.
how to use it
Use the framework to change a decision, not to fill a worksheet. Start narrow, add evidence, then inspect what the product-market fit pyramid worksheet / visual makes clearer.
Write the concrete product-market fit choice, tradeoff, or conversation the framework should change.
Fill the important slots: Levels from foundation to peak, labels.
Mark what is measured, what comes from customers, and what is still judgment.
End with the next move, the riskiest assumption, or the evidence that would change the product-market fit pyramid worksheet / visual.
quality check
Use this check after the artifact is filled. Blank fields are not failure; they are the next research question. Look for concrete evidence, missing constraints, and assumptions that would change the next move.
The framework needs a concrete decision. Broad intent turns it into a worksheet, not a decision aid.
Good framework output makes assumptions visible enough for someone else to challenge.
The diagram is useful only if it changes the next product conversation.
common mistakes
Do not use Product-Market Fit Pyramid as a worksheet. Name the choice, conversation, or tradeoff the output should change.
Separate measured facts, customer evidence, and leadership judgment so weak assumptions stay visible.
If the diagram does not match the decision, switch frameworks instead of stretching the boxes.
The framework should clarify the next move. It should not replace strategy, sequencing, or judgment.
use something else when
Connect mission, strategy, goals, roadmap and tasks.
Align vision, target group, needs, product, business goals and strategy.
Map desired outcome to opportunities, solutions and experiments.
faq
Map target customer, underserved needs, value proposition, feature set and UX.
Business context; objectives; available evidence; stakeholder judgment
Product-Market Fit Pyramid worksheet / visual
Use Product-Market Fit Pyramid when the decision matches this job: Map target customer, underserved needs, value proposition, feature set and UX.
Avoid it when you need Product Strategy Stack's output instead: Connect mission, strategy, goals, roadmap and tasks.
It is both: a structure for thinking and a visible pyramid / hierarchy that makes the decision easier to inspect.
A good input names the real decision, uses concrete evidence, and separates facts from assumptions.
Use the product-market fit pyramid worksheet / visual to choose the next move, name the riskiest assumption, or decide what evidence would change the call.
Use Product Strategy Stack when the real output you need is closer to: Connect mission, strategy, goals, roadmap and tasks.
Yes. Describe your context and Ask PL can ask for missing inputs, render the pyramid / hierarchy, and explain what decision it should change.