Workflow Management Software: Stop RunningYour Process From Memory

Your best process has a single point of failure, and it is a person. The one who remembers to chase the approval. The one who spots the request before it goes cold. The one who knows whose turn is next. Put them on a flight for six hours and watch what happens: the approvals stall, the requests pile up in five different inboxes, and nobody notices until the deadline has already passed. You did not build a process. You built a dependency on one person’s memory and you have been calling it a process.

Workflow management software is how you fix that. It turns the steps you currently hold in your head into a defined process: work arrives one way, moves to the right person automatically, and stays visible from the first request to the final sign-off. Done well, the process stops depending on memory and starts running itself.

This guide covers what a workflow management system actually is, the four workflow types worth knowing, and exactly how to build one, using Asana, the platform we implement for teams every week.

"53% of the average knowledge worker’s time goes to “work about work,” not the work itself."

"90 workdays a year one 240-person agency saved on internal coordination after standardising workflows"

"1 source of truth replaces the five inboxes a request used to scatter across"

Why processes break when they run on memory

Before you can fix a process, it helps to name exactly how it fails. In our implementation work, broken workflows almost always break in one of three places and none of them show up on a deliverable. They show up on your calendar and in your retrospectives.

1. Requests arrive five different ways

A design request lands in a direct message with no deadline and no brief. A vendor sign-off sits in an email. A new-hire setup starts as a hallway conversation. When work comes in through every channel at once, there is no single place to see what your team has actually been asked to do, so priorities get set by whoever asks the loudest, not by what matters most.

2. Someone has to remember the next step

An approval waits on a manager who is out of office, and nobody realises it is their turn until the deadline has already passed. When handoffs run on memory, your process moves only as fast as whoever happens to be paying attention. That is not a people problem. It is a design problem.

3. You discover the bottleneck in the retrospective

At the quarterly review, the team learns that every request sat for four days waiting on legal. Nobody could see it while it was happening, so a delay you could have fixed in a week ended up costing a quarter. Spreadsheets and chat threads are not workflow management tools they can hold information, but they cannot route it, escalate it, or show you where it is stuck. A real workflow management system is built to catch all three of these failures before they cost you anything.

What a workflow management system actually is

A checklist tells you what to do. A workflow management system decides who does it next and shows you where the work stopped. The difference is everything that happens between the steps and that gap is exactly where most processes break. Every genuine workflow has four moving parts:

● A trigger — the event that starts the work, like a submitted intake form or a new hire’s start date.

● Stages with owners — the work moves through defined steps, and each stage has one person clearly responsible for it.

● Conditions — when more than one path is possible, a rule decides which way the work goes (for example, routing purchases over €5,000 to finance).

● Reporting — a live record of where everything stands, so status is visible without anyone having to ask. The checklist test A checklist has only the stages. It cannot tell your teammate when it is their turn, so the moment a second person gets involved, you are back to sending reminders. If your “process” is a document people are supposed to follow, you do not have a workflow management system yet you have a wish.

The checklist test

"A checklist has only the stages. It cannot tell your teammate when it is their turn, so the moment a second person gets involved, you are back to sending reminders. If your “process” is a document people are supposed to follow, you do not have a workflow management system yet, you have a wish."

The four types of workflow worth knowing

Most processes follow one of four patterns. Knowing which one you are dealing with tells you how to build it and stops you forcing a judgement-heavy process into rigid steps, or vice versa.

Four workflow types

Type	How it moves	Example
Sequential	Each steps wait for the one before it	A contract can't go out for signature utill legal signs off
Parallel	Steps run at the same time	IT sets up a laptop while HR handles paperwork
Conditional	The path changes based on an answer	A purcahse under  €5,000 goes to the team lead; anything larger adds finance
Case	The path is left to judgement as work unfolds	A customer escalation that could go several ways

How to build a workflow management system in Asana

This is the part teams overthink. You do not need code, and you do not need to boil the ocean. Pick the single request your team gets asked about most, and build these six pieces for it. By next Monday you will see exactly where that process slows down.

Step 1 — Map the process and its stages Before you set anything up, write down what kicks off the workflow and who owns each stage. Most teams find at least one step that two people both think they own surfacing that alone is worth the exercise. Keep it to a single page: trigger, stages, owners, and the decision points where the path can branch.

Step 2 — Build the intake with a form Swap scattered requests for one intake form that feeds a single project. Turn the details you always end up chasing the deadline, the brief, the budget into required fields, so every request arrives ready to start. You get one queue for everything your team handles, instead of five inboxes you have to keep checking. This one change removes more friction than any other.

Step 3 — Turn the stages into sections or custom fields The stages you mapped become the structure of the project; where a task sits tells you where the work stands. From there, each person picks the view that matches how they think. Designers move work across a board, you plan dates on a timeline, someone who just wants a quick status scans the list, and the launch team watches deadlines on a calendar. One process, seen four ways.

Step 4 — Add rules for assignment, routing and status This is where workflow automation earns its keep. When a request moves to review, a rule assigns it to the right approver and tells the requester it is in progress. When a due date gets close, a rule nudges the owner. Nobody has to remember whose turn it is, because the system remembers for them.

Step 5 — Package it as a bundle so other teams reuse it Once the workflow runs, a bundle applies the whole setup,forms, fields, rules and all to other projects in one step. The next team starts from the version that already works instead of rebuilding their own from scratch. This is how a good process spreads across an organisation without a committee.

Step 6 — Track it on a dashboard and fix the bottleneck A dashboard shows how many requests sit at each stage and which are overdue. If approvals start stacking up at legal, you see it this week while it is still a four-day delay and not a lost quarter. Connect the apps your team already uses, and work that starts in chat or email still lands in the same workflow instead of escaping it.

"Start narrow, then widen Do not try to systematise every process at once. Build the intake form and two rules for your single most-requested item. Prove it works for one team, then use a bundle to roll the proven version out to the next. Momentum beats completeness a workflow running Monday is worth more than a perfect one still in planning."

What it looks like for each team

A workflow management system pays off fastest on the processes you run again and again. Here is what that looks like across an organisation.

Marketing — campaign and creative requests

How many creative requests are already waiting on review? Marketing can answer that before committing to a launch date. Every request comes in through a form that asks for the brief and deadline up front, so no work starts without a brief. A rule routes each request to the right designer, and the work moves through review until it is approved.

Operations — approvals and internal requests

A new vendor needs sign-off. In the past that request would have sat in someone’s inbox. Now it comes in through the same form as every other purchase, and rules route it to the right approver based on amount or category. When a due date nears, a rule nudges them. You can see who owns each request and how long it has been waiting without chasing anyone.

HR and IT — onboarding and provisioning

Your twentieth hire should onboard exactly like your first. When a hiring manager submits a new-hire form, that person gets a project built from the same bundle as everyone before them. IT has equipment and accounts ready before day one, and the manager’s first-week check-ins are already on the calendar. Nobody rebuilds the checklist from memory.

“By standardising and automating processes, our teams stay on top of things, save time, and can focus on what really matters.”

— Christian Röhrich, Team Lead, Pitch & Project Management, We Are Era

We Are Era, a pan-European talent agency and content studio with 240 employees across eight locations, moved its work requests and client inquiries onto intake forms, let rules move work forward by due date, and gave every team the same starting process through templates. The result: roughly 90 workdays a year saved on internal coordination, with actions taken in the platform growing 15% year over year as more work ran through it.

Where workflow management ends and the bigger picture begins

Workflow management sits inside a wider discipline. Business process management (BPM) is the broader practice of improving how a company operates; managing individual workflows is one part of it. Before you build anything, map out the steps of your process and turn them into a simple workflow diagram the clarity you gain there is what makes the build fast. And as AI agents start to sit inside the same projects as your team, the line between "managing the workflow" and "running the workflow" is shifting. We covered that shift in agentic work management vs project management.

Not sure which process to systematise first?

Take our Spreadsheet Scorecard to see where your processes leak the most time and effort or book a free 30-minute call and we’ll map your highest-friction workflow with you. As a certified Asana Solutions Partner, we build the system so your process runs without you holding it together.

→ Take the Spreadheet Scorecard

→ Book a free 30-minute workflow call