mvv-create

MVV Create

Shared Reference

Use ../../references/product-management-principles.md for general product management principles. Apply the outcome, tradeoff, discovery, and common failure mode sections when turning strategy context into MVV language.

Workflow

1. Identify the entity: company, product, team, business unit, or initiative.
2. Extract the audience, problem, belief, target customer, market change, and intended impact.
3. Ask only for missing information that materially changes the MVV. If the user wants momentum, proceed with explicit assumptions.
4. Draft multiple options when the direction is still open; draft one polished version when the direction is already clear.
5. Separate aspirational language from operational values. Values must guide decisions and tradeoffs.

Product Management Principles

• Mission explains the enduring job and beneficiary in the present tense.
• Vision describes the future state created if the work succeeds.
• Values define observable behaviors and tradeoffs, not generic virtues.
• MVV should help teams choose between plausible options, not only sound good in a presentation.

Practical Operating Guidance

• Extract the repeated belief behind the product or organization: what must be true about customers, the market, or the team for this work to matter.
• Name the primary audience before polishing language: customers, employees, partners, investors, community, or internal teams.
• Keep mission stable, vision directional, and values operational.
• Prefer concrete verbs and beneficiaries over abstract claims.
• If context is thin, provide 2-3 distinct draft directions and label the assumptions behind each.

Output

Return a concise artifact with:

• Mission: present-tense purpose and who benefits.
• Vision: future state if the work succeeds.
• Values: 3-6 behavioral principles with a short explanation for each.
• Strategic notes: assumptions, sharp tradeoffs, and language that may need stakeholder review.

Common Failure Modes

• Mission is a slogan instead of a purpose.
• Vision is just a roadmap milestone.
• Values are interchangeable with any competitor's values.
• Language is emotionally polished but does not resolve product, hiring, brand, or prioritization decisions.
• The artifact hides the real tradeoff the organization needs to make.

Quality Bar

Favor specific, memorable, decision-useful language. Avoid generic claims such as "make the world better", "customer first", or "innovation" unless grounded in concrete behavior.