In this guide
Every suggestion needs an answer
  1. 01Receive and clarify
  2. 02Assign the decision
  3. 03Test when justified
  4. 04Explain the outcome
An original operating route. Receiving or approving an idea is different from implementing an innovation.

An idea management system gives suggestions a visible route from submission to an accountable decision, useful feedback and, where justified, a test. Its most important feature is an answer that someone owns. A large collection of ideas with no next step is an inventory of unresolved promises.

Use this guide when workshops produce suggestions that disappear, contributors cannot tell what happened or reviewers keep asking for complete business cases too early. Idea evaluation explains how to judge an individual proposal; this guide builds the route around that judgement.

Decide what the system is for

Separate a suggestion, a project and an implemented innovation. The Oslo Manual makes implementation part of its innovation definition. Receiving a suggestion therefore does not mean that the organization has created an innovation, and approving a trial does not mean that a product is ready to launch.

Define the scope of the route. A local improvement scheme might address how a print shop prepares jobs. An innovation portfolio may investigate new services or markets. They can share an entry point, but they need different review questions, authority and resource commitments.

Also define what goes elsewhere. An urgent equipment problem should have an operational response route; a personal complaint should not depend on an innovation vote. Tell contributors where those issues belong and who can help redirect them. A broad suggestion box should not become a hidden substitute for essential management responsibilities.

Build a route from suggestion to decision

Consider a hypothetical print shop. Employees suggest ways to reduce setup waste, but the shared mailbox contains a mixture of process observations, requests for new equipment and unfamiliar product concepts. Nobody has explicit time to respond. Contributors conclude that another idea workshop would add little.

A worker holds up one printed sample beside a large pile of papers while a colleague listens.
Figure 1. Build a route from suggestion to decision.Illustration credits

Start with a modest intake record: the situation, the people affected, the observed difficulty and the proposed next inquiry. A contributor may include a solution, but should not need to produce a forecast or polished presentation to have a problem considered.

Give every item an owner and an understandable status. For example:

StatusMeaningNext responsibility
ReceivedThe suggestion has reached the routeNamed coordinator acknowledges it
ClarifyingA question or missing observation needs attentionReviewer and contributor clarify together
Ready for decisionThe next commitment is sufficiently definedAuthorized person decides
In a bounded testA specific inquiry has resourcesTest owner records observations
DeferredThe idea has a stated condition for reconsiderationOwner reviews the condition
ClosedThe decision and reason are recordedContributor receives the explanation

These are proposed operating states, not a standard software specification. Keep the route small enough that someone actually maintains it. A spreadsheet may be sufficient before a dedicated platform is justified.

Match review effort to the commitment

Ask what the next decision would commit, rather than whether the entire idea is attractive. A proposal to change paper loading may need observation and a supervised rehearsal. A proposal for a new print service may first need customer interviews. Neither necessarily needs a complete investment case at intake.

The owner’s Stage-Gate description distinguishes learning activities from decisions about continuing resources. You can borrow that distinction without imposing a full gating system on every suggestion. A small local adjustment and a new production line should not receive identical paperwork.

Write decision criteria in ordinary language: relevance to the problem, important uncertainties, possible harm, dependencies and the cost of the proposed inquiry. Avoid scoring weak evidence as though it were a precise estimate. The weighted decision matrix can support a comparison when its assumptions are visible, but a total is not a substitute for judgement.

Give reviewers authority appropriate to the commitment. If they can recommend but cannot release equipment time, the route needs a further decision owner. Otherwise “approved” can mean that nobody has said no while nothing can actually happen.

Protect the contributor’s ability to clarify

A written suggestion often leaves out context. Let the reviewer ask questions before rejecting it. Ask what the contributor observed and which part of the solution is negotiable. A suggestion to buy a machine might reveal a recurring queue that could be addressed several ways.

Amabile’s creativity framework includes the social work environment. This is a reason to examine the conditions around contribution, rather than treat suggestion volume as a simple measure of employee creativity. The framework does not prove that a particular recognition scheme increases useful ideas.

Use active listening when a suggestion arrives in frustrated language. Check the account of the work before rewriting it into management terminology. Preserve the contributor’s credit and make clear how collaboration will be acknowledged if other people develop the idea.

Provide different ways to contribute where needed. A colleague away from a desk should not need an elaborate online submission. At the same time, avoid creating several disconnected queues. The coordinator should bring the routes into the same accountable record.

Close the loop with the contributor

Suppose the fictional shop agrees to investigate a revised print setup. The next commitment might be a supervised comparison of preparation steps using approved materials. Name the person responsible, the question, the operating boundary and the date for a review.

Two print-shop colleagues inspect a trial print together beside an organized press and workbench.
Figure 2. Close the loop with the contributor.Illustration credits

Strategyzer’s Test Card explanation separates the assumption, the test, the measure and the decision threshold. Use that discipline in the record without copying its worksheet. A useful entry might ask whether a proposed preparation order can be performed consistently under specified job conditions. It should also note what the test cannot establish about other equipment or shift patterns.

After the review, tell the contributor what happened. A useful rejection explains the relevant constraint or evidence and whether reconsideration is possible. A deferral names a condition and an owner. “Not a priority” without a next decision leaves the same uncertainty as silence.

If the idea changes substantially during development, keep the history understandable. Record which problem it still addresses and what prompted the change. Pivot-or-persevere decisions concern the evidence behind continuing, changing or stopping; they should not be disguised as a status update.

Measure whether the route works

Track whether items have an owner, whether contributors receive an answer and whether authorized tests produce a reviewed learning record. Inspect the age of unresolved items and the reasons for repeated deferral. These measures describe the process; they do not establish the economic value of innovation.

Suggestion counts and approval rates are ambiguous. More submissions may reflect better access, duplicated ideas or a backlog of unresolved problems. A higher rejection rate may reflect clearer boundaries or unhelpful screening. Read the underlying decisions before declaring that the system is improving.

Ask contributors and reviewers which steps consume effort without helping a decision. Remove a field if nobody uses it, but preserve information needed to explain the commitment. Continuous improvement provides a way to change the route itself through bounded tests.

Limitations and the first operating cycle

This proposed route is an original synthesis of innovation definitions, model-owner guidance and practical design reasoning. It is not a validated suggestion-system intervention, and the print shop is hypothetical. No source here establishes a universally correct response deadline, committee size or financial return.

Begin with one problem area and a manageable queue. Assign its coordinator, decision owner and first review. Before asking for more ideas, choose an existing unresolved suggestion and take it through clarification, decision and feedback. That first complete cycle will expose more useful design questions than a longer submission form.

Sources: