Enterprise Architecture Value Model - Embed architects in at-risk and high-risk initiatives
Enterprise Architecture Value Model
Embed architects in at-risk and high-risk initiatives
The at-risk and high-risk initiative practice is the single most effective mechanism for making your architecture function’s value undeniable to you and to the executive leadership who controls its budget. It is also the engagement model that most reliably produces the organizational credibility required to advance toward Level 4.
Why This Is the Right Starting Point
At-risk and high-risk initiatives are the moments in your portfolio calendar when your attention and the attention of your peers is most concentrated. These are the programs where you are in weekly status meetings, where the CEO is asking for updates, where the board has line-of-sight to delivery timelines, and where your organization’s ability to execute is most directly on display. They are also the programs where architectural complexity is most likely to be a root cause of the risk — where unresolved integration dependencies, poorly understood cross-domain relationships, technology choices made without enterprise context, or governance failures that accumulated quietly have created conditions for failure that no amount of delivery velocity will overcome.
When your architecture function steps into these programs and takes ownership of the architectural track of their recovery — when it makes hard calls, resolves architectural root causes, and moves programs toward successful delivery — it demonstrates value at the exact moment when value is most visible, to the exact audience that controls its budget and organizational scope. You will remember which team was in the room when things were hardest. So will your CTO, your delivery leaders, and your business unit heads.
Distinguishing At-Risk from High-Risk Programs
A high-risk program carries significant potential for failure before it begins — due to its strategic stakes, technical complexity, scale, dependency profile, or novelty. For high-risk programs, your architecture function’s posture should be preventive: embed early, establish architectural guardrails, surface and sequence dependencies, and provide the decision authority that keeps the program on a sound structural footing before the conditions for failure develop.
An at-risk program has already become endangered in flight. Timelines have slipped, integration assumptions have proved incorrect, a vendor has underperformed, or a dependency was not visible when the program was scoped. For at-risk programs, the posture should be interventional: triage the architectural state, identify root causes, produce a credible remediation plan, and take accountability for the architectural track of the recovery. Your architecture function should have a defined intake process for both types — catching high-risk programs early and engaging at-risk programs before their situation becomes unrecoverable.
The Delivery-Accountable Engagement Model
What makes the Level 3 engagement qualitatively different from advisory engagement is the nature of the commitment. The Level 3 architect embedded in a program owns architectural decisions within the scope of the engagement, maintains a current architectural risk register reported directly to the executive sponsor, coordinates across all architectural domains to ensure the recovery plan is coherent, and is measured by whether the program delivers. This requires architects who can make hard calls under pressure, defend those calls when they are challenged, and communicate risk clearly and directly to you and to other executive sponsors. These are not comfortable positions — and that discomfort is precisely what makes the engagement organizationally significant.
The Compounding Track Record
As your Level 3 practice accumulates a track record — programs rescued, architectural risks resolved, delivery timelines recovered — it builds an evidence portfolio that is qualitatively different from anything the advisory model can produce. The question you ask about your architecture function shifts from “is it worth the investment?” to “do we have enough capacity to cover all the programs that could benefit from its engagement?” That shift in the question is the organizational evidence that Level 3 is working — and it is the argument for the Level 4 investment that follows.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers