Technical

Overview

What technical readiness asks

• Technical readiness is the infrastructure dimension: identity, access controls, integration capacity, the ability to run or call models in a way that meets the organisation's security posture. For a mid-sized professional services firm this often resolves to the limits of the current Microsoft or Google environment; for a hospital network it becomes a much harder conversation about clinical systems and data egress.
• Technical readiness is the dimension most easily mistaken for the whole of the question, particularly inside IT functions, and it is also almost never the binding constraint. Naming it last is deliberate: a strategy that begins with infrastructure has usually let the IT function set the agenda for an organisational problem. The framework's stance is that infrastructure follows pattern allocation rather than the other way around.
• Closing the technical-readiness gap is standard engineering and architecture work: provisioning identity, expanding integration capacity, building the security posture the deployment will need. The work is recognisable to any IT function with experience operating SaaS platforms in regulated environments. Technical readiness is the dimension Encapsulated Utility depends on most heavily, because Utility deployments are mostly software-engineering exercises in which the AI happens to be probabilistic and the surrounding system makes them operational.