Keeping an idea backlog alive without a committee
Picture the portal: 340 ideas, 290 of them marked under review, most for more than a year, and a committee that meets once a quarter to not decide. The problem is not the number. A backlog without states, owners and dates is a list, and a list is where ideas go to be forgotten politely. This piece gives you six rules and a monthly 45-minute routine that keep the backlog moving without a committee.
Why the number is not the problem
A backlog of 340 ideas is fine if 300 are parked or dropped with a reason and 40 are moving. It is a graveyard if 290 are under review, because under review is not a state but the absence of a decision.
Six principles
Every idea has a state, and the states are few
Seven are enough: new, scored, in concept, in test, decided, parked, dropped. If you need an eighth, you are naming a sub-step of in concept.
Every new or scored idea has a date
An idea in new or scored gets 30 days. By then it moves to in concept, or it is parked. Write the date next to the idea: it turns "we should look at this" into "before the 19th, or we park it".
Parked and dropped keep their reason
Parked has a reason and a revisit trigger ("when the new pricing is live"). Dropped has a reason. Both stay visible as part of your innovation memory. A deleted idea is a question the next new hire asks again.
Nobody owns the backlog, people own ideas
A backlog owner becomes a bottleneck and then a committee. The proposer owns an idea until it is scored, then whoever picks it up. An idea nobody picks up within 30 days is parked with the reason "no owner", not dead.
Scoring happens in batches, in the room
Scoring by email takes three weeks and produces a thread. A 45-minute monthly session with the people who would do the work produces decisions. Use the same criteria every month, weighted scoring works well.
Read the backlog from the top
Sort by last change, not by age. The first question in every session is "what moved this month", not "what is oldest".
The states and the question that moves an idea on
| State | The question that moves it out |
|---|---|
| New | Is it clear enough to score? |
| Scored | Will someone pick it up in the next 30 days? |
| In concept | Do we know enough to test, or to stop? |
| In test | Did it meet the criteria we set before starting? |
| Decided | Is it in a roadmap, a budget or a named project? |
| Parked | Has the revisit trigger happened? |
| Dropped | None. It stays, with its reason, as a record. |
The monthly 45 minutes
- Read what moved. Five minutes. The facilitator reads the ideas that changed state since last month, one line each.
- Score the new ones silently. Everyone scores alone, criteria on the wall. Talk only where scores differ by more than one point.
- Decide what goes to concept. For each scored idea, one question: who picks it up? A name and a date, or it waits.
- Park with reasons. Ideas past their 30 days without an owner are parked. Say the reason out loud, write it down, add the revisit trigger.
- Drop with reasons. Ideas that failed a test, or that nobody would pick up even with more time, are dropped. One sentence each, in the decision log.
- Pick the three for next month. Name the three ideas the room wants to look at next time. That is the whole agenda.
Once a quarter, read the parked list out loud, reasons and triggers included. One of them has become timely, and the room will hear it.
A backlog where nothing is ever dropped is a graveyard with hope. Drop ideas, write the reason, and the proposer will submit again, usually with a better version.
What keeps ideas stuck in the backlog
- The committee. It meets quarterly, reviews everything and decides nothing, because nobody in the room would do the work.
- Under review as a permanent state. If an idea can stay in a state forever, it will. Every state except parked, dropped and decided needs a date.
- Ideas without a proposer. An idea submitted "by the team" has nobody to answer questions in step 3. Ask for a name.
- A portal that counts submissions as success. 340 submissions is an input. The output is how many ideas reached decided.
- Deleting dropped ideas. The reason is the valuable part. Delete it and the idea comes back in eight months with the same flaw. Tools like IdeaHone keep each idea and its state in the space after the session, so the record does not depend on someone's spreadsheet.
Never lose an idea between sessions
IdeaHone follows every idea from first mention to decision, across all your workshops and teams.
How do you manage an idea backlog?
Give every idea a state, an owner and a date. Score new ideas monthly with the people who would do the work, and park or drop anything that does not move within 30 days, with the reason.
How often should you review an idea backlog?
Monthly, in 45 minutes, with the people who would do the work. Once a quarter, read the parked list out loud to catch ideas that have become timely.
What do you do with ideas you do not pursue?
Park them with a reason and a revisit trigger, or drop them with a reason. Keep both visible, so nobody proposes the same idea unchanged.
