--- title: Where the Capability Framework Was First Practiced — Zero Fog description: A methodological provenance case. The seven-module operating model we helped design at a top-tier strategy firm became the conceptual basis for Zero Fog's Capability Framework primitive. --- [![Zero Fog](https://www.zero-fog.com/hubfs/Zero-fog-site/zero-fog-logo.png)](https://www.zero-fog.com/?hsLang=en) [The Firm](https://www.zero-fog.com/about?hsLang=en) [About](https://www.zero-fog.com/about?hsLang=en) [Practitioners](https://www.zero-fog.com/careers?hsLang=en) [Methodology](https://www.zero-fog.com/methodology?hsLang=en) [Methodology](https://www.zero-fog.com/methodology?hsLang=en) [Reference Cases](https://www.zero-fog.com/reference-cases?hsLang=en) [Engage](https://www.zero-fog.com/how-we-engage?hsLang=en) [Situations](https://www.zero-fog.com/situations?hsLang=en) [All Situations](https://www.zero-fog.com/situations?hsLang=en) The Six [Board-Ready Diagnosis](https://www.zero-fog.com/situations/board-narrative?hsLang=en) [Portfolio Value Creation Sprint](https://www.zero-fog.com/situations/pe-value-creation?hsLang=en) [Pre-Exit Readiness](https://www.zero-fog.com/situations/pre-exit-readiness?hsLang=en) [AI Initiative Sequencing](https://www.zero-fog.com/situations/ai-readiness-assessment?hsLang=en) [Transformation Sequencing](https://www.zero-fog.com/situations/transformation-sequencing?hsLang=en) [Revenue & Retention Diagnostic](https://www.zero-fog.com/situations/revenue-retention-diagnostic?hsLang=en) [Rejoyce](https://www.zero-fog.com/rejoyce?hsLang=en) [Insights](https://www.zero-fog.com/insights?hsLang=en) [Contact](https://www.zero-fog.com/contact?hsLang=en) Methodological Provenance · 05 # Where the Capability Framework was first practiced. **The Situation:** A top-tier global strategy and advisory firm needed to make a portfolio of flagship strategic offerings genuinely scalable — across regions, sectors, and several thousand client-facing professionals. The intellectual property was fragmented. The delivery model varied widely. The commercialization velocity lagged the firm's own growth thesis. We were brought in as one of a small group of partners to design and deploy a firmwide operating model. Why This Case Sits Separately ## This is not a client outcome story. It is a methodological provenance case. The four reference cases above answer the question *does the discipline work*. This case answers a different question: *where did the discipline come from*. We surface it not because it produced a commercial outcome — although it did — but because the operating-model architecture we helped design here became the conceptual basis for what is now the Capability Framework primitive on the methodology page. The numbers are real. They appear at the end of this case for completeness. They are not the reason this case is on the site. The Operating Model We Helped Design ## Seven modules. One governance architecture. Quarterly release cycles. Provenance pattern Capability operating model PROVENANCE · CAPABILITY ARCHITECTURE — FIRST PRACTICED AT SCALE TOPIC LEADER + PRODUCT MANAGEMENT TEAM Governance and ownership architecture SEVEN OPERATING MODULES Valueproposition01 Productarchitecture02 Packagedprograms03 OKRs04 Backlogs05 Teamstructure06 SectorGTM07 QUARTERLY EXECUTION CYCLES · RELEASE-BASED EVOLUTION 90-day cadence — backlog → build → measure → repeat LATER GENERALIZED INTO → THE CAPABILITY FRAMEWORK PRIMITIVE Today's Capabilities primitive scores 110 sub-dimensions; the architecture began here. **The architectural pattern.** The seven-module operating model — Value Proposition, Product Architecture, Packaged Programs, OKRs, Backlogs, Team Structure, Sector GTM — codified what it took to operate a portfolio of strategic offerings at firmwide scale. The Topic Leader plus Product Management Team governance layer above it answered the ownership question. The quarterly cycles below it answered the evolution question. - **Module-by-module codification**Each of the seven modules was a discrete operating practice with its own templates, governance, and metrics. The codification work — moving from "the way the best partners did it" to "the way the firm did it" — was the underlying value. The seven modules became the conceptual basis for the multi-dimensional capability architecture we now use across engagements. - **Governance pattern**The Topic Leader plus Product Management Team architecture answered the question of who owned what. Topic Leader carried strategic ownership; Product Management Team carried operational execution. This pattern — separable strategic and operational ownership of the same capability — is recognizable across every Zero Fog engagement today. - **Release-based evolution**Capabilities are not deliverables. They evolve, or they decay. The 90-day release cycle was the answer to how capability practice stays current under real operating pressure. The cadence directly anticipated what is now the Quarterly Execution Cycle. - **Causal-model thinking applied to commercial outcomes**Working out the actual drivers of program success — value proofs, packaging quality, sector alignment, teaming behaviors — was the first time the practice systematically used causal mapping to interpret commercial outcomes. That thinking shows up directly in how the Mirror primitive operates today. For Completeness ## What the engagement produced commercially. $1B+ Incremental program value Over the first two years of operation, across the supported portfolio. Multiple drivers; the operating-model redesign was one. 8–10× Average deal size From the previous baseline. Driven by packaging, governance, and sector GTM working in combination. Global Standardization The operating model became the firmwide internal standard for how flagship offerings were built, sold, and evolved. We present these numbers here, in the last section of the case, because the commercial outcome matters as scale evidence — the operating model held up under enterprise pressure and produced meaningful value. The numbers are not the lead because the methodological provenance is what makes this case worth including on the site. The other four cases are about the discipline producing client outcomes. This one is about where the discipline came from. ### The Capability Framework is interrogable end-to-end. Start with the methodology page, or talk to a senior practitioner. 30 minutes · Senior practitioner · No deck [Request fit call](https://www.zero-fog.com/contact?hsLang=en) Return to #### [Methodology The Capability Framework primitive in current form.](https://www.zero-fog.com/methodology?hsLang=en) #### [Reference Cases Back to the index.](https://www.zero-fog.com/reference-cases?hsLang=en) #### [04 · Related provenance The other case with direct methodological lineage to Rejoyce.](https://www.zero-fog.com/reference-cases/strategic-intelligence-velocity?hsLang=en) [![Zero Fog](https://www.zero-fog.com/hubfs/Zero-fog-site/Transparent%20Logo_white%20logo%20side.png)](https://www.zero-fog.com/?hsLang=en) The founding practice of Strategic Execution Intelligence. Built on Rejoyce. Site [The Firm](https://www.zero-fog.com/about?hsLang=en) [Methodology](https://www.zero-fog.com/methodology?hsLang=en) [Engage](https://www.zero-fog.com/how-we-engage?hsLang=en) [Situations](https://www.zero-fog.com/situations?hsLang=en) [Insights](https://www.zero-fog.com/insights?hsLang=en) [Reference Cases](https://www.zero-fog.com/reference-cases?hsLang=en) More [Rejoyce](https://www.zero-fog.com/rejoyce?hsLang=en) [Careers](https://www.zero-fog.com/careers?hsLang=en) [Contact](https://www.zero-fog.com/contact?hsLang=en) Contact hello@zero-fog.com © 2026 Zero Fog, LLC. All rights reserved. · Massachusetts, USA [Privacy](https://www.zero-fog.com/privacy?hsLang=en) · [Terms](https://www.zero-fog.com/terms?hsLang=en) · [LinkedIn](https://www.linkedin.com/company/zero-fog) An independent firm. Peer to Rejoyce in the founding of Strategic Execution Intelligence.