Overview
A useful suggestion from a frontline employee disappears in a meeting note. A customer complaint hints at a new service model, but no one owns it. A technology opportunity is discussed enthusiastically, then delayed because the business case is unclear. Six months later, leadership asks why the innovation pipeline feels thin.
An idea management system exists to solve that problem, by creating a disciplined way to recognize, evaluate, develop, and decide what should happen next.
ISO 56007:2023 provides guidance for managing opportunities and ideas, including preparation for front-end innovation, people and organizational factors, related innovation activities, and evaluation considerations.
What Is an Idea Management System?
An idea management system is the set of roles, processes, criteria, tools, and governance used to manage ideas from early capture to decision.
The system should answer five practical questions:
- Where do ideas come from?
- How are they captured?
- How are they evaluated?
- Who decides what happens next?
- How is learning retained?
The strongest systems are the ones that don’t treat every idea as equal. A minor process improvement, a new product concept, and a business model opportunity require different evaluation logic. Applying the same template to all three creates administrative noise.
That is where many idea programs fail. They confuse participation with progress.
Importance of ISO 56007
ISO 56007 is useful because it focuses on the unstable early part of innovation, where ideas are still incomplete and evidence is limited. This stage is often called the front end of innovation.
At this point, organizations must avoid two opposite mistakes:
- Approving weak ideas too quickly because they sound exciting.
- Rejecting promising ideas too early because they are not yet fully proven.
A good idea management process creates enough structure to make decisions without demanding false certainty.
That is the main value of ISO 56007. It helps organizations manage opportunities and ideas systematically before they become formal projects, investments, or innovation initiatives.
The Idea Management Process: From Signal to Decision
A mature idea management process usually includes the following stages, although the exact design should depend on the organization.
1. Opportunity Recognition
Ideas usually begin as signals:
- Customer frustration
- Operational inefficiency
- Regulatory change
- New technology
- Market shifts
- Employee observations
- Partner insights
The first task is to notice these signals and translate them into opportunity areas.
For example, a logistics company may receive repeated complaints about delivery time windows. The weak response is to ask employees for “ideas to improve customer experience.” The stronger response is to define the opportunity more clearly: reduce uncertainty for customers between dispatch and delivery.
That framing produces better innovation ideas because people are solving a real constraint, not reacting to a vague theme.
2. Idea Capture
Capturing ideas should be easy, but not careless. A useful submission format should ask for enough information to understand the idea without turning the process into a mini business case.
At minimum, capture:
- The problem or opportunity
- The proposed idea
- The intended user or beneficiary
- Expected value
- The person or team submitting it
Some organizations in initial stages also capture:
- Key assumptions
- Potential risks or dependencies
Avoid long forms at the beginning. Long forms reduce participation and often reward people who are good at writing, not people who have valuable insight.
3. Initial Screening
Initial screening should remove ideas that clearly do not fit strategic priorities, legal constraints, customer needs, or operational reality.
This stage should be quick. Its purpose is not to find winners. Its purpose is to decide which ideas deserve more attention.
Potential screening criteria include:
- Strategic relevance
- Potential value
- Feasibility
- Novelty relative to current practice
- Evidence of need
- Time sensitivity
- Fit with available capabilities
A strong claim: the quality of screening criteria matters more than the number of submitted ideas. A company with 80 well-framed ideas and clear criteria is in a better position than a company with 3,000 vague suggestions and no decision discipline.
4. Development and Enrichment
Promising ideas at some point need refinement. This may involve customer interviews, technical checks, small experiments, cost estimates, stakeholder reviews, or prototype development.
At this stage, the idea may change significantly. That is healthy. The purpose is not to protect the original suggestion, but to develop something worth deciding on.
This is also where cross-functional collaboration becomes important. Ideas fail because they are evaluated too narrowly. A product team may see customer value, while operations sees implementation complexity and finance sees margin risk. All three views matter.
5. Evaluation and Prioritization
Evaluation should match the type of idea:
- A cost-saving idea may need operational data
- A customer experience idea may need user evidence
- A platform innovation may need strategic evaluation
- A radical concept may need staged experimentation rather than a conventional return-on-investment calculation
Forcing early-stage innovation ideas into standard financial templates can kill valuable opportunities. Early evidence is often incomplete. The better question is not always “What is the return?” Sometimes it is “What must be true for this to become attractive?”
6. Decision and Portfolio Fit
Ideas also need a decision path. Possible outcomes include:
- Reject
- Hold for later
- Request more evidence
- Combine with another idea
- Run an experiment
- Move into development
- Assign to a business unit
- Add to the innovation portfolio
The decision should be documented. This is important because unmanaged rejection damages trust. When people submit ideas and hear nothing, they stop contributing.
A transparent “no” is better than silence.
What a Good Idea Management System Includes
An effective system needs more than software. Platforms help with visibility, tracking, and collaboration, but they cannot compensate for weak governance.
The core components are:
Clear Ownership
Someone must own the system. That does not mean one person owns every idea. It means there is accountability for process quality, decision flow, criteria, communication, and improvement.
Without ownership, idea management becomes a campaign activity: energetic for a few weeks, then forgotten.
Defined Roles
Common roles include:
- Idea submitters
- Challenge owners
- Reviewers
- Subject-matter experts
- Innovation managers
- Decision makers
- Sponsors
- Implementation teams
Each role should know what it is expected to do. Reviewers, in particular, need guidance. Otherwise, they rely on personal preference, seniority, or risk appetite.
Decision Criteria
Criteria should be visible before ideas are submitted. Hidden criteria create frustration and political behavior.
For example, if the organization only wants ideas aligned with three strategic priorities, say so. If ideas requiring regulatory approval need a special review path, make that clear. If incremental improvements and breakthrough concepts are evaluated differently, explain the difference.
Feedback Loops
Feedback is not a courtesy. It is part of system performance.
People need to know:
- Was the idea reviewed?
- What was the decision?
- Why was that decision made?
- What could improve the idea?
- Will similar ideas be considered later?
Feedback also improves future submissions. Over time, contributors learn how to frame stronger ideas.
Learning Records
A rejected idea may still contain useful insight. A failed experiment may reveal a customer behavior, technical limitation, or market signal.
The system should preserve learning, not just track approvals.
Scenario: Idea Management in a Manufacturing Company
A mid-sized manufacturer is facing rising energy costs. Leadership launches an internal challenge: reduce energy waste in production without reducing output quality.
Employees submit 120 ideas. In a weak system, the ideas are exported to a spreadsheet, discussed once, and gradually forgotten.
In a stronger idea management system, the process works differently.
First, the challenge owner defines the opportunity clearly: reduce avoidable energy use in three high-consumption production areas.
Second, each idea is tagged by type: maintenance improvement, process change, equipment investment, behavioral change, or data-monitoring opportunity.
Third, reviewers apply different criteria by category. A behavioral change can be tested quickly. An equipment investment requires payback analysis. A process change requires quality and safety review.
Fourth, the company selects 12 ideas for rapid validation. Four are implemented immediately. Five need experiments. Three are rejected because they conflict with quality standards.
Fifth, all contributors receive feedback. The company publishes the implemented ideas, estimated savings, and lessons learned.
As a result, the organization gets a better energy performance, but also learns how to run a focused idea challenge tied to business value.
Common Failure Cases
Collecting Ideas Without Decision Capacity
Organizations invite ideas before they have reviewers, criteria, or sponsors. This creates a backlog that looks like engagement but functions like waste.
Do not open the funnel wider than the organization can manage.
Treating Software as the System
An idea platform can support the process, but it is not the process. Without ownership, decision rights, and feedback expectations, the platform becomes a digital suggestion box.
Using One Evaluation Model for Every Idea
Small improvements, adjacent innovations, and transformational opportunities should not compete under identical criteria. Incremental ideas often look safer. Radical ideas often look weaker because evidence is immature.
Portfolio logic matters.
Ignoring Culture
People will not submit serious ideas if they believe managers punish failure, take credit, or ignore feedback. ISO 56007 recognizes the importance of leadership, culture, strategy, and people-related issues in managing opportunities and ideas.
How to Implement an Idea Management System
Start smaller than you think.
Choose one strategic opportunity area. Define the problem. Assign an owner. Set criteria. Run a time-bound challenge. Review ideas quickly. Communicate decisions. Implement a few visible outcomes. Learn from the cycle.
Then improve the system.
A practical implementation sequence:
- Define the purpose of idea management.
- Connect it to innovation strategy.
- Identify opportunity sources.
- Design submission and screening rules.
- Set decision rights.
- Choose supporting tools.
- Train reviewers and sponsors.
- Run a pilot challenge.
- Measure process performance.
- Improve based on evidence.
Do not begin with a company-wide launch unless the organization is ready to process the volume. A failed launch damages credibility.
What to Measure
The wrong metrics can distort behavior. Counting ideas alone encourages volume, not value.
Better measures include:
- Percentage of ideas reviewed within target time
- Percentage receiving feedback
- Number of ideas moved to validation
- Cycle time from submission to decision
- Value generated from implemented ideas
- Participation by function or location
- Quality of submitted problem statements
- Learning captured from rejected or tested ideas
The most important metric depends on maturity. Early on, responsiveness and trust may matter more than financial return. Later, portfolio contribution and realized value become more important.
Final Point: Idea Management Is a Decision System
Creativity matters, but unmanaged creativity does not reliably become innovation. The real purpose of an idea management system is disciplined movement from possibility to decision.
ISO 56007 gives organizations a useful reference point for managing opportunities and ideas before they become formal innovation projects. Used well, it helps leaders create a system where valuable ideas are noticed, developed, challenged, and acted on.
The practical test is simple: when a good idea appears, does the organization know what to do with it?
If the answer is unclear, the organization has an idea management problem.