Before 'To Do': the status your PM tool is missing

To-do, In Progress, Done — those statuses describe the execution layer. They assume you already know what to do. The real problem is the gap before that: the messy, half-formed layer where ideas live before anyone can act on them.

The fix isn't a different set of statuses. It's recognising that "idea" and "task" are different objects and need to be treated that way.

One thing that helped bridge the gap: applying the GTD "next action" principle earlier than most people do. Rather than waiting until something hits the sprint, tag it with a next action the moment it enters the backlog — even if that action is just "write a clearer definition." In Jira, a custom field works well for this. For anything at an early strategic stage, it might say "schedule a 30-min scoping session" or "find a comparable completed ticket." That one addition makes a vague initiative feel actionable rather than frozen.

Another approach worth stealing from PM colleagues: a dedicated formalisation sprint. The statuses are still Open, In Progress, and Done — but the goal isn't completing the task. It's moving it from "strategic idea" to "something a developer can pick up." Ambiguity becomes visible in the process rather than something everyone pretends doesn't exist.

What a journey from broad idea to prioritised user story actually looks like: idea captured with one concrete next action, even if that's just "define this better"; a formalisation pass (scoping session, comparable tickets found, definition written); acceptance criteria added and now it's a user story; prioritised against other ready stories and moved to the sprint backlog.

The jump from idea to sprint isn't a leap. It's a short pipeline with three or four steps, each of which anyone can actually do.

Yours, in one file,
Zhenia