AI for leadersPublished 10 min readRead in Vietnamese

Which tasks should you give AI? A stake-and-ambiguity matrix

For team leads, operations managers and SME owners listing the week's tasks and unsure which to hand to AI. Score each task on the damage if it is wrong and on ambiguity, read off one of four cells, then run a single trial before you trust the cell.

View .mdLinkedIn

Your list for the week has 20 lines. Which go straight to AI, which does AI draft for you to review, and which do you keep? I try an answer on a hypothetical case: Lan, operations manager at Chuyến Mẫu ("sample trip"), a delivery firm with 15 lorries in Can Tho. The firm, Lan and every figure are my invention.

The framework she uses is The AI delegate matrix. Its two axes have sources. The four cells do not: no source proposes this matrix.

Which tasks should you give to AI, and which two axes decide?

Ask two questions of each task: how much damage follows if AI gets it wrong, and is the brief clear or ambiguous? The answers put the task in one of four cells.

The AI delegate matrix

When a team lead hands out work to an AI-assisted team, which tasks can AI do alone, which need AI to draft and a person to review, and which stay human, given the stake and the ambiguity?

LowAmbiguity of the taskHigh
AI drafts, human reviewsMedium risk
Human onlyHigh risk
AI does it allLow risk
Human does it, AI challengesMedium risk
LowStake if wrongHigh
Figure 1 · The horizontal axis is the stake if wrong, the vertical axis the ambiguity of the task.Framework page

The stake axis borrows from Parasuraman, Sheridan and Wickens (2000), a paper written for designers of automated systems such as air traffic control. They define the risk of a decision as the cost of an error multiplied by the probability of that error, and write that low-risk decisions are strong candidates for high-level automation (Parasuraman et al., 2000, p. 292). I borrow that one idea.

"Ambiguity" is the site's word, not any paper's. What the research offers is the jagged technological frontier. Dell'Acqua and colleagues tested 758 consultants at Boston Consulting Group in spring 2023: one group had no AI, two had GPT-4. On 18 tasks inside AI's reach, AI users completed 12.2% more tasks, finished 25.1% faster, and human graders rated their work more than 40% higher. On one task built to sit outside its reach, AI users were 19 percentage points less likely to be correct (Dell'Acqua et al., 2023). The authors stress that tasks of similar apparent difficulty can fall on either side, and that even professionals struggle to see where the frontier runs.

So ambiguity predicts little about whether AI will fail. The experiment's inside-the-frontier tasks were fairly open, such as proposing at least ten ideas for a new shoe or drafting a press release (Dell'Acqua et al., 2023). The axis tells you how much judgement a person must supply: a clear task can be checked against a known answer, an ambiguous one has none.

How do you score a week's 20 tasks?

List all 20 and score each from 1 to 5 on both axes; 3 or above counts as high. The scale and threshold are mine, not any source's. Stake 1 means a fix takes minutes, 5 means losing a major customer or breaching a contract. Ambiguity 1 means you can write down what "right" looks like and check it in five minutes, 5 means many answers would be acceptable.

Here are 8 of Lan's 20 tasks. Every score is hypothetical.

Task Stake Ambiguity Cell
1. Copy orders from customer emails into the dispatch sheet 2 1 AI does it all
2. Sort 30 complaint messages into fault types 2 3 AI drafts, human reviews
3. Think up 10 names for the same-day city delivery package 1 5 AI drafts, human reviews
4. Reconcile the subcontracted haulier's rate card with the monthly invoice 4 1 Human does it, AI challenges
5. Draft a price-rise addendum for a large client, with a late-delivery penalty 5 2 Human does it, AI challenges
6. Letter to a large client explaining a two-day delay and compensation 4 4 Human only
7. Decide how to handle a driver after a collision 5 5 Human only
8. Pick 3 routes where returns jumped, from the order sheet and dispatcher's notes 2 1 AI does it all (pending trial)

Across all 20, Lan counts 7 tasks in "AI does it all", 6 in the drafting cell, 4 in "human does it, AI challenges" and 3 human only. Task 3 runs against instinct: ambiguity 5 does not mean AI is weak, because the creative tasks in the 2023 experiment sat inside GPT-4's reach (Dell'Acqua et al., 2023).

How do you run a one-trial test before trusting a cell?

Take a past case with a known answer, give it to AI exactly as you would give it to a person, and compare. The trial beats the cell. Four steps:

  1. Pick a finished case whose answer you trust.
  2. Give AI the information the person doing the job would have. The five-part context bundle lists five parts to keep ready.
  3. Compare every figure and conclusion.
  4. If it matches, keep the cell. If it is wrong in a way a skim would miss, move the cell towards the person. If the error is obvious, keep the cell and add a review step.

The frontier cannot be read off how hard a task looks, and in the experiment the people who did worse with AI tended to adopt its output and question it less (Dell'Acqua et al., 2023). One trial is not proof; where money is involved, I would run three cases.

Task 8 shows why. Lan scored it stake 2, ambiguity 1: clear figures, fifteen minutes' work. She gives AI last week's spreadsheet, which she has already analysed. Suppose AI picks the route with the most returns. But one line in the dispatcher's notes says 40 of those returns came from a single customer recalling a faulty batch, not from a trend. The figures match, so a skim would miss it. Lan moves the task to "AI drafts, human reviews" and logs: check the notes column too.

The outcome is invented; only the shape of the problem is borrowed. The outside-the-frontier task in the 2023 experiment was built from a spreadsheet and interview notes whose details changed the conclusion: 84.5% were right without AI, 60% and 70% with it (Dell'Acqua et al., 2023). The paper does not say what AI would do with Lan's spreadsheet today.

When do three quick questions do instead of the matrix?

When you have no time to score the list, ask three questions before each new task. They are Minimum viable judgement, this site's grouping of three more detailed frameworks; "minimum viable judgement" is the site's own label.

  1. Is it worth giving to AI? Anthropic (2024) says agentic systems often trade latency and cost for better task performance, and that you should consider when the trade makes sense (Anthropic, 2024). For the person delegating, I read that as: how long to write the brief and check the result, against doing it yourself?
  2. What does AI need to know? Anthropic (2025) advises aiming for the minimal set of information that fully outlines the behaviour you expect, and notes that minimal does not necessarily mean short (Anthropic, 2025). See The five-part context bundle.
  3. What is the damage if it is wrong? The cost of consequences is one criterion for choosing a level of automation (Parasuraman et al., 2000, p. 292). See The five-rung verification ladder and the five-rung verification ladder post.

A hypothetical example: Lan needs a 40-page warehouse lease summarised for the director before renewal. It is worth giving, because reading it all takes two hours. AI needs to know the decision is whether to renew, and to look hard at the early-termination penalty. If the summary misses that clause, the firm renews on the wrong terms, so Lan reads the clauses the summary points to. With large consequences, three questions are not enough on their own.

Going deeper: what do the sources show, and what do they not show?

Dell'Acqua and colleagues (2023) is a Harvard Business School working paper dated 22 September 2023. The study was pre-registered. They used the version of GPT-4 available at the end of April 2023 and randomly assigned people to no AI, GPT-4, or GPT-4 plus a prompting overview. The inside-the-frontier experiment had 385 people and the outside one 373 (Dell'Acqua et al., 2023). Limits I draw from the text itself:

  • One firm, one model, one moment, and a very high-skill group; the authors note that "higher-skill" is only relative. I have no data on the models of today.
  • There is only one outside-the-frontier task, built by the authors so that GPT-4 would err. They write that it was difficult to design a task outside the frontier where skilled people would consistently beat AI. So the paper does not say how common such tasks are in real work.
  • The "more than 40%" is the human graders' score. GPT-4 grading gave smaller gains, about 17% to 19%, and the authors note that GPT-4 is a more lenient grader.
  • The paper does not measure damage in money, so the stake axis does not come from it.
  • The version I read is a working paper that calls itself a draft. Some authors work at BCG, as the paper discloses.

Parasuraman, Sheridan and Wickens (2000) set out a model of four types of automation, each with graded levels, before generative AI existed. They say the model does not prescribe what should be automated (Parasuraman et al., 2000, p. 286), describe it as qualitative, and admit they have not said how to weigh the criteria against each other (Parasuraman et al., 2000, p. 294). The two Anthropic posts are a model developer's guidance to agent builders; I use one sentence from each. The four-cell matrix and the three questions are the site's own grouping, and no source proposes them.

I read the body of the Dell'Acqua paper from the MIT Sloan PDF, but only the captions of its figures; I did not read the tables after Table 1 or the appendices closely, nor any later version. From Parasuraman and colleagues I read the abstract, the model, the criteria (pp. 290–293) and the limitations (p. 294), and skimmed the rest. I read both Anthropic posts in full as they stand today.

Quick questions

Does the "AI does it all" cell mean nobody checks the work?

No. Parasuraman and colleagues treat low-risk decisions as strong candidates for high-level automation (Parasuraman et al., 2000, p. 292), but they also describe complacency: when a system is highly but not perfectly reliable, operators may stop monitoring it and miss the occasions when it fails (Parasuraman et al., 2000, p. 291). For this cell I suggest glancing at one sample of the output each week. That habit is mine; no source prescribes it.

Where do the 1 to 5 scale and the threshold of 3 come from?

From me, not from any source. The sources give two ideas only: the cost of consequences is one criterion for choosing a level of automation, and AI's frontier cannot be read off how hard a task looks. You can move the threshold. What matters is scoring consistently across the whole list and letting a one-trial test have the last word.

How often should I retest a cell?

No source gives a schedule. Dell'Acqua and colleagues write that AI's capability boundary keeps expanding, so professionals must recalibrate their picture of it (Dell'Acqua et al., 2023). My own rule: retest when the tool or model version changes, when an error slips through, and at least once a quarter for any cell that carries a lot of your work.

If AI takes the easy tasks, how do new staff learn?

The authors of the 2023 experiment call this an immediate danger: people stop delegating work inside the frontier to junior staff, leaving a long-term training deficit (Dell'Acqua et al., 2023). They raise the danger; they do not measure it. One way to soften it, and this is my own idea, is to have a new hire write the first draft of some tasks in the "AI drafts, human reviews" cell and then compare it with the AI's version.

References

Listed A–Z by author surname, Harvard style. A source with a DOI links to https://doi.org/…; one without links to its page or says plainly that it has no DOI.

  1. Anthropic (2024) Building effective AI agents. Anthropic Research.No DOIanthropic.comCited in 6 articles
  2. Anthropic (2025) Effective context engineering for AI agents. Anthropic Research.No DOIanthropic.comCited in 4 articles
  3. Dell'Acqua, F. et al. (2023) Navigating the jagged technological frontier: field experimental evidence of the effects of AI on knowledge worker productivity and quality. (Harvard Business School Working Paper No. 24-013).doi:10.2139/ssrn.4573321Cited in 2 articles
  4. Parasuraman, R., Sheridan, T.B. and Wickens, C.D. (2000) ‘A model for types and levels of human interaction with automation’, IEEE Transactions on Systems, Man, and Cybernetics, Part A: Systems and Humans, 30(3), pp. 286–297.doi:10.1109/3468.844354Cited in 2 articles
Keep reading

Related articles

All articles

Was this article useful?

Rate the article from 1 to 5 stars

No ratings yet.

Comments (0)

No comments yet. Be the first.

Leave a comment

Comments are moderated before they appear. That can take a few hours.