Knowledge Tree
and Butterfly
More thinking, less grinding

How much of your week could a do-bot take?

Self-assessment · eight questions · two minutes

Most analytical weeks hold a repeatable core: the quarterly report, the monthly refresh, the table someone asks for every Tuesday. Some of it an agent could take over safely. Some of it should stay in human hands. Some of it could stop.

Pick one piece of recurring work and answer for that, as it actually runs rather than how it should. The questions are about the work, not how keen you are on AI. Nothing is recorded until you send it.

Rung 1Head and handsThe work runs because you run it.
Rung 2Written downThe steps are recorded, but hands still move the numbers.
Rung 3ScriptedCode does most of it. Checks and finishing still live in people's eyes.
Rung 4Hand-over readyMapped, scripted, with a person's check at each hand-over.
  1. Q1Are the steps of this work written down anywhere?
  2. Q2How much of it is copying and pasting between tools?
  3. Q3You are off sick on the day. Could someone else run it?
  4. Q4How are the tables and charts in the final output made?
  5. Q5Where do the human checks sit?
  6. Q6Which steps would nobody miss if they stopped?
  7. Q7Is there a picture of the whole workflow, start to finish?
  8. Q8An agent takes one step tomorrow. How would you check its work?

Your result

Answer the 8 questions

The button opens an email to us, copied to Rabbie, our robot, who keeps the diary. Your result travels in it so we can prepare. You can change or delete it before you send, and nothing leaves your browser until you do.

Conventions Codified is where we map a workflow like yours and mark what to automate, what to keep and what to stop, and Roboduck is the half-minute film version.

Back to Conventions Codified →

Score –/24result ↓