Can Harborview support the future combined company?
This review evaluates Harborview Medical Network as one current coordination system in the acquisition. The purpose is to understand whether Harborview’s operating conditions can support the future combined company the transaction requires.
Current System Exposed Under Future Load
Harborview can operate today, but the system is not structurally ready to absorb substantial integration pressure. The dominant constraint is Decision Traceability. The largest reality gap also appears in Decision Traceability, which means leadership and execution layers do not experience the operating system the same way.
Harborview must strengthen operating memory, decision reconstruction, ownership clarity, and escalation discipline before integration load increases.
Teams will struggle to reconstruct who decided what, when, and why once integration adds more parallel decisions, dependencies, and handoffs.
Executives rate the operating system much stronger than directors, managers, and individual contributors. This creates risk that leadership will add pressure before the execution system is actually ready.
As load increases, informal coordination will fail to preserve decision history, rationale, ownership, current state, and handoff context.
- Teams will struggle to reconstruct who decided what, when, and why.
- Escalation paths may absorb work that should be resolved closer to execution.
- Operating pressure may produce local workarounds instead of coordinated adaptation.
Executive Summary
Harborview currently relies on informal coordination, executive-centered interpretation, local workarounds, and memory-dependent decision reconstruction. This can work under familiar conditions, but it becomes fragile when integration increases decision volume and cross-boundary dependencies.
The acquisition requires Harborview to become part of a future combined company. That future system will require stronger operating memory, shared visibility, containment, and adaptation than Harborview currently demonstrates.
Current System Interpretation
Harborview operates through informal coordination.
Work moves through relationships, side conversations, manager interpretation, and executive clarification rather than through consistently reconstructable operating records.
This makes the current system dependent on people remembering context, interpreting intent, and carrying operational state across handoffs.
Leadership sees more stability than the rest of the system experiences.
Harborview shows a Significant Perception Gap across every operating dimension.
The average gap is 1.90. The largest gap is Decision Traceability at 2.01.
This matters because integration decisions are usually made by leaders who may overestimate the system’s readiness.
The first integration weakness is operating memory.
Harborview’s weakest structural condition is not effort, capability, or intent. It is the ability to reconstruct decision history and operating state reliably across layers.
Under integration pressure, this creates rework, duplicated context-building, reopened decisions, unclear accountability, and increased escalation.
Reality Alignment
This signal compares how executives, directors, managers, and individual contributors experience the same operating system.
| Operating Area | Executives | Directors | Managers | IC | Gap | Signal |
|---|---|---|---|---|---|---|
| Adaptation Capacity | 2.32 | 1.45 | 0.69 | 0.62 | 1.70 | Significant Perception Gap |
| Bottleneck Visibility | 2.49 | 1.52 | 0.63 | 0.59 | 1.90 | Significant Perception Gap |
| Decision Authority | 2.63 | 1.79 | 0.86 | 0.73 | 1.90 | Significant Perception Gap |
| Execution Containment | 2.49 | 1.51 | 0.70 | 0.52 | 1.97 | Significant Perception Gap |
| Decision Traceability | 2.52 | 1.43 | 0.63 | 0.51 | 2.01 | Significant Perception Gap |
Conditions Preventing Future-System Readiness
Decision Traceability
CriticalObserved
Execution depends on informal coordination, making it hard to reconstruct decisions and work status across layers.
Expected Impact
As integration adds parallel workstreams, teams will revisit decisions, lose rationale, and escalate for clarification.
What Must Become True
Decision history and execution state must be reconstructable without relying on memory or side conversations.
Authority Compression
CriticalObserved
Decision authority appears clearer at the top than it is experienced below director level.
Expected Impact
Integration questions will route upward, increasing leadership bottlenecks and delaying execution.
What Must Become True
Ownership, decision rights, and escalation paths must become interpretable and consistent across layers.
Constraint Opacity
CriticalObserved
Executives believe constraints are visible while managers and ICs experience bottlenecks as late-stage surprises.
Expected Impact
Integration bottlenecks will surface after commitments are made rather than before execution risk compounds.
What Must Become True
Harborview needs shared bottleneck visibility before cross-company dependencies multiply.
Containment by Heroics
CriticalObserved
Failures are contained through manager intervention, informal fixes, and priority reshuffling.
Expected Impact
Integration failures will spread before they are recognized and isolated.
What Must Become True
Failures need defined ownership, containment boundaries, and correction routines.
Stabilization Sequence
- Immediate Require documented decision and execution records for core operating workflows.
- Immediate Create shared visibility into active work, ownership, status, dependencies, and decision history.
- Next Standardize escalation behavior so recurring issues do not automatically move upward to leadership.
- Next Clarify which workflows require review before commitments, decisions, or changes move forward.
- Scale Carefully Increase integration load only after ownership, traceability, visibility, and correction routines hold in day-to-day operations.
Supporting Evidence
Operating Reality
Work moves forward through personal relationships, informal updates, and manager-level interpretation rather than through clearly defined processes. Accountability often hinges on who is present or vocal in discussions, with handoffs and decisions tracked loosely, if at all.
Coordination Under Load
As the number of decisions and dependencies rises, coordination becomes heavier and less predictable. Teams may wait for clarification on shifting priorities or revisit decisions, creating cycles of delay and rework.
Divergence and Alignment Signals
Executives believe routines are effective and can absorb additional pressure, while directors, managers, and individual contributors see more risk in informal coordination and unclear ownership. This divide leads to leadership assuming stability while execution teams absorb uncertainty and fix issues as they emerge.