Your tracker has no private draft state, and it shows

Every issue tracker I have encountered follows a familiar pattern: Backlog, In Progress, Done. Not a single one offers a private space to develop a task before others can view it. This missing stage creates a distinct problem that is easy to spot once noticed. The issue The process of brainstorming an idea and preparing a task to execute it are two separate activities requiring different approaches.

Brainstorming aims to be as effortless as possible. Adding any obstacles at this stage causes people to abandon recording their thoughts, which is less desirable. One-line notes with no additional information, no estimates, and no assigned owners work well for brainstorming. The more complex preparation stage involves defining the task's scope, determining what makes the outcome acceptable, providing necessary background information, and deciding if the task is worthwhile.

Combining both stages The absence of a private stage leads to tasks being published prematurely, inadequately prepared, and then requiring extensive revisions in public, which is costly. Publishing as a gate Implementing a real draft state provides a clear signal when a task is ready to be shared. Moving a task from draft to the board signifies that it is prepared for others' input, which is valuable information.

However, not all trackers support this, so a workaround is to use a label like "Draft" or "Not Ready" and treat items with such labels as invisible. Until they pass through the draft state, they should not be estimated, started, or commented on by anyone other than the author. Making the gate effective To ensure the gate is effective, it must be deliberate and have explicit exit criteria.

These criteria should include defining the scope, conducting an acceptance check, attaching relevant context, and making the transition deliberate and straightforward. A one-line note that is later developed into a draft is acceptable, but immediately converting a one-line note into a ticket defeats the purpose. Simplifying the process A real state like this is more explicit than a convention and recovers most of the benefits.

Wagglet's workflow is one of the most explicit implementations, featuring a rough request, a draft used as a preparation room, a deliberate publication to the board, and separate stages for claiming, providing evidence, and review. While the process may seem extended on paper, it was always present, merely occurring implicitly within a single column and comment thread.