What a workflow is
A workflow is the path a piece of work follows from the moment it arrives to the moment it is finished. It might be handling a customer request, producing a weekly report, publishing a post or processing invoices. Most people have a handful of these recurring paths, and they often evolved by accident rather than by design.
Because a workflow grows one patch at a time, it tends to collect extra steps: a check added after one mistake, a copy kept “just in case,” an approval that nobody remembers the reason for. Simplifying it means looking at the whole path once and removing what no longer serves a purpose.
Step 1: Pick one workflow
Choose a process that repeats often and that annoys you a bit. Starting with one keeps the effort small. Good candidates are things you do weekly or daily, where you notice yourself hunting for information or waiting on someone.
Avoid beginning with the largest, most political process in your organization. A small personal workflow is a safer place to practice.
Step 2: Write down what actually happens
Take a sheet of paper and list each workflow step in the order it really occurs, not the order it is supposed to. For each step, note:
- What you do
- Where it happens (which tool or place)
- Who else is involved
- Roughly how long it takes, or how long it waits
The waiting matters. In many processes, the work itself is short while the time between steps is long. Seeing this on paper often shows where the real delay hides.
Doing this once, honestly, is the core of the exercise. You do not need special software; boxes and arrows on a page are enough.
Step 3: Look for four kinds of waste
Read through your map and mark steps that fall into these groups:
- Duplicates. The same information entered or stored twice.
- Handoffs. Moments when work passes from one person or tool to another. Each handoff risks delay and misunderstanding, since the receiver needs context.
- Checks without purpose. Approvals or reviews that rarely change anything.
- Detours. Steps that exist because of an old tool or a problem that has since been fixed.
Not everything marked is removable. Some checks protect against real risks, and some handoffs are unavoidable, such as when another person has the needed skill or authority. The goal is to find the ones you can question, not to strip everything out.
Step 4: Ask what would happen if a step vanished
For each marked step, ask: if I skipped this, what would go wrong, and how likely is it? If the honest answer is “nothing much,” try removing it. If the answer is “something important,” keep it and perhaps find a lighter way to do it, such as a short checklist instead of a long review.
When a step involves other people, talk to them before changing it. A step that looks pointless from your seat may support someone downstream. In a workplace, this is also a moment to be careful with anything related to safety, money, legal obligations or customer data, where rules often exist for good reasons.
Step 5: Reduce handoffs
Fewer handoffs usually mean fewer delays. A few common approaches:
- Let one person own a task from start to finish where possible.
- Put the needed information in the request itself so the receiver does not have to ask.
- Use one shared place for status instead of several message threads.
- Agree on a standard format so people do not reformat each time.
If you work alone, handoffs may be between your own tools, such as notes in one app, tasks in another and files in a third. Consolidating these reduces the copying.
Step 6: Write the new version down
Once you have a shorter path, write it as a simple numbered list of three to eight steps. If it is longer than that, the process may be two processes. A short written version is easier to follow, to teach to someone else and to improve later. Keep it somewhere you actually look.
Then run it for a few weeks before judging. First attempts often reveal a small snag you can adjust.
A small hypothetical example
Imagine a weekly status update that currently goes like this: collect numbers from two spreadsheets, paste them into a document, send the draft to a colleague for review, wait, fix small wording changes, send it to a manager, and then copy the final version into a team chat. That is six steps and at least one wait.
A simplified version might be to keep the numbers in one shared sheet, write the update from a saved template, skip the colleague review when nothing unusual happened, and post it directly to the one place people read it. That is three steps (update the sheet, write from the template, post) and no waiting on a reviewer. The example is hypothetical, and a real process may have reasons for more steps, but it shows the kind of question to ask.
Keeping it simple afterward
Workflows drift back toward complexity unless someone looks at them. A quick look at your key processes during a weekly review or every few months is usually enough. Ask whether a step has been added that you cannot explain. If so, question it.
Simpler is not always faster or better, and some complexity is necessary. But a workflow you can describe in a few lines is one you are more likely to follow consistently, and that is where most of the benefit tends to come from.