Structural Parallels, Part 4: Operational Immersion
This is the fourth essay in the Structural Parallels series, which explores how identifying parallels across industries can accelerate transformation. Part 1 established the importance of recognizing structural parallels. Part 2 suggested that many adaptive systems can be read as following three‑phase patterns. Part 3 showed how human cognitive biases scale into organizational architecture. This essay examines what is required to transfer knowledge across domains—and why many external advisory models struggle to enable genuine transformation.
The Advisory Structural Problem
In theory, advisory work exists to help organizations transform. In practice, for many firms, client dependence is less a flaw than a business model. Some of the most profitable clients are not those who complete transformation, but those who remain in long‑term support cycles. Multiple analyses note that major firms tend to earn their highest margins through long‑tail engagements, repeat contracts, and “transformation support” work (Alvesson & Johansson, 2002).
Critical examinations, such as those by David Craig, describe recurring dependency cycles as intentionally structured, designed to maximize margins through repeat business (Craig, 2018). Likewise, accounts of large firms, including McKinsey, often describe models in which personnel embed to extract and document core organizational knowledge, which can then be used to perpetuate ongoing engagements.
When external expertise is consistently privileged over internal capability, systems can drift toward dependence rather than transformation. What appears as strategic advisory can, in effect, extract organizational intelligence, repackage it as deliverables, and sell it back as a form of intellectual rent: payment for access to knowledge the organization already possesses but has not yet synthesized.
The Synthesis Gap
Traditional consulting frequently operates through extraction: interviewing staff, analyzing data, benchmarking against peers, and delivering recommendations. Modern complexity tends to demand contextual intelligence as much as abstract frameworks. Data reveals what happens; immersed participation can reveal why it happens.
A process map shows the official workflow. Sustained observation tends to reveal the informal networks, workarounds, and unspoken rules that keep operations functional when official systems fail. Surfacing these hidden dynamics through participation is one way to understand how an organization actually works.
The difference is epistemological—about how we decide what counts as valid knowledge. As Henry Mintzberg argued, “Management is not a science. It’s a practice, and practices are learned through experience” (Mintzberg, 2004). What looks like progress on slides can collapse under operational reality, because contextual intelligence—not abstract data alone—often shapes whether implementation succeeds (Kahneman & Klein, 2009).
Often, organizations do not lack information so much as synthesis. Employees hold fragmented insights that rarely connect across silos. The knowledge exists; it tends to remain invisible.
Dasein: Knowledge from Being‑There
The philosopher Martin Heidegger argued that authentic understanding often requires Dasein (“being‑there”): knowledge emerging from immersion rather than distant observation (Heidegger, 1962). It is difficult to fully understand a system by studying it only from the outside.
Understanding frequently requires participating in its constraints, experiencing its tensions, and dwelling in its operational reality. Abstract recommendations tend to fail when they overlook contextual constraints the observer may never encounter:
A reorganization that breaks trust networks.
A process change that disrupts informal coordination.
A software deployment that adds five steps nobody has time for.
A policy that quietly collides with unstated cultural norms.
As Karl Weick noted, “How can I know what I think until I see what I say?” (Weick, 1995). Meaning tends to emerge from action and engagement, not observation alone. Tacit knowledge—the unspoken, experiential understanding described by Michael Polanyi—is often central to how systems actually function (Polanyi, 1966).
Three‑Phase Method: Immerse, Map, Identify
Shifting from extraction toward synthesis suggests a disciplined method:
Immerse
Spend sustained time within the system. Surface‑level analysis tends to miss tacit knowledge embedded in daily practice (Schein, 1999).
Frontline workers know which workarounds actually function.
Middle managers know which approval processes get bypassed.
Cross‑functional staff know where handoffs consistently fail.
Case: Contract Research Organization (CRO)
A 375‑employee CRO faced systemic coordination failures across three critical areas, echoing the structural shortcomings described in Part 3:
Lead generation breakdown. Marketing deployed unfocused campaigns measuring activity (touches) rather than outcomes (conversions)—a familiar expression of present bias and short‑term metrics.
Operational silos. No formal handoff process between Business Development and Operations; client relationships fractured at transition points—a scaled form of in‑group bias.
Knowledge concentration risk. Critical institutional knowledge trapped with individual employees; rapid growth outpaced documentation systems—a centralization bottleneck.
The engagement was embedded in the organization for eight weeks, entering through Business Development and extending across eight functions. Not interviewing from outside. Not observing from conference rooms.
Attended meetings spanning marketing, services, contracting, technical, and software initiatives.
Documented informal decision patterns and key personnel dependencies.
Maintained trust through sustained participation rather than external judgment.
What Actually Emerged
The CRO showed systemic mismatches, largely hidden by siloed operations and reinforced by misaligned KPIs:
Single‑point knowledge risk: data dictionary and infrastructure depended heavily on one leader’s tacit knowledge.
Siloed innovation: Operations, BD, and IT pursued separate AI initiatives.
Knowledge gaps: senior leaders’ institutional memory rarely reached operational staff.
Infrastructure chaos: enterprise data was scattered after a botched migration, and new software was deployed without consulting IT.
Map
From early in the engagement, the work moved to map the constraints, dynamics, and failure modes that shape daily reality. Systems often reveal their structure most clearly when they break down. The mapping phase focused on:
Charting personnel relationships and coordination points.
Surfacing active and redundant initiatives and cross‑department collaboration points.
Visualizing how the current system operates and where it tends to fail.
Identifying process and workflow pain points.
Through synthesis, operational data was combined with on‑the‑ground experience. Visualizing responsibility and authority (for example, via a RACI view) helped surface the organization’s “hot‑potato” approach to accountability—illustrating a disconnect between leadership design and functional practice.
Identify
The final step was to look for domains that share structural characteristics, not surface similarities.
Structural recognition. The CRO’s need for high retention and seamless client projects resembled the high‑touch service and coordination requirements of the restaurant industry.
Pattern transfer. The storytelling framework was applied to the client life cycle, treating touchpoints (BD, Ops) as sequential chapters that ideally maintain a single, coherent client narrative to avoid fracturing relationships.
Contextual translation. Insights were packaged into a consultative story tailored to leadership’s preferred style, drawing on molecular and biological parallels and visualizations to highlight process problems. Solutions emerged by recognizing parallel architectures and translating them into this context (Gentner, 1983).
Core Insight
A central finding of this process was the value of zero‑cost recommendations. The organization did not appear to need a new strategy, software platform, or training module, each of which would have carried significant capital expense. What it seemed to need was someone to slow down, immerse in the day‑to‑day, and observe without assumptions.
That immersion surfaced a fundamental constraint: a structural misalignment between individual stress incentives and the company’s stated priorities. Once mapped, the pattern became clearer. The issue seemed to be less effort or intent than the absence of a structural mechanism to identify, articulate, and communicate that misalignment in a way leadership could act on. The most effective solutions were structural—closer to governance changes than to funding decisions.
Building Capacity Instead of Dependency
This is not a rejection of consulting, but a shift toward integrative practice. As complexity increases, organizations tend to need adaptive capacity more than prescriptive frameworks. Developing that capacity, and gradually reducing dependence on external advisors, can become a strategic advantage rather than a threat.
In modern environments, the consultant’s role can shift from delivering knowledge to catalyzing it. Many organizations do not lack expertise so much as translation. The work is making implicit knowledge visible, connecting fragmented insights, and aligning them with operational reality. The value lies less in specialized technique than in contextual awareness.
Until organizations value presence alongside analysis, they are likely to keep relying on external problem‑solvers who address symptoms while overlooking underlying structure. The real output is less a set of recommendations than organizational sight: helping teams recognize their recurring patterns and inherited biases.
Tomorrow’s advisory models may need to embrace the idea that genuine understanding tends to arise from dwelling within the system one seeks to change. The open question is whether consulting can adapt to this posture, or whether its economic incentives make that shift difficult.
References
Alvesson, M., & Johansson, A. W. (2002). Professionalism and Politics in Management Consultancy Work. Organization, 9(4).
Craig, D. (2018). Rip-Off: The Scandalous Inside Story of the Management Consulting Money Machine. Icon Books.
Mintzberg, H. (2004). Managers Not MBAs. Berrett‑Koehler Publishers.
Kahneman, D., & Klein, G. (2009). Conditions for Intuitive Expertise: A Failure to Disagree. American Psychologist, 64(6), 515–526.
Heidegger, M. (1962). Being and Time. Harper & Row.
Weick, K. E. (1995). Sensemaking in Organizations. Sage Publications.
Polanyi, M. (1966). The Tacit Dimension. University of Chicago Press.
Schein, E. H. (1999). Process Consultation Revisited: Building the Helping Relationship. Addison‑Wesley.
Gentner, D. (1983). Structure‑Mapping: A Theoretical Framework for Analogy. Cognitive Science, 7(2), 155–170.