THE USEFUL PART

What to take into your next project

  • Choose work that repeats and has a clear owner.
  • Use actual examples, including the awkward cases.
  • Agree how quality and effort will be compared.
01

Choose a task with a visible next step.

Look for work your team repeats: research, document preparation, enquiries, reports or follow up. Identify what comes in, what needs to happen and who owns the result. A narrowly defined task is easier to test than a brief to “add AI”.

02

Check the information before choosing the tool.

Gather representative examples, including the awkward cases. Check which documents, records and systems are needed, whether the team can access them and where information is missing. This determines the integration work as much as the model choice.

03

Agree what a useful result looks like.

Record a baseline: handling time, completeness, rework or time to the next action. Choose one primary measure and a small set of quality checks. Compare the proof of concept against the existing process using real examples.

04

Make review part of the workflow.

Define what the system can prepare or execute, what needs approval and how exceptions reach a person. The first build should make these boundaries visible so your team can test them.

Turn the idea into a first brief.

Write down the task, its owner, the records it uses and the result you would want to improve.

Use the discovery checklist ↗