How to Build a Project Management Workflow

Start with the stages work actually passes through

The instinct when building a workflow is to open a board tool and start adding columns from memory: To Do, In Progress, Done. That produces a board that looks like a workflow without functioning like one, because it was designed from what sounded reasonable rather than from what actually happens to a piece of work in that team.

The better starting point is to pick five recently finished pieces of work, say a hiring requisition, a marketing asset, a support ticket, whatever the team produces, and write down, honestly, every state each one passed through before it was done, including the ones nobody's proud of, like "waiting for someone to approve it" or "sitting in someone's inbox for four days." That messy list is the real workflow. The clean one you'd have written from memory usually isn't.

How many columns is enough

Two failure modes show up at opposite ends. Too few columns, typically just To Do, Doing, Done, hide where work actually gets stuck, because everything in "Doing" looks identical whether it's ten minutes from finished or blocked on someone else for a week. Too many columns, on the other hand, turn the board into a form to fill out rather than a picture of reality, and people start skipping stages just to avoid the friction.

Four to six columns covers most workflows well: something like Requested, Ready, In progress, In review, Done, with a Blocked marker that sits alongside a column rather than replacing it, since "blocked" can happen at almost any stage, not just one.

Setting WIP limits without guessing

A reasonable starting limit for any given stage is the number of people who actually work that stage, plus one: enough headroom that someone isn't blocked the instant a colleague is mid-task, but not so much that ten things can pile up unattended. It'll look too strict at first. That reaction is normal and usually wrong. The discomfort of a limit is what forces a team to finish something before starting the next thing, and finishing-before-starting is reliably what increases how much actually gets delivered, even though it feels like it should slow things down.

Adjust the number after a few weeks of real data, not before. A limit set from a guess and never revisited is barely better than no limit at all.

Writing a definition of done that holds up

"Done" without a written definition means whatever the person moving the card believes it means, and that belief varies by person and by how close the deadline is. A workable definition of done is short, specific and checkable by someone who wasn't involved in the work: "reviewed by someone other than the author" is checkable; "good quality" is not.

Every column deserves its own definition, not just the final one. A column called "Ready" needs its own answer to "ready for what, exactly," or items arrive there in wildly different states of actual readiness, and the next stage inherits the inconsistency.

Is the workflow actually built?

• Could someone new to the team read the board and understand what each column means, without asking?
• Does every column have a written definition of done, not just a name?
• Is there one place new requests land, rather than several depending on who's asked?
• Does at least one column have a WIP limit that's actually enforced, not just suggested?
• Has anyone looked at the workflow in the last quarter and asked whether it still matches reality?

Where a tool can help without becoming the point

Everything above can be built with a whiteboard and index cards, and plenty of teams run it that way for years. Where software earns a place is making the same workflow usable across departments that don't share vocabulary: engineering talks in sprints and tickets, HR in requisitions and candidates, marketing in campaigns and assets. ShipSprint gives each of those its own template and terms on one subscription, so a hiring workflow and a sprint board can sit side by side without forcing one team to adopt the other's language. New requests land in a shared triage inbox instead of someone's messages, and each column carries its own WIP limit, which covers the intake and limit decisions above directly.