A useful workflow map explains how work moves, what evidence each step needs and who decides when something is ready. It does not need a sophisticated diagramming app. Begin with one repeatable outcome, then write the path from trigger to completion in the language the person doing the work uses.

Before you start

Pick a task you can observe this week, such as preparing a client report. Gather one ordinary example and one awkward example. Keep the current process separate from the process you would like to have. Otherwise the map quietly becomes a proposal and stops describing where the real friction is.

The workflow

  1. Name the trigger as an observable event. “Monday at 9 am” or “a signed agreement arrives” can start a process. “When needed” hides the decision about when work should begin.
  2. List the inputs and their source of truth. A report might require an approved date range, source exports and account notes. Specify what happens when one input is absent or stale.
  3. Write each action as a verb with an output: collect metrics, reconcile totals, draft commentary, request approval. Split a step when its owner or required permission changes.
  4. Mark every decision. Separate exact checks from judgments requiring context. For each branch, write the condition and destination, including the case where the condition cannot be determined.
  5. Define completion and failure. “Sent” may be the end of delivery, but the record should also hold the approved version and timestamp. Give failures a named owner and a visible queue.

Worked example

Illustrative example: the monthly reporting map starts when the month closes. The workflow collects exports, checks date ranges, reconciles totals and drafts a summary. A missing export routes to the account owner instead of producing a partial report labeled complete. Approval releases the exact reviewed version; an edit after approval returns it to review. This is a proposed blueprint, not an installed integration.

Your worksheet

  • Outcome and boundary: ___
  • Trigger and expected frequency: ___
  • Inputs, owners and source systems: ___
  • Steps with output for each: ___
  • Decision conditions and fallback path: ___
  • Human approval and evidence: ___
  • Completion record and failure owner: ___

Test it

  1. Walk a normal example through the map without skipping a box.
  2. Remove one input and verify the map still tells you what happens.
  3. Ask a teammate to explain the map back using only its labels and notes.

What to measure

Record active work time, waiting time and corrections separately. The map is ready for an automation discussion when each handoff has an owner and every branch has a destination, including uncertainty.