What is a Workflow?
Workflow
A workflow is the defined sequence of stages a piece of work moves through from start to finish, along with the rules for what moves it forward.
A workflow is the path a piece of work follows from the moment it enters a system to the moment it's delivered, plus the rules that decide when it moves from one stage to the next. On a Kanban board, the columns are the visible part of a workflow: To Do, In Progress, Review, Done. The workflow is the whole system behind those columns, who can move a card between them, what has to be true before it moves, and what happens automatically when it does.
Every team already runs a workflow, whether or not anyone wrote it down. A designer who always drafts, sends for feedback, then finalizes is following a three-stage workflow, even if it only lives in her head. Writing it down and building it into a board turns an informal habit into something the whole team can rely on, and something a new hire can follow without asking.
The value of a defined workflow is consistency, not rigidity. A good workflow still lets a task skip a stage when a client waives feedback, or bounce back a stage when revisions are needed. What it removes is the ambiguity of "what happens next" that every workflow-less team eventually runs into.
The Three Parts of a Workflow
A workflow has three components working together, and most confusion about the term comes from treating them as one thing.
- Stages, the distinct states a piece of work passes through (Backlog, In Progress, Review, Done)
- Transitions, the moves allowed between stages, and who's permitted to make each one
- Triggers, actions that fire automatically when a transition happens, a notification, an assignment, an alert
Workflow vs Process vs Kanban Board
These three terms get used interchangeably, but they sit at different layers. A process is the general method a team uses for a category of work, how we onboard a client, how we ship a design. A workflow is that process expressed as specific stages with rules for moving between them. A Kanban board is one common way to run a workflow visually, columns for stages, cards for the work moving through them, but a workflow can exist without a board; a checklist with sign-offs is a workflow too.
For the full mechanics of how a Kanban board works, its columns, WIP limits, and swimlanes, see the Kanban entry. This entry focuses on the workflow underneath the board, not the board itself.
Designing a Workflow: Stages, Owners, Exit Criteria
A workflow stage needs three things to function: a name that describes a state, not an instruction; an owner responsible for moving work out of it; and exit criteria, the specific condition that has to be true before a card can leave. "Review" with no exit criteria means different things to different people. "Review, exits when the account manager approves the draft" means one thing.
- Name each stage as a state (In Review), not an instruction (Send to Client)
- Assign one role responsible for moving work out of each stage
- Write the exit criteria for every stage before the board goes live
- Add a new stage only for a state with a genuinely different owner or approval step, not every sub-step of existing work
Automation Triggers: What Can Fire on a Transition
The most useful workflows don't only define stages, they attach actions to the transitions between them. A trigger fires automatically the moment a card crosses a boundary, so nobody has to remember to send the update by hand.
Common triggers: a notification to the next owner when a card enters their stage, an email to the client when a card reaches "Delivered", a timer that starts when a card enters "In Progress" and stops when it leaves, and a risk alert when a card sits in one stage past a set number of days. That last trigger overlaps with Project Alerts, the module that watches for stalled work across every workflow in the workspace rather than one board at a time.
A Worked Example: A Content Approval Workflow
A 12-person marketing agency runs a five-stage workflow for every blog post and social asset:
| Stage | Owner | Exit criteria | Trigger on entry |
|---|---|---|---|
| Brief | Account manager | Topic, word count and deadline filled in | Assigns to a writer |
| Draft | Writer | First full draft attached to the card | Notifies the editor |
| Internal Review | Editor | Edits complete, no open comments | Moves the card forward or back to Draft |
| Client Approval | Account manager | Client approves or requests changes | Emails the client a link to the draft |
| Published | Account manager | Live URL added to the card | Notifies the client and closes the card |
When to Add a Stage, and When Not To
A new stage earns its place when it represents a state with a genuinely different owner or a real waiting period, not every small step inside a stage that already exists. Splitting "Draft" into "Outline" and "Full Draft" makes sense if a different person owns outlining than writing. It doesn't make sense if the same writer does both back to back with no handoff or wait between them.
A workflow with 3 to 6 stages covers most agency work. Past 7 or 8, most teams find that some stages exist to track sub-steps rather than real state changes, and cards start to feel like they're moving through admin instead of work. Revisit the workflow after the first month of real use, not before, since the mismatches that matter only show up once real work has run through it.
Workflows in Melororium
Every project's Kanban board is a customizable workflow: columns are renamed and reordered per project, so a design team's five-stage approval flow and a dev team's four-stage sprint board run side by side in the same workspace. Project Alerts adds the automation layer, six trigger types including a bottleneck alert when a card hasn't moved in a set number of days, delivered to Inbox, Slack or email. Recurring Projects reruns an entire workflow on schedule for retainer clients, cloning the same stages and resetting statuses at the start of each cycle instead of rebuilding the board by hand. Agency plan is $59/mo for 15 users and includes both.
In Melororium
Build custom workflows in Melororium
Common mistakes with workflow
What teams get wrong most often, and what to do instead.
- 1
Naming stages as instructions instead of states
Labeling a column "Send to Client" instead of "Awaiting Client Approval". An instruction describes an action someone forgot to do; a state describes where the work stands, and only one of those is useful on a board six people are looking at.
- 2
No exit criteria on a stage
Leaving "Review" undefined, so one person moves a card forward after a five-minute skim and another holds it for two days waiting for a second opinion. Without a written condition for leaving a stage, the same stage means something different depending on who's running it.
- 3
A trigger for every transition
Wiring a notification to fire on every single move a card makes. Within a week the channel is full of noise nobody reads, including the transitions that mattered.
- 4
Designing it once and never touching it again
Building the workflow at kickoff and treating it as fixed. Real work exposes stages that don't fit within the first few weeks, and a workflow that never gets revised stops matching how the team operates day to day.
Frequently asked questions
Is a workflow the same thing as a process?
Related but not identical. A process is the general method (how we approve a design). A workflow is that process turned into specific stages with rules for what moves work from one to the next. Most teams have processes long before they formalize them into a workflow.
How many stages should a workflow have?
Most agency workflows run well with 3 to 6 stages. Add a stage only when it represents a genuinely different owner or a real wait, not another sub-step of work already covered by an existing stage.
Can a project run more than one workflow at the same time?
Yes. Different task types on the same project often need different stages. A dev team might run a 4-stage sprint workflow for code tasks and a separate 3-stage workflow for bug reports on the same board, using swimlanes or tags to keep them apart.
What's the difference between a workflow trigger and a project alert?
A workflow trigger fires on a specific transition inside one board, like notifying the next owner when a card enters their stage. A project alert watches thresholds across every project in the workspace, like a task that's been stalled for 5 days regardless of which board it's on.
Does Melororium let me build a custom workflow?
Yes. Kanban columns are fully customizable per project, so each team defines its own stages, and Project Alerts layers automation on top with six configurable trigger types.
