---
id: KB-MA-007
url: https://app.codecontract.io/help/marta/turning-an-answer-into-work
idioma: en
categoria: marta
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-MA-006, KB-MA-004]
citadoPor: [KB-MA-015]
---

# Turning an answer into work

_What to do with the list it just gave you, so it does not stay a curiosity._

**Responde a:** what do i do with the assistant's answer · from answer to action · the assistant gives me data but nothing changes · getting value from ai answers

Asking is the easy part and the one that hooks you. The problem shows up three weeks in: you ask, an interesting list appears, you close the screen and nothing happens. An answer that does not end in an action is time spent feeling informed.

## The rule of three exits

Every answer should end in one of these three. If it ends in none, the question was badly framed:

| Exit | When | What you do |
| --- | --- | --- |
| A call or a message | Someone specific has to move something | Write to them from the case itself |
| A change in the system | A wrong value, a missing expiry, a permission too many | Fix it there and then, not note it down |
| A decision to close | Whatever has been dead three months | Close it with its reason |

## The commonest mistake

Copying the list somewhere else — a note, an email to yourself — to deal with later. That "later" competes with everything else and loses. If the list has four names, resolve them now; if it has forty, the question was too broad and needs narrowing.

> [!WARNING]
> If you ask the same thing every week and the same unresolved list keeps appearing, the problem is not the question: nobody has been assigned to resolve it. No assistant fixes that.

> [!NOTE]
> A question that serves you every week deserves to be a saved filter, not a question. The assistant is for exploring; what repeats belongs one click away.

> [!IMPORTANT]
> Before acting on a fact with consequences — blocking a supplier, clearing an access — open it and check. The answer got you there in seconds; checking is still faster than having searched.

**Can it make the changes for me?**

It takes you there; actions that change something you confirm yourself.

**What if the list is huge?**

Narrow it: a shorter period, one site, one owner.

**Does it remember what I already resolved?**

The case reflects what you did; the next answer comes out different.

## Ejemplos

**A manager asks every Monday what is stuck and copies the list into a notebook.**

- Stops copying
- Resolves the four cases on the spot, from the case itself

→ Within a month the Monday list drops from twelve to three, because the ones that never got resolved stop reappearing.

**The answer says what is missing and nobody requests it.**

- Launches the request from there

→ The query becomes work done.

**The list is copied by hand somewhere else.**

- Acts on the files it returns

→ The copying step disappears.

**A gap is spotted and forgotten.**

- Turns the finding into a task

→ What was spotted is not lost.

**The same thing is asked weekly and acted on identically.**

- Turns the query into a process

→ The action happens by itself.

**The answer flags an error in a figure.**

- Corrects the figure from the document itself

→ The error closes where it started.
