How to Create V2MOM Vision and Values Statements That Drive Alignment
This skill teaches you to craft a clear, time-bound vision statement and a prioritized set of values that together form the foundation of the V2MOM framework, giving every person on your team a shared definition of where you are headed and how you will make decisions along the way.
Start by drafting a vision statement of one to two sentences that describes your desired future state in concrete, measurable terms. Then identify three to five values ranked by priority that will guide every decision your team makes toward that vision. Test both by asking whether a new team member could use them to make a correct trade-off decision without asking their manager. Revise until the answer is yes.
Outcome: You produce a one-to-two sentence vision statement and a rank-ordered list of three to five values, both validated by stakeholders, that serve as the decision-making foundation for every downstream element of your V2MOM.
Prerequisites
- Understanding of the V2MOM framework structure (Vision, Values, Methods, Obstacles, Measures)
- Clarity on your team or organization's strategic context, including recent performance, market position, and leadership priorities
- Access to stakeholders who can validate or pressure-test your draft statements
- Familiarity with your company's existing mission or strategy documents, if any
Overview
Vision and values are the first two letters of the V2MOM Framework, and they do the heaviest lifting in the entire document. The vision tells everyone where the team is headed over a defined time horizon. The values tell everyone how to make decisions when they inevitably face trade-offs getting there. If you get these two components right, methods, obstacles, and measures almost write themselves. If you get them wrong, the rest of the V2MOM will feel like a collection of disconnected tasks rather than a coherent strategy.
The specific problem this skill solves is strategic ambiguity. Most teams suffer not from a lack of goals but from a lack of shared understanding about which goals matter most and which principles should govern the hundreds of micro-decisions made every week. A well-written vision statement eliminates the ambiguity of "where are we going?" and a well-ordered values list eliminates the ambiguity of "what matters more when two good things conflict?" The artifact you produce is deceptively simple: a concise paragraph for the vision and a short ranked list for the values. But the thinking required to reach that simplicity is where the real strategic work happens.
This skill sits at the very start of the V2MOM creation workflow. You should complete your vision and values before attempting to define methods and action plans or set measures and success metrics. The reason is structural: every method should be in service of the vision, and every trade-off between methods should be resolvable by consulting the ranked values. If you skip ahead, you will find yourself retrofitting a vision to justify methods you already chose, which defeats the purpose of the framework. Success looks like a vision statement that a new hire can read on day one and immediately understand what the team is trying to accomplish, paired with a values list that two reasonable people on the team would use to reach the same conclusion when forced to choose between competing priorities.
How It Works
The V2MOM vision statement works because it compresses strategic intent into a format that is memorable, testable, and time-bound. Unlike a corporate mission statement, which tends to be permanent and abstract ("empower every person and organization on the planet"), a V2MOM vision is tied to a specific planning cycle, usually a quarter, half-year, or full year. This temporal constraint forces you to be concrete. You cannot hide behind aspirational language when the clock is ticking.
The mental model behind the vision is a "future snapshot." Imagine you are standing at the end of the planning period, looking back. What is true now that was not true before? The best visions answer this question in plain language. They describe a changed state of the world, not an activity. "Launch the mobile app" is an activity. "Mobile users represent 30% of active weekly usage" is a changed state. The distinction matters because activities can be completed without producing the intended outcome, while changed states force you to think about impact.
Values in the V2MOM framework are different from corporate values like "integrity" or "innovation." They are decision-making priorities specific to this planning period. They answer the question: "When two good things are in conflict, which one wins?" For example, if your values list ranks "speed to market" above "feature completeness," then any team member facing a scope decision should cut features to hit the date, without needing to escalate. This is why values must be rank-ordered, not just listed. An unranked list of values is functionally useless because the whole point is to resolve conflicts, and conflicts only get resolved when one value clearly outranks another.
The ranking mechanism is what distinguishes V2MOM values from the values you might find on a poster in the break room. When Marc Benioff originally designed the V2MOM Framework at Salesforce, the explicit instruction was that values must be in priority order. Value number one beats value number two whenever they collide. This ordering creates a decision tree that every person in the organization can apply independently. The result is distributed decision-making without distributed chaos.
One important nuance: values are not permanent truths. They shift between planning cycles based on what the organization needs most right now. In a growth phase, "customer acquisition velocity" might outrank "unit economics." In a post-funding phase, the order might reverse. The vision tells you the destination, and the values tell you the driving rules for this particular leg of the journey. Together, they form a contract between leadership and the rest of the organization: here is what we are trying to achieve, and here is how we expect you to prioritize when things get hard.
Step-by-Step
Step 1: Gather Strategic Inputs
Before you write a single word, collect the raw materials you will synthesize into your vision and values. Pull together your company or team's current strategic plan, the previous V2MOM if one exists, recent board decks or investor updates, competitive analysis, customer feedback themes from the last quarter, and any quantitative performance data (revenue, retention, NPS, usage metrics). Read through these documents and highlight recurring themes, stated priorities, and any explicit statements about what matters most. Create a one-page summary of the top five to seven themes you see repeated across sources.
This summary becomes your working brief.
Tip: If you are writing a team-level V2MOM, make sure you have also read the leadership-level V2MOM above yours. Your vision should nest inside theirs, not contradict it. See the skill on [cascading V2MOMs across teams](/skills/cascading-v2moms-across-teams) for more detail.
Step 2: Draft Three Candidate Vision Statements
Do not try to write the perfect vision on your first attempt. Instead, write three distinct candidates, each taking a slightly different angle on the future you want to create. One might emphasize a customer outcome ("Enterprise customers consider us the default choice for X"). 99% uptime").
A third might emphasize a market position ("We are the top-ranked solution in the G2 mid-market category"). Keep each candidate to one or two sentences. Use plain language that a new team member could understand without an acronym glossary. Include at least one concrete, observable indicator in each candidate so the vision is testable, not just inspirational.
Tip: Read each candidate aloud. If it sounds like it could appear on any company's website without modification, it is too generic. The best test: could a competitor honestly claim the same vision? If yes, rewrite until the answer is no.
Step 3: Apply the Specificity and Timeframe Test
Take each candidate vision and run it through two filters. First, the specificity test: does it describe a concrete, observable future state, or does it use vague language like "be the best" or "drive innovation"? Replace any vague phrase with a measurable outcome. Second, the timeframe test: is there a clear planning period implied or stated?
A vision should be achievable within your V2MOM cycle (typically one quarter to one year). If the vision would take three years, it is a mission, not a V2MOM vision. Narrow it to what the next cycle's contribution looks like. After filtering, you should have three tighter candidates.
Select the one that best captures the single most important change you need to create, and set the other two aside as potential inputs for your methods section.
Tip: A useful heuristic: your vision should be ambitious enough that achieving it would genuinely excite the team, but specific enough that you could tell a stranger at a coffee shop exactly how you would know whether you succeeded.
Step 4: Brainstorm a Long List of Values
Shift to values. Start by brainstorming every principle, priority, or trade-off preference that you believe should guide the team during this planning cycle. Do not filter yet. Write down everything: speed, quality, customer satisfaction, revenue growth, team morale, technical debt reduction, innovation, cost efficiency, partnership development.
Aim for ten to fifteen items on your initial list. Pull from the strategic inputs you gathered in Step 1. Look especially at the tensions you noticed, because tensions reveal where values will actually matter. If your strategic inputs show pressure to grow fast AND pressure to improve margins, both of those are candidate values, and you will need to decide which one ranks higher.
Tip: Ask yourself: "In the last quarter, what decisions did we get wrong because we did not have clear priorities?" Each wrong decision usually points to a missing or misordered value.
Step 5: Consolidate and Rank-Order Your Values
Reduce your long list to three to five values. Start by grouping synonyms and near-duplicates. "Ship fast" and "speed to market" are the same value. "Quality" and "reliability" might be the same or different depending on your context, so make that call explicitly.
Once you have your short list, rank them from most important to least important. This is the hardest part of the entire V2MOM process. The ranking is what gives values their power, because an unranked list cannot resolve trade-offs. To force the ranking, use pairwise comparison: take values A and B, imagine a real scenario where they conflict, and decide which one wins.
Repeat for every pair. Write each value as a short phrase (two to five words) followed by one clarifying sentence that explains what this value means in practice during this cycle.
Tip: If you cannot bring yourself to rank one value above another, you have not defined them concretely enough. "Customer trust" and "rapid experimentation" feel like they cannot be ranked, but "never ship a feature without security review" and "run at least two A/B tests per sprint" can absolutely be ranked.
Step 6: Write the Conflict Scenario Test
For each pair of adjacent values in your ranked list, write a one-paragraph scenario where those two values come into direct conflict. For example, if value 1 is "revenue growth" and value 2 is "customer experience," your scenario might be: "A major enterprise prospect wants custom features that would delay the roadmap for existing customers by six weeks. " Then write the answer that your ranking implies. If the answer feels wrong, either your ranking is wrong or your value definitions need adjustment.
This step catches errors before they become real organizational pain. Each scenario should take about five minutes to write and discuss. Document these scenarios because they become invaluable onboarding material for new team members.
Tip: Share these conflict scenarios with two or three peers who were not involved in drafting. If they reach a different conclusion from the ranking, your values are either unclear or misordered. Treat disagreement at this stage as a feature, not a bug.
Step 7: Validate with Stakeholders
Present your draft vision and ranked values to the people who will live with them: your leadership chain (to ensure alignment with organizational direction) and your direct team (to ensure the vision is understood and the values feel authentic). For leadership review, share the document asynchronously first and let reviewers provide written feedback before any live discussion. This prevents groupthink and ensures you hear from quieter voices. For team review, run a short working session where you present each conflict scenario from Step 6 and ask the team to independently write down their answer before sharing.
If fewer than 80% of the group reaches the same answer, revisit the value definitions and ranking. Capture all feedback and prepare a revised draft.
Tip: Do not try to get universal agreement on every word. Your goal is alignment on direction and priority order, not consensus on phrasing. If the team agrees on what matters most but wants to reword the vision, accommodate the rewording. If they disagree on the ranking, that requires real discussion.
Step 8: Finalize and Format for Cascading
Incorporate stakeholder feedback into a final version. Format the vision as one to two sentences at the top of your V2MOM document. Format each value as a bolded phrase followed by a one-sentence clarification and (optionally) the conflict scenario that illustrates it. Number the values to make the rank order unmistakable.
Add a "last updated" date and the author's name. Store the final V2MOM in whatever tool your organization uses (a shared doc, a wiki page, a V2MOM template). Ensure the document is accessible to everyone who will need to create a cascaded V2MOM beneath yours. The vision and values you just wrote become the constraint set for the next step: defining methods and action plans.
Tip: Resist the temptation to add caveats or footnotes that soften the ranking. Phrases like "these are all equally important" undo the entire exercise. If a value is on the list, it matters. The ranking determines what wins when two important things collide.
Examples
Example: Early-Stage B2B SaaS Startup (10-Person Team)
A seed-funded project management tool for design agencies has 50 paying customers, $15K MRR, and a six-month runway. The CEO is writing the company's first V2MOM for Q3-Q4 to align the entire team of 10 on what matters most. The competitive landscape includes three well-funded alternatives. The team needs to find product-market fit before the next fundraise.
The CEO gathers inputs: customer interview transcripts showing that design agencies love the visual timeline feature but churn when they outgrow the free tier, NPS data showing a score of 42, and investor feedback emphasizing the need for clear growth metrics before a Series A. " For values, the brainstorm produces: speed to market, customer love, hiring great people, technical quality, and revenue growth. "), the ranked list becomes: (1) Customer retention: reduce churn to under 5% monthly by solving the top three reasons customers leave. (2) Speed to market: ship one meaningful feature per sprint, cutting scope rather than slipping dates.
(3) Revenue growth: prioritize features that expand seat count within existing accounts over net-new acquisition features. , a retention-critical bug requires pausing feature work), retention wins. This V2MOM gives every team member a clear basis for daily prioritization decisions without waiting for CEO approval.
Example: Enterprise Product Division (150-Person Team)
A VP of Product at a mid-market enterprise software company is writing the annual V2MOM for a 150-person product and engineering division. The division manages three product lines, two of which are mature and one is a recent acquisition. The company's board-level V2MOM emphasizes profitability over growth for the upcoming year. Cross-functional alignment between product, sales, and customer success has been a recurring challenge.
The VP gathers inputs from the board-level V2MOM (which emphasizes operating margin improvement), the last two quarters of product analytics (showing the acquired product has 60% lower engagement than the core products), sales pipeline data (showing 40% of deals involve multi-product bundles), and exit interview themes from three senior engineers who cited "unclear priorities" as a reason for leaving. " Values after consolidation and ranking: (1) Platform integration: every feature decision must move toward a single integrated experience, not three separate products. (2) Margin discipline: no new project is approved without a clear path to positive unit economics within two quarters. (3) Customer retention: invest in reducing churn of existing high-value accounts over acquiring new logos.
(4) Engineering velocity: reduce time-to-ship by eliminating cross-team dependencies, not by adding headcount. (5) Talent retention: make priority clarity a competitive advantage in recruiting. The conflict scenario between values 1 and 2: "The integration project will cost $500K in engineering time with no direct revenue impact for 6 months. " Answer: Yes, because integration (value 1) outranks margin discipline (value 2), and the long-term margin improvement from reduced maintenance costs justifies the short-term investment.
This clarity prevents months of back-and-forth between product managers arguing for their own product line.
Example: Consumer Mobile App (Cross-Functional Squad)
A squad lead at a consumer fintech company is writing a quarterly V2MOM for a cross-functional squad of 8 (2 designers, 3 engineers, 1 data analyst, 1 PM, 1 QA). The squad owns the savings product within a broader personal finance app. The company-level V2MOM emphasizes user growth and engagement. The squad's previous quarter was spent on technical debt, and leadership is expecting visible user-facing progress this quarter.
The squad lead reviews the company V2MOM (emphasizing DAU growth to 500K), the squad's backlog (37 tickets, 12 of which are carryover tech debt items), user research from the last round of interviews (users want automated savings rules but find the current manual process confusing), and analytics showing that only 18% of app users have activated the savings feature. " Values: (1) User simplicity: every interaction must be completable in under 3 taps, and we cut features before adding complexity. (2) Activation over depth: prioritize getting more users into savings over adding advanced features for power users. (3) Shipping cadence: release to production at least every two weeks, using feature flags to decouple deployment from launch.
The conflict test between values 1 and 2: "Users request a feature to customize savings rule thresholds, but adding it requires a settings screen with 5 input fields. " Answer: No, because user simplicity (value 1) outranks activation (value 2), and a complex settings screen will reduce the activation rate we are trying to grow. Instead, ship smart defaults that work for 80% of users. This V2MOM keeps the small squad focused and prevents scope creep from well-intentioned feature requests.
Example: Internal Platform Team (Non-Revenue Function)
An engineering manager leads an internal developer platform team of 12 engineers at a 500-person company. The team builds shared infrastructure (CI/CD pipelines, internal APIs, monitoring tools) used by all other engineering teams. The team has no direct revenue and often struggles to articulate its value in business terms. The previous quarter saw two major incidents caused by teams using the internal platform incorrectly.
The EM gathers inputs: incident post-mortems (both incidents traced to undocumented API changes), developer experience survey results (NPS of internal platform is 22, with "hard to find documentation" as the top complaint), and the CTO's V2MOM (which lists "engineering efficiency" as value 2). " Values: (1) Reliability: never ship a platform change without a rollback plan and migration guide. Any change that risks a P1 gets an additional review cycle. (2) Self-service: build documentation and guardrails into the platform itself rather than relying on Slack support.
Every new API ships with a runbook. (3) Developer speed: measure success by how fast product teams ship, not by how many platform features we release. (4) Transparency: publish weekly platform health metrics and roadmap updates to all engineering. The conflict test: "A product team urgently needs a new API endpoint, but shipping it without documentation would violate the self-service value.
" Answer: No, because reliability (value 1) and self-service (value 2) both outrank developer speed (value 3). Ship the endpoint with at minimum a runbook, even if it takes an extra day. This decision framework prevents the platform team from becoming a firefighting bottleneck.
Best Practices
Write the vision in present tense as if describing the future state that already exists. "We are the default platform for mid-market e-commerce teams" is more galvanizing and testable than "We will try to become a leading platform." Present tense forces concreteness and creates a psychological anchor that pulls the team forward. If you write in future tense, the vision feels perpetually distant.
Limit values to three to five items per V2MOM. Every value you add dilutes the decision-making power of the list. If you have seven values, the person making a daily trade-off cannot hold them all in working memory and will default to their own judgment, which is exactly what the values are supposed to replace. Three values are easy to remember. Five are manageable. Seven are decorative.
Rank values using pairwise conflict scenarios, not abstract importance ratings. Asking "is quality more important than speed?" in a vacuum produces meaningless answers. Asking "would you delay the launch by two weeks to fix a performance regression that affects 5% of users?" produces an answer that reveals the real ranking. Always ground the ranking in situations the team has actually faced or could realistically face.
Rewrite your vision and values every planning cycle, even if the direction has not fundamentally changed. The act of rewriting forces you to reexamine assumptions, incorporate new information, and recommit publicly. Teams that carry over the same V2MOM from the previous cycle tend to stop reading it. A fresh document signals that leadership is actively steering, not coasting.
Include one quantitative element in your vision statement. "Become the trusted platform for HR teams" is hard to evaluate. "Achieve 40% market penetration among HR teams at companies with 200 to 2,000 employees" is unambiguous. The number does not need to be the only thing in the vision, but it provides an anchor that prevents reinterpretation.
If you omit numbers entirely, different team members will hold different mental thresholds for success.
Make values action-oriented rather than noun-oriented. "Customer obsession" is a noun phrase that can mean anything. "Resolve every support ticket within 4 hours" is an action that leaves no room for interpretation. Even if your value is broader than a single metric, phrase it as a behavioral commitment: "Ship weekly, even if the release is small" beats "velocity" every time.
People can follow instructions but they cannot follow abstract concepts.
Test your vision statement with the "stranger at a coffee shop" standard. Read it to someone outside your organization. If they can tell you what the team is trying to accomplish and roughly how they would know they succeeded, the vision passes. If they nod politely and change the subject, it is too vague.
External readers are ruthlessly honest about clarity because they have no context to fill in the gaps.
Document the reasoning behind your value ranking, not just the ranking itself. When a new team member or a skeptical peer asks why speed outranks quality, you need a crisp answer grounded in the current strategic context. "Because we are in a land-grab market where the first mover with adequate quality wins, and a perfect product shipped six months late loses" is a convincing rationale. Without documented reasoning, the ranking feels arbitrary and people will quietly ignore it.
Common Mistakes
Writing a vision statement that is actually a mission statement
Correction
The most common error is writing something timeless and abstract like "Empower teams to do their best work" and calling it a V2MOM vision. This happens because people confuse mission (permanent purpose) with vision (time-bound future state). The signal to watch for is whether your statement would still be true five years from now regardless of what happens. If yes, it is a mission.
A proper V2MOM vision is specific to this planning cycle and will be replaced or substantially revised at the next cycle.
Listing values without rank-ordering them
Correction
Teams often list four or five values as a bulleted list and consider the job done. This happens because ranking forces uncomfortable conversations about trade-offs, and avoiding discomfort feels like team harmony. The signal is a values list where every item uses the same formatting with no numbers, no hierarchy, and no stated priority. An unranked list is functionally identical to having no values at all, because it cannot resolve the conflicts that values exist to resolve.
Force yourself to number them 1 through N and write a conflict scenario for each adjacent pair to confirm the ordering.
Including too many values, diluting their decision-making power
Correction
Some teams list seven, eight, or even ten values because every stakeholder insists their priority should be represented. This happens when the V2MOM drafting process is treated as a political exercise rather than a strategic one. The signal is a values list so long that no one on the team can recite them from memory. When a list is unmemorizable, it is unused.
Consolidate aggressively by grouping related items and forcing a hard cap of five. If someone insists their priority is missing, ask them which existing value they would remove to make room. That conversation is the actual strategic work.
Writing values as generic corporate virtues instead of contextual priorities
Correction
Values like "integrity," "excellence," and "teamwork" appear in V2MOMs constantly and add zero decision-making value. This happens because people default to the vocabulary of corporate posters rather than thinking about the specific trade-offs their team faces this cycle. The signal is that you could swap your values list with any other company's and neither team would notice a difference. Replace each generic virtue with a specific behavioral commitment tied to your current context. "Integrity" becomes "publish our error rates publicly on the status page even when they are embarrassing." "Excellence" becomes "no feature ships without passing the accessibility audit."
Drafting the vision in isolation without strategic inputs
Correction
Leaders sometimes sit down and write a vision statement purely from intuition, skipping the input-gathering step. This happens because the vision feels like a creative exercise rather than a synthesis exercise. The signal is a vision that surprises the team or conflicts with data the team already has. A vision written without inputs tends to reflect the leader's personal excitement rather than the organization's strategic reality.
Always start by reviewing the previous V2MOM's outcomes, current metrics, competitive positioning, and customer feedback. The vision should feel like the obvious next step, not a bolt from the blue.
Failing to update the vision when the strategic context changes mid-cycle
Correction
Some teams treat the V2MOM as a set-and-forget document, continuing to pursue an original vision even after a major market shift, a key competitor move, or a significant internal change. This happens because revising a V2MOM feels like admitting the original was wrong. The signal is a growing gap between what the V2MOM says and what the team is actually working on day to day. A V2MOM is a living document.
If the strategic context shifts materially, revisit the vision and values within two weeks. A mid-cycle revision is a sign of strategic agility, not failure.
Other Skills in This Method
Comparing V2MOM with OKRs and Other Goal-Setting Frameworks
How to evaluate when to use V2MOM versus OKRs, balanced scorecards, or other strategic planning frameworks based on organizational needs.
Facilitating Collaborative V2MOM Planning Sessions
How to run effective workshops and meetings to collaboratively develop, review, and refine V2MOMs with leadership teams and cross-functional stakeholders.
Building V2MOM Templates and Worksheets
How to design reusable V2MOM templates, worksheets, and documents that standardize the planning process across your organization.
Cascading V2MOMs from Leadership to Individual Contributors
How to align organizational V2MOMs by cascading them from company-level down through departments, teams, and individual contributors for full strategic alignment.
Defining Methods and Actionable Steps in V2MOM
How to translate your vision and values into specific, executable methods and tactical action plans that drive results.
Identifying Obstacles and Building Mitigation Strategies
How to systematically surface potential challenges, blockers, and risks within your V2MOM and create proactive plans to address them.
Setting Measurable Success Criteria for V2MOM
How to define quantifiable measures and key metrics that track progress and determine whether your V2MOM goals have been achieved.
Frequently Asked Questions
How long should a V2MOM vision statement be?
One to two sentences, typically 20 to 40 words. The constraint is not arbitrary. A vision needs to be short enough that every team member can recall it from memory without looking it up. If your vision is a full paragraph, it contains methods or context that belong in other sections of the V2MOM. Cut until only the essential future state and its primary measurable indicator remain.
Should I write vision and values before or after defining methods?
Always before. The vision constrains which methods are relevant, and the ranked values determine how you prioritize between competing methods. If you write methods first, you will unconsciously reverse-engineer a vision to justify the work you already wanted to do, which defeats the purpose of strategic alignment. See [defining methods and action plans](/skills/defining-methods-and-action-plans) for the next step after your vision and values are finalized.
How do I create a V2MOM vision for a team that does not generate revenue?
Frame the vision around the impact your team has on the teams that do generate revenue, or on the user experience that drives revenue. Internal teams like platform engineering, design systems, or data infrastructure can measure themselves by the speed, reliability, or quality they enable for customer-facing teams. "Product teams deploy independently in under 10 minutes" is a perfectly valid vision for an internal platform team. The key is finding the measurable outcome your internal customers care about most.
How many values should a V2MOM have?
Three to five, strictly ranked. Fewer than three and you have not done enough strategic thinking about trade-offs. More than five and the list becomes impossible to memorize and therefore impossible to use in daily decisions. If you have difficulty cutting below five, look for values that can be combined into one ("customer trust" and "data security" might be a single value) or values that are really methods in disguise ("hire a VP of Sales" is a method, not a value).
What if my team disagrees on the ranking of values?
Disagreement about ranking is the most valuable output of the V2MOM process, because it surfaces strategic misalignment that would otherwise show up as execution friction weeks or months later. Do not resolve disagreement by compromising on an ambiguous ranking. Instead, present specific conflict scenarios where the two disputed values collide and ask each person to write down their answer independently. Discuss the answers openly. If the team still cannot agree, the leader with final authority makes the call and documents the reasoning. Transparent disagreement followed by a clear decision is far better than false consensus.
Can values change mid-cycle, or are they locked for the entire planning period?
Values can and should change if the strategic context shifts materially. A major competitive move, a key customer loss, a funding event, or an organizational restructuring can all invalidate the trade-off assumptions your values were built on. The trigger for reconsidering values is when team members start making decisions that conflict with the ranked values and those decisions feel correct. That is a signal that the values no longer reflect reality. Rewrite and re-rank, then communicate the change clearly with the reasoning behind it.
Why does my vision statement keep feeling too generic?
Generic visions almost always result from skipping the input-gathering step or from trying to accommodate too many stakeholders. When you skip inputs, you default to aspirational language because you do not have enough specifics to anchor the vision. When you accommodate too many stakeholders, you sand off every distinctive edge to avoid disagreement. Fix this by returning to your strategic inputs and identifying the single most important change your team needs to create this cycle. Write the vision about that one change and include a specific number. "Reduce customer onboarding time from 14 days to 3 days" cannot be confused with any other team's vision.