The Three-Column Trap
Every project management tool starts the same way: three columns, three statuses, one size fits all. Todo. In Progress. Done.
It works for a weekend side project. It falls apart the moment a real team touches it.
Design teams need Review, Revision, Approved. Engineering teams need Ready for QA, In QA, Blocked, Deployed. Sales teams need Qualified, Proposal Sent, Negotiation, Closed Won. The moment you try to map any of these flows onto three generic buckets, you lose information — and you lose trust in the board.
What Happens When Status Doesn’t Match Reality
When the status system doesn’t reflect how work actually moves, people stop updating it. Cards pile up in “In Progress” because there’s no “Waiting for Client”. “Done” gets used loosely because there’s no “Deployed to Production”. The board stops being useful and becomes a compliance checkbox — something you update before the standup, not something you actually work from.
Custom Status Models in FlowEra
FlowEra lets you define status models from scratch, or inherit them from your team’s templates. Each status has a label, a category (not started / in progress / done / cancelled), and a color. You assign a status model to a flow — and that model governs every task in that flow.
This means your Design flow can have its own statuses, your Engineering flow has its own, and your Marketing flow has its own. They don’t have to overlap. Drag-and-drop ordering controls the visual sequence on the board.
When you change a status model, all tasks in that flow immediately reflect the updated labels. No manual migration.
Status Categories Unlock Analytics
Because every status maps to a category, FlowEra can calculate meaningful metrics regardless of what you name your statuses. A task that moves from any “in progress” status to any “done” status contributes to your lead time calculation. Burndown charts know which tasks are complete even when “complete” is called “Shipped” in one flow and “Published” in another.
You get custom language without losing cross-flow analytics.
Exit Criteria — What “Done” Actually Means
Custom statuses are the mechanism. The meaning comes from your team agreeing on what it takes to move a card from one status to the next. FlowEra doesn’t enforce checklists on status transitions — that’s intentional. Rigid gates create bureaucracy. What matters is that your status names are explicit enough that everyone on the team knows exactly what they mean.
If “Ready for QA” means the branch is merged and the staging environment is updated, name it that. Don’t make people guess.
Getting Started
When you create a new flow in FlowEra, you choose a status model — either one of the built-in templates or a custom model your admin has configured. You can update the model at any time, and the change takes effect immediately across the board, list, and Gantt views.