The V2MOM Framework: Aligning Strategy from Top to Bottom

Created by Marc Benioff - https://www.salesforce.com/blog/how-to-create-alignment-within-your-company/

Overview

The V2MOM framework is a one-page planning document built from five parts: Vision, Values, Methods, Obstacles and Measures. Marc Benioff, the founder of Salesforce, describes it as a set of five questions: what do you want, what is important about it, how will you get it, what might stand in the way, and how will you know you have it. In his own write-up of the practice, he asks authors to rank their values in order of importance and to rank their methods in order of priority. Those two rankings are what turn a short statement of intent into a tool for making tradeoffs.

Benioff developed the format while he was an executive at Oracle, as a way to help the divisions he ran get clear on their vision and goals, according to Salesforce's Trailhead module on organizational alignment. When he left to start Salesforce, he and his cofounders wrote a V2MOM in the company's first weeks. CRM Magazine's account of the story dates that first version to April 1999, scrawled on the back of an American Express envelope that cofounder Parker Harris kept for five years. Benioff tells the fuller story in his book "Behind the Cloud," which the Salesforce post excerpts.

The document is short on purpose. Vision names the destination. Values state the principles that govern choices on the way there, in rank order, so that when two of them collide the higher one wins. Methods are the actions and initiatives that move the work forward, again in priority order. Obstacles name what could stop those methods, which makes risk part of the plan from the first draft. Measures state the observable results that show whether the vision was reached. Trailhead's personal V2MOM module adds a useful constraint on the last part: measures describe outcomes, not the routine activities someone does every week.

What makes V2MOM an alignment system, rather than one leader's plan, is who writes it. At Salesforce every department and every employee drafts their own V2MOM each year, and the documents are published internally instead of being filed away, as Benioff describes in the Salesforce post. The corporate V2MOM is written first by the CEO and his direct reports, then cascades to functions, teams and individuals, and any employee can open a colleague's V2MOM, per Trailhead. Writing your own version, and checking it against your manager's, is where alignment actually forms.

V2MOM sits between a mission statement and a full strategic plan. It asks for more structure than a mission statement because it forces rankings, names obstacles and commits to measures. It asks for far less than a planning process with budgets, dependency maps and project timelines. Compared with OKRs, which What Matters describes as quarterly objectives paired with specific, time-bound key results, V2MOM covers more ground on direction and principles and less on the quarterly scoring rhythm. Many teams run both: a V2MOM for the year's direction and OKRs for quarterly execution.

The format has limits worth knowing up front. It will not fix a toxic culture or inexperienced leadership, as Cascade's guide to V2MOM points out, because it depends on leaders being willing to write down real priorities and let people read them. It also adds little for a very small team that already shares context every day. It earns its keep in organizations large enough that people can no longer hear every decision being made, and where new hires need a written answer to "what matters here and why."

Teams that keep their V2MOMs in Hamster can hold the company, team and individual documents side by side so the links between levels stay visible as plans change.

Core Principles

Rank values and methods

A V2MOM lists its values and its methods in priority order, and the order is the point. Benioff describes ranking both lists explicitly in the Salesforce post. An unranked list of values offers no guidance when speed and quality, or growth and profitability, pull in different directions. A ranked list settles the argument in advance, and the discomfort of ranking is the conversation the team would otherwise have in the middle of a crisis.

One page, read by everyone

The document is meant to be read cold by anyone in the organization, so it has to be short. If the five sections will not fit on a page, the author has not yet decided what matters most. Compression forces choices about what to leave out, and those omissions tell readers as much as the items that remain. A long plan can sit alongside the V2MOM, but it does not replace it.

Alignment comes from authorship

Distributing the CEO's V2MOM does not align anyone. Each person writes their own V2MOM against the one above it, and the act of translating a parent method into their own vision and methods is what builds understanding. Trailhead describes the cascade running from the corporate V2MOM to functions, teams and individuals. A manager who writes a report's V2MOM for them removes the mechanism that makes the method work.

Obstacles belong in the plan

Obstacles are one of the five parts, with the same standing as vision and methods. Naming them in the document tells readers that leadership has looked honestly at what could go wrong. It also gives people permission to raise risks early, because the plan already expects them. A V2MOM with an empty or sanitized obstacles section usually signals that people did not feel safe writing the real ones down.

Measures describe outcomes

Measures answer how you will know you succeeded. Trailhead's personal V2MOM guidance says they should capture measurable outcomes of the work rather than day-to-day activity. "Improve customer satisfaction" gives no signal. A named metric with a baseline, a target and a date does. Without that precision a V2MOM becomes an aspirational document with no way to check progress.

A living document

A V2MOM is written once a year and revised as conditions change. Benioff calls it a living and breathing document in the Salesforce post, and managers discuss priorities with their people throughout the year. CRM Magazine reported that Benioff revisits his own V2MOM every six months or so. A document nobody has opened since January is a record, not a plan.

Transparency keeps the cascade honest

People can only check their V2MOM against their manager's if they can read it. Salesforce publishes V2MOMs on its internal network so employees can see each other's, as both Benioff and Trailhead describe. Visibility also exposes gaps and overlaps between peer teams that a manager reading only their own reports would miss.

Steps

1. Write the company V2MOM The CEO and the leadership team draft the top-level document first, because every other V2MOM will point back to it. Start with a one-sentence vision that is specific enough for someone to tell whether it came true. Rank the values, and do not move on until the group agrees on the order. List the methods in priority order, name the obstacles honestly, and give each measure a baseline, a target and a date. Test the draft by handing it to someone outside the room and asking them to explain the company's top priority back to you.

2. Share it with the whole organization Publish the document itself, not a slide summary of it. Walk through it in a company-wide session and explain the reasoning behind each ranking, since that is where questions cluster. Invite pushback on the values order and the obstacles, and treat disagreement as information about how the plan reads. Record what people misunderstood so the next revision can clarify it.

3. Cascade to departments and teams Each department lead writes a V2MOM that takes one or more company methods as its starting point. The department's vision describes what it will achieve in service of those methods, and its measures show how it contributes to company measures. Leads should share drafts with peer departments before finalizing, because conflicts over shared resources surface fastest in side-by-side reading. A department method that supports no company method is either missing from the company V2MOM or should not be on the list.

4. Have every individual write their own Individual contributors write V2MOMs that connect to their team's methods. The vision can be personal, as long as the methods show which team priorities the person is moving. Managers review and give feedback, but the author does the writing, because that is where the understanding forms. Keep individual documents short, since their job is to link daily work to a team method, not to replace a project plan.

5. Check alignment across levels Once documents exist at every level, read them against each other and look for three problems. Gaps are company methods that no team has picked up. Conflicts are teams whose methods compete for the same people or budget. Orphans are team or individual methods that trace back to nothing above them. Resolve each by conversation, and be ready to change the company V2MOM when a team's reading reveals a flaw in it.

6. Publish and keep them findable Store every V2MOM where anyone in the organization can browse it, with consistent naming by level and owner. Link each document to its parent so a reader can follow the chain upward. Access matters more than the tool. A new hire should be able to find their team's and the company's V2MOM in their first week.

7. Review on a regular cadence Revisit the documents at a set interval, often quarterly, and at any major change in the business. At each review, authors ask whether the vision still holds, whether the obstacles have shifted and whether the measures are on track. Update the document instead of letting it drift, and keep a short change note so readers can see what moved and why. Treat the review as recalibration, separate from performance evaluation, so people report honestly.

When to Use

• Your company has grown past the point where everyone hears every decision, and teams are starting to make choices that contradict each other. V2MOM gives each person a written link between their work and the company's direction.
• You are starting a fiscal year or facing a major shift, such as entering a new market or changing the business model. The ranking exercise forces leadership to say what it will deprioritize, not only what it wants.
• The leadership team agrees on the destination but keeps arguing about the route. Separating vision and values from methods and obstacles shows which layer the disagreement actually sits in.
• You are hiring quickly after a funding round or acquisition. A team V2MOM gives a new hire priorities, tradeoffs and success criteria in one page they can read on day one.
• You want a planning format that individual contributors use themselves. Personal V2MOMs let an engineer or designer tie their quarter to a team method in their own words.

When Not to Use

• The team is a handful of people working on one initiative and talking every day. Shared context already does the job, and a formal cascade adds process without solving a problem.
• You need detailed execution planning with timelines, dependencies and resourcing. A V2MOM sets direction on one page, so pair it with a project plan instead of stretching the methods section into one.
• Leadership is unwilling to rank priorities or publish them. Without rankings the document becomes a list of everything, and without transparency the cascade cannot be checked.
• The problem is capacity or execution, not direction. If teams already agree on priorities but cannot ship, fix the constraint first, because a sharper V2MOM will not add people or remove technical debt.