Dear Andy: Getting Executive Buy in for OKRs  🔗 **Source:** [Dear Andy: Getting Executive Buy in for OKRs](https://mailchi.mp/whatmatters.com/dearandy-july26?e=2bfae2a2b7) > [!note]+ Document Notes > tags: [okrs, goal-setting, executive-buy-in, change-management, organizational-alignment] > author: Billy Casey > source: What Matters (Measure What Matters) > reference: https://mailchi.mp/whatmatters.com/dearandy-july26 > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: Dear Andy: Getting Executive Buy In for OKRs > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [What Matters — OKRs Explained](https://www.whatmatters.com/okrs-explained) - [Google's OKR Playbook](https://www.whatmatters.com/resources/google-okr-playbook) - [Rolling out OKRs](https://www.whatmatters.com/faqs/rolling-out-okrs-objectives-and-key-results) - [How Pinterest Uses OKRs to Achieve Stretch Goals](https://www.whatmatters.com/articles/how-pinterest-uses-okrs-to-achieve-stretch-goals) - [Using OKRs to Streamline and Transform a Nonprofit (YMCA)](https://www.whatmatters.com/articles/using-okrs-to-streamline-and-transform-a-nonprofit) ## 📝 Summary - **What happened.** A reader named Sara wrote to the "Dear Andy" advice column asking for hard-dollar ROI data to convince an apprehensive executive team before rolling OKRs out to 3,500 employees. Columnist Billy Casey, writing for the What Matters team, replies that no such study is known to them but makes a qualitative case for OKRs and recommends a phased, top-down rollout. - **Why it matters.** Executive buy-in is the most common blocker to a large OKR adoption. The column reframes the ask: rather than proving ROI up front, prove value with a small pilot the execs can watch. - **Key stakeholders.** Sara (change agent driving the rollout), her apprehensive executive team, the ~3,500 employees who would eventually adopt OKRs, and What Matters as the advisory brand. - **Risks and tradeoffs.** The reply substitutes brand-name social proof and qualitative benefits for the empirical evidence the reader explicitly requested; the phased approach trades speed of impact for reduced risk and easier buy-in. - **Bottom line.** Don't wait for a study and don't boil the ocean — start with three or four company-wide OKRs at the top and let results earn the executives' confidence. ## 📖 Main Content - **The core argument.** OKRs (Objectives and Key Results) are the best available way to extract maximum value from goals a team is likely already setting. The claimed mechanism is focus plus transparency: OKRs make teams "pinpoint what matters most" and, paired with visibility, put everyone "on the same page … but the right page as well." - **Cadence, not set-and-forget.** A second pillar is rhythm — frequent check-ins and honest grading sessions create commitment and regular chances to course-correct. This is the operational core that separates OKRs from annual goal documents that get filed and forgotten. - **Rollout strategy.** Casey's practical recommendation is to *not* deploy to all 3,500 people at once. Start small, start at the top, with three or four high-level company-wide OKRs. Once leadership sees results firsthand, appetite for expansion grows organically. - **Social proof as evidence substitute.** In place of the requested study, the column offers a roster of successful adopters (Google, Microsoft, Samsung, Yahoo, Uber, LinkedIn, Adobe, Spotify, Netflix, Allbirds) with an explicit hedge that OKRs weren't the sole cause of their success — "a common one," not the only one. - **Terms defined.** *OKR* = a goal-setting framework pairing a qualitative Objective (the "what") with 3–5 measurable Key Results (the "how you know"). *Grading* = periodically scoring KRs (often 0.0–1.0) to gauge progress. *Stretch goal* = an ambitious target where ~70% attainment is considered success. - **Contested claim.** The reader asked for a study proving OKR companies outperform non-OKR companies. The column concedes none is known and pivots to anecdote and framework logic. That concession is honest but leaves the original request unmet. ### 🗒️ Notes - Reader's real problem is political, not analytical: the executives are "a little apprehensive," so the request for dollar figures is a proxy for "help me lower their perceived risk." - The strongest, most reusable idea in the piece is the reframe from *prove ROI first* to *pilot small and let results speak* — it sidesteps the impossible-evidence trap. - The list of famous adopters is correlation, not causation, and the author names that limitation directly, which slightly softens the appeal-to-popularity. - "No set-it-and-forget-it" is the operational heart: check-ins + grading = commitment + course-correction. - Tone is deliberately breezy ("the bees' knees," "discombobulated," "Let us count the ways") — an advice-column register, not a research brief. - Byline note: Billy Casey is described as "a former actor turned writer based in Brooklyn, NY … OKR Shepherd for the What Matters team," which signals the piece is editorial/marketing content, not primary research. ## 📚 References - [OKRs Explained — John Doerr intro series](https://www.whatmatters.com/okrs-explained) - [Google's OKR Playbook](https://www.whatmatters.com/resources/google-okr-playbook) - [OKR culture / teams who align](https://www.whatmatters.com/faqs/okr-culture) - [Weekly OKR grading check-in](https://www.whatmatters.com/faqs/weekly-okr-grading-check-in/) - [How to grade OKRs](https://www.whatmatters.com/faqs/how-to-grade-okrs) - [Rolling out OKRs](https://www.whatmatters.com/faqs/rolling-out-okrs-objectives-and-key-results) - [Getting Team Buy-In for OKRs](https://www.whatmatters.com/faqs/introducing-okrs-to-team) - [How Pinterest Uses OKRs to Achieve Stretch Goals](https://www.whatmatters.com/articles/how-pinterest-uses-okrs-to-achieve-stretch-goals) - [Using OKRs to Streamline and Transform a Nonprofit (YMCA)](https://www.whatmatters.com/articles/using-okrs-to-streamline-and-transform-a-nonprofit) - [Allbirds mission statement & OKRs](https://www.whatmatters.com/articles/okrs-mission-statement-allbirds-sustainability) ## 🗣️ Paraphrase - Sara is beginning a 3,500-person OKR rollout and wants a study quantifying, in dollars, how much OKR-using companies outperform non-users, because her execs are nervous. - Casey replies that he knows of no such study but that aligned teams reliably beat their own expectations, and points to a roster of well-known OKR adopters while noting OKRs weren't the sole cause of their success. - His case for OKRs: they force focus on what matters, add transparency so everyone works the right priorities, and replace set-and-forget goals with frequent check-ins and honest grading. - His practical advice: don't roll out to everyone at once; begin with three or four company-wide OKRs at the top, and let firsthand results convince skeptical leaders to expand. - He closes by directing Sara to the "stories" page of real-company examples to reassure and inspire the executive team. ## 📰 Newsletter - **The evidence you want may not exist — so change the ask.** This week's "Dear Andy" fields a classic adoption question: how do I prove OKRs pay off before we commit? The honest answer — there's no tidy study — is oddly freeing. Swap "prove the ROI" for "run a small pilot the boss can watch," and the political knot loosens. WordPress teams shipping quarterly goals will recognize the pattern: nobody green-lights the whole roadmap on a spreadsheet; they green-light it after the first release lands. Start with three or four company-wide objectives, keep the check-ins honest, and let results do the persuading. Worth a read if you're introducing any new planning ritual to a wary leadership team. ## ✅ Action Items #### DevRel - Developer advocacy: frame new-process pitches (OKRs, RFCs, planning rituals) as small watchable pilots rather than up-front ROI proofs. - Education: build a "starter OKR" workshop capped at 3–4 company-wide objectives for teams adopting the framework. - Developer experience: template a lightweight weekly check-in + grading doc so cadence is turnkey. - Developer marketing: collect internal before/after case studies as the social proof leadership actually trusts. - Community management: survey adopting teams after one cycle to capture firsthand-results testimony. - Internal/external/cross-project: align on a single grading scale (0.0–1.0) before rollout to avoid metric drift. #### OSPO - Policy & Governance: set a charter clause that new org-wide processes pilot at the top before mandating org-wide. - License Compliance: Not applicable to this source — the column is about goal-setting, not licensing. - Security Management: Not applicable to this source — no security surface in an advice column on OKRs. - Software Inventory: Not applicable to this source — no SBOM or inventory content. - Developer Support: offer consultation hours for teams standing up their first OKR cycle. - Community Engagement: Not applicable to this source — no upstream funding or operator-agreement content. - Strategic Alignment: use OKRs as the executive-reporting spine, starting with three or four company-wide objectives. #### Community - Maintainers: run a quarterly "objectives clinic" to keep goals to a focused few. - Contributors: pair new contributors with a single measurable key result to build the habit. - Sponsors: report progress via graded KRs for transparent milestone tracking. - Ecosystem: Not applicable to this source — no cross-project incident content here. #### WordPress - Core: pilot OKRs on one release cycle before proposing project-wide adoption. - Core Performance: express perf goals as measurable KRs (e.g., LCP targets) inside a single objective. - Core AI: Not applicable to this source — no AI-guardrail content in the column. - **Core Program Team:** adopt frequent check-ins and honest grading as the coordination ritual. - Mobile / Playground / TV / Photos: Not applicable to this source — no product-specific content. - Community: template a company-wide OKR starter kit for Make teams. - Training: build a lesson path on writing objectives vs. key results. - Marketing: gather firsthand results stories as adoption narratives. - Support / Design / Documentation: Not applicable to this source — no direct tie beyond generic goal-setting. - Polyglots / Accessibility / Meta / CLI / Hosting / Tide / Openverse / Themes / Plugins: Not applicable to this source — the column is framework-agnostic advice. #### The WPCC - Programs: fund a small OKR pilot cohort before scaling stipends to the full program. - Projects: Not applicable to this source — no governance-clinic content. - Funding experiments: tie milestone payouts to graded key results. ### FAIR - Technical independence: Not applicable to this source — no metadata/provenance content. - Policies and covenants: Not applicable to this source — no funding-transparency content. - Productized governance artifacts: adapt the "three or four company-wide OKRs" pattern into a scorecard template. ## 🧪 Hypotheses - Phased, top-down OKR rollouts (starting with 3–4 company-wide objectives) achieve higher sustained adoption than simultaneous org-wide launches. - Executive apprehension about OKRs drops more after a visible small pilot than after presentation of external ROI studies. - Teams that pair check-ins with honest grading course-correct faster than teams that set goals without a grading cadence. - Social proof (named adopter logos) moves skeptical executives less than an internal before/after case study. - Companies requesting hard-dollar OKR ROI data before adoption are, in fact, surfacing a risk-tolerance concern rather than an evidence gap. - Limiting an initial rollout to a small number of objectives improves focus and measured attainment versus launching with many. ### 📊 Methodology - Run a controlled comparison across business units: phased top-down rollout vs. simultaneous org-wide rollout; measure adoption, attainment, and retention of the practice at 2 and 4 quarters. - Pre/post executive sentiment survey (Likert) administered before rollout, after an external-evidence briefing, and after a live pilot, to isolate which intervention shifts apprehension. - Cohort study correlating grading cadence (weekly/monthly/none) with course-correction frequency and KR attainment. - A/B test persuasion assets: adopter-logo deck vs. internal case study, measuring executive commitment to expand. - Content-analyze inbound "Dear Andy"-style questions to test whether ROI requests co-occur with stated apprehension. ### ❓ Questions - What is the smallest pilot that still produces executive-convincing results? - Does the optimal number of initial company-wide OKRs vary by org size (3,500 vs. 350)? - How honest is "honest grading" in practice, and what governance keeps it honest? - Which single metric best predicts whether an OKR rollout will stick? - At what point does adding more OKRs erode the focus benefit the framework promises? ### 🔮 Future Research - A genuine longitudinal study comparing matched OKR-adopting and non-adopting firms — the exact gap the column concedes. - Research on the causal weight of OKRs within multi-factor company success (isolating from talent, capital, market). - Study of rollout sequencing (top-down vs. bottom-up vs. hybrid) on adoption durability. - Investigation of grading-scale design and its effect on gaming vs. genuine stretch behavior. ### 💡 Implications - **Practice:** Change agents should lead with a pilot, not a business case, when leadership is nervous. - **Policy:** Governance can encode "pilot-before-mandate" as a default for new org-wide processes. - **Security:** Not applicable to this source — no security dimension. - **Education:** Curricula should teach the objective-vs-key-result distinction and the grading cadence, not just the concept. - **Funding models:** Milestone funding maps cleanly onto graded key results. ### 🧠 Learning Styles Assessment - Reading level estimate: approximately Flesch-Kincaid Grade 9–10 (Flesch Reading Ease ~55–60) — conversational but with some long, clause-heavy sentences. #### 👀 Visual learners - Present: decorative header images and CTA graphics; no explanatory diagrams. - Improve: add a phased-rollout diagram (top → teams) and a sample OKR scorecard. #### 🔊 Aural learners - Present: none in the email itself, though the brand links an OKRs video series. - Improve: offer a 2–3 minute audio version of each column. #### 🗣️ Verbal learners - Present: strong — analogies ("bees' knees"), plain-language framing, defined pivot. - Improve: add a short glossary (Objective, Key Result, grading, stretch goal). #### 🧩 Kinesthetic learners - Present: links to examples and templates ("get examples," "stories" page). - Improve: include a fill-in-the-blank first-OKR worksheet. #### 🧠 Logical learners - Present: implicit cause→effect (focus + transparency → alignment). - Improve: a decision tree for "roll out to all vs. pilot at top." #### 🧑‍🤝‍🧑 Social learners - Present: the advice-column format models a Q&A exchange; "Send your question" CTA. - Improve: add a community thread of rollout stories. #### 🧘‍♀️ Solitary learners - Present: self-paced reading with links to explore alone. - Improve: reflection prompts on the reader's own executive concerns. #### 🌿 Naturalistic learners - Present: Allbirds sustainability example linked. - Improve: frame OKR lifecycle (plan → check-in → grade → adapt) as an iterative cycle. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: some heading structure (h2/h3/h4) in the email HTML. - Improve: decorative images carry empty `alt=""`, which is fine, but CTA images lack descriptive alt text. #### Keyboard navigation - Present: standard email links are keyboard-reachable. - Improve: ensure focus order in the rendered email is logical across image-link stacks. #### Contrast and readability - Present: standard body text on light background. - Improve: verify CTA image-text meets 4.5:1; image-based text can't be resized. #### Text resizing and reflow - Present: Mailchimp responsive template. - Improve: replace image-embedded text with live text to survive 200% zoom. #### Media and captions - Present: no inline video/audio in the email. - Improve: caption the linked OKRs video series and provide a transcript. #### Forms and interactions - Present: external Airtable question form and Mailchimp preference links. - Improve: confirm the Airtable form has labeled fields and visible error handling. #### Standards reference - Maps to WCAG 2.2 AA: 1.1.1 (non-text content), 1.4.3 (contrast), 1.4.4 (resize text), 1.4.5 (images of text). ### 🌍 DEIB Assessment #### Cultural breadth - Present: adopters span consumer, enterprise, and nonprofit (YMCA); mostly US/global-brand examples. - Improve: add non-US and small-org examples; the reader's 3,500-person org may not resemble Google. #### Inclusive language - Present: gender-neutral, friendly, jargon defined in context. - Improve: expand a glossary for non-native English readers; idioms ("bees' knees," "discombobulated") may not translate. #### Neurodiversity support - Present: short paragraphs, consistent structure. - Improve: reduce idiom density; add headings within the reply for scannability. #### Representation - Present: named author bio; brand voice. - Improve: feature varied practitioner voices beyond the single columnist persona. #### Psychological safety - Present: warm, reassuring tone that legitimizes the reader's uncertainty. - Improve: acknowledge that OKRs can be misused as surveillance; note guardrails for honest grading. ### ✅ Logical Validity #### Strong reasoning - **Analogical/pragmatic (rollout advice):** the recommendation to "start small and start at the top" is a sound risk-reduction analogy to piloting — it reduces blast radius and creates observable evidence. Strong because it directly addresses the execs' apprehension rather than the literal ROI request. Clarify by attaching a concrete success threshold for the pilot. - **Honest concession (evidence gap):** admitting no known study exists strengthens credibility and avoids fabricating data. Clarify by pointing to what *would* count as evidence (an internal pilot's results). #### Fallacies - **Appeal to popularity / bandwagon:** the roster of famous adopters ("Google, Microsoft, Samsung … are all wildly successful organizations that have used OKRs") implies OKRs cause success. Weakness: correlation without controls. Fix: the author partly self-corrects ("not the only factor … but a common one"); strengthen by citing a controlled comparison or an internal before/after. - **Ignoratio elenchi (missing the point) / red herring:** the reader asked for a dollar-quantified study; the reply pivots to qualitative benefits and anecdotes. Weakness: the explicit request goes unanswered. Fix: name the reframe openly ("here's why a pilot beats a study for your situation") so the pivot is transparent, not evasive. - **Hasty generalization:** "the results almost always are [revolutionary]" overstates from selected success stories. Fix: qualify with conditions under which OKRs underdeliver (poor grading discipline, too many objectives). #### Tone of voice - Warm, witty, reassuring advice-column register: "Let us count the ways," "the bees' knees," "keep us posted on your OKR journey." Persuasive and friendly, occasionally at the expense of rigor. ### 🛡️ DARVO Analysis - Deny: Mild — the piece denies the premise's feasibility ("We aren't aware of a study like the one you mention") but does so honestly rather than to dodge accountability. - Attack: Not applicable to this source — no accuser and no credibility attack; the exchange is cooperative advice. - Reverse victim/offender: Not applicable to this source — no victim/offender dynamic exists in a goal-setting advice column. - Emotional cues/rhetoric: reassurance-driven ("help assuage some of those executives' fears"), using warmth and social proof to lower anxiety, not to deflect blame. ## 🎯 Conclusion - **Bottom line.** There's no known study proving OKR companies outperform non-OKR companies, so stop treating that as the gate. The persuasive move is to pilot small — three or four company-wide OKRs at the top — and let firsthand results convince apprehensive leadership. - **Next steps for readers.** Reframe the executive ask from ROI-proof to watchable pilot; define a concrete success threshold; install a weekly check-in and honest grading cadence; capture the pilot's before/after as the internal case study that external logos can't provide; expand only after leadership sees results. ## 🔄 Refactor Appendix — Dear Andy: Getting Executive Buy In for OKRs > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. > > Konik claim-header rules: present tense, declarative, ≤10 words when > possible, searchable, unique, mirrors annotation focus if present. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) #### [H1] Pilot OKRs at the top before org-wide rollout > [!quote] ID:rw_01kwz6q3qagyr3zn4jtcrv7fwc > We recommended starting small and starting at the top. Three or four high-level, company-wide OKRs are the best way to get started. **Context & use**: - Reply paragraph advising against a simultaneous 3,500-person launch. - The strongest reusable move: reduce blast radius and create observable evidence for skeptics. **Tags**: #xref #aphorisms **Highlight**: [view highlight](readwise://read/01kwz6q3qagyr3zn4jtcrv7fwc) <!-- atomicity: 1 idea ✓ --> #### [H2] Check-ins and grading replace set-and-forget goals > [!quote] ID:rw_01kwz6q3qagyr3zn4jtcrv7fwc > there’s no “set it and forget it” with OKRs, because **Context & use**: - Names the operational core distinguishing OKRs from annual goal docs. - Cadence (check-ins + honest grading) is what creates commitment and course-correction. **Tags**: #xref **Highlight**: [view highlight](readwise://read/01kwz6q3qagyr3zn4jtcrv7fwc) <!-- atomicity: 1 idea ✓ --> #### [H3] Adopter logos are correlation, not proof > [!quote] ID:rw_01kwz6q3qagyr3zn4jtcrv7fwc > We’re not saying OKRs were the only factor in these companies’ success, of course, but they certainly were a common one. **Context & use**: - The author self-limits an appeal-to-popularity move. - Useful as a reminder to hunt for internal before/after evidence over borrowed brand success. **Tags**: #xref **Highlight**: [view highlight](readwise://read/01kwz6q3qagyr3zn4jtcrv7fwc) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] Buy-in comes from a watchable pilot, not up-front proof **Claim** (one sentence, Courtney's voice): When leadership is apprehensive about a new process, a small visible pilot earns commitment faster than external ROI evidence ever will. **Evidence pointer**: [[#H1]] **Scope & conditions**: Holds when a pilot can produce observable results within a quarter; breaks when the process only pays off at full scale or results aren't visible to decision-makers. **Links**: - [[Change management]] — because extends - [[Evidence-based decision making]] — because contrasts on {proof timing} - [[OKR rollout sequencing]] — because applies-in {org-wide adoption} <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Does the ideal count of initial company-wide OKRs scale with org size? — https://mailchi.mp/whatmatters.com/dearandy-july26 #fleeting #inbox - [F2] Find or build the missing controlled study comparing OKR vs. non-OKR firm performance. #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Draft a one-page "pilot-not-proof" template for pitching new processes to wary leadership — #things - [ ] Template a weekly OKR check-in + grading doc for adopting teams — #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Dear Andy Getting Executive Buy in for OKRs.md|Dear Andy: Getting Executive Buy in for OKRs by mailchi.mp]] ## Highlights - We’re not saying OKRs were the only factor in these companies’ success, of course, but they certainly were a common one. ([View Highlight](https://read.readwise.io/read/01kx43dyb213x8xp6ty7qt96m3)) - Note: Author self-limits the appeal-to-popularity / adopter-logos argument. - Tags: atom/literature/h3 - there’s no “set it and forget it” with OKRs, because ([View Highlight](https://read.readwise.io/read/01kx43ds9y0zwt2wmmz5p49az1)) - Note: Names the operational core — check-ins + grading cadence. - Tags: atom/literature/h2 - We recommended starting small and starting at the top. Three or four high-level, company-wide OKRs are the best way to get started. ([View Highlight](https://read.readwise.io/read/01kx43dk86y7v0fhyt9yb01zbr)) - Note: Core reusable move: pilot at the top instead of an org-wide launch. - Tags: atom/literature/h1 - once higher-ups have a chance to see the results of OKRs firsthand, they’ll be more ready to take things to the next level. ([View Highlight](https://read.readwise.io/read/01kx43e2s0v5ajwj5vx7xnn7tr)) - Note: Buy-in mechanism: firsthand pilot results earn expansion. - Tags: atom/literature/h6 ## Links - [[Instincts Are Reliable Ideas Are Not So Test Small Bets on Proven Foundations]] — applies-in: a bounded pilot tests the change before a 3,500-person rollout. - [[Enterprise Adoption Validates a Platform Through Authority Transfer]] — contrasts: executive sponsorship begins adoption, but observed results must earn broader authority transfer.