The V2MOM Framework: Aligning Strategy from Top to Bottom
V2MOM is a strategic planning framework created by Marc Benioff at Salesforce. It stands for Vision, Values, Methods, Obstacles, and Measures. Teams write a one-page document answering five questions: Where are we going? What matters most? How will we get there? What stands in the way? How will we know we succeeded? V2MOMs cascade from the CEO down to every individual, creating full organizational alignment.
Overview
V2MOM is a one-page strategic alignment framework built around five components: Vision, Values, Methods, Obstacles, and Measures. Marc Benioff created V2MOM in 1999 when he founded Salesforce, drawing on a practice he had first developed during his time at Oracle. He needed a tool that could communicate what the company was building, why it mattered, and how every person's work connected to the larger mission. The first Salesforce V2MOM was written on the back of an envelope. As the company grew from a small apartment startup to a publicly traded enterprise with tens of thousands of employees, V2MOM scaled with it. Benioff has described V2MOM as "the most important process at Salesforce," and the company still writes them annually at every level of the organization.
The mental model behind V2MOM is deceptively simple. Most strategic planning breaks down not because the strategy is wrong, but because people across the organization carry different assumptions about what success looks like and what they should prioritize when tradeoffs arise. V2MOM addresses this by forcing clarity on five dimensions in a fixed sequence. Vision defines the aspirational destination. Values establish the ranked principles that guide decisions when priorities conflict. Methods lay out the concrete actions and initiatives that move the organization toward the vision. Obstacles name the known challenges, risks, and constraints that could derail those methods. Measures define the specific, quantifiable criteria that indicate progress and success. The sequential ordering matters: values are explicitly ranked, which means when two good things compete for resources, the V2MOM tells you which one wins.
What distinguishes V2MOM from other goal-setting frameworks is its emphasis on cascading alignment and its insistence on ranking. OKRs, for example, set objectives and key results but typically do not force-rank values or explicitly name obstacles as a first-class element. Balanced Scorecards offer multi-dimensional measurement but are heavier on reporting infrastructure and lighter on individual connection. V2MOM sits in the middle: more structured than a simple mission statement, less complex than a full strategic planning process, and designed to be written by everyone, not just executives. Each person's V2MOM should nest within their manager's, which nests within the department's, which nests within the company's. This creates a traceable line from the CEO's vision to an individual contributor's weekly work.
Since its introduction, V2MOM has evolved beyond Salesforce. Startups and growth-stage companies have adopted it because the framework is lightweight enough to implement without specialized tooling and structured enough to bring real discipline to planning conversations. Some organizations have modified the format, combining it with OKR-style key results or adding time-bound milestones to the Methods section. Others use V2MOM primarily as a quarterly exercise rather than an annual one. The core innovation, that strategic alignment is achieved not by pushing a plan down from the top but by having every person articulate their own version of the plan and check it against their team's, remains the framework's most powerful feature.
V2MOM works best in organizations where leadership is willing to be transparent about priorities and where the culture values written clarity over verbal hand-waving. It is particularly effective for companies in rapid growth phases, where the pace of hiring means new people constantly need to understand what matters and why. It is also valuable when an organization has survived on implicit alignment (a small founding team that "just knows" the priorities) and needs to transition to explicit alignment as it scales. If you're looking for a framework that connects long-range vision to daily decisions without requiring a consulting engagement or a 50-slide deck, V2MOM is one of the most battle-tested options available. Hamster provides a workspace where teams can build, cascade, and review V2MOMs collaboratively with AI agents that help maintain alignment as plans evolve.
How It Works
Step 1: Write the Company-Level V2MOM
The CEO or founding team writes the top-level V2MOM first. This document sets the direction that every other V2MOM in the organization will reference. Start with the Vision: a single sentence that captures where the company is headed. This should be aspirational but specific enough to be falsifiable. " Then articulate Values, ranked in order of priority. This is the hardest step and the most important. If you cannot bring yourself to rank them, you are not done. Next, define Methods: the 3-5 major initiatives that will move you toward the vision. Obstacles follow: what known risks, dependencies, or constraints could prevent success. Finally, Measures: the specific, quantifiable results that will tell you whether you've succeeded. A good company V2MOM should fit on one page and be understandable to any employee who reads it cold.
Step 2: Share the Company V2MOM Transparently
Once the company V2MOM is finalized, share it with the entire organization. Do not summarize it, paraphrase it, or present it as slides. Share the actual document. Hold a company-wide session where the CEO walks through each section, explains the reasoning behind the rankings, and answers questions. The goal is not just transmission of information but shared understanding. People should leave knowing not just what the V2MOM says but why each choice was made. Pay special attention to the Values ranking and the Obstacles section, as these are the areas where questions and misunderstandings cluster. If people push back on the ranking, treat that as a feature of the process, not a bug.
Step 3: Department Leads Write Their V2MOMs
Each department or team lead writes their own V2MOM that nests within the company V2MOM. Their Vision should describe what their team specifically aims to achieve in service of the company vision. Their Values should reflect the company values but may include team-specific additions (still ranked). Methods should be the concrete initiatives the team will pursue. Obstacles should include both company-level obstacles that affect the team and team-specific challenges. Measures should be the team's contribution to the company-level measures plus any team-specific metrics. The most common mistake at this stage is writing a V2MOM that is disconnected from the company's. Each department V2MOM should be checkable against the level above. If a department's methods don't clearly support a company method, something is misaligned.
Step 4: Individual Contributors Write Their V2MOMs
Every individual contributor writes their own V2MOM, aligned with their team's. This is where the framework's power is most visible and most easily lost. An engineer's V2MOM should articulate what they personally aim to accomplish, which of the team's methods they're contributing to, and what obstacles they foresee in their own work. The Vision can be personal: "Become the team's go-to expert on performance optimization" is a valid individual vision if it aligns with the team's methods. Managers should review each report's V2MOM to check alignment and provide feedback, but should not dictate the content. The act of writing is what generates understanding. A common shortcut that undermines the process is having managers write V2MOMs for their reports. This defeats the purpose.
Step 5: Cross-Check Alignment Across Levels
Once V2MOMs are written at every level, do an alignment check. This can be as simple as a manager reading their reports' V2MOMs and flagging misalignment, or as structured as a facilitated session where teams present their V2MOMs and compare them side-by-side. Look for three common problems. First, gaps: a company method that no team's V2MOM supports. Second, conflicts: two teams whose methods compete for the same resource or contradict each other. Third, orphans: individual or team V2MOMs that don't connect to any company-level priority. When you find misalignment, the fix is not to force conformity but to have a conversation. Sometimes the misalignment reveals a flaw in the company V2MOM, not in the team's interpretation of it.
Step 6: Publish and Make V2MOMs Accessible
Store all V2MOMs in a shared, accessible location. At Salesforce, any employee can read any other employee's V2MOM, including the CEO's. This transparency is not optional; it is what makes the cascading mechanism work. If V2MOMs are locked in private documents or buried in performance management tools, they lose their power as alignment artifacts. Choose a tool that allows easy browsing: a shared wiki, a document repository with clear naming conventions, or a dedicated V2MOM space in your team workspace. The format matters less than the accessibility. Someone joining the company next month should be able to find and read every V2MOM within their first week.
Step 7: Review and Update V2MOMs on a Regular Cadence
Set a regular review cadence, typically quarterly for fast-moving companies or semi-annually for more stable organizations. During each review, every V2MOM author revisits their document and asks three questions. Has our vision changed? Have our obstacles shifted? Are our measures on track? The review is not a formal performance evaluation. It is a recalibration exercise. Markets shift, competitors move, customers reveal new information, and key hires arrive or depart. A V2MOM that was perfectly aligned in January may be stale by April. Updating the document keeps it relevant and signals to the team that the framework is a living practice, not annual paperwork. Track significant changes so you can see how your thinking evolved over the year.
When to Use
- When your company has grown past the stage where everyone fits in one room and implicit alignment is breaking down. You notice that teams are making conflicting decisions, product and sales are chasing different definitions of success, and new hires take months to understand what actually matters. V2MOM gives every person a structured way to connect their work to the company's direction.
- When you are entering a new fiscal year or a major strategic inflection point, such as entering a new market, launching a new product line, or pivoting your business model. These moments demand that the entire organization re-anchor on a shared vision, and the V2MOM format forces leadership to articulate not just what they want to achieve but what they are willing to deprioritize.
- When your leadership team agrees on the destination but keeps arguing about how to get there. V2MOM separates the "what" (Vision, Values) from the "how" (Methods) and the "what could go wrong" (Obstacles), which helps teams realize they may be aligned on goals but misaligned on approach, or vice versa. Surfacing the specific layer of disagreement accelerates resolution.
- When you need to onboard a large cohort of new employees quickly, such as after a funding round, an acquisition, or a seasonal hiring push. Handing someone a well-written V2MOM for their team and the company gives them a faster path to context than any onboarding deck. They can see priorities, tradeoffs, and success criteria in a single document.
- When you want a lightweight planning framework that every individual contributor can use, not just managers. V2MOM scales down to personal V2MOMs where an engineer or designer articulates their own vision for the quarter, connects it to their team's V2MOM, and identifies their own obstacles and measures. This bottom-up engagement is valuable in high-autonomy cultures.
When Not to Use
- When your team is fewer than five people working on a single focused initiative with daily face-to-face communication. At this stage, V2MOM adds process overhead without solving a real alignment problem. Small co-located teams typically maintain alignment through conversation and shared context. Introducing V2MOM too early can feel bureaucratic and slow down a team that needs speed more than structure.
- When you need deep operational planning with detailed timelines, dependencies, resource allocation, and risk mitigation plans. V2MOM is a one-page alignment tool, not a project plan. Teams that try to cram execution-level detail into the Methods and Obstacles sections end up with a document that is too long to serve as alignment and too shallow to serve as a plan. Use V2MOM for direction-setting and pair it with a separate execution framework for the details.
- When your organization's culture is deeply resistant to ranking priorities or making values explicit. V2MOM's power comes from forcing hard choices: this value matters more than that one, this method is the path we're choosing instead of that one. In organizations where consensus-driven culture means no one is willing to rank or exclude, V2MOM becomes a list of everything, which defeats its purpose. The framework requires leadership willing to say "this matters more" publicly.
- When the primary challenge is not alignment but execution. If your teams clearly understand the vision and priorities but are struggling with capacity, technical debt, process bottlenecks, or individual performance issues, V2MOM will not solve those problems. Writing a crisp V2MOM while the team cannot ship because of infrastructure failures is an exercise in frustration. Address the execution constraints first, then use V2MOM to align on what to do with recovered capacity.
- When your planning cycle is extremely short-term and tactical, such as a two-week sprint cycle where priorities shift based on daily customer feedback. V2MOM is designed for quarterly or annual horizons. Applying it to a two-week cadence creates churn: teams would spend more time rewriting V2MOMs than doing the work. In high-frequency iteration environments, lighter tools like sprint goals or weekly priorities are more appropriate.
Examples
Example: Series B SaaS Company Entering a New Market Segment
A 120-person B2B SaaS company selling project management software to agencies decided to expand into the enterprise segment. " Values were ranked: enterprise readiness first, then customer retention, then new feature velocity. This ranking was controversial because the product team had been prioritizing feature velocity for two years. Methods included building SSO and audit logging, hiring an enterprise sales team of 8, and establishing SOC 2 compliance. Obstacles named were: 18-month enterprise sales cycles, existing customers fearing neglect, and no enterprise reference accounts. Measures included 5 signed enterprise contracts over $100K ARR by year-end and maintaining agency churn below 3%. Department V2MOMs cascaded cleanly: engineering's V2MOM prioritized the SSO and compliance work, while customer success's V2MOM focused on proactive outreach to existing agency customers to address the neglect risk. The explicit ranking of values helped resolve three resource allocation disputes in the first quarter alone, because teams could point to the V2MOM instead of relitigating priorities each time.
Example: Non-Profit Organization Aligning After Leadership Transition
A 45-person education non-profit brought in a new executive director after the founder's retirement. Staff morale was low, priorities were unclear, and three major programs were competing for the same pool of grant funding. The new director used V2MOM as her first strategic exercise. " Values were ranked: student outcomes first, then financial sustainability, then program innovation. This ranking was a deliberate signal that the organization would stop launching new pilot programs unless they could demonstrate student impact. Methods included consolidating from seven programs to four, building a donor pipeline targeting three new foundation relationships, and hiring a data analyst to track outcomes. The Obstacles section named what everyone knew but hadn't said aloud: the founder's pet program had poor outcomes but strong emotional attachment among board members. 2M, and a student completion rate above 78%. Board members later said that seeing the obstacles named openly was the moment they trusted the new leader. Within 18 months, the organization hit 2,100 students and secured two of the three targeted foundation grants.
Example: Engineering Team Using V2MOM for a Platform Migration
A 30-person engineering department at a fintech company needed to migrate from a monolithic Rails application to a microservices architecture while continuing to ship customer-facing features. " Values ranked reliability first, then migration velocity, then new feature development. Methods included extracting three core services in Q1 (payments, user auth, notifications), establishing a feature-flag system to support parallel running, and dedicating 60% of engineering capacity to migration and 40% to feature work. Obstacles listed were: the legacy system's lack of test coverage making safe extraction risky, two senior engineers who had announced planned departures in Q2, and customer contractual commitments requiring specific feature delivery dates. Measures were concrete: three services fully migrated by end of Q2, zero P1 incidents caused by migration, and at least 4 of 7 committed customer features shipped on schedule. Individual engineer V2MOMs helped surface a hidden problem: three people had written obstacles about the same undocumented billing logic, which prompted the team to prioritize a documentation sprint before beginning the extraction. The team would do one thing differently next time: involve customer success earlier, as several customer-facing features were deprioritized without adequate customer communication.
Example: Marketing Team at a Growth-Stage E-Commerce Company
A 15-person marketing team at a direct-to-consumer skincare brand was spending across six channels with no shared understanding of what mattered most. The CMO introduced V2MOM after a quarter where the team hit their aggregate revenue number but missed profitability targets because of overspending on paid social. " Values were ranked: profitability (measured as blended CAC under $38) first, then channel diversification, then brand awareness. Methods included launching an SEO content program targeting 50 high-intent keywords, building an email lifecycle program to reduce reliance on paid re-acquisition, testing two new channels (podcast sponsorships and affiliate partnerships), and reducing paid social spend by 25% over two quarters. Obstacles named included the founder's emotional attachment to Instagram as the brand's identity channel, limited data infrastructure making cross-channel attribution unreliable, and a content team of only two people needing to produce at a higher volume. Measures included blended CAC at or below $38, no single channel exceeding 40% of revenue by Q4, email revenue growing from 12% to 25% of total, and organic search traffic increasing by 150%. The ranked values made the paid social budget conversation easier because the team could reference the V2MOM rather than framing it as a personal disagreement with the founder's preference. Six months in, the team was at a $41 blended CAC (close but not there) and had successfully reduced paid social from 52% to 39% of revenue.
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.
Writing Compelling Vision and Values Statements
How to craft clear, inspiring vision statements and define the core values that guide decision-making within the V2MOM framework.
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.