alexe-ev Craft Product Mission
Purpose
Help teams articulate a mission statement that anchors day-to-day decisions: what the product does, for whom, and what value it delivers right now.
Skill type
Conceptual skill
Use this skill when
- The team confuses vision and mission or uses them interchangeably
- A mission statement is too vague to guide product trade-offs
- A new product area needs a mission before planning begins
- Team alignment breaks down because there is no shared "what we do and for whom"
Do not use this skill when
- The goal is long-term aspirational direction (use define-product-vision)
- The goal is competitive positioning (use define-strategic-positioning)
Required inputs
- Target user or customer segment
- Core value the product delivers
- Product area or type
Optional inputs
- Existing mission or vision drafts
- Business model context
- OKRs or strategic goals
Upstream context
Works best when:
- Vision is defined or being developed in parallel
- Target segment is identified
If upstream context is missing
Draft a provisional mission and list what must be validated before it can be used to make decisions.
Downstream handoff
Output can feed:
- build-portfolio-roadmap-strategy (mission constrains what goes on the roadmap)
- set-goals-okrs-kpis (OKRs should map to mission)
- develop-positioning-messaging (mission is the backbone of external messaging)
Instructions
- Identify who the product serves (specific segment, not everyone).
- Identify the core job or problem the product addresses.
- Identify the value delivered (outcome, not feature).
- Draft a mission statement: "[Product] helps [who] [do what] so they can [outcome]."
- Test the draft: is it specific enough to say no to things? Would it exclude irrelevant features?
- Flag what is still assumed vs. validated.
Output
Provide:
- Mission statement
- Who it serves
- Core job or problem addressed
- Value delivered
- Specificity test: what would this mission say no to?
- Confidence level: provisional / context-informed / validated
- Open questions
Risks / caveats
- "Helps everyone do everything better" is not a mission
- Mission must be present-tense and achievable — vision is aspirational, mission is operational
- If the mission can't be used to reject bad ideas, it's too vague