What is a workflow.
The word workflow gets used to describe a meeting, a checklist, a piece of software, an email chain, and a wall of sticky notes. None of those are workflows. This lesson defines the term in a way that lets you recognise one when you see it, and identify when you do not have one yet.
Every lesson in the workshop builds toward the same destination. An operation you can see, scale, and step away from. This lesson is the foundation. Without an agreed definition, nothing in the lessons that follow holds together.
The plain definition.
A workflow is a repeatable sequence of work that moves through defined stages, has clear ownership at each stage, and produces a defined output. Three components. If any one is missing you do not have a workflow, you have an activity.
Repeatable means it happens more than once and broadly the same way each time. Defined stages means you can name the steps in order without making them up. Clear ownership means each stage has a person or role accountable for it. Defined output means you know what done looks like before you start.
That is the whole definition. Everything else in this workshop builds on it.
Workflow, process, SOP, automation.
These four words get used as if they mean the same thing. They do not, and the confusion is one of the main reasons businesses cannot decide what to fix.
A process is the broad activity. Onboarding a client. Approving an invoice. Closing the month. It describes what is happening at a high level.
A workflow is the specific path that process follows. For client onboarding it might be intake, KYC, engagement letter, system setup, kickoff call. The workflow makes the process concrete.
An SOP, a standard operating procedure, is a document describing how a person should do their part of a workflow. It is a reference, not the workflow itself. An SOP without a workflow is a document that lives in a folder. A workflow without SOPs still functions, the institutional memory just lives in people.
An automation is software doing one or more steps of a workflow without a person. Automation is a property of a stage, not the workflow itself. You can have a fully manual workflow, a partly automated workflow, or a fully automated workflow. All three are still workflows.
The anatomy of a workflow.
Every workflow has five parts. If you cannot name all five for a piece of work, the workflow does not yet exist.
The trigger. What starts the workflow. A signed engagement letter, an inbound enquiry, a calendar date, an alert from a system. The trigger is the moment the work begins.
The stages. The named steps the work passes through. Each stage is a distinct unit of work with a beginning and an end, not a vague description of activity.
The owners. The person or role accountable for each stage. Not who might do it on a good day, but who is responsible for it being done.
The handoffs. How the work moves between stages. This is where most workflows break. An email, a verbal update, a status change in a system, a meeting. Handoffs that are not defined are the source of most operational friction.
The exit. The condition that means the workflow is complete. Without an explicit exit, work drifts back into the workflow indefinitely.
A worked example.
Take client onboarding at a fiduciary firm. Most firms will tell you they have a process for it. Some will tell you they have a workflow. Here is what a workflow actually looks like when you write it out.
Trigger. The signed engagement letter is returned by the client.
Stages. KYC pack collection, screening, structuring review, document execution, account setup, kickoff call.
Owners. KYC sits with the onboarding administrator. Screening with compliance. Structuring with the engagement lead. Execution with the partner. Account setup with operations. The kickoff with the relationship manager.
Handoffs. Today most of these handoffs happen by email, which is why nobody can answer the question, where is this client right now.
Exit. The first invoice has been issued and the client has had their kickoff call.
That is a workflow. The same firm may describe twenty pieces of work as workflows and only have one or two that pass this test.
Why the definition matters.
If you cannot answer what the trigger is, what the stages are, who owns each stage, how the handoffs happen, and when it ends, then you do not have a workflow. You have an activity that happens by habit.
The habit version of a workflow is cheap. It needs no tooling and no documentation. It works when volumes are low, the team is small, and the people running it have been there a long time.
It is also the version that breaks the moment any one of those three conditions changes. Volume goes up. Team grows. Someone leaves. The habit version cannot survive any of those, because the workflow only existed in the heads of the people running it.
The next lesson covers why that matters financially, and what a defined workflow actually buys you.