---
title: "Not everything is yes or no: the trust scale by task type"
slug: escala-no-todo-es-si-o-no
lang: en
situation: liderar
format: hoja
minutes: 5
video: 18
updated: 2026-10-19
---

# Not everything is yes or no: the trust scale by task type

> For anyone debating "do we let AI do this?" with their team and feeling there are only two answers.

## When to use it

- The committee argues approve everything or reject everything, and nobody proposes the middle.
- A task has been "in pilot" for months and nobody knows what would expand it.
- Someone said no out of fear, or yes to everything, and the conversation needs order.

## The sheet

Deciding on AI is not just yes or no. Many of the best decisions are a third answer: yes, but changing something (scope, data or contract). This scale turns that "something" into five levels of autonomy; the last column is the question that moves a task up one level.

| Level | The answer | What it means in operations | Illustrative task | Question that moves it up a level |
|---|---|---|---|---|
| 1 | No, for now: it stays with a person | AI does not take part; reviewed in six months. | Deciding a dismissal; signing a contract. | What would have to be true to try it in one small area? |
| 2 | Yes, changing the scope: one area, not the whole company | Pilot in one team; one person reviews all output. | First draft of client replies in one team. | Is the data it uses clean and approved? |
| 3 | Yes, changing the data: sort the information first | Clean, permitted data; full review. | Summarising contracts for a person to review. | Is there an easy exit, and a number to track? |
| 4 | Yes, changing the contract: an easy exit | More areas; sample review; can be switched off cheaply. | Classifying support tickets and proposing a reply. | Three months of sample review, no incidents and one number that improved? |
| 5 | Yes, in full: it operates with an owner | AI executes; a named person answers for the result; quarterly review. | Transcribing and summarising internal meetings. | No level 6: does it still have an owner and a review date? |

Reading rule: a task moves up one level at a time, only when someone answers the question with evidence, not enthusiasm.

## How to fill it in 5 minutes

1. List the tasks in the area where AI is already used or someone wants to use it.
2. Place each one on a level using the "what it means in operations" column, not "the answer".
3. Answer each level's question with what exists today: clean data, easy exit, a number; yes or no.
4. Check the tasks at level 1 or 5: do they belong there, or did nobody want to discuss the middle?
5. The most common mistake: approving a task straight to level 5 because "the tool already does it". The level is set by your operation, not the vendor.

## The line that is almost always missing

The last column. A committee places tasks on levels and leaves them there forever. The question that moves a task up turns the scale into a decision that advances: it protects you from saying no out of fear and yes to everything. If a task cannot answer it, it stays where it is; that is a decision too.

## If this becomes a big decision

If moving a task up a level involves a contract that is hard to reverse and carries your name, the free tools at vicsol.org/decision-clarity/ help you structure it. They do not replace a formal review.

---

Vic Sol · Decision Desk · vicsol.org/resources/ · Free to use with attribution.
This sheet structures a conversation; it is not legal, financial or audit advice.