Why does status tracking fail?

The most common reason status tracking fails: Tracking status without defining valid transitions. When any state can follow any other state — when a task can jump from 'not started' to 'done' without passing through 'in progress' — you lose the workflow that status types are supposed to provide. Status becomes decoration instead of infrastructure. The other failure mode is too many statuses: fifteen states for a three-step process buries the signal under administrative overhead.

The fix: Pick one recurring process in your life — a project, a piece of writing, a personal goal, a purchase. Map the lifecycle states it actually passes through from beginning to end. Write each state as a node. Draw arrows between them showing which transitions are allowed. Then ask: are there states missing? Are there transitions you've been making that skip necessary intermediate steps? Name the lifecycle explicitly and keep the diagram.

The underlying principle is straightforward: Objects often move through defined states — tracking these states enables workflow.