Start with the workflow, not the chatbot

Most failed AI initiatives start too broadly. The organisation selects a tool, announces an AI program and asks staff to find uses for it. A stronger path begins with one workflow that already matters.

What makes a strong first workflow

Look for work that happens frequently, follows a recognisable pattern and currently creates delay, duplication or rework. Good candidates often include enquiry qualification, meeting preparation, proposal assembly, client onboarding, document requests, progress reporting and recurring compliance tasks.

Avoid beginning with a use case that makes high-stakes decisions about people, safety, credit, employment or legal rights. The National AI Centre stresses that risk depends on the specific use, not simply the tool. Drafting a marketing email and screening job applicants may use similar technology, but they require very different controls.

Map the current state in plain language

• Trigger: what starts the work?
• Inputs: what information is required, and where does it live?
• Steps: what do people actually do, including informal workarounds?
• Decisions: who decides, using what criteria?
• Handoffs: where does work wait, duplicate or lose context?
• Output: what does the customer or next person receive?
• Evidence: how will the business know the new workflow is better?

Separate deterministic work from judgement

Traditional automation is best for fixed rules: create a task, validate a required field, send a reminder or update a status. AI is useful where the work involves language or pattern recognition: summarise notes, classify an enquiry, draft a response or retrieve relevant knowledge. Human judgement remains essential where the answer is consequential, ambiguous or requires professional accountability.

Define the pilot before building

Write a one-page pilot contract covering the outcome, users, data, risks, acceptance tests, human approval points and baseline measures. If that cannot be explained simply, the use case is probably still too broad. A focused workflow can create a credible result in weeks and a reusable pattern for the next process.