Practical AI at work
What Should You Delegate to AI at Work? Start With One Task
You do not need to hand over an entire job to make AI useful. Choose one recurring task, decide what you want the tool to do, and set a clear way to check its work. This guide gives you a simple delegation card you can try on a meeting summary, document, research task, or team workflow.
What does it mean to delegate a task to AI?
Delegating work to AI means assigning a tool a defined part of a task while people remain responsible for deciding what happens next. The AI might produce a first draft, sort information into categories, or summarise a supplied document. A person checks whether the result is accurate, appropriate, and useful before acting on it.
This is different from asking a tool to “do my job” or making it responsible for a consequential choice. Most work contains smaller steps with different levels of risk. Drafting a routine status update is not the same as deciding what a customer should be promised, which candidate to hire, or how a team role should change.
A useful first experiment isolates one repeatable step. That makes the task easier to explain, the output easier to inspect, and the result easier to compare with the way you work now.
Why start with one task?
AI's value depends on the work, the person using it, and the way the task is set up. A study of 5,179 customer-support agents examined a generative AI assistant used during customer conversations. In that setting, the researchers reported a 14% average increase in issues resolved per hour. The gains were larger for newer and lower-skilled agents, while experienced and highly skilled agents saw minimal impact.
That finding is not a forecast for every role or workplace. It shows why a team should test a tool on a particular task rather than assume the same benefit will reach everyone. A small trial can reveal whether the tool saves time, whether the quality is acceptable, and who needs additional guidance.
Starting small also makes it easier to notice problems. If a summary invents an action item, or a draft changes the meaning of a policy, you can tighten the instructions or decide that the task is not suitable for AI support.
The one-task AI delegation card
Choose a task that happens often and has an output you can check. Write down the answers to these five prompts before opening an AI tool:
- Task: What specific, repeatable piece of work do I want help with?
- AI's role: Should the tool draft, summarise, compare, or organise information?
- My check: Which source, facts, or criteria will I use to verify the result?
- Human decision: What judgement, approval, or communication remains with me?
- Worth repeating? Did it save enough time without lowering the quality I need or creating extra checking work?
Each prompt prevents a different kind of mismatch. A specific task narrows the request. Naming the AI's role makes the expected output clearer. The check gives you a standard for judging it. Identifying the human decision prevents an assistant's draft from being mistaken for approval. The final question tests whether the process is useful, not just impressive on a first try.
Keep the card with the task notes. After one or two trials, you can update the prompt, add a missing check, or decide not to use AI for that task. You do not need to turn every experiment into a permanent workflow.
Worked example: turn meeting notes into follow-ups
Imagine that after a project meeting you need to share a clear record with colleagues. The source is a set of notes, and the desired result is a short list of decisions, action items, and open questions.
| Delegation card field | Example answer |
|---|---|
| Task | Organise these meeting notes into decisions, action items, and open questions. |
| AI's role | Summarise and group information from the supplied notes only. |
| My check | Compare every item with the original notes; confirm names, dates, and wording. |
| Human decision | Confirm the record and decide whether it is ready to share. |
| Worth repeating? | Check whether the organised draft saves time after review and corrections. |
You could phrase the instruction like this:
“Use only the notes below. Organise the information into decisions, action items, and open questions. Include an owner or deadline only when it is explicitly stated. If an owner or deadline is missing, write ‘not specified’. Do not infer missing details or add recommendations.”
When you review the result, check whether a discussion point has been presented as a decision, whether an action has been invented, and whether an owner or deadline has been guessed. If the notes are unclear, correct the record with the people who were in the meeting rather than asking AI to resolve the ambiguity.
Other tasks you can test with the same card
The framework works across many kinds of routine work. The key is to define the boundary: what material the tool can use, what output it should produce, and what you will inspect before relying on it.
- Email: Ask for a first draft from bullet points you provide. Check names, commitments, tone, and whether the draft says more than you intended before sending.
- Documents: Ask for a summary of a supplied policy or report. Verify important statements against the original, especially exceptions, conditions, and dates.
- Research: Ask the tool to organise questions or compare claims from sources you provide. Check that each claim is supported by those sources and that important disagreements are not hidden.
- Team workflows: Ask AI to map steps from an approved process description. Ask team members to confirm what happens in practice before changing responsibilities or measures.
These are starting points, not automatic approvals to use AI for every version of the task. The data involved, the cost of a mistake, and your organisation's rules can change what is appropriate.
How to review the result and decide whether to repeat it
Before you begin, decide what “good enough” means for this task. A summary might need to include all decisions and omit interpretation. An email draft might need to keep the original intent and contain no unapproved promise. A comparison might need to show the same criteria for each option.
Then compare the output with its source. For work that affects people, money, safety, legal obligations, customer commitments, or organisational decisions, use an appropriate human reviewer and the checks required by your organisation. Do not rely on a fluent answer as proof that it is correct.
Also count the whole task, not only the time spent generating the output. Include the time required to prepare inputs, correct errors, verify facts, and explain the result to others. If AI saves a few minutes but adds substantial review or risk, it may not be worth repeating.
After the trial, record a simple outcome: repeat as written, revise the instructions, use a different tool or source, or keep the task fully human-led. A clear “not suitable” result is useful learning too.
From a personal test to a team workflow
A successful personal experiment is not automatically ready for a team. Before adopting it more widely, agree on the task's purpose, permitted information, review standard, ownership, and how people can report errors. Ask the people who do the work where the process might fail or create extra effort.
NIST's AI Risk Management Framework offers one way to think about organisational responsibility through four functions: Govern, Map, Measure, and Manage. In plain terms, teams can set who is responsible and what rules apply, understand the use case and its risks, evaluate how it performs, and make changes when issues appear. The framework is voluntary; it is a useful structure for discussion, not a substitute for your organisation's own policies.
For a first team discussion, use these questions:
- Which specific task are we trying to improve, and who performs it today?
- What information is allowed in the tool, and what must stay out?
- What does a correct, useful result look like, and who checks it?
- Which decisions remain with a person, and how will we handle mistakes?
- How will we know whether the change saves time or improves the work without shifting hidden effort to someone else?
These questions connect everyday tool use to workflow design. The goal is not to automate for its own sake. It is to decide where AI can assist, where people need to remain involved, and how the team will learn from the result.
Take your next step with AI
Choose the session that fits your next question: leading organisational change, or using AI in everyday work.
Leading AI Transformation: People, Culture & Strategy
11 November 2026 · 5pm CET
Explore how to redesign work, support teams through changing roles, and plan practical next steps for AI-driven change.
Register for the transformation masterclass
ChatGPT, Claude or Gemini? Make AI Useful in 60 Minutes
12 November 2026 · 6pm CET
Practise choosing tools, checking answers, and applying AI to everyday tasks while keeping human judgement and safe use in view.