Vision-Mission-Strategy-Objectives Pyramid
Translate a long-term destination into near-term work the team can execute
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 99%
This pyramid turns strategic aspiration into executable work by moving downward through four levels. Vision describes the ideal five-to-ten-year destination. Mission states how the organization will help bring that destination to life. Strategy identifies the important choices and path required to make progress. Objectives then convert those choices into measurable work for the next three to six months. Build the pyramid with broad input but clear ownership: gather organizational constraints and leadership context, run a cross-functional brainstorm, synthesize the ideas into a draft, and seek feedback without voting on the final strategy. Once approved, communicate changes quickly and revisit the objectives in regular team meetings. The test is bidirectional: quarterly work should ladder up to strategy, while the long-term strategy should be concrete enough to guide what the team declines.
Origin
Skarstad called the vision, mission, strategy, and objectives pyramid a simple framework she uses for work she loves. She paired it with a remote workshop process, quarterly OKRs at Duolingo, leadership review, and regular communication back to the team.
Core principles
- 01Move from a long horizon to increasingly concrete choices
- 02Involve the team without turning strategy into a vote
- 03Gather company and leadership context before drafting
- 04Objectives should express strategy in the next three to six months
- 05Every feature should connect upward to a strategy and long-term destination
How to run it
- 1
Gather the operating context
Talk with the team, business leaders, founder, or CEO before drafting. Learn about company strategy, overlapping efforts, platform constraints, and the resources leadership is willing to provide.
Pro tip Bring people along early while keeping one person accountable for the final strategic choice.
Watch out A strategy built in a vacuum can be directionally sensible and still conflict with the organization.
- 2
Explore the long horizon
Run a cross-functional brainstorm about the world five to ten years ahead, including customer experiences, the competitive landscape, and meaningful future possibilities. Use a prepared digital whiteboard, prompts, timeboxes, and optional pre-reading.
Pro tip Invite perspectives beyond product, such as marketing or policy, and explicitly free participants from today's constraints during ideation.
Watch out Do not force the group to finalize the vision inside the brainstorm.
- 3
Synthesize the vision
Cluster similar ideas during the session, then draft the desired long-term destination afterward. Circulate the draft for feedback and refine it while preserving clear decision ownership.
Pro tip A vivid prompt about a memorable customer experience can produce more useful material than asking for abstract vision statements.
Watch out Team participation creates input and buy-in, not a democratic vote on strategy.
- 4
Define mission and strategy
State how the organization will bring the vision to life, then choose the path and priorities required. Make the strategy specific enough to reject attractive work that does not serve it.
Pro tip Check the strategy again with the leaders who control resources and adjacent initiatives.
Watch out Strategy that remains entirely abstract cannot guide a roadmap.
- 5
Set near-term objectives
Translate the strategy into objectives and key results for the next three to six months, or use another shared goal framework. Select the work with the highest impact on the long-term plan and calibrate commitments using the current quarter's results.
Pro tip Use one goal-setting language across functions even if the team does not use formal OKRs.
Watch out Quarterly goals without a longer-term plan feel arbitrary and make prioritization unstable.
- 6
Close the execution loop
Share leadership feedback and approved changes quickly, kick off the work, and revisit strategy and goals in regular team meetings. Use the pyramid to explain why shiny objects are out of scope.
Pro tip A short recorded update can return leadership feedback to a remote team faster than waiting for the next meeting.
Watch out Approval is not alignment if the team stops hearing about the strategy once execution begins.
In the wild
Skarstad would prepare a Miro or FigJam board with headers, prompts, an agenda, and optional competitive pre-reading. A cross-functional group ideates on a five-to-ten-year horizon, reviews the ideas, and clusters similar concepts. She then takes the material away, drafts the vision, and returns it for feedback.
→ The team contributes to the strategic journey while one leader retains responsibility for synthesis and the final direction.
In the third month of a quarter, Skarstad's team reviews progress and whether it committed to the right amount, then spends a few weeks identifying the next quarter's highest-impact work. Objectives and key results go through leadership review, and she quickly shares the feedback and resulting changes with the team.
→ Near-term commitments stay connected to a longer-term plan and the team sees how its input survived the review process.
Common mistakes
Writing strategy alone
Presenting a finished document to an uninvolved team creates a costly buy-in problem even when the strategy itself is sound.
Voting on the direction
Broad input should improve the strategy, but decision ownership becomes unclear when every strategic choice is treated as democratic.
Living only in the clouds
A vision that never becomes near-term goals cannot connect to the features and tickets the team must actually build.
Is it for you?
Best for
Product leaders aligning cross-functional teams around a new initiative, business, or quarterly planning cycle.
Not ideal for
A narrow, reversible task that does not need long-term strategic alignment or leadership resourcing.
From the episode
Nickey Skarstad (Airbnb, Etsy, Shopify, Duolingo) on translating vision into goals, operationalizing product quality, second-order decisions, brainstorming, influence, and much more