Operating Model Grid (Standardization and Integration)
When you need this method
You are facing a consolidation: one CRM for all units, one billing stack, one process. The stated reason is synergy, and the reason itself is never tested. Where units share neither customers nor process logic, consolidation costs money and attention while no customer and no cost line benefits. In portfolios and after acquisitions this is the most expensive quiet mistake, because it never surfaces as a decision, only as the obvious next step.
Approach
- 1Name the core processes the business runs on: order to cash, onboarding, service, development, billing.
- 2Assess the standardization axis for each core process: do customers or costs measurably benefit from running this process the same way in every unit?
- 3Assess the integration axis for each core process: does completing a transaction in one unit depend on the availability, accuracy and timeliness of another unit's data?
- 4Read off the quadrant and state it in writing, then hold every running initiative against it and mark the contradictions, typically a unification project inside a business that operates by diversification.
- 5Derive from the quadrant which capabilities are built jointly and which stay local, and from that the sequence of investment.
- 6For acquisitions, fix the buyer's target model in writing before closing, then align only the processes that model requires and deliberately leave the rest alone.
Typical application
A typical case: a software portfolio holding seven acquired vendors decides on a shared platform, because each company runs its own CRM, its own billing and its own support stack. Working through the grid shows that six of the seven have no customers in common; a transaction in one company never needs another company's data. On the standardization axis, however, renewals and invoicing could run the same way everywhere and currently tie up staff in every single company. The portfolio names replication as its target model instead of unification: billing and renewals are unified, CRM and support stay local. The originally planned platform project shrinks to a fraction of its scope, and the product teams keep the customer proximity they were bought for.
Limits and counter-indications
The grid names the required degree of uniformity and coupling, not the path there; it does not replace a migration and decommissioning plan. Both axes are judgements, not measurements: two teams can classify the same business differently, and the discipline lies in the written justification per core process, not in the picture with four boxes. A quadrant only ever holds for one level; a group can be diversified at group level and unified inside a division, and applying the grid to the whole house at once produces a wrong answer. The authors' evidence comes from their own surveys and case work using self-reported effectiveness measures, which supports plausibility rather than causality. The grid says nothing about people, incentive systems or culture, although that is where most consolidations fail. And it comes out of the IT architecture world of around 2005: data integration is technically cheaper today, which shifts the integration axis but leaves the process standardization question untouched.
How to measure impact
Record for each core process which degree of standardization and which degree of integration it requires, then measure what share of running initiatives matches the stated quadrant. For acquisitions, also track the number of processes actually aligned against the number the target model requires, plus the time to the first joint billing run.
Related methods
Tools for this
Sources
- 1.Jeanne W. Ross: Forget Strategy: Focus IT on Your Operating Model, MIT CISR Research Briefing Vol. V, No. 3C (opens in a new tab) · MIT Center for Information Systems Research · 2005-12-09 · academic and scholarly literature · supports the underlying mechanismCarries the core of the method: according to this briefing, business strategy rarely gives clear enough direction for stable process and IT capabilities, so a firm instead fixes an operating model that states the required degree of business process integration and standardization. Limit: the freely accessible page holds the abstract and an audio version, the four quadrants are not spelled out there.
- 2.Diversification, Coordination, Replication, and Unification (Archivbeitrag von J.D. Meier mit wörtlichen Zitaten aus dem Buch) (opens in a new tab) · Microsoft Learn, Blog-Archiv · 2013-02-24 · practitioner source · describes the methodCarries the applicable procedure: it quotes the authors' two diagnostic questions verbatim, namely whether completing one unit's transaction depends on the availability, accuracy and timeliness of other units' data, and whether the company benefits from units running operations the same way, along with the definitions of the four quadrants and the note that different levels of a group can sit in different models. Limit: a blog restatement rather than the book itself; the effectiveness percentages quoted there are mistranscribed and are not carried over here.
- 3.Enterprise Architecture as Strategy: Creating a Foundation for Business Execution, Ross, Weill & Robertson, Buchseite des MIT CISR (opens in a new tab) · MIT Center for Information Systems Research · 2006-08 · academic and scholarly literature · provides the contextEstablishes authorship, the 2006 publication year and the framing: the operating model is described as a firm's vision of how it will survive and grow, implemented through its enterprise architecture. Limit: the page is a book announcement and contains neither the two axes nor the four quadrants.
- 4.Enterprise Architecture as Strategy, Aufbereitung mit den Nachteilen je Betriebsmodell (Željko Obrenović) (opens in a new tab) · grounded-architecture.io · ohne Datumsangabe, abgerufen 2026-07-30 · practitioner source · provides the contextNames the downside of each quadrant and thereby supports the limits section: diversification forgoes possible synergies, coordination buys data continuity at the price of integration effort, replication leaves units working without a shared view of each other, unification restricts the adaptability of individual units. Limit: a practitioner's restatement with no original research, no publication date and no critical examination of the grid itself.
Origin: Ross/Weill/Robertson (MIT CISR)