D06 - Technology Coherence
Definition
Whether your tech stack was designed or whether it accumulated. One tool per problem, never revisited, until nobody can say what you're actually paying for.
Why It Matters
Technology fragmentation is not a line-item cost problem. It is a coordination tax: the hours your team spends manually syncing information across tools that should never have been allowed to duplicate each other in the first place. The cost compounds every week the portfolio goes unreviewed.
The Diagnostic Question
List your five most operationally critical systems. Classify each as Tier 1 (failure stops the operation), Tier 2 (failure significantly degrades it), or Tier 3 (failure is inconvenient).
For each Tier 1 system, name its documented stress limit under concurrent operational pressure and the person authorized to initiate an emergency halt.
If you cannot answer both questions for any Tier 1 system, you have an unassessed single point of failure — and its risk level is unknown, which is treated as the highest-risk classification.
What This Dimension Looks Like When It's Working
- Every system in the technology stack is classified by operational tier, with a review cadence and governance standard appropriate to its criticality — Tier 1 systems are reviewed most frequently with the most explicit fitness assessment.
- Tier 1 systems have documented stress limits, tested backup or halt protocols with named authority, and at least one leading indicator monitoring proximity to their operational ceiling.
- New tools pass a four-question evaluation before adoption — not acquired because one team member already knew the tool and had a problem to solve.
- Technology decisions are made on total cost of ownership, including implementation time, integration development, internal training, and eventual replacement — not on license cost alone.
The Most Common False Positive
A functioning technology stack is not a coherent one.
All three Operational Failure Archive entries in this dimension had functioning systems that were not coherent:
- Target Canada's SAP ERP processed transactions correctly on seven of eight servers.
- Southwest's SkySolver managed crew scheduling effectively under normal conditions.
- Knight Capital's SMARS had processed millions of trades without incident.
Each system failed not because it malfunctioned under ordinary conditions, but because it had never been assessed for the specific failure scenario that eventually produced it.
The Failure It Prevents
Target Canada's $4.1 billion net loss. Southwest Airlines' $800 million Q4 2022 impact. Knight Capital's $440 million loss in 45 minutes.
All three trace to the same root cause: a Tier 1 system deployed or managed without the governance standards appropriate to a system whose failure stops the operation.
All three failures were preventable. All three are documented in the Operational Failure Archive — this is the only dimension with three direct real-world case studies.
What This Dimension Requires And Enables
D06 requires D01 — Every major Tier 1 system implementation requires processes to be documented before configuration begins, not after. A system configured against undocumented processes is configured against assumptions.
D06 requires D05 — Tier 1 systems need leading indicators for operational health, not just lagging failure metrics that confirm a problem after it has materialized.
D06 enables D10 — Technology decisions made on TCO basis rather than license cost basis protect operational leverage as the stack scales with revenue and complexity.
Terms
Operational Failure Archive
Industry Articles
Apply
- The Headroom HQ AI Starter Kit
- The Operations Tech Stack Audit
- The SaaS Audit and Consolidation Checklist
Take the HQ Score assessment to see whether your technology stack was designed or accumulated →