OPERATIONS

Read a run before you automate it

Use one trace to find the missing context behind a workflow failure.

4 MIN READ

Three frosted lavender glass planes folded across the image

Before a workflow runs on a schedule, follow a single request through each step. Read the input, the decision and the output the way a teammate would. The trace should make it easy to explain why the request went where it did.

Inspect the transition

Focus on the moments where information changes hands. Check whether the next owner knows why they got the work, what action is expected and what to do when something is missing. If you cannot answer those questions from the trace, improve the handoff.

Use the last confusing request

Test a request that already caused trouble. When the revised workflow handles it, ask a teammate to read the trace and explain the decision in their own words. Their explanation will tell you where the workflow still needs context.

NEXT READ

Explore more field notes.

Browse the journal for more ways to design workflows around the people using them.

Create a free website with Framer, the website builder loved by startups, designers and agencies.