The Architecture Review
Enterprise AI Playbook
Part 02 · 2026-07-13

Aligning AI Initiatives with Business Readiness

A readiness model for matching AI ambition to organizational capacity across five dimensions — strategic fit, data foundation, platform & skills, process fit, and risk & governance — multiplied by the change capacity nobody budgets for. Readiness Gap = Ambition − Capacity.

By Tom Ward, Enterprise Architect — Cloud & AI

Download the deep-dive PDF6 pages — the full framework in detail, a readiness checklist, and curated references. Free, no signup.
Aligning AI Initiatives with Business Readiness — architecture infographic
Why the org chart fails before the architecture does

The five readiness dimensions

01

Strategic Fit

Tied to an outcome, or to FOMO?

Every initiative must trace to a business outcome someone in the business — not IT — will be measured on. An initiative without an executive sponsor who will defend its budget in the next downturn isn't ready; it's a science project with good PR.

02

Data Foundation

Can you actually feed it?

The dimension that quietly kills the most programs. Your demo ran on a clean sample; production runs on the real thing — accessible, governed, sufficient quality, and legal to use. All four. Scope it per use case, not as a paralyzing enterprise-data problem.

03

Platform & Skills

Can you build it and run it?

Building a prototype and running a production capability are different sports. You need the platform to deploy, monitor, evaluate, and roll back — and the people to operate a non-deterministic system over time. Ask who runs this on day 90, and whether they're hired yet.

04

Process Fit

Can the workflow absorb it?

AI amplifies a process; it doesn't fix a broken one. Drop a model into an unmapped, unstable workflow and you get automated chaos, faster. Readiness includes a deliberate human-in-the-loop design matched to the error tolerance you set in Strategic Fit.

05

Risk & Governance

Can you stand behind the output?

Set your risk appetite deliberately, map compliance obligations, and name who is accountable — before you build, not at the launch review. Treated as a design input the way NIST's AI RMF frames it, governance becomes requirements you can build against rather than a blocker.

Six gating questions

Answer each honestly for a specific initiative — not your organization in the abstract. Every “no” is the dimension to close before you commit the budget.

  1. This initiative traces to a measurable business outcome with a named executive sponsor who will defend the budget.
  2. The data it needs is accessible, governed, sufficient quality, and legal to use — verified, not assumed.
  3. You can not just build it but operate it — deploy, monitor, evaluate, roll back — with people who already exist.
  4. The target workflow is stable and mapped, with a deliberate human-in-the-loop design.
  5. The risk tier is set, compliance is mapped, and one person is accountable for the system's output.
  6. Your organization has the change capacity — bandwidth, trust, training, sponsor stamina — to absorb it.

Going deeper

Sources worth your time, roughly in the order a program team should read them.

Next parts ship over the coming weeks.

Get the next part by email