Skip to content

Start with useful work. Prove the result.

Choose one recurring task, test it with the people who do the work and compare the result with their current process. Expand from a result the team can explain.

What a useful workflow needs

Look beyond a fluent answer. Review how a proposed tool gets information, uses permissions, records decisions and returns uncertain work to a person.

A clear place to review the work

People need to see the request, inspect the proposed result and choose the next action.

A reliable path through the task

Track what has finished, what is waiting and how to recover without repeating an action.

The right system access

Check whether the proposed tool can access the exact records and actions your task needs. Test each connection and its permission limits.

Sources the team can check

Check that people can see the source for an answer and that access rules still apply when a model retrieves information.

Approvals at the right moment

Define which decisions need approval, which actions are prohibited and what records a reviewer needs.

A useful record of what happened

Record the source, proposed action and result so the responsible person can review a problem.

Questions for the people responsible for the work

Before a wider rollout, review security requirements, test mistakes and confirm how people can correct or stop the work.

OWASP LLM Top 10 Mitigations

Include tests for misleading instructions, unsafe use of an answer, unreliable source material and actions outside the tool’s permissions.

Prompt Injection Output Validation Access Control Data Exposure Supply Chain

NIST AI Risk Management

Use a risk framework to organize the questions: who is affected, what could go wrong, who reviews the result and how the team monitors changes.

Risk Identification Trustworthiness Lifecycle Evaluation Documentation

Checks to agree before a wider rollout

Tool Access

Least privilege with separate service accounts and scoped tokens for each integration.

Human Approvals

Required at risk points: money movement, customer comms, record deletion, policy changes.

Output Validation

Test allowed actions and business rules, including how a request is stopped when the needed permission or information is missing.

Full Audit Trail

Agree which inputs, sources, actions and approvals must be recorded, then verify that reviewers can find them.

Make each next step a clear decision

Agree what evidence is needed before moving from a test to broader use. The person responsible for the work should be able to explain why the result is useful.

1

Understand the task

Describe the task, the available information, the current process and the decisions that need a person.

2

Measure the current process

Measure the current process and agree what a useful change would look like before setting a target.

3

Test the result

Test representative cases, difficult inputs and permission failures. Compare the result with the current process.

4

Production Launch

Check the agreed requirements, review responsibilities and fallback process before expanding access.

5

Review and improve

Review mistakes and changes regularly. Test again when the information, model, permissions or business rules change.

Plan for change

Compare the cost of changing providers, exporting information and maintaining connections before choosing an approach.

Compare provider options

Identify the provider-specific features a task needs and the effort required to test or change them.

Confirm each connection

Confirm the exact system access a project requires. Vendor names alone do not establish a working connection or permission to change records.

Keep the workflow maintainable

Ask how the workflow is maintained, where its records are stored and what it takes to move or replace a component.

What would a useful test need to show?

Bring a specific task, a few representative examples and the questions your team needs answered before choosing a tool.