Idea management is how an organisation collects ideas from the people around it, decides what to do with each one, and tells the person who suggested it what happened. The ideas can come from customers, employees, students, volunteers or members, and they can be about anything: a product feature, a process, a policy, a service. This page is for product, operations, HR and innovation teams, and for schools and non-profits, that want suggestions to lead somewhere. It covers the stages of idea management, how it differs from feature request management and from a suggestion box, real examples, and the point where most programmes quietly fail.
The Four Stages of Idea Management
- Collection. Ideas arrive from wherever people are: a suggestion box, an idea board, a form, a support conversation, a staff meeting.
- Evaluation. Someone assesses each idea for impact, effort and fit with current priorities.
- Routing and decision. The idea goes to whoever can actually act on it, and they decide: do it, plan it, park it, or decline it.
- Response. The person who suggested it hears the outcome, including a "no" and the reason.
Most organisations are good at the first stage and weak at the other three. The result is a pile of submissions nobody trusts and a team that stops suggesting things. The most common failure is a campaign that collects hundreds of ideas, followed by silence, so the next campaign gets almost none.
Idea Management vs Feature Request Management
Idea management is the wider practice. Feature request management is the product-shaped subset of it.
A feature request has a known destination: a product backlog, ranked against other candidate work, shipped or declined. An idea might be a process change, a service offering, a policy, or something for a department with no backlog at all. That is what makes idea management harder: there is no single queue to put things in, so the "who answers this?" question has to be settled per category rather than once.
Two consequences worth planning for:
- Routing matters more than ranking. A misrouted idea dies silently. A mis-ranked one just waits.
- Closing the loop is harder. Telling a user their requested feature shipped is easy. Telling an employee what happened to their suggestion about the onboarding process needs someone outside product to be accountable for the reply.
If every submission you receive is a product change from a product user, run feature request management and skip the broader framing.
How It Relates to Other Practices
| Practice | Focus | Relationship to idea management |
|---|---|---|
| Suggestion box | Open, often anonymous collection | A collection channel that feeds idea management |
| Feature voting | Users ranking product requests | One evaluation input, mostly for product ideas |
| Feedback management | All input, including complaints and bugs | The broader category; ideas are one kind of feedback |
| Innovation management | Structured programmes for new products or ventures | Idea management is the everyday operational layer beneath it |
A suggestion box that people can use without an account is often the easiest way to start collecting, especially for staff and members. What turns it into idea management is everything that happens after the submission arrives.
Examples of Idea Management
A product team runs a public idea board. Users post ideas and vote on each other's; the team reviews weekly, merges duplicates, and moves the strongest ideas into the backlog. Each idea shows a status, and the person who posted it gets an update when it changes.
A retail business gives store managers an internal channel for operational ideas. A named reviewer scores each one against cost and impact, accepted ideas get an owner and a date, and declined ones get a written reason.
A university department runs a suggestion campaign each semester for students and staff about course delivery. Ideas are grouped by theme and reviewed by a committee, and the department publishes which ones will shape next year's plans.
A digital agency gives each client a private board for requests and ideas. The agency decides what goes into the next sprint using a mix of client priority and effort, and clients see statuses without needing a call.
How to Run a Simple Idea Management Process
Pick one primary intake. Several channels are fine, but ideas should end up in one list. Otherwise duplicates multiply and nobody has the full picture.
Decide routing before you launch. List the kinds of ideas you expect, such as product, process, facilities or policy, and name who answers each kind. This is the step most programmes skip, and it is why ideas outside product usually die.
Score against the same criteria every time. Impact, effort, strategic fit and how often the idea comes up are enough. Votes are a useful input, but they reflect who participates, not necessarily who matters.
Answer everything. "Planned", "not now, because…" and "no, because…" are all answers. Silence is not.
Review parked ideas. Something impractical six months ago may be easy now. A quarterly look through the parked list stops good ideas being buried for good.
Common Mistakes
- Treating an inbox as the system. Email and chat threads have no status, no owner and no history.
- Ranking only by votes. A single idea from a frontline employee or a key client can matter more than twenty votes from casual users.
- No owner outside product. Process and policy ideas need someone accountable for the reply, or they vanish.
- Mixing ideas with bug reports. They need different handling; in one queue, both get handled badly.
- Letting the backlog grow forever. An unpruned list becomes a graveyard, and people stop trusting it.
Tools for Idea Management
- Suggestion box and idea board tools handle collection, voting and status updates for ideas from customers, staff or members.
- Survey and form tools collect ideas but leave evaluation, routing and replies to you.
- Project management tools can track accepted ideas as work, but are not built for public submission, voting or replying to submitters.
- Innovation management platforms suit large organisations running formal challenges with stage gates and review panels.
FlagUp covers the collection and response side: anonymous-friendly suggestion boxes, a feedback board where people vote on ideas, categories you define per project, a public roadmap, and an email to the submitter when an idea's status changes. On paid plans it can also group duplicate submissions and summarise what came in. Routing ideas to the right person inside your organisation is still a process you set up. See what each plan includes.
Frequently Asked Questions
What is idea management in simple terms?
It is collecting ideas from customers, employees or members, deciding what to do with each one, and telling the person who suggested it what happened.
Is idea management only for product teams?
No. Schools, non-profits, agencies, retailers and internal teams all receive suggestions about how they work. Product ideas are the easiest kind to route, which is why most tools focus on them.
What is the difference between idea management and feedback management?
Feedback management covers every kind of input, including complaints, bug reports and general comments. Idea management focuses on suggestions and proposals, and on making sure each one gets a decision and a reply.
Do I need software for idea management?
Not to start. A shared list with a status column and a named owner for each type of idea works for small teams. Dedicated tools help once volume grows or when you want people to vote and see statuses themselves.
How should ideas be prioritised?
Combine votes with a simple scoring framework covering impact, effort and fit with current priorities. Voting alone favours whoever participates most; scoring adds judgement about what matters to the organisation.
What if nobody submits ideas?
Usually the channel is hard to find, the process feels like effort, or people do not believe anything will happen. Publishing what changed because of past suggestions is the most reliable way to fix all three.
FlagUp helps teams, schools and organisations collect ideas in one place, let people vote on them, and show everyone what was decided. Start free or compare plans.