START HERE

What you will learn

  • Describe a task as a sequence of visible steps.
  • Place AI assistance where its output can be checked.
  • Include a practical response to missing inputs, bad results and failed tools.

Before you start: Choose a task you know well. You can make the map on paper.

Map the work, not the software menu

A useful workflow describes what happens in the real task. “Open the AI tool” is a software action; “compare the three approved options” is work with a recognisable purpose. Start with the purpose so the map still makes sense if the tool changes.

Each step should have an input and an output. A decision should have labelled outcomes, such as accept, revise or request more information. These details make it easier to see who owns a step and where a process can stall. You do not need specialist diagramming notation to begin.

Separate drafting from taking action

Generating an outline is different from publishing it. Suggesting a command is different from running it. The map should show where a draft becomes an action and what check permits that transition.

This is especially useful for agent-assisted work. An agent is software that can select or carry out steps using tools. If it can send a message or change a system, the permission and approval for that action need to be explicit. Do not let a single box labelled “AI does the task” hide several different authorities.

Step-by-step process

  1. Name the trigger and finished result

    For example: “A new research question arrives” and “I publish a checked one-page brief.” Keep the start and finish small enough to explain.

  2. List the current steps in order

    Include collecting information, waiting for answers, checking and correcting. These steps often consume more effort than writing the first draft.

  3. Mark the decisions and owners

    Write who decides that sources are adequate, that a claim is supported or that a result may be released. “Human review” should refer to a specific decision.

  4. Choose one AI-assisted step

    Replace a clearly defined activity, such as producing a draft outline. Keep the surrounding information and review steps visible.

  5. Draw the alternative routes

    What happens when a document is missing, an output fails a check or a tool is unavailable? Include a manual route or a pause with a named next decision.

  6. Walk a real example through the map

    Use an ordinary case and an awkward one. If you cannot explain the next step when something fails, the map is not finished yet.

FOLLOW ONE EXAMPLE

Worked scenario

A personal research brief with an approval point

You are preparing a recommendation from three approved documents. AI can help draft the comparison, but you retain responsibility for the recommendation.

  1. Collect the documents and check that they answer the research question. If one is missing, request it before asking for a definitive comparison.
  2. Generate the comparison draft, then inspect its claims against the sources. Unsupported claims return to correction rather than going straight to publication.
  3. Write the recommendation using the checked comparison. Save the brief with references so the reader can inspect the evidence.

What this shows: The map explains where AI saves drafting effort and where your judgement remains necessary. It also tells you what to do when the evidence is incomplete.

The process at a glance

This map includes the two loops the example needs: request missing evidence and correct unsupported claims before publication.
ProcessDecisionHuman checkpoint
Read Mermaid diagram source
flowchart TD
 A[Research question] --> B[Collect approved documents]
 B --> C{Enough information?}
 C -->|No| D[Request missing evidence]
 D --> B
 C -->|Yes| E[AI drafts comparison]
 E --> F[Human checks claims]
 F --> G{Claims supported?}
 G -->|No| H[Correct the draft]
 H --> F
 G -->|Yes| I[Publish recommendation]

What you should have at the end

  • A map that another person can follow from trigger to finished work.
  • A visible boundary between an AI suggestion and an authorised action.
  • A manual or escalation route for each important failure.

Common mistakes and how to avoid them

Drawing only the successful route

A workflow is incomplete if a failed check has no next step.

Hiding decisions inside a large AI box

Separate finding evidence, drafting, approving and publishing.

Automating a poorly understood task

First clarify missing information and ownership. Automation will not resolve ambiguity by itself.

APPLY THE IDEA

Try it yourself

Your task: Map a task you completed this week using no more than eight steps. Add one missing-input case and one failed-quality-check case.

What to produce: A simple diagram with inputs, outputs, decision owners and two alternative routes.

Check your understanding: Could you hand the map to someone else and have them explain what happens when the draft is wrong?

Key terms in plain English

Trigger
The event that starts a workflow.
Handoff
The point where work or responsibility moves to another step or person.
Approval gate
A check that must pass before an action is permitted.
Recovery route
The planned response when the normal process cannot continue.