An AI strategy the company can sustain

The problem it solves

Marketing bought the first one. Somebody in operations brought in the second because it solved a specific nuisance. The third arrived bundled inside a system the company was already paying for. Taken one at a time, none of those decisions was wrong.

Together they produce a situation nobody chose. The company cannot say precisely what of its information sits inside each service, who authorised each use, or what happens to everything accumulated there on the day it wants to move. When renewal comes round it cannot say which one to cancel either, because there is no criterion to measure any of the three against. The vendor conversation is led by the vendor.

Left to itself the pattern repeats, and the next purchase gets decided the way the last one did: by the quality of the demonstration and by the urgency of the department asking. What grows is not the organisation's capability but its dependence, and dependence is discovered late, once renegotiating has stopped being a comfortable conversation.

What it covers

The programme does not start with tools. It starts with the business. The opening block is a process map drawn by the leadership team over its own operation: where each decision is taken, on what information, who answers for it, and at which points the work stops and waits. Only then are the places marked where a tool would change something verifiable, and, with equal care, the places where it would change nothing at all.

The second block sets rules. The team drafts the organisation's principles of use, the classification of its information by whether it may leave the company, and a named owner for every use case being considered. This is group drafting with open disagreement in it, because the value sits in the agreement reached rather than in the document left behind.

The third block is assessment. Through scenario analysis the group works through a vendor proposal without leaning on the demonstration: which problem on the map it solves, what information it asks for, what happens to everything accumulated if the relationship ends, and what capability remains inside the company once the contract does. A management simulation closes the block with a decision to approve, defer or retire, argued in front of the rest of the group.

The final block builds the plan. Stages with progress criteria rather than dates chosen out of enthusiasm, an explicit retirement condition for each tool, and a long conversation about internal capability: what the organisation has to be able to do itself so that it is not dependent on whoever is selling to it. The programme ends when every decision in the plan carries a named owner and a review date.

What participants learn

• Map the business processes and locate the points where a tool would change something verifiable.
• Define principles of use, information limits and a named owner for each use case.
• Evaluate a vendor proposal from your own problem rather than from the demonstration.
• Design a staged plan with progress criteria instead of dates chosen out of enthusiasm.
• Establish how a tool is approved, reviewed and retired in this organisation.

Agenda

1. 01Process map and the points where a tool changes something
2. 02Principles of use and the organisation's information limits
3. 03Named responsibility for each use case
4. 04Assessing a vendor without being led by the demo
5. 05Data: where it lives, who maintains it, who may see it
6. 06A staged plan and the criteria for moving between stages
7. 07Internal capability versus external dependence
8. 08How and when a tool that did not work gets retired

What the organisation leaves with

• A process map marking where a tool would have an effect and where it would have none.
• A document of principles of use and information limits, argued through and approved by the leadership.
• A vendor assessment routine written in the language of the business rather than of the product.
• A staged plan with the criteria that authorise moving on, and the retirement condition for each tool.