Chapter 1 · The Observation
What we discuss in this chapter: In structured interviews with corporate leaders, a consistent pattern recurs: organizations do not fail at documenting, but at deriving reliable self-knowledge from existing documentation. This chapter unfolds the pattern matrix of these field observations, their methodology, and anonymized direct quotes from practice.
Your leverage as a decision-maker: Your organization almost certainly possesses more documented knowledge than any executive board could ever retrieve. What matters, therefore, is not the next documentation initiative, but the timeframe between a concrete strategic query and a reliable answer. This timeframe can be measured and reduced.
1.1 Where This Observation Originates
How quickly does your executive team receive a reliable answer when a critical question about your own processes arises?
In most enterprises, such questions take not minutes, but days or even weeks to answer. This delay—operational query latency—is no cosmetic flaw; it causes massive friction losses. It paralyzes strategic decisions, elevates audit risks, and drives up the costs of upcoming transformation projects.
This book therefore begins not with abstract academic theory, but with the hard reality of roughly 150 structured executive interviews. Over a period of three years, we engaged in deep exchanges with managing directors, department heads, quality managers, and CIOs across industry and public administration. A single phenomenon recurred with striking regularity: companies continuously invest in capturing workflows, yet gain virtually no functioning self-knowledge from these efforts.
The dataset stems from exploratory business discussions in industry practice rather than an academic double-blind study. Naturally, the sample primarily captures organizations already experiencing the pain of deficient query capability. The operational value of these observations lies in their remarkable consistency across diverse industries, company sizes, and legal forms. The frequencies shown are provisional and reflect the current state of corpus evaluation.
1.2 The Pattern Table
Five characteristic behavioral patterns underpin this field observation. Percentage frequencies are provisional; multiple selections were possible, as a single interview could exhibit several patterns simultaneously.
| No. | Pattern | Typical Statement in Discussions | Frequency (Provisional) |
|---|---|---|---|
| M1 | Documented, but unfindable: Knowledge exists, search fails | "That's definitely written down somewhere." | approx. 71% |
| M2 | Multiply documented, contradictory: Multiple valid versions of the same item | "It depends on who you ask." | approx. 64% |
| M3 | Tied to individuals: Answers depend on specific key experts | "You'll have to ask Mr. X about that." | approx. 58% |
| M4 | Project-bound obsolescence: Documentation created for a project and died with it | "That was the state of the 2019 rollout." | approx. 47% |
| M5 | Query only via new survey: Every major question triggers a new as-is discovery | "Then let's run some workshops first." | approx. 39% |
All figures are provisional reference values from the interview corpus. These five behavioral patterns describe the daily barriers to organizational information retrieval in detail:
The first pattern (M1: Documented, but unfindable) describes a paradoxical phenomenon. Although the sought-after process description exists on some network drive or intranet page, a lack of consistent structure renders it unfindable. Employees abandon time-consuming searches after a few minutes and rely on gut feeling instead.
The second pattern (M2: Multiply documented, contradictory) exacerbates this issue. Information exists in multiple copies, but with diverging procedural steps. When quality management maintains a PDF while production relies on a custom Excel spreadsheet, binding procedural governance collapses.
The third pattern (M3: Tied to individuals) reveals the extreme expert-reliance of many organizations. Knowledge regarding actual workflows depends entirely on specific senior experts. If a key individual goes on leave or retires, actionable operational knowledge vanishes abruptly.
The fourth pattern (M4: Project-bound obsolescence) originates from temporary documentation surges. Knowledge is structured once at high resource expense for an ISO certification or software implementation. Once the project finishes, documentation becomes orphaned and quietly obsolete.
The fifth pattern (M5: Query only via new survey) illustrates the most expensive consequence of missing transparency. Distrusting existing documentation, every strategic realignment or restructuring triggers yet another lengthy as-is assessment through time-consuming workshop cascades.
What is striking about this diagnosis is what is missing from the list. In virtually no interview did executives complain about a lack of documents. The sentiment was almost never "We haven't written anything down," but almost universally "We simply can no longer navigate what we have written down."
This aligns impressively with a fundamental insight from organizational research: Chris Argyris and Donald Schön demonstrated early on how an organization's officially proclaimed theory (espoused theory) systematically drifts apart from its actual practice (theory-in-use). Furthermore, Daniel Wegner described the principle of transactive memory: the collective directory of who possesses what knowledge within the organization. When this directory exists solely in the minds of individual experts, organizational memory seamlessly retires alongside pattern M3.
1.3 Direct Quotes
The following quotes reflect anonymized insights from the empirical interview corpus: stylistically polished, content original. They systematically organize practical experience by industry, use case, and decision-making tier:
| Slot | Category | Quote (Anonymized) |
|---|---|---|
| Z1 | Pattern M2, Industry | "We have three valid versions of the exact same process. Which one actually applies is ultimately decided by whoever has been here the longest." (Head of Division, Plant & Machinery Engineering) |
| Z2 | Pattern M3, Retirement | "When our most senior colleague leaves next year, three decades of procedural knowledge walk out the door. We don't have a plan to capture it." (Plant Manager, Automotive Supplier) |
| Z3 | Pattern M5, Consulting Loop | "This is now the third as-is assessment in six years. The same people are interviewed and the same diagrams drawn—only the logo on the slide deck changes." (VP of Operations, Consumer Goods) |
| Z4 | Pattern M1, Search | "It's all in the intranet somewhere. But my team would rather ask the colleague next to them than search for an hour." (CIO, Energy Utility) |
| Z5 | Pattern M4, Project Doc | "Our process landscape reflects the state of a consulting project from 2019. We've had two reorganizations since then." (Head of Quality Management, Medical Devices) |
| Z6 | Public Sector | "Every query from city council costs us two weeks of digging through files—not because we don't know the answer, but because we can't prove it." (Head of Department, Municipal Administration) |
| Z7 | Regulated/Audit | "Before every audit, there's three weeks of state-of-emergency. We hunt for proof of things we do correctly every single day." (Compliance Officer, Aerospace Supplier) |
| Z8 | Executive Board | "I get every financial metric in real time. But when I ask how Plant Two actually operates, I wait four weeks for an answer." (Board Member, Industrial Conglomerate) |
All eight quotes are anonymized, stylistically refined versions of real interview situations. This structured presentation ensures empirical coverage across regulated mid-market enterprises, public administration, and corporate executive suites.
1.4 Muster AG: The Model Enterprise of This Book
To keep these five patterns concrete, a reference company accompanies us throughout the book. Muster AG is a fictitious model enterprise representing the upper mid-market. It manufactures specialized machinery across three production sites and employs approximately 1,800 people.
At first glance, Muster AG is excellently positioned and thoroughly documented: a classic quality management manual, a widely used process wiki, and an ERP system with twelve years of history form its visible foundation. However, two impending operational events threaten to unbalance the organization: a major ERP migration is imminent, and the most senior expert will retire in fourteen months. In our field interviews, these exact two business triggers frequently occurred together. Muster AG thus embodies standard operational reality rather than an extreme crisis scenario.
All five patterns exert their operational effect at Muster AG without any organizational malice:
When attempting to clarify the process for handling complex customer complaints, searching uncovers three contradictory documents on different network drives (M1, M2).
The sobering answer to pressing questions regarding the upcoming data migration is simply "You'll have to ask Mr. Feld about that" (M3).
The central process landscape on the intranet merely reflects the state of a past consulting project from 2021 (M4).
To advance the migration architecture despite this, the next costly as-is survey has already been initiated via external consultants and internal workshops (M5).
1.5 The Finding as a Thesis
Documented knowledge in modern organizations grows continuously, but actual query capability fails to keep pace with this growth.
A wide gap opens between the volume of information available and the ability to maintain confident self-knowledge. This gap can be closed neither by search technologies alone nor by appealing to employee discipline. What constitutes this gap, why it can be closed precisely today, and what operational prerequisites are required will be detailed in the following chapters. The first step takes us into the historical evolution of digital tools, as the problem carries a defining history across three epochs.
💡 What We Discussed
In many enterprises, pressing questions take days rather than minutes to answer, despite abundant documentation lying dormant across your organization.
Field practice reveals five characteristic barriers: from unfindable work instructions and contradictory variants to expert-dependent tacit knowledge and outdated project documents.
The core problem lies not in a lack of records, but in the eroding capability for reliable self-knowledge.
This widening gap between information volume and strategic orientation carries a long history, whose roots we trace back across three technological epochs.