Institutional Viability
“Can the organization sustain it?”
Ensures workflow capacity, post-handover ownership, vendor exit paths, and funded operating rhythms.
Can the organization sustain the review, escalation, and retraining burden once the implementation team leaves?
Treating AI deployment as a completed project handover rather than a permanent operational commitment.
A funded operating cadence and post-project RACI must be signed off before production release.
Institutional Viability: Operating Capacity & Review Queue Load Simulator
An AI system that creates more review and escalation burden than the organization can comfortably absorb will inevitably collapse into rubber-stamping or operational failure.
Demand: 25.0 hrs/day vs Supply: 42 hrs/day
SUSTAINABLE CAPACITY
Reviewers have adequate time for independent diligence without fatigue.
Evidence Conditions for Institutional Viability
Can the real workflow absorb the system’s review, escalation, exception and fallback burden without relying on heroic effort?
Are operating roles, decision rights and handover responsibilities defined for the period after the original project team leaves?
Are the skills, vendor dependencies and exit paths sufficient to sustain, change or retire the system over time?
Is there a funded operating cadence for monitoring, evidence renewal, incident review, retraining and periodic permission renewal?
Companion Book Chapters (3)
Monitoring, Drift, and Permission Renewal
Continued Operation as an Active Permission Decision
Vendor Dependency and Platform Risk
Managing External Foundation Models and Vendor Lock-in
The Decision Quality Playbook
Institutionalizing Decision-Grade AI Across the Enterprise
Operational Artefacts (2)
Monitoring Contract
Defines runtime SLOs, drift thresholds, error budget depletion rules, and quarterly permission renewal triggers.
Vendor Dependency & Portability Review
Audit external foundation model and API dependencies for operational lock-in, SLA drift, and exit portability.