Framework guide

V2MOM Framework: Vision, Values, Methods, Obstacles, Measures

V2MOM is the alignment framework Marc Benioff wrote on the back of an envelope in Salesforce's first year and still runs the company on. Its strength is not the acronym — it is that a single page forces leadership to state what matters, what will get in the way, and what number proves it worked. This guide covers how to write each section and how to operationalise it so it survives past January.

1. The five components

ComponentQuestion it answersExecution artefact
VisionWhat do we want to achieve?Strategy statement / destination
ValuesWhat matters while we achieve it?Decision-making tie-breakers
MethodsHow will we get there?Initiatives, programmes, projects
ObstaclesWhat stands in the way?Risk register entries with owners
MeasuresHow will we know we succeeded?KPIs with targets and RAG status

2. Writing the Vision

One or two sentences, outcome-led, time-bound, and free of internal jargon. A good test: a new joiner should be able to repeat it after reading it once. Avoid stacking three ambitions into one sentence — if it needs an "and also", it belongs in Methods.

If you need worked examples, see our vision statement examples guide.

3. Values are ranked, not listed

The mistake most teams make is writing five values of equal weight. Values in a V2MOM are ordered, because their job is to resolve trade-offs: when speed and compliance collide mid-year, the order tells the team which one wins without escalating. Three to five, ranked, each with one line of "what this means when we have to choose".

4. Methods: the executable layer

Methods are the only section that consumes budget and headcount. Keep them to five to seven at the enterprise level, each with a single accountable owner, a start and end date, and a funding line. Anything smaller is a task inside a Method, not a Method.

5. Obstacles: name them before they bite

Obstacles are the section teams delete first and regret most. Writing them down converts a vague worry into an owned, mitigated risk with a review date. Treat each Obstacle as a risk register entry: likelihood, impact, mitigation, owner, next review.

6. Measures: two per Method, maximum

Measures must be quantified, sourced from a system rather than a slide, and scored on a fixed cadence. Two per Method is enough — one leading, one lagging. Define the RAG bands up front so status is computed, not negotiated; see the RAG threshold guide.

7. Cascading V2MOM across the organisation

  1. Enterprise V2MOM is written and published first — visible to everyone.
  2. Each business unit writes its own, where its Vision supports a parent Method.
  3. Team-level V2MOMs follow, ideally within three weeks of the enterprise version.
  4. Every level's Measures roll up mathematically, not narratively.

8. V2MOM vs OKRs vs Balanced Scorecard

V2MOMOKRsBalanced Scorecard
CycleAnnual, reviewed quarterlyQuarterlyAnnual, reviewed monthly
StrengthAlignment and trade-off clarityFocus and velocityBalanced performance view
Handles riskYes (Obstacles)NoPartially
Best forCompany-wide narrativeTeam executionBoard and regulator reporting

These are not mutually exclusive. The pattern we see most in GCC enterprises: an annual V2MOM for narrative and alignment, quarterly OKRs inside the Methods, and a balanced scorecard for board reporting.

9. Running your V2MOM in StratexHub

StratexHub models a V2MOM natively: the Vision and Values live on the strategy record, Methods become initiatives and programmes with owners and budgets, Obstacles become risk register entries with mitigation workflows, and Measures become KPIs with targets, actuals and automatic RAG scoring. Cascading is structural, so a divisional Measure rolls into the enterprise view without a re-keyed spreadsheet.

See the strategy management platform overview, or start a trial and write your first V2MOM in the product.

Visit PMO-ConnectPMO-Connect platform logo