Why Your 78/100 DTRA Score Is a Lie: The Three-Gate Model That Predicts Failure

01 The 78-Point Scorecard: Why the Number Lied

A manufacturing company launched a digital transformation with ample budget, a cutting-edge architecture, and a full TOGAF-based DTRA assessment scoring 78/100—above the internally agreed 75 passing line. Yet within six months daily active users plummeted from an expected 2,000 to 130, and staff reverted to Excel. The project lead presented the assessment: three categories (Foundational 30, Impact 95, Sustaining 60, each out of 100) weighted 10%, 60%, 30% respectively, yielding 3 + 57 + 18 = 78.

Three flaws emerged, none in the scoring mechanics:

"Conditions met" ≠ "conditions sufficient." Executive support was evidenced by a kickoff speech and signed charter, but the real test—whether the CEO would personally resolve departmental conflicts and sustain funding for three years—was unchecked.

The passing line was arbitrary. The 75 threshold came from a room of department heads agreeing "75 feels safe." No external benchmark or target-state definition backed it.

Weighted averaging erased veto items. The foundational score of 30 (only 10% weight) was drowned out by high impact (95) and sustaining (60) scores. The DTRA standard explicitly states:

If the organization does not meet the requirements of the foundational factors, it is futile to evaluate for impact and sustaining factors.

The three factor groups are not parallel scoring dimensions but three serial gates : fail the first, and later efforts are wasted.

An image illustrates the three additive components (3, 57, 18) showing the foundation contributes only 3 points to the total.

02 Three Gates, Layer by Layer

The DTRA model's 5-5-5 structure (five items per gate) signals equal granularity across three sequential checkpoints:

Gate 1 – Foundational Factors (Entry Ticket): Vision, Sponsorship & Guidance, IT Capability, Culture, Business Case. This gate answers only: "Does the organization qualify to start?" A single failure—misaligned vision, transient sponsorship, pervasive resistance—means the project should not launch regardless of budget or tech.

Gate 2 – Impact Factors (Risk Control Line): Business Model Fit, Skills & Competency, Technology Maturity, Ecosystem, Implementation Path. This gate doesn't veto but determines rollout difficulty and rework probability. Typical failure patterns: new system merely digitizes old processes; training collapses at first exception; upstream/downstream data remains disconnected, requiring manual spreadsheet shuttling.

Gate 3 – Sustaining Factors (Long-Term Operations Baseline): Value Realization, Policy & Regulation, Funding & Resources, Scope & Scale, Governance & Compliance. This gate assesses post-launch viability. The last two items—Scope & Scale, Governance & Compliance—appear only here because the standard treats "how far to roll out" and "who owns it" as survival issues, not startup issues. The most common outcome is "peak at launch": usage spikes week one, then zero maintenance, zero iteration, zero value review; years later the system runs but nobody remembers its purpose.

A diagram shows the three gates chained—later gates inaccessible if earlier ones fail.

When the project lead suggested raising the passing bar to 90 across all three, the expert countered: the gates are serial, not parallel. Even with perfect scores on gates 2 and 3, a 30 on gate 1 means do not start —whether you average, take the minimum, or set a higher threshold.

03 Borrow the Ruler, Not the Passing Line

No score exists without a ruler; the passing line must be tailored to the enterprise's own transformation goal. The same "staff skill = 60" means something completely different under two objectives:

Tool replacement only → 60 is adequate.

End-to-end business process integration → 60 may cause systemic disaster.

The assessment chain must run in sequence:

Define transformation goal → Customize assessment ruler → Gap analysis against current state → Produce shortfall list → Design governance improvement strategy

. An image depicts this flow.

04 Three Shortfall Types, Three Distinct Action Sets—Never Mix

Assessment's end is not a problem list but an action plan. Each gate's gaps demand a dedicated strategy; mixing them cancels effectiveness.

Foundational gaps → Repair the soil, control the tempo. Convert leadership vision into executable clauses with a three-year stable-funding commitment; lock in a project sponsor with monthly dedicated reviews (not a one-off kickoff); reshape change culture to tolerate failure and add retrospective mechanisms; shore up IT infrastructure; replace "competitors did it" with a calculable ROI business case.

Impact gaps → Shrink scope, target fixes. Run focused training and external hiring for skill gaps—not blanket literacy drives; pilot only in departments with highest business-process fit; pre-integrate ecosystem interfaces and data-exchange pain points; adopt a phased rollout rhythm, never big-bang. Small-step pilots allowed; full-scale launch forbidden.

Sustaining gaps → Front-load mechanisms, build in phases. Lock value KPIs and review cadence before go-live; separate one-time build budget from long-term iteration funding; institutionalize policy-compliance tracking; embed operations, iteration, and value management into fixed role descriptions. Pre-define rollout scope/scale ceilings—overextension without governance turns "in use" into "merely running." Pilot phase may relax sustaining mechanisms; scale-up phase must have all three gates solid.

When asked "Can we launch first and fix sustaining later?" the answer: "You can launch, but you buy 'launch,' not 'survival.' On the budget sheet they're the same line item; three years later they're two different endings."

Epilogue

Digital transformation is never a pure technology battle; it's a tug-of-war between organizational maturity and change cadence. Technology can be bought, software deployed. The three hardest gaps—unified top-down vision, fault-tolerant culture, and a complete talent pipeline—cannot be solved by spending money. The standard's closing line is blunt: Technology is no longer the real problem; culture is what stalls most transformations.

Readiness assessment is not a report card for ranking; it's a dashboard for pacing. A report card ranks; a dashboard tells you whether to accelerate or brake right now. First see which gate you're stuck at, then decide how big a step to take next.