The first 90 days — an AI adoption working plan

A sequencing guide for a bounded organisational initiative. These time windows organise the work; they are not a promise of delivery.

Days 1–15: define and baseline

Choose one operational problem, name its owner and speak to the people doing the work. Record volume, quality and effort. Identify the affected users and the decisions the system must not make without approval.

Days 16–30: prepare and design

Review data access, supplier options and integration. Build the evaluation set and fallback process. Agree the acceptance criteria and the review meeting before testing starts.

Days 31–60: test with supervision

Run a limited evaluation with representative users. Log errors and correction effort. Compare the new workflow against the baseline and revise the design where the evidence shows a problem.

Days 61–75: test operation

Exercise monitoring, incident handling, training and rollback. Confirm that the service can be supported by the team that will own it. Test what happens when sources, volumes or model behaviour change.

Days 76–90: decide

Present measured results and remaining uncertainty. Choose scale, revise or stop. Assign the next review date and continuing budget only when the operational case supports it.

AIStrategy.gr working resource · 6 November 2026. Adapt this template to the actual workflow and responsible teams.