Plan, pause or decline: four honest outcomes for incoming work
Not every request should become a project. Four honest outcomes for an incoming ask — and how to tell which one you're looking at.
Most intake processes have exactly one outcome: yes. The request comes in, it lands on the backlog, and "no" is something that happens by neglect months later — while the ask sits there quietly embarrassing everyone.
A healthier intake has four outcomes, and picks one on purpose.
1. Commit
You understand the problem, the outcome is clear, an owner exists, and it's worth doing now. Commit it — with a real scope and a real date, not a vibe. Commitment should be the rarest of the four, not the default. If everything gets committed, the word means nothing and your roadmap is just a queue.
2. Shape further
The request matters but it isn't ready. The problem is fuzzy, the scope is contested, or there's an open question big enough to change the plan. Don't commit and don't drop it — shape it. Naming this as a real, valid state is what stops half-formed asks from quietly becoming half-formed projects.
3. Pause
A good idea at the wrong time. Nothing is wrong with the request except that something else matters more right now. Pausing honestly — "not this quarter, revisit after year-end close" — is a gift: it tells the requester the truth instead of parking them on a backlog that whispers "maybe" forever.
4. Decline
Sometimes the answer is no. The problem isn't real, the outcome isn't worth the cost, or it's genuinely another team's job. Declining early, with a reason, is the kindest and cheapest of the four — it saves the requester from waiting and your team from building something that shouldn't exist.
The discipline is choosing
None of these four is hard to understand. The hard part is forcing the choice at intake, instead of letting "yes by default, no by neglect" run your roadmap. Give every incoming ask one of four labels, out loud — and your team starts doing the right work instead of all of it.