| name | itk-mission-vision |
| description | Develop clear statements about your organization’s future aspirations and present activities. |
| intent | Establish clarity and consensus about the team’s present activities, desired future, and the link between the two. Ensure the team’s activities are well-aligned with their objectives. |
| type | component |
| phase | define |
| outcome | define |
| difficulty | intermediate |
| group_size | 6+ people |
| time_required | 60+ minutes |
| best_for | ["Forming a new product team or pod that needs shared purpose before committing to a roadmap","Realigning a squad after a strategic pivot when teams disagree about what they're actually building toward","Translating fuzzy executive ambitions into a concrete mission that anchors quarterly OKRs","Onboarding a cross-functional team where engineering, design, and business hold conflicting definitions of success","Pre-work before a portfolio or roadmap review where product purpose must be articulated to stakeholders"] |
| sources | ["MITRE Innovation Toolkit (ITK)","https://itk.mitre.org/toolkit-tools/mission-and-vision-canvas/"] |
MISsion & Vision Canvas
What Is It
Develop clear statements about your organization’s future aspirations and present activities.
Why Use It
Establish clarity and consensus about the team’s present activities, desired future, and the link between the two. Ensure the team’s activities are well-aligned with their objectives.
When to Use It
When a team or organization is first forming. Any time there is a significant shift in focus or effort. When the organization’s efforts and purpose need clarification.
How to Do It
- Assemble a small team and provide each member with a copy of the Mission and Vision Canvases, as well as the third page of instructions and examples. Spend a few moments discussing the objective of this session and the difference between a Mission Statement and a Vision Statement. A VISION statement should describe future conditions in aspirational terms. A MISSION statement should describe present activities in concrete terms. TIP: Begin with a VISION statement if you are starting from scratch. Begin with a MISSION statement if the organization has already started or has a general vision established.
- Invite the group to spend 4-6 minutes quietly writing responses to the questions in the boxes from the canvas labeled A – D (Vision) or A – E (Mission). Don’t miss the Bonus box in the Mission canvas.
- The facilitator then leads the group through a discussion of the questions in the boxes, capturing key ideas, insights, and phrases for each. Use clarifying questions and prompts such as “Say more words about that…” or “Can you be more specific?” The “Five Why’s” is a good technique as well.
- Highlight or circle key words from the lettered boxes, then use them to draft a Mission or Vision statement in the box on the right of the canvas. Refer to the fill-in-the-blank example below that box as a guide, but feel free to use other formulas or formats.
- Assess the draft statement using the quality check guidelines and the Test provided on the lower right section of the canvas. EXAMPLE: Feeding America Vision : A Hunger Free America (aspirational and future-oriented) Mission : To feed America’s hungry through a nationwide network of member food banks and engage our country in the fight to end hunger (concrete and present-oriented)
Key Concepts
Vision Statement — An aspirational description of the future state the product seeks to create, written in directional, time-independent terms. It sets the north star that prioritization and roadmap trade-offs are measured against.
Mission Statement — A concrete description of what the team does today, for whom, and how. It grounds daily backlog and sprint decisions in present-tense activity rather than aspiration.
Vision–Mission Linkage — The explicit connection showing how current activities (mission) advance the desired future (vision). A weak link is an early signal that the roadmap is busywork disconnected from strategic intent.
Five Whys — An iterative questioning technique that drills past surface answers to underlying purpose. Used here to extract the genuine 'why we exist' rather than restating product features.
Quality Check / Test — A validation rubric on the canvas used to pressure-test draft statements for specificity, aspiration, and clarity. Prevents shipping vague platitudes that fail to guide real decisions.
Aspirational vs. Concrete Framing — The deliberate separation of future-oriented language (vision) from present-tense, measurable language (mission). Conflating the two produces statements that neither inspire nor direct execution.
PM Applications
- Establishing a team charter and north star statement during the kickoff of a new product, pod, or value stream before any roadmap planning begins.
- Anchoring an OKR-setting workshop by deriving annual objectives directly from the mission so each quarter's key results trace back to organizational purpose.
- Producing the 'Vision' and 'Strategic Context' sections of a PRD or product strategy doc with language the whole team co-authored and endorses.
- Realigning a squad after a strategic pivot by re-running the canvas to surface where current backlog items no longer serve the updated direction.
- Preparing a stakeholder or executive briefing where product purpose must be stated crisply to win alignment across conflicting business priorities.
- Framing the opening of a roadmap or portfolio review so prioritization debates reference an agreed mission rather than individual opinions.
Benefits
- Helps answer the question “Who are we and what do we do around here?”
Common Pitfalls
- Wordsmithing the statement to perfection in the first session instead of treating it as an iterative draft — this burns the group's energy on syntax before consensus on substance exists.
- Writing a vision that's actually a mission (or vice versa), producing a 'future aspiration' full of present-day tactics that fails to inspire or a 'mission' so abstract it can't guide sprint decisions.
- Letting the loudest voice or HiPPO dictate the wording, which yields a statement the team nominally signs off on but doesn't actually believe or use in trade-off discussions.
- Filling the canvas boxes with feature lists and KPIs rather than purpose, so the resulting statements describe what you ship instead of why the product exists.
- Skipping the Five Whys and accepting first-pass answers, leaving the real underlying purpose unexamined and the statement interchangeable with any competitor's.
- Treating the finished canvas as a one-time poster, never revisiting it after pivots or annual planning, so it silently decouples from the actual roadmap and OKRs.
Combine With
Problem Framing Storyboarding
Assets
Metadata
| Field | Value |
|---|
| ITK Phase | DEFINE |
| Difficulty | Intermediate |
| Group Size | 6+ people |
| Time Required | 60+ minutes |
| Source | itk.mitre.org |
