Innovation Management Process: From Ideas to Implementation

Weeks later, employees still have no decisions. A few initiatives have begun without success criteria, while promising proposals remain untouched.

This guide follows the innovation management process from idea intake and screening through prioritisation, business cases, pilots and evidence-based implementation.

It extends beyond brainstorming. Each stage should generate evidence that supports a decision about whether to proceed, refine or stop an initiative.

A practical innovation process model follows:

This is an illustrative sequence, not a rigid checklist. New evidence may require revisiting earlier decisions.

Two concepts help explain how the process works:

ISO 56007:2023 provides guidance on identifying opportunities, developing innovation concepts and validating them. Solution development and deployment fall outside its scope.

An innovation funnel should make it easy to submit ideas and clear what happens next. Employees, customers, service complaints and operational data can all reveal opportunities, but scattered suggestions rarely provide enough evidence for a decision.

Start with the problem, not the proposed solution. For example, recurring customer service delays may signal an approval bottleneck. Business process analysis and modelling can help establish where delays occur before the organisation invests in a particular idea.

A Practical Idea Intake and Screening Checklist

Use a shared document or spreadsheet to capture five essentials:

Before detailed evaluation, apply a simple idea screening process:

• Does the idea support an organisational priority?
• Is the problem supported by credible evidence?
• Is a similar initiative already underway?
• Are there significant legal, security or operational barriers?

Early screening should not eliminate promising ideas simply because information is incomplete. Request clarification or defer consideration when appropriate.

Record every decision, advance, revise, defer or decline—with a brief explanation and communicate it to the contributor.

The University of Cambridge's Innovation Funnel illustrates this balance: encourage diverse inputs, then focus resources on opportunities worth developing.

Choosing which ideas deserve investment requires more than enthusiasm or persuasive presentations. A practical innovation framework helps managers compare proposals against consistent criteria rather than favouring the most exciting suggestion.

For our fictional service organisation, three idea evaluation criteria provide a starting point:

Score each criterion from 1 (weak) to 5 (strong). For Risk Manageability, a higher score means risks are easier to control, not more severe.

Worked Example: Comparing Three Innovation Ideas

The weighted score multiplies each rating by its assigned weight and adds the results.

For automated request routing:

What explains the differences?

• Customer portal: High potential value, but significant development and customer adoption challenges.
• Automated routing: Strong feasibility using existing capabilities, with operational risks that can be tested.
• AI assistant: Promising benefits, but greater uncertainty around accuracy, data protection and integration.

These ratings are hypothetical. Real assessments require documented reasoning and evidence behind each score.

A decision matrix makes trade-offs visible, but it does not prove that an innovation will succeed.

That distinction keeps the innovation pipeline focused on evidence rather than rankings alone.

A high evaluation score identifies a promising proposal, not a proven investment. Before advancing automated request routing, the organisation needs a concise business case for innovation that explains its expected benefits and unresolved uncertainties.

The business case should establish:

• Expected benefit: Potential reductions in routing delays and service errors.
• Total cost: Development, integration, training, operation and maintenance.
• Critical assumptions: Whether automation can handle real request volumes and variations.
• Risks and alternatives: Potential failures, their consequences and simpler available solutions.
• Decision owner: Who authorises the pilot, budget and next investment decision.

The aim is sufficient evidence to justify a controlled experiment, not an elaborate financial forecast.

Pilot Scorecard: Continue, Refine or Stop?

Test automated routing with one request category, a defined operations team and a representative sample of cases. Establish baseline performance before comparing results.

These targets are hypothetical and must reflect operational requirements. Test a range of critical exception scenarios, even if none occurs naturally during the pilot.

These results are encouraging, but they do not establish that exception handling has succeeded. Before expanding, managers must verify that the exception criterion is met, the sample reflects normal workloads and improvements are not explained by unrelated operational changes.

The next decision should follow the evidence:

This reflects the decision-gate principle described in the Stage-Gate Discovery-to-Launch Process: investment decisions follow evidence gathered during defined stages.

Our approach is a simplified managerial application, not the full Stage-Gate model.

For our automated request routing example, expanding beyond the pilot requires more than technical approval. Managers must establish ownership, prepare employees and verify that improvements remain sustainable.

Before expanding, agree on the rollout sequence, responsibilities and conditions that would require intervention or suspension.

This is where strategy execution becomes essential: translating an approved investment decision into coordinated action, resources and measurable responsibilities.

Suppose automated routing reduces processing delays but introduces additional rework or expensive manual intervention. The apparent efficiency gain may disappear once these costs are considered.

At the post-implementation review, ask:

1. 1
   Has the innovation delivered the intended operational or customer benefit?
2. 2
   What additional costs, risks or workload have emerged?
3. 3
   Should we expand, adjust or discontinue the solution?

Compare representative operational data with the original baseline, allowing for changes in demand and case complexity.

ISO 56002:2019 provides broader guidance on establishing, implementing and continually improving an innovation management system, without prescribing specific implementation methods.