Readiness begins with an operating outcome
A credible AI initiative starts with a measurable change in an existing operation: less handling time, higher decision consistency, lower risk, improved conversion, or a better customer experience. “Use AI” is a technology preference, not a business case.
Write down the baseline, the intended change, and the people accountable for the metric. If the organization cannot establish a baseline, the first phase should usually be measurement and process discovery rather than model development.
Five conditions to test
A weak condition does not always stop the work, but it should change the scope, sequence, and level of assurance.
- Value: a specific metric, cost, delay, service level, or risk is expected to improve.
- Workflow: a named owner understands the current process, exceptions, and decision rights.
- Data: authoritative sources, permissions, quality gaps, and retention rules can be identified.
- Risk: unacceptable outputs, escalation rules, and human oversight can be described before launch.
- Operation: a team can monitor, support, update, and eventually retire the system.
Use the result to shape the first engagement
When value and workflow ownership are strong but data is weak, begin with data access and quality. When the workflow and data are understood but failure consequences are high, begin with risk classification, evaluation design, and human review. When all five conditions are credible, a bounded production pilot can test the system and its operating model together.
This framing aligns with NIST’s emphasis on governing, mapping, measuring, and managing AI risk, and with ISO/IEC 42001’s management-system view of organizational accountability. The readiness decision is therefore not only technical; it is operational and managerial.