Chapter 15 · The First 90 Days

What we discuss in this chapter: The operational deployment of organizational self-understanding follows a structured, repeatable 90-day pattern (define scope, consolidate knowledge, resolve conflicts, and prove value measurably) rather than proceeding as a classic software rollout. The chapter outlines the four-phase implementation model with specific roles and decision milestones, the four most dangerous anti-patterns, and the practical implementation guide for Muster AG.

Your leverage as a decision-maker: The most fatal misconception in this field is the intuitive trap of perfectionist completeness: trying to model the entire enterprise before the first insight delivers value. The 90-day pattern reverses this logic: it guides a narrow, business-critical scope directly to full response capability. Your leadership role as sponsor is focused on three clear moments: scope approval, conflict escalation, and final value sign-off.

---

15.1 Why "Rollout" Is the Wrong Metaphor

Traditional software is rolled out into an organization; organizational self-understanding, by contrast, must be built incrementally.

This linguistic distinction marks not a subtle nuance, but a fundamental strategic divergence. An IT rollout is considered formally completed once the application is installed on servers and licenses are assigned to users. Knowledge consolidation, by contrast, unfolds business value only when the first uncovered conflicts between QM guidelines and daily operational practice are resolved; this management work can be performed exclusively by your organization's domain experts.

For this reason, an entry approach has established itself that this book designates as a Proof of Understanding: a tightly scoped pilot initiative whose goal lies not in technical system readiness, but in the proven capability of the organization to deliver authoritative information on a defined core value stream instantly. Case studies A, B, and D in Chapter 11 illustrate successful variations of this approach.

15.2 The Four-Phase Implementation Model

The field-tested 90-day framework is divided into four operational phases. Each phase features a clearly defined objective, specific role responsibilities, an essential decision gate, and a direct measurement connection.

15.2.1 Phase 1 (Days 1 to 15): Scope and Baseline

At the outset, you select a knowledge domain alongside executive leadership that satisfies three strict criteria: it must exhibit high business urgency, be source-rich (documented across at least two distinct system landscapes), and be tied to an imminent operational milestone, such as an upcoming system migration, a pending audit, or generational turnover in a key role. Concurrently, the baseline measurement week from Chapter 10 launches to empirically establish the starting position.

• Roles: The sponsor leads prioritization; knowledge owners define source systems.
• Decision Gate: The formal decision milestone at the end of this phase rests solely with the sponsor: the chosen scope is bindingly approved or narrowed down, never expanded.
• Measurement Connection: The collection of baseline values (search times, clarification durations, manual preparation times) marks the zero point for subsequent value measurement.

15.2.2 Phase 2 (Days 16 to 60): Consolidation and Conflict Report

In the second phase, automated adapters populate the governed ontology with content from source systems. While consolidation logic runs in the background, conflict detection identifies remaining contradictions across document and data assets. This phase culminates in the organization's first structured conflict report: How frequently do guidelines contradict each other in the selected domain, where do differences occur, and what operational severity do they carry? For the first time, this report confronts decision-makers in black and white with organizational fractures whose extent was previously merely guessed; initial projects indicate typical bands of 12 to 19 conflicts per 100 Claims.

• Roles: The technical lead manages adapter pipelines; knowledge owners verify ingestion quality.
• Decision Gate: Formal receipt of the conflict report by the sponsor and binding allocation of review capacity for domain experts.
• Measurement Connection: Initial capture of Conflict Density (total count and severity of identified contradictions within scope).

15.2.3 Phase 3 (Days 61 to 85): Four-Zone Review and Approvals

Designated domain leads systematically resolve uncovered conflicts using the four-zone procedure from Chapter 7. This is where actual organizational value creation occurs, and where the initiative stalls if you as sponsor fail to protect the experts' required time budgets from daily operational demands. A strict escalation rule applies to unresolved scenarios: anything that cannot be resolved after two technical sessions moves into the repository as a Zone 4 entry accompanied by documented justification, transparently marked as an open question rather than bureaucratically deferred.

• Roles: Domain experts conduct reviews; knowledge owners issue formal approvals; the sponsor decides operational escalations.
• Decision Gate: Escalation decision by the sponsor in cases of unresolved policy conflicts between departments.
• Measurement Connection: Tracking of conflict resolution rate (proportion of reviewed and approved Claims relative to total yield in the conflict report).

15.2.4 Phase 4 (Days 86 to 90): Value Measurement and Expansion Decision

During the final five days, you re-measure the key metrics from the baseline week. The before-and-after comparison goes directly to the sponsor, whereupon executive leadership decides on the initiative's future: expansion to the next scope, targeted pivot, or a reasoned stop. A reasoned stop represents a fully legitimate outcome; what is expensive and harmful is the unreflective continuation of failed initiatives.

• Roles: The sponsor evaluates the deliverable package; quality management and works council receive the final report.
• Decision Gate: Strategic three-way decision by the sponsor (Scale, Pivot, Stop).
• Measurement Connection: Determination of empirical delta proof (e.g., percentage reduction in search times and response latencies compared to Phase 1 baseline).

15.3 Roles and Responsibilities in Detail

The success pattern rests on four clearly defined roles whose interplay determines the outcome:

1. The Sponsor: Represents the initiative at the C-level, owns the scope decision, decides operational escalations, and determines future scaling; experience shows that without active executive backing, the initiative quickly succumbs to the inertia of daily business.
2. Knowledge Owners: This role manages domain areas, oversees the accuracy of ingested source systems, and issues formal approvals for consolidated knowledge assets.
3. Domain Experts: These individuals contribute unvarnished operational perspectives, explicitly pointing out where daily reality contradicts official QM documentation; it is precisely in this dissenting knowledge that the highest return for the organization lies.
4. Works Council and Data Protection Officers: Both bodies participate from the initial scope discussion; they help define goals and establish binding evaluation boundaries (Chapter 14.5). Inviting employee representatives only during final sign-off risks negotiating over a completed system rather than a co-created operating system.

15.4 Four Leadership Anti-Patterns

In practice, four typical anti-patterns regularly emerge as clear executive missteps that jeopardize success:

• The Perfectionist Completeness Trap: This leadership failure stems from academic perfectionism. Management demands that the entire process house of the organization be modeled before the first value deliverable. The result is a massive mountain of data that becomes obsolete before ever achieving response capability.
• Tool before Scope: This misstep occurs when management decisions are substituted by premature software procurement. Leadership procures a platform before establishing clarity on the operational use case. Tool selection belongs at the end of Phase 1, never at its beginning.
• Deferring Conflicts: Here, executive leadership dodges operational confrontation. The conflict report is favorably acknowledged, but technical reviews are postponed to "after business hours" without granting experts real time budgets. A repository full of unresolved contradictions delivers no operational value.
• The Omitted Baseline: This failure manifests as a fear of true measurability. Skipping initial baseline measurement forfeits any ability to empirically demonstrate achieved value later—inviting critics to challenge the success of the entire initiative.

Seven Years, 500 Million Euros, Back to Square One

How expensive the combination of "Tool before Scope" and deferred conflicts can be was demonstrated by Lidl between 2011 and 2018. The discount retailer intended to replace its legacy inventory system with SAP for Retail, but realized early that its actual operational business logic (inventory valuation at cost price) fundamentally conflicted with the system's standard assumption (valuation at retail price). Instead of resolving this single conflict at the executive board level, it was bypassed via custom code: for seven years, with hundreds of consultants, while complexity and costs skyrocketed. In July 2018, executive management pulled the plug: strategic goals were no longer achievable "at reasonable expense." Roughly 500 million euros were written off, and the company returned to its legacy system. A single, early-documented and formally resolved conflict between declared system assumptions and lived practice—exactly what Phase 1 of the 90-day model enforces—would likely have been the most profitable review meeting in corporate history.

— Henrico Dolfing, Case Study: Lidl's €500 Million SAP Debacle

15.5 Muster AG: The Plan Before Migration

For executive leadership at Muster AG, the concrete implementation plan derives from this logic as a fully calculated practical narrative. The board selects order fulfillment across its three production sites as its scope: business-critical, inadequately consolidated across the QM manual, knowledge wiki, and ERP customizations, and facing high time pressure from an upcoming ERP system migration and the impending retirement of its senior-most expert.

During Days 1 through 15, the organization gathers baseline metrics: how much working time is tied up daily in searching for valid order fulfillment rules and how long site audit preparation actually takes. The sponsor formally signs off on this tightly defined scope. Between Days 16 and 60, adapters ingest data from the three sources. The generated conflict report reveals for the first time how many explicit contradictions actually exist between the QM manual, wiki, and ERP customizations—including the complaint root-cause analyzed in Chapter 1, where quality guidelines for special inspections contradicted the standard workflow configured in the ERP.

During Days 61 through 85, plant managers and quality leadership conduct zone reviews. The retiring expert contributes invaluable tacit insight during every session, anchoring it into the versioned repository rather than letting it vanish upon retirement. On Day 90, follow-up measurement compares each parameter against the baseline: daily search times, lead-time to an audit-ready report extract, and the proportion of resolved contradictions in the conflict report. If this comparison proves compelling, executive management at Muster AG expands the model to procurement over the subsequent 90 days.

Case Study — Case D: A European biologics manufacturer structures its entry as a POC across 10–15 work packages over three cycles: value stream reference for ERP migration, conflict detection between SOP status and practice, handover format for the program. → detailed in Chapter 11.

There remains the fundamental question every sponsor asks before approving Day 1: What investments does this model require, and what costs does maintaining the status quo incur? The following chapter completely lays bare the economics of this category.

💡 What We Discussed

The operational deployment of your organizational self-understanding succeeds not through an enterprise-wide software rollout, but via an incremental approach with a clear focal point.

The four-phase 90-day framework guides a tightly scoped business domain purposefully from initial baseline measurement through automated consolidation and expert conflict resolution to provable value.

In doing so, you prevent typical executive missteps like premature software procurement or academic perfectionism by bindingly engaging the sponsor during key decision and escalation gates.

What investments this approach demands and what hidden expenses remaining in the status quo causes are illuminated in the following chapter on the economics of the category.