-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathv2mom-framework.html
More file actions
205 lines (184 loc) · 21 KB
/
Copy pathv2mom-framework.html
File metadata and controls
205 lines (184 loc) · 21 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>V2MOM — Salesforce's alignment cascade</title>
<link rel="stylesheet" href="framework.css">
<style>
/* Page-accent — overrides framework.css fallback */
:root{--page-accent:var(--gold);--page-accent-soft:var(--gold-soft)}
/* the 5 letters */
.letters{display:grid;grid-template-columns:repeat(5,1fr);gap:10px;margin:14px 0}
.ltr{background:#fff;border:1px solid var(--line);border-top:5px solid var(--page-accent);border-radius:10px;padding:16px 14px;text-align:center}
.ltr .big{font-family:Georgia,serif;font-size:32px;color:var(--page-accent);font-weight:700;line-height:1}
.ltr .nm{font-weight:700;font-size:13px;margin:5px 0 4px}
.ltr .ds{font-size:12px;color:var(--ink-soft);line-height:1.4}
/* worked example V2MOM */
.v2example{background:#fff;border:1px solid var(--line);border-radius:12px;padding:20px 24px;margin:14px 0;box-shadow:var(--shadow);border-left:5px solid var(--page-accent)}
.v2example h3{margin:0 0 10px;font-size:18px;font-family:Georgia,serif}
.v2row{display:grid;grid-template-columns:140px 1fr;gap:14px;padding:10px 0;border-top:1px solid var(--line);font-size:14.5px}
.v2row:first-of-type{border-top:none}
.v2row .l{font-weight:700;color:var(--page-accent);font-family:Georgia,serif}
.v2row .b{color:var(--ink)}
@media(max-width:680px){.letters{grid-template-columns:repeat(2,1fr)}.v2row{grid-template-columns:1fr}}
</style>
</head>
<body>
<nav class="sitenav">
<details>
<summary>📑 Jump to</summary>
<div class="navmenu">
<div class="navgrp"><h4>Start here</h4>
<a href="index.html"><b>← Home (goal & map)</b></a>
<a href="impact-saas-companies.html">SaaS / B2B field study</a>
<a href="impact-consumer-companies.html">Consumer-tech field study</a>
<a href="methodologies-comparison.html"><b>All methods compared →</b></a>
<a href="experiment-trustworthiness.html">How 40k tests actually work →</a>
<a href="jargon.html">Jargon (glossary)</a>
</div>
<div class="navgrp"><h4>Scoring & Input modeling</h4>
<a href="rice-framework.html">RICE (Intercom)</a>
<a href="north-star-framework.html">North Star (Amplitude / Slack)</a>
</div>
<div class="navgrp"><h4>Goal-laddering / Define first</h4>
<a class="cur" href="v2mom-framework.html">V2MOM (Salesforce)</a>
<a href="pyramid-of-clarity-framework.html">Pyramid of Clarity (Asana)</a>
<a href="pr-faq-framework.html">PR-FAQ / Working Backwards (Amazon)</a>
<a href="heart-framework.html">HEART (Google)</a>
<a href="dibb-framework.html">DIBB (Spotify)</a>
</div>
<div class="navgrp"><h4>Experimentation (SaaS)</h4>
<a href="microsoft-exp-framework.html">Microsoft ExP / CUPED</a>
<a href="linkedin-xlnt-framework.html">LinkedIn T-REX</a>
</div>
<div class="navgrp"><h4>Experimentation (Consumer)</h4>
<a href="netflix-experimentation.html">Netflix · ABlaze</a>
<a href="booking-experimentation.html">Booking.com</a>
<a href="airbnb-erf-framework.html">Airbnb ERF</a>
<a href="uber-xp-framework.html">Uber XP</a>
<a href="doordash-switchback-framework.html">DoorDash switchback</a>
<a href="lyft-experimentation.html">Lyft</a>
<a href="pinterest-ab-framework.html">Pinterest</a>
</div>
<div class="navgrp"><h4>AI labs</h4>
<a href="anthropic-pm-on-ai-exponential.html">Anthropic · PM on AI exponential</a>
<a href="google-customer-zero-2026.html">Google · "Customer zero" 2026</a>
</div>
<div class="navgrp"><h4>Written discipline</h4>
<a href="stripe-shaping-framework.html">Stripe shaping</a>
</div>
</div>
</details>
</nav>
<div class="wrap">
<header class="masthead">
<p class="kicker">Methods · Deep-dive · Goal-laddering</p>
<h1>V2MOM — Salesforce's five-line alignment cascade <span class="srcyr">1999</span></h1>
<p class="sub">Marc Benioff and Salesforce's co-founders wrote the company's first V2MOM in its earliest weeks (the original — scribbled on a large American Express envelope — was kept by co-founder Parker Harris and framed on Salesforce's IPO day, per the Salesforce blog). Five questions every leader, team, and individual answers in one page.</p>
<p class="sub">It is an <em>alignment</em> mechanism, not a feature-impact estimator — and being honest about that is the whole point.</p>
<div class="goal"><span>Goal</span><br>Decide features by data-backed expected impact — choose by outcome, not by to-do list or opinion.</div>
</header>
<div class="eli">
<div class="lbl">🎓 8th-grade version</div>
V2MOM is five questions you (and everyone in the company) answer on one page. <b>V</b>ision: what are we trying to do? <b>V</b>alues: what won't we compromise on? <b>M</b>ethods: how will we do it? <b>O</b>bstacles: what's in the way? <b>M</b>easures: how will we know it worked? The CEO writes one, then every team writes one that fits inside it, then every person writes one that fits inside their team's. If your page doesn't connect to the page above you, that's a problem worth talking about. It doesn't pick which feature to build — it picks which <em>direction</em> your features should pull in.
</div>
<nav class="toc">
<a href="#headline">Honest headline</a>
<a href="#anatomy">The five letters</a>
<a href="#mechanism">How it picks work</a>
<a href="#example">Worked example</a>
<a href="#limits">What it doesn't do</a>
<a href="#apply">Apply to a sheet</a>
<a href="methodologies-comparison.html" style="color:var(--gold);font-weight:700">Comparison table →</a>
</nav>
<div class="finding" id="headline">
<h2>The honest headline: it's a one-page cascade, not a scoring formula</h2>
<p>V2MOM doesn't tell you what to build. It tells you what you're <b>trying to do</b>, what you'll <b>refuse to compromise on</b>, <b>how</b> you'll do it, what's <b>in the way</b>, and how you'll <b>know it worked</b> — written by every leader, cascaded to every team. The discipline is that <em>everyone in the company</em> can read the CEO's V2MOM and write a coherent one of their own that lines up with it.</p>
<p>Benioff's own framing, verbatim from the Salesforce blog: V2MOM is <b>"the glue that binds us together"</b>, the management process Salesforce has used to maintain alignment from four people to 50,000+. Useful precisely <em>because</em> it doesn't pretend to estimate per-feature impact — it forces clarity at the level above.</p>
</div>
<!-- ANATOMY -->
<h2 class="sec" id="anatomy">The five letters</h2>
<p class="secsub">Every V2MOM answers the same five questions in the same order. The ordering is load-bearing: you can't write a sensible "Method" until you've written the "Values" that constrain it.</p>
<div class="letters">
<div class="ltr"><div class="big">V</div><div class="nm">Vision</div><div class="ds">"What do you want to achieve?" — Benioff. One sentence, ambitious, unambiguous.</div></div>
<div class="ltr"><div class="big">V</div><div class="nm">Values</div><div class="ds">"What's important to you?" — the principles that guide the work; what we will <em>not</em> compromise on.</div></div>
<div class="ltr"><div class="big">M</div><div class="nm">Methods</div><div class="ds">"How do you get it?" — the strategic actions (typically 3–5).</div></div>
<div class="ltr"><div class="big">O</div><div class="nm">Obstacles</div><div class="ds">"What is preventing you from being successful?" — honest naming of risks & gaps.</div></div>
<div class="ltr"><div class="big">M</div><div class="nm">Measures</div><div class="ds">"How do you know you have it?" — concrete results (often, but not always, numeric).</div></div>
</div>
<div class="src">Source: <a class="cite" href="https://www.salesforce.com/blog/how-to-create-alignment-within-your-company/">Salesforce — "What is the Salesforce V2MOM?" (Benioff, originally 2013, refreshed Dec 11, 2024)</a> · companion: Benioff's books <em>Behind the Cloud</em> (Wiley, 2009) and <em>Trailblazer</em> (which the blog draws excerpts from) tell the founding-envelope origin story.</div>
<!-- MECHANISM -->
<h2 class="sec" id="mechanism">How V2MOM actually picks the work</h2>
<p class="secsub">It picks <strong>strategic direction</strong>, not features. The mechanism is the <em>cascade</em>: CEO writes one, every leader writes one aligned to it, every team writes one aligned to their leader's, every individual writes one aligned to their team's. Misalignment is visible in writing.</p>
<div class="step"><div class="num">1</div><div><h3>CEO writes the company V2MOM first</h3><p>Single page. <b>Vision</b> is one sentence. <b>Methods</b> are the 3–5 strategies — these are what the rest of the company must align to.</p></div></div>
<div class="step"><div class="num">2</div><div><h3>Each org/team writes their own V2MOM that ladders up</h3><p>The team's <b>Vision</b> is a slice of the CEO's; the team's <b>Methods</b> support one of the CEO's Methods. If a team's V2MOM doesn't connect, that's a misalignment to debate.</p></div></div>
<div class="step"><div class="num">3</div><div><h3>Individuals write personal V2MOMs aligned to their team</h3><p>Everyone, on a regular cadence (Salesforce uses annual; many teams refresh more often). The cumulative effect: each person can point at how their work ladders to the CEO's Vision.</p></div></div>
<div class="step"><div class="num">4</div><div><h3>Measures get tracked. Methods get revised.</h3><p>Periodically — Benioff frames it as "constant iteration" — you check Measures and re-write the V2MOM. It is <b>not static</b>; it adapts as reality moves.</p></div></div>
<!-- WORKED EXAMPLE -->
<h2 class="sec" id="example">Worked example — Benioff's actual 1999 V2MOM</h2>
<p class="secsub">Reconstructed from <em>Behind the Cloud</em> and the Salesforce blog. The point isn't this exact wording — it's that the whole strategy of a company that became a $200B business fits on one page.</p>
<div class="v2example">
<h3>Salesforce, 1999 — the founding V2MOM (paraphrased from Benioff)</h3>
<div class="v2row"><div class="l">Vision</div><div class="b">Rapidly create a world-class internet company / web site for sales force automation.</div></div>
<div class="v2row"><div class="l">Values</div><div class="b">World-class organization · Time to market · Functionality · Usability · Value to customer.</div></div>
<div class="v2row"><div class="l">Methods</div><div class="b">Hire the team · Finalize product specifications & technology · Build prototype · Run beta tests · Launch site.</div></div>
<div class="v2row"><div class="l">Obstacles</div><div class="b">Hiring engineering talent · Funding · Building rapidly with quality.</div></div>
<div class="v2row"><div class="l">Measures</div><div class="b">A working web site · Customers using it · Press coverage at launch.</div></div>
</div>
<p style="font-size:13px;color:var(--ink-soft)">Note the Measures: they are <b>outcomes</b> (working site, customers using it), not output counts (features shipped). And there is <em>no per-feature impact estimate anywhere</em> — that's the point.</p>
<!-- LIMITS -->
<h2 class="sec" id="limits">What V2MOM does <em>not</em> do</h2>
<div class="warn">
<b>It is not a prioritisation framework.</b> A V2MOM tells your team <em>which direction</em> they're pushing in. It does <strong>not</strong> tell them whether to ship Feature A or Feature B next quarter. Inside a single "Method," you still need a scoring framework (<a class="cite" href="rice-framework.html">RICE</a>), an input model (<a class="cite" href="north-star-framework.html">North Star</a>), or experimentation (<a class="cite" href="microsoft-exp-framework.html">ExP</a>) to pick the bets that move the Measures.<br><br>
<b>It is not <a class="j" href="jargon.html#okr">OKRs</a>.</b> OKRs are an objective + measurable key results, per cycle. V2MOM is a full strategic statement (vision, values, obstacles too) — many companies use V2MOM at leadership level and OKRs at team level. (Asana's <a class="cite" href="pyramid-of-clarity-framework.html">Pyramid of Clarity</a> takes the OKR side of the same shape.)
</div>
<!-- APPLY TO A SHEET -->
<h2 class="sec" id="apply">Apply to a feature sheet</h2>
<p class="secsub">V2MOM doesn't score features — it <em>filters</em> them against the team's Methods. If you adopt it, every backlog row must declare <strong>which Method it supports</strong> and <strong>which Measure it moves</strong>. Features that don't trace to a Method aren't ranked low; they're out of scope this cycle, full stop.</p>
<div class="note" style="background:var(--teal-soft);border-left-color:var(--teal)"><b>Try it Monday morning (30 minutes).</b> Open a blank page. Write your team's V2MOM right now — five lines, ugly first draft. Vision: one sentence. Values: three to five words. Methods: three to five strategic actions. Obstacles: name the real ones. Measures: how you'll know it worked. Then take your team's last sprint backlog and put a "M#" column next to every item. Rows with no Method are the conversation you needed to have.</div>
<p style="font-size:13.5px;color:var(--ink-soft);margin:0 0 12px">For the worked example below, assume this team's V2MOM:<br>
<b>Vision:</b> "Be the most-trusted analytics dashboard for product teams."
<b>Methods:</b> <code style="background:var(--gold-soft);padding:2px 6px;border-radius:4px;font-size:12.5px">M1 — Ship 5 high-quality integrations</code> · <code style="background:var(--gold-soft);padding:2px 6px;border-radius:4px;font-size:12.5px">M2 — Cut time-to-first-insight to < 2 min</code> · <code style="background:var(--gold-soft);padding:2px 6px;border-radius:4px;font-size:12.5px">M3 — Reach enterprise-grade SSO & SCIM (SSO = single sign-on; SCIM = automated user provisioning, the two enterprise procurement gates)</code> · <code style="background:var(--gold-soft);padding:2px 6px;border-radius:4px;font-size:12.5px">M4 — NPS ≥ 50 in mid-market (NPS = Net Promoter Score, a 0–10 "would you recommend" survey)</code></p>
<div class="extable">
<table class="ex">
<thead><tr><th>Column to add</th><th>What it captures</th><th>How you fill it</th></tr></thead>
<tbody>
<tr><td>Feature</td><td>Backlog item</td><td>Existing title</td></tr>
<tr><td>Method #</td><td>Which of the team's 3–5 Methods this feature supports</td><td>M1 / M2 / M3 / M4 — or "none" to surface the orphan</td></tr>
<tr><td>Measure moved</td><td>Which specific Measure from the V2MOM this feature lifts</td><td>Pull from the V2MOM's Measures list — must be named</td></tr>
<tr><td>Value compromised?</td><td>Does this feature push against a stated Value (e.g. Usability, Time-to-market)?</td><td>None / which Value & how — surfaces trade-offs</td></tr>
<tr><td>Obstacle reduced</td><td>Does it remove a named Obstacle from the V2MOM?</td><td>Optional bonus — strengthens the case</td></tr>
<tr><td>Effort</td><td>For ranking among in-scope features</td><td>T-shirt or person-months</td></tr>
<tr><td>In-scope this cycle?</td><td>The verdict</td><td>In (Method trace + Measure) / Re-shape (loose trace) / Out (no Method)</td></tr>
</tbody>
</table>
</div>
<h3 style="font-family:Georgia,serif;font-size:18px;margin:24px 0 8px">Worked example — backlog snapshot against the team's V2MOM</h3>
<p style="font-size:13.5px;color:var(--ink-soft);margin:0 0 12px">Eight features. The filter quickly separates work-that-serves-the-strategy from work-that-merely-exists-on-the-backlog.</p>
<div class="extable">
<table class="ex">
<thead><tr><th>Feature</th><th>Method</th><th>Measure moved</th><th>Value compromised?</th><th>Obstacle reduced</th><th>Effort (PM)</th><th>Verdict</th></tr></thead>
<tbody>
<tr class="top"><td>Add Slack notification integration</td><td>M1</td><td># integrations live</td><td>No</td><td>—</td><td>3</td><td class="score">In</td></tr>
<tr class="top"><td>Bulk <a class="j" href="jargon.html#scim">SCIM</a> user import</td><td>M3</td><td><a class="j" href="jargon.html#sso">SSO</a>/SCIM sign-up rate</td><td>No</td><td>Enterprise procurement gate</td><td>2</td><td class="score">In</td></tr>
<tr class="top"><td>First-run wizard with sample data</td><td>M2</td><td>p50 time-to-first-insight</td><td>No</td><td>Cold-start friction</td><td>4</td><td class="score">In</td></tr>
<tr class="top"><td>In-app <a class="j" href="jargon.html#nps">NPS</a> prompt & feedback widget</td><td>M4</td><td>NPS (response volume)</td><td>Usability — adds friction; mitigate w/ 1-tap dismiss</td><td>—</td><td>1</td><td class="score">In</td></tr>
<tr><td>AI-generated insights panel</td><td>M2 (claimed)</td><td>p50 <a class="j" href="jargon.html#ttfi">TTFI</a> (unverified)</td><td>Usability — adds cognitive load</td><td>—</td><td>8</td><td class="score" style="color:var(--gold)">Re-shape — Method trace too loose</td></tr>
<tr><td>Re-engagement email campaign</td><td>M4 (claimed)</td><td>Retention (not a Measure)</td><td>No</td><td>—</td><td>2</td><td class="score" style="color:var(--gold)">Re-shape — doesn't move a named Measure</td></tr>
<tr><td>Customisable dashboard widgets</td><td>None — "user request"</td><td>—</td><td>—</td><td>—</td><td>4</td><td class="score" style="color:var(--ink-soft)">Out · no Method</td></tr>
<tr><td>Mobile dark mode</td><td>None</td><td>—</td><td>—</td><td>—</td><td>1</td><td class="score" style="color:var(--accent)">Out · vanity</td></tr>
</tbody>
</table>
</div>
<div class="note" style="background:var(--accent-soft);border-left-color:var(--accent);margin-top:18px"><b>The most important reading skill on this page.</b> Notice that V2MOM doesn't ask "is this feature good?" — it asks "<em>does this feature trace upward to something we already wrote down</em>?" That's the entire trick. The framework converts the question "what should we build?" into the easier question "what did we already agree to do?" — and makes orphan features visible as a verdict, not an opinion. The four Re-shape/Out verdicts in the table are not value judgments. They are <em>traceability failures</em>, and they're objective.</div>
<div class="note" style="margin-top:18px"><b>Decision rule.</b> Three gates. <b>(1)</b> Does the feature name a Method it supports? Orphans are out — that's the V2MOM doing its job. <b>(2)</b> Does it move a Measure that's literally in the V2MOM's Measures section? "Adjacent" doesn't count; re-shape until the Measure is exact. <b>(3)</b> Does it compromise a Value? If yes, it must declare the mitigation. Features passing all three enter the ranked build queue, where you score them with <a class="cite" href="rice-framework.html">RICE</a> or run experiments. V2MOM doesn't score features — it tells you which ones earn the right to be scored.</div>
<div class="note"><b>Why V2MOM is on the list anyway.</b> Every other framework on this site assumes you've already agreed <em>what you're trying to do</em>. V2MOM is the artifact that produces that agreement and forces it into writing. Without it, RICE scores a wishlist; with it, RICE scores candidates that all support the same Method.</div>
<footer>
Companion to <a href="impact-saas-companies.html#goal">← SaaS case studies · Goal-laddering</a> · <a href="methodologies-comparison.html">All methods compared</a> · related: <a href="pyramid-of-clarity-framework.html">Pyramid of Clarity</a> (Asana's variant)<br>
<b>Grounded in</b> <a href="https://www.salesforce.com/blog/how-to-create-alignment-within-your-company/">Salesforce's V2MOM post (Benioff, originally 2013, refreshed Dec 11, 2024)</a> and Marc Benioff's <em>Behind the Cloud</em> (Wiley, 2009) / <em>Trailblazer</em> (which the blog draws excerpts from). <b>Verbatim from the Salesforce blog:</b> the V2MOM acronym; the five questions per letter ("What do you want to achieve?", "What's important to you?", "How do you get it?", "What is preventing you from being successful?", "How do you know you have it?"); the Parker Harris / IPO-day American Express envelope origin; "the glue that binds us together"; "If everything is a priority, nothing is"; and that Salesforce now has 50,000+ employees with everyone drafting their own V2MOM annually, published internally for transparency. <b>Paraphrased from public sources:</b> the Salesforce 1999 founding V2MOM contents (multiple slightly differing renderings are in circulation; the wording shown is the most-commonly-cited paraphrase). <b>Added by us, not in Benioff's writings:</b> the "M1/M2/M3/M4" sheet column convention, the "Method trace + Measure moved + Value compromise" three-gate decision rule, the analytics-dashboard worked example (illustrative).<br>
<em>Note: a 2026-05-26 source-verification pass against the Salesforce blog replaced an earlier verbatim attribution ("best-kept secret to the fast growth and excellence") that does not actually appear in the blog (it's commonly attributed to Behind the Cloud rather than this source). The April 1999 / American Airlines flight specifics were also removed from the masthead — those details come from the book, not the cited blog.</em>
</footer>
</div>
</body>
</html>