Marc Benioff wrote the first one on the back of an envelope on a plane in 1999. He needed every person at the new company he was building to point in the same direction without a thick strategy binder nobody would read. So he wrote five questions. He called it V2MOM. Salesforce still runs on it today, top to bottom, every year.
The good news for you: V2MOM is not a Salesforce secret. It is a clean, simple alignment model, and any leadership team can use it this week. The five boxes are genuinely easy to fill in. That is also the trap. The boxes are the easy 20%. The 80% that decides whether the page changes anything is the leadership behavior the template can't supply.
This page is both. First, V2MOM explained honestly, so you could build one with your team. Then the harder truth about why most of them end up framed on a wall and ignored.
What V2MOM Actually Is
V2MOM stands for five things, in order. The order matters, because each answer constrains the next.
Vision. What do you want? One clear sentence about the future you are building toward. Not a slogan. A destination a director two levels down could repeat and act on. "Be the most trusted partner in mid-market logistics by 2027" is a vision. "Excellence in everything" is wallpaper.
Values. What is important about that vision? Three to five principles that decide the close calls. Values earn their place only when they help you choose between two good options. If a value would never make you turn down a deal or change a plan, cut it. It is decoration.
Methods. How do you get there? The handful of things you will actually do. Not twenty. Five or six concrete plays, in priority order, so when two compete for the same week, everyone already knows which one wins.
Obstacles. What stands in the way? This is the box most frameworks skip and the one that makes V2MOM honest. Name the real barriers out loud — the capability you lack, the market shift, the internal resistance. A plan that pretends it has no obstacles is a wish.
Measures. How will you know you are winning? A specific result for each method, with a number and a date. Something that tells you in 90 days whether the method is working, not in 18 months when it is too late to adjust.
Five questions. One page. Vision, Values, Methods, Obstacles, Measures. You can fill it in for the whole company, then each leader fills in their own that ladders up to it. That cascade is the part Salesforce is famous for — everyone has a V2MOM, and every one of them connects to the one above it.
Why It Works on Paper
V2MOM is a good model, and it is worth saying why before we get to the catch.
It forces order. Vision before methods means you cannot start with a pile of activity and reverse-engineer a reason. You have to know what you want first.
It forces honesty about obstacles. Most planning tools let a team list what it will do and skip what is in the way. V2MOM puts the obstacle in writing, next to the method, where it cannot be quietly ignored.
It forces measures. Every method has to carry a number. That alone kills the vague "improve customer experience" priority that no one can ever mark as done.
And it fits on one page, which means a leader can hold the whole strategy in their head. If you want the broader case for that discipline, the one-page strategic plan template walks through the same idea across several frameworks, including this one — the page is a forcing function, not a magic trick.
So if the model is this clean, why do so many V2MOMs end up as decoration?
The 80% the Template Can't Do
Here is the number that should stop every leader cold. Only about 5% of employees understand their company's strategy well enough to act on it. Not 5% have read it. 5% understand it. The other 95% have seen the page, nodded in the meeting, and gone back to their desks with no idea how their Tuesday connects to the Vision box.
A V2MOM does not fix that. A V2MOM is the page the 95% don't understand. The model is the easy 20%. The 80% is everything that has to happen in the room for the page to become shared belief instead of shared text.
Think about what filling in a V2MOM honestly actually requires.
The Methods box forces a leadership team to cut. You have twenty things you could do and room for six. Cutting fourteen means someone's favorite project dies, and they have to sit there while it does. That is not a writing exercise. That is a hard conversation between peers about whose priority matters more, and most teams flinch from it. They let all twenty onto the page in soft language, and the forcing function is gone.
The Obstacles box forces a team to admit what is broken. The real obstacle is often a capability the team itself lacks, or a leader who is not delivering. Naming that out loud, in front of the person it implicates, takes a level of trust most leadership teams have never built. So the obstacle box fills up with safe, external barriers — "market conditions," "budget" — and the real wall goes unnamed.
The cascade forces every leader to translate the top-level V2MOM into their own. That translation is where strategy dies in most companies, because the leader can repeat the Vision but cannot convert it into what their team should start and stop doing on Monday. For the structural side of that cascade, Hoshin Kanri for leadership teams maps the catchball rhythm that keeps a top-level plan connected to the front line instead of emailed and forgotten.
None of these are template problems. You cannot fix them with a better box layout. They are behavior problems. And behavior is not installed by reading a model. It is installed by practicing it under pressure, with something real on the line.
What Has to Be True in the Room
A V2MOM works when the leadership team filling it in already has three capabilities, and fails when they don't.
They can argue substantively without it turning personal. Cutting fourteen methods to six surfaces what each leader values most. If the team can't have that argument cleanly, the Methods box defaults to the longest, softest version, and prioritization never happens.
They can name a real obstacle in front of the person it touches. If the team can't surface a hard truth about a peer or about itself without it becoming a status fight, the Obstacles box fills with weather and the plan stays a wish.
They can translate the page into local decisions and carry a shared picture across functions. Alignment is not a document the team signs. It is a trust the team builds, which is the whole point of cross-functional alignment — the leaders have to understand each other's world well enough to pull together when the V2MOM meets reality.
These three capabilities are what turn a filled-in template into a strategy a company can act on. And they are exactly the capabilities a one-day lecture on strategy will never build, because they are behaviors, not concepts.
Where the Behaviors Get Built
This is the gap the Lead the Endurance experience was built to close. Leadership teams step into Ernest Shackleton's 1914 Antarctic expedition as his senior advisors. The ship gets crushed. The plan they arrived with is gone. They have to argue through what to do next, name the obstacle in front of them honestly, and make decisions together under real pressure, with consequences for their team.
That is the V2MOM conversation, with the safety stripped away. There is no soft language to hide behind on the ice. Leaders practice cutting options to the few that matter, surfacing the hard obstacle, and carrying a shared picture across the people who have to execute it. By the time they are back at the table writing a real V2MOM, the behaviors are installed. The page becomes useful because the team is finally capable of using it.
The structured version of that work, designed for a senior team, is the executive development path — built to install the three capabilities a V2MOM depends on before the team ever picks up the template.
What It's Worth
The proof is in what changes after the behaviors land, not after the page is filled in.
At ArcelorMittal, 710 leaders went through Lead the Endurance via Duke Corporate Education and made decisions 30 to 40% faster afterward. Not because they had a better template. Because the team behind the plan could finally argue, surface obstacles, and align without routing every choice through suspicion.
Bell MTS grew from $800 million toward $1.4 billion in revenue in a single year — leaders across functions who finally understood each other well enough to pull one direction.
Build the V2MOM. It is a good model, and you could have a draft on one page by Friday. Then look hard at the three conversations the page depends on, and be honest about which ones your team can already have. The framework is the easy 20%. The 80% that makes it real is the leadership behavior underneath it — and that is the part worth investing in.
Read next: One Page Strategic Plan Template (And Why the Page Isn't the Point)