What should you consider before bringing AI into your work?

Start with one role and one question type. Bring source samples, the desired result and the points that need human review.
Discuss your AI pilot
View checklist text

Prepare a useful sample set

  • Task samples: collect recurring questions or tasks and explain how people currently find information, organise it or complete the work.
  • Source samples: choose an authorised document collection and identify sources, versions, owners and applicable scope.
  • Result samples: bring a manual example or desired answer, including its format, source references and criteria for use.

Explain where the task fits

  • Entry point: identify who starts the task, where they do it and where the input comes from.
  • Handover: explain who receives the output, what happens next and whether editing or approval is required.
  • Tools and access: list existing systems, available documentation and permitted access, with unresolved items flagged.

Define how the pilot will be reviewed

  • Ownership: identify who asks questions, checks results, maintains materials and approves publication.
  • Evaluation tasks: use the same real questions to check sources and results, recording missing information, human review and out-of-scope cases.
  • First scope: define the initial sources and user roles, review for external actions, and the timing and budget direction.

Four questions for an AI task

Define one task’s input, sources, handover and exception handling before choosing the size of the collection or integration scope.

What is the input?

Show real examples of questions, files or tasks, with the output format the user needs.

Where is the supporting information?

Identify authorised sources, current versions and owners, with access expectations for each role.

Who receives the output?

Place the result in the existing workflow, with ownership of checking, editing and the next action.

How is uncertainty handled?

Define whether missing or out-of-scope information should prompt clarification, a pause or human judgement.

More questions to work through together

Start with a focused discussion. Bring a usable collection and one real task, with other items marked for confirmation.

How do we choose between document versions?

Identify the current version, owner and update rules. List conflicting or uncertain materials separately before deciding whether to include them.

Can AI outputs be left unchecked?

Define review around the use case. Internal reference, customer messages and system updates have different approval responsibilities; important results need verifiable support.

Let's talk about your project

Websites / Business systems / AI applications

Chat on WhatsApp