In 30 seconds

Good states are few, clearly different, and tied to a real change in what happens next. Define them by looking at where work actually waits and who is responsible at each point.

Why this comes up

When status lives in people's heads or in the wording of emails, work gets forgotten, duplicated or handled out of order. Clear states fix this cheaply, before any automation, and they are what lets software act safely later.

How to find the right states

Start from where work waits

Look at your map. Wherever an item pauses, waiting for a person, a decision or information, there is probably a state. "Waiting for approval" and "waiting for customer reply" are real states because the item genuinely sits there.

Name each state by what happens next

A good state name tells you who should act and what they should do. "Ready for review" is clearer than "in progress," because it names the next action and its owner.

Define the entry condition

For each state, write what has to be true for an item to enter it. "An item becomes ready for review when all required fields are complete." Clear entry conditions are what let a rule or an AI move items safely.

Keep the set small

If two states never lead to different actions, they are one state with two names. Merge them. A workflow with five clear states is far more usable than one with fifteen overlapping ones.

A useful test: can everyone involved say, for any item, exactly which state it is in and why? If not, the states are too many or too vague.

A small example

A grant review process had a dozen informal statuses scribbled in a shared sheet. Reduced to five clear states, received, screened, under review, decided, and returned for more information, the backlog became visible and handoffs stopped falling through. The work did not change. The clarity did.

What this does not solve

States describe where work is, not whether it is correct. An item in "approved" can still be an error. States organize flow; reviews and checks handle correctness.

Good enough to move on when

  • Every state has a clear name tied to the next action.
  • Each state has a written entry condition.
  • No two states lead to identical handling.
  • Anyone can say which state an item is in and why.