# Grove's 90-Minute Meeting: Why 9-Day Cadence Beats 35 Days

Helena Frost · August 25, 2026

> Grove's 90-Minute Meeting: Why 9-Day Cadence Beats 35 Days. A substantial tally of person-hours a year — that is what a seven-perso...

| Takeaway | Detail |
| --- | --- |
| Control comes from forced decisions, not meeting count. | Folding the pipeline council, the forecast call, and the ops review into a single 90-minute review cuts the standing-forum load by roughly 40% while forcing every agenda line to close with a named owner and a dated decision. |
| Two names on a number means nobody owns it. | The accountability chart's no-shared-ownership rule — Alice and Bob both owning it means nobody owns it — is why the review tracks twelve numbers with exactly one owner apiece; in crowded forum stacks, unowned metrics can absorb up to 60% of review time without producing a single decision. |
| A nine-day replan clock beats riding out a 35-day cycle. | Replanning costs drop when the structural calendar stays stable, so a fixed nine-day loop turns each replan into a check of what changed — reclaiming roughly 40% of the coordination time that dependency-driven Gantt files lose when one department's pivot forces a whole-file rebuild. |
| A weekly scorecard surfaces drift while the quarter can still absorb it. | The scorecard runs on a weekly rhythm as core framework vocabulary alongside rocks and the issues list; because every leader enters with the same current picture instead of a stale plan, corrections land mid-cycle and roughly 60% of the usual quarter-end scramble never forms. |

A substantial tally of person-hours a year — that is what a seven-person leadership team burns sitting through five extra weekly forums before a single decision changes the plan. The meetings feel like oversight. Mostly they are theater: status recitation, forecast readings, a Gantt chart last updated three weeks earlier pulled up live on screen. None of it moves the plan, because none of it forces a decision.

The contrarian claim is blunt: delete the pipeline council, the forecast call, and the ops review. Replace the lot with one 90-minute review, twelve owned numbers, and a nine-day replan clock. Control does not scale with meeting count; it comes from forced decisions — an agenda where every line ends with a name and a date, run on a cadence fast enough to catch drift while there is still quarter left to correct it.

The replacement mechanics are unglamorous: a weekly scorecard so every leader enters with the same picture instead of a stale plan, an accountability chart enforcing the rule that two owners mean no owner, and replans priced as quick checks of what changed rather than whole-file rebuilds. Forum load drops by roughly 40%, yet oversight tightens — because the hours that remain are spent deciding, not reporting.

![Grove's 90-Minute Meeting](https://static.mm-ais.com/article-images-ai/grove-s-90-minute-meeting-why-9-day-cade-ai-f3afa5a0.jpg)

## Anatomy of the 90

Andy Grove's argument in "High Output Management" was never that executives should meet less — it was that meetings are the medium of managerial work, and the only question worth asking is what each one manufactures. The 90-minute review runs as a closed loop that works because every stage terminates in a hard artifact, not conversation: the weekly review detects variance, the 12-metric scorecard localizes it to one accountable owner, and the 9-day replan converts the red into a re-versioned plan. Detection without localization is venting; localization without a replan clock is theater. According to MIT Sloan Management Review's 2025 finding (reported by Actiosoftware), companies pairing structured strategic planning with agile monitoring loops such as OKRs and PDCA cycles are 40% more effective at adapting to market changes — loops pay when each handoff produces a file.

The agenda enforces that artifact discipline minute-by-minute:

| Minutes | Segment | Operating rule |
| --- | --- | --- |
| 0–10 | Scorecard sweep | Greens are never spoken aloud |
| 10–25 | Yellow explanations | Restricted to the owning executive; yellows only |
| 25–75 | Structured debate | Reds only; conflict over variance fills the time |
| 75–85 | Decisions recorded | Every call carries a named owner and a date |
| 85–90 | Pre-read check | Confirm next week's pre-reads before adjourning |

A mandatory one-page pre-read circulates 24 hours ahead, so zero minutes are spent on status reporting — the room arrives having already read, and the design buys 50 uninterrupted minutes of argument about what is actually broken.

| Tier | Metrics and green bands |
| --- | --- |
| Growth (4) | Net-new ARR per month; pipeline coverage ≥3.5x; win rate; qualified pipeline created |
| Efficiency (4) | Burn multiple ≤1.5x (David Sacks' formula: net burn ÷ net-new ARR); magic number ≥0.75; CAC payback ≤18 months; gross margin held above a band recalibrated annually |
| Durability (4) | NRR held above a recalibrated band; logo retention likewise; runway ≥24 months; hiring-plan adherence within a set tolerance |

Every metric carries exactly one named owner — two names on a metric means nobody owns it — and the red/yellow/green bands reset annually so a survived crisis cannot calcify into a permanent baseline.

The 12-metric ceiling is inherited, not invented. Kaplan and Norton's original guidance in "The Balanced Scorecard — Measures That Drive Performance" (HBR, 1996) holds that an executive scorecard should stay under roughly 20 measures; beyond that, attention fragments and ownership blurs. Twelve is the deliberate Series B subset of that discipline — four growth, four efficiency, four durability — sized so there is room for nothing unowned.

| Replan clock | Actor | Required output |
| --- | --- | --- |
| Day 0 | System | Trigger logged: any metric red in two consecutive reviews |
| Days 1–3 | Owning VP | Diagnosis memo, maximum two pages |
| Days 4–6 | Owning VP | Exactly two countermeasure options with cost and headcount deltas |
| Days 7–8 | CFO | Stress-test of both options against runway and Rule-of-40 trajectory |
| Day 9 | CEO | Picks one option in a 45-minute decision session; revised plan ships as a new version |

What separates this cadence from status theater is what it leaves behind: three audit artifacts. The one-page scorecard (12 rows, trend arrows, RAG bands), the two-page diagnosis memo, and a plan changelog versioned like software — "Plan v3.2 — May 9, 2026" — so any board member can reconstruct what changed and why without attending a single session. Patrick Lencioni's "Death by Meeting" supplies the underlying principle: tactical meetings work only when conflict over variance, not reporting, fills the time. This is also where the ceremony myth dies. The belief that reaching Series B means importing public-company rhythm — monthly business reviews, quarterly ceremonies, annual planning marathons — mistakes paperwork for judgment. A QBR manufactures slides; this loop manufactures a re-versioned operating plan every time a number stays red.

![Anatomy of the 90 — Grove's 90-Minute Meeting](https://static.mm-ais.com/article-images-ai/grove-s-90-minute-meeting-why-9-day-cade-ai-6614c4e1.jpg)

## The Receipts

Nearly 23 hours. That is what Leslie Perlow, Constance Hadley, and Eun found when they audited executive calendars for "Stop the Meeting Madness" (Harvard Business Review) — and most of the senior managers they surveyed called those meetings unproductive and inefficient. Set that baseline against the roughly-half reduction this operating system promises, and the claim reads as conservative, not aggressive. The mechanism isn't meeting-hating discipline; it's consolidation. When one weekly review replaces the forum stack, most of those 23 hours don't get run better — they stop being scheduled.

The upside receipt comes from McKinsey's "decision making in the age of urgency" survey: managers spend a large share of their working time making decisions and report that more than half of that time is used ineffectively. At Series B, ineffectiveness usually means latency — a decision that needed one room and instead drifted across monthly forums until nobody remembered why it mattered. Forcing it inside a fixed weekly window is how "correct decisions in under two weeks" stops being a slogan: the container is the deadline.

Then the viability receipt — and it kills the founding myth of B-stage bureaucracy: that scale demands ceremony. EOS Worldwide reports adoption across a large base of companies, and its flagship Level 10 leadership meeting runs exactly 90 minutes on a fixed weekly agenda. Flag that as a vendor-reported figure if you like; it is still market-scale evidence that a single 90-minute weekly executive meeting sustains an operating company. Nobody stacking monthly business reviews and annual planning marathons onto a mid-sized company holds a comparable adoption receipt for the ceremony side of the ledger.

OpenView's 2023 SaaS Benchmarks Report fixes the band the scorecard must police: median net revenue retention sitting just above the flat line, with top-quartile companies well clear of it. Read that band carefully — the distance between median and decay is a few points wide. NRR sitting red twice consecutively at that margin isn't sampling noise; it's the leading edge of a compounding problem, which is exactly why the two-strike trigger fires a replan rather than a discussion item.

The last receipt is the gate. According to APQC's finance benchmarking, top-quartile teams close their monthly books in about 4.8 days while bottom-quartile teams take 10-plus. The 9-day replan clock runs on validated numbers; if your close takes longer than the clock, you cannot honestly commit to shipping a revised plan inside it — the data won't exist yet. Slow-close organizations don't adopt this cadence on faith; they fix the close first, because the cadence presumes the spine.

These receipts are not equal, and in 2026 the sequencing matters more than the pile. Run one audit before you adopt: pull last week's total executive meeting hours (against the 23-hour baseline), last month's days-to-close (against 4.8 versus 10-plus), and trailing NRR (against the median-to-top-quartile band). If your close exceeds ten days, build the data spine before the scorecard — five of these receipts argue for the system, but the sixth decides whether you're allowed to run it.

| Receipt | Figure | What it licenses |
| --- | --- | --- |
| Perlow, Hadley & Eun, HBR | ~23 hrs/week in meetings; most senior managers rate them unproductive | Baseline burden the single review retires |
| Doodle State of Meetings | The aggregate annual cost of poorly organized meetings | Sprawl priced; cadence carries near-zero marginal cost |
| McKinsey urgency survey | Large share of time deciding; more than half ineffective | Fixed window converts decision time into decisions |
| EOS Worldwide | Adoption across a large base of companies; Level 10 = exactly 90 min weekly | Sustainability proof at market scale |
| OpenView SaaS Benchmarks 2023 | Median NRR just above flat; top quartile well above | The band the scorecard polices |
| APQC finance benchmarking | Top-quartile close ~4.8 days; bottom quartile 10+ days | Feasibility gate for the 9-day replan clock |

Roughly thirty-five days against nine: that is the entire argument between the three executive operating systems competing for a 2026 Series B command center. An operating system is ultimately an allocation of decision rights — who is forced to move, and how fast, when a metric turns red. Lay the contenders side by side — the 90/12/9 weekly review, the classic public-company MBR/QBR rhythm, and dashboard-only async (a shared Looker board plus Slack threads) — and the trade-offs stop being a matter of taste.

![The Receipts — Grove's 90-Minute Meeting](https://static.mm-ais.com/article-images-pixabay/grove-s-90-minute-meeting-why-9-day-cade-f0745c03.jpg)

## Three Operating Systems, One Winner

The 90/12/9 cadence wins outright on the two columns that compound: latency (nine days or fewer, versus roughly thirty-five-plus for an MBR cycle that catches the miss at month-end, debates it weeks later, and ships the revised plan after the next quarterly event) and executive hours (about six per month versus twelve to twenty). As the Practicetestgeeks comparison frames it, the team that can pivot in a two-week sprint beats the team locked into a twelve-month roadmap, because plans go stale while markets shift. Latency is not a convenience feature here; it is the product.

| Operating system | Decision latency (red metric → revised plan) | Executive hours per month | Artifact trail | Characteristic failure mode |
| --- | --- | --- | --- | --- |
| 90/12/9 weekly review | ≤9 days | About 6 | Weekly scorecard snapshots plus versioned operating plans | Definition creep — metrics kept green by loosening thresholds |
| Classic MBR/QBR rhythm | Roughly 35+ days | 12–20 | Formal monthly packs, board decks, QBR binders | Decisions batched until the forum; problems age in queue |
| Dashboard-only async | Unbounded — no revision deadline exists | Near zero scheduled | Slack threads and dashboard links that decay | Ownership diffusion — everyone saw the red, nobody owned the fix |

A verdict asserted, though, is a verdict dismissed — so here is the rubric behind it, with each system rated 1–5 per criterion and weighted:

Note what the rubric exposes: MBR/QBR wins the auditability column alone — formal monthly packs remain unmatched as evidence artifacts — and still loses the weighted total by more than two points. The winner is rubric-dependent, not asserted; shift auditability to a 40% weight and the ranking genuinely flips. That honesty matters, because both losing systems hold legitimate home turf.

| Criterion | Weight | 90/12/9 | MBR/QBR | Dashboard-only |
| --- | --- | --- | --- | --- |
| Decision latency | 40% | 5 | 1 | 3 |
| Executive hour cost | Second-highest | 5 | 2 | 5 |
| Auditability | Mid-weight | 3 | 5 | 1 |
| Fit for B-stage volatility | Lowest | 5 | 2 | 3 |
| Weighted total | 100% | 4.60 | 2.20 | 3.10 |

The migration ruling follows directly: teams currently on MBR/QBR should collapse forums in a single quarter — kill the pipeline council, the forecast call, and the ops review in week one, absorbing their content into pre-reads — rather than run a hybrid. Dual-running doubles meeting load during the transition and reliably kills the new cadence before it compounds. According to Plandisc, quarterly replanning costs drop significantly when the structural calendar stays stable; a hybrid keeps two calendars churning, which is exactly the instability the cutover exists to remove. One quarter, one clean break.

Before defending your current forum, run your own calendar through the rubric above — if you cannot name which column it wins, you are paying for ceremony.

Abraham Wald's bombers are the correct mental model for this section. During World War II, analysts wanted to armor the spots on returning aircraft that showed the most bullet damage; Wald argued the armor belonged where the returners were clean, because the planes hit there never made it home. Every published account of a company collapsing its executive forums into one weekly review is a returning aircraft. The founding teams that adopted the cadence, found it brittle, and quietly rebuilt their monthly ritual never publish the post-mortem — so the surviving case material flatters the system by construction.

| Your situation | Ruling | Why |
| --- | --- | --- |
| Series B, unregulated | Adopt 90/12/9 | ≤9-day latency at about 6 executive-hours monthly |
| Regulated industry, or scaled well past Series B in revenue and headcount | Keep the formal monthly pack | Statutory reporting outranks cadence efficiency |
| Earlier-stage than Series B and under 20 people | Stay dashboard-only | One room; meetings add ceremony, not decision rights |
| Currently running MBR/QBR anywhere above | Cutover in one quarter | Hybrids double load and die before compounding |

Three defects limit how far the headline results travel. First, the calendar evidence is self-reported: executives reconstruct their own meeting hours from memory and assistant logs, and both undercount consistently. Second, adoption is confounded with founder attention — a CEO disciplined enough to enforce a twelve-metric scorecard every week would likely outperform under almost any format, so the cadence absorbs credit that belongs to the enforcement. Third, there is no matched control. The comparisons are before-and-after inside a single firm, which tangles the operating system's effect with whatever else changed that year: a new CFO, a repricing, a market turn. Read the speed-to-decision and load-reduction figures as directional, not causal.

![Three Operating Systems, One Winner — Grove's 90-Minute Meeting](https://static.mm-ais.com/article-images-pixabay/grove-s-90-minute-meeting-why-9-day-cade-b21dd44f.jpg)

## What the Data Doesn't Tell You

The spread across cases is wider than any summary conveys. The cadence held comfortably in most documented adoptions to date; strain appeared in predictable places — teams whose scorecards leaned on freshly instrumented metrics, where early reds often reflect telemetry gaps rather than business deterioration; firms with quarterly board rhythms, where the weekly drum must be translated upward every third month; and volatile product lines that generate genuine trigger events often enough that replanning starts to feel like permanent churn. Where the scorecard was mature and reds were rare, the system looked almost boring. That boringness is the point — and it is exactly why averages mislead a founder evaluating the model.

The rule breaks at identifiable edges, and none of them argue for going back. An active crisis — a security incident, a key-account blowup — legitimately spawns an event-driven war room; the canonical rule replaces recurring forums, and a room that dissolves when the incident ends is not a competing cadence. A lagging metric sitting red twice through a seasonal trough fires the trigger on noise; the repair is scoping that replan to leading indicators, not skipping it. And any number reviewed weekly becomes a target — Goodhart's law — so expect periodic gaming; the countermeasure is re-versioning the suspect metric's definition at the next scheduled replan. Every failure mode is repaired inside the ninety-minute container. Nothing here rehabilitates the belief that reaching Series B means importing public-company ceremony: the fix for a brittle scorecard is a stricter scorecard, never a slower meeting.

Treat the thesis as holding by default and this table as the pre-adoption audit: walk your current scorecard against each row and pre-decide the repair for every one you fail. If you cannot fill in the third column for your own company, the honest conclusion is not that the cadence is wrong — it is that your scorecard isn't ready to carry it. Tighten the definitions first, then collapse the forums.

Every adoption statistic behind this operating system shares a single provenance problem: it was published by the party selling the system. Vendor white papers and consultancy case libraries supply the success stories, and as of early 2026 no independent longitudinal study links the 90-minute weekly format to Series B survival or follow-on funding rates. That makes the cadence a plausible mechanism, not a proven causal treatment — you are adopting a well-argued hypothesis about executive attention, and it deserves the skepticism you'd give any unreplicated result. The old "scale demands ceremony" doctrine earned its death; its leaner replacement has not yet earned canonization.

| Boundary condition | What typically happens | Move that keeps the cadence intact |
| --- | --- | --- |
| Metric in its first quarter of clean data | Telemetry gaps fire spurious reds | Flag it provisional; exclude from the two-red trigger until a trend is established |
| Lagging metric red through a seasonal trough | Replan gets built on seasonal noise | Run the replan on schedule; scope it to leading indicators |
| Live incident — outage, security, key-account loss | Pressure to convene daily exec standups | Allow the war room; dissolve it at resolution — recurring forums stay collapsed |
| Quarterly board cycle | Weekly drum needs translating upward | Generate the board pack from the same scorecard; never build a parallel deck |
| Gaming emerges on a reviewed metric | The number improves; the business doesn't | Re-version the metric's definition at the next scheduled replan |
| Decisions migrate to hallways | A shadow cadence regrows | Log hallway calls into the next review; repeats signal a missing metric |

A fixed twelve-number scoreboard also changes what your team optimizes. When pipeline coverage must hold inside the 3.5x band, the cheapest way to keep the ratio green is admitting unqualified deals — the number stays compliant while the funnel rots, and the damage resurfaces roughly two quarters later as degraded win rate and NRR. Goodhart's law is not a footnote here; it is the predictable failure mode of any metric promoted into a target. The scorecard measures quantity faithfully and detects quality erosion only after the quality has been spent.

![What the Data Doesn't Tell You — Grove's 90-Minute Meeting](https://static.mm-ais.com/article-images-pixabay/grove-s-90-minute-meeting-why-9-day-cade-1c7d7bd5.jpg)

## What the Cadence Can't See

The bands themselves carry someone else's business model. Efficiency thresholds like the oft-cited 0.75 magic-number floor were calibrated largely on mature, velocity-driven SaaS motions. A bottom-up enterprise sale running eighteen-month cycles can be genuinely healthy at 0.5 for four consecutive quarters — a rigid red band flags that health as failure purely through motion mismatch. Re-derive any inherited threshold against your own cycle length and deal profile before the first review, or your opening red may be an artifact rather than a symptom.

Concede the exogenous limit too. A 2026 demand shock — rate moves, or AI-driven repricing compressing seat-based ARR — can turn half the scorecard red in one week for reasons no replan controls. The nine-day revision clock accelerates acknowledgment and resource reallocation; it is response speed, not a hedge against market-level variance. Simultaneous cross-functional reds should be read as weather before anyone reads them as execution.

The format also presumes a precondition the adoption data ignores: a six-to-eight-person executive team that accepts pre-reads and cedes airtime. In founder-dominated cultures where the CEO re-litigates settled items, the fifty-minute red-debate block collapses into status defense regardless of agenda design. The cadence amplifies existing trust levels; it does not manufacture them. Deploy it on a low-trust bench and you reproduce the meetings without the decisions.

Finally, the arithmetic of refresh rates. NRR, CAC payback, and logo retention resolve on quarterly or slower windows while the review runs weekly, so roughly half the scorecard is effectively static between quarters — the heartbeat outruns its own durability instruments. According to Profit.co's comparison of organizational agility and operational efficiency, one documented pattern anchors quarterly replanning against multi-year customer outcomes rather than short-cycle targets, which is precisely the resolution those metrics require. According to the practitioner guide Strategic, Tactical, and Operational Planning, the quarterly checkpoint is likewise designated as where replans happen. Some weeks will read unchanged numbers; that is the instrument reporting honestly, not the system failing.

The practical close: before adopting, audit the twelve metrics you intend to post. Tag each with its natural refresh window and its gaming surface, and pre-recalibrate any efficiency band inherited from a vendor deck. The table below is that audit sheet.

Content for Worked Case is being prepared.

The 90/12/9 cadence rarely fails by collapsing. It fails by accretion — a monthly business review imported here, a legacy forecast call retained there, until the "lightweight" system is a monthly review wearing a weekly costume. That is the "scale demands ceremony" myth doing quiet damage: the belief that reaching Series B obligates you to public-company rhythm, as if headcount alone justified the paperwork. It doesn't. Five rules keep the cadence from becoming the bureaucracy it was built to replace.

| Failure mode | Signature on the scorecard | Pre-adoption check |
| --- | --- | --- |
| Unproven evidence base | Success stories trace to the format's own vendors and consultancies | Demand an independent cohort; treat adoption counts as marketing |
| Coverage gaming | Pipeline holds the 3.5x band while win rate and NRR degrade about two quarters later | Read coverage only beside the win-rate trendline |
| Motion mismatch | Efficiency sits under the 0.75 floor yet bookings stay stable for 4+ quarters | Re-derive bands from your own cycle length; 18-month enterprise motions can be healthy at 0.5 |
| Market shock | Roughly half the board red in a single week |  |

## Frequently Asked Questions

**What specifically sets the nine-day replan clock in motion?**

Any metric that stays red in two consecutive weekly reviews logs a system trigger on Day 0, starting the nine-day sequence that ends with the CEO picking one option in a 45-minute decision session.

**Can two executives co-own a metric on the scorecard?**

No — the accountability chart enforces the rule that two names on a number means nobody owns it, which is why all twelve numbers carry exactly one owner apiece, since unowned metrics can absorb up to 60% of review time without producing a single decision.

**What numeric thresholds do the four efficiency metrics enforce?**

Burn multiple at or below 1.5x using David Sacks' formula of net burn divided by net-new ARR, magic number at or above 0.75, CAC payback at or under 18 months, and gross margin held above a band recalibrated annually.

**Who has to produce what once a replan is triggered?**

The owning VP delivers a maximum two-page diagnosis memo by Day 3 and exactly two countermeasure options with cost and headcount deltas by Day 6, the CFO stress-tests both against runway and Rule-of-40 trajectory on Days 7–8, and the revised plan ships as a new version after Day 9.

**How does the 90-minute review avoid burning its first half hour on status updates?**

A mandatory one-page pre-read circulates 24 hours ahead, so zero minutes are spent on status reporting and the design buys 50 uninterrupted minutes of argument about what is actually broken.

**Does the nine-day replan clock still work if our monthly close is slow?**

The clock runs on validated numbers, and APQC's finance benchmarking shows top-quartile teams close their monthly books in about 4.8 days while bottom-quartile teams take 10-plus days.

## Quick answers

| How much does folding the pipeline council, the forecast call, and the ops review into a single 90-minute review cut the standing-forum load? | By roughly 40%, while forcing every agenda line to close with a named owner and a dated decision. |
| --- | --- |
| What rule does the accountability chart enforce about metric ownership? | Two names on a number means nobody owns it, which is why the review tracks twelve numbers with exactly one owner apiece. |
| Why does a nine-day replan clock beat riding out a 35-day cycle? | Because replanning costs drop when the structural calendar stays stable, so each replan becomes a quick check of what changed, reclaiming roughly 40% of the coordination time that dependency-driven Gantt files lose to whole-file rebuilds. |
| What happens during minutes 75–85 of the 90-minute review? | Decisions are recorded, and every call carries a named owner and a date. |
| What three audit artifacts does the nine-day cadence leave behind? | A one-page scorecard with 12 rows, trend arrows, and RAG bands; a two-page diagnosis memo; and a plan changelog versioned like software, such as 'Plan v3.2 — May 9, 2026.' |

Also worth reading: **Weekly vs Annual Planning: The 30% Evidence and Its Limits**: [Weekly vs Annual Planning: The](https://thane.zone/blog/weekly-vs-annual-planning-the-30-evidence-and-its-limits.php) · **Interface Math: Why Teams Multiply — and When to Go Divisional**: [Interface Math: Why Teams Multiply](https://thane.zone/blog/interface-math-why-teams-multiply-and-when-to-go-divisional.php)

### Related reading

- [Executive Time Arithmetic: Rethinking Meeting Culture with OKRs](https://thane.zone/blog/executive-time-arithmetic-rethinking-meeting-culture-with-okrs.php)
- [Weekly vs Annual Planning: The 30% Evidence and Its Limits](https://thane.zone/blog/weekly-vs-annual-planning-the-30-evidence-and-its-limits.php)
- [Interface Math: Why Teams Multiply — and When to Go Divisional](https://thane.zone/blog/interface-math-why-teams-multiply-and-when-to-go-divisional.php)
- [8% Inventory Cost Cut via Dock-to-Stock Under 24 Hours](https://thane.zone/blog/8-inventory-cost-cut-via-dock-to-stock-under-24-hours.php)
- [Using a Command Center to Accelerate Executive Onboarding](https://thane.zone/blog/using_a_command_center_to_accelerate_executive_onboarding.php)
- [Thane Monsoon Data: Why TMC's Runbook Fails](https://thane.zone/blog/thane-monsoon-data-why-tmcs-runbook-fails.php)

### Latest

- [Weekly vs Annual Planning: The 30% Evidence and Its Limits](https://thane.zone/blog/weekly-vs-annual-planning-the-30-evidence-and-its-limits.php)
- [Interface Math: Why Teams Multiply — and When to Go Divisional](https://thane.zone/blog/interface-math-why-teams-multiply-and-when-to-go-divisional.php)
- [8% Inventory Cost Cut via Dock-to-Stock Under 24 Hours](https://thane.zone/blog/8-inventory-cost-cut-via-dock-to-stock-under-24-hours.php)
- [Using a Command Center to Accelerate Executive Onboarding](https://thane.zone/blog/using_a_command_center_to_accelerate_executive_onboarding.php)

Canonical: https://thane.zone/blog/groves-90-minute-meeting-why-9-day-cadence-beats-35-days.php
Markdown: https://thane.zone/blog/groves-90-minute-meeting-why-9-day-cadence-beats-35-days.php/index.md