Key facts
The guide defines innovation management and examines pipeline leaks through idea management. It explains stage-gate and how it turns into bureaucracy before addressing portfolio prioritisation against capacity. The consumer goods NPD process leads into measurement of innovation rate, followed by governance and risk. The final section explains where to start.
- Idea funnel. Stevens and Burley's 1997 study estimated that it takes about 3,000 raw ideas to produce 1 commercial success.
- Success rates. Five waves of Product Development and Management Association (PDMA) benchmarking since 1990 put the five-year new product success rate between 58% and 61%.
- Renovation share. Mintel's product database shows that only 35% of global CPG launches in the first five months of 2024 were genuinely new. The other 65% were renovations.
- Stage-Gate adoption. An estimated 75 percent of major US companies have adopted Stage-Gate.
What innovation management covers
Innovation management covers every decision between a consumer insight and a product that sells. It determines which opportunities to pursue and which ideas get funded. It also governs how projects move or stop and how results are measured. Consumer goods companies manage it in four connected layers. A strategy sets where the business wants growth. A front end turns insight into concepts. A development process takes concepts to launch. Over all of these sits a portfolio view that decides what gets people and money.
The layers fail when they're run by different teams that don't share data. Marketing owns the strategy deck, while R&D's project list is separate from Finance's business cases. Then nobody can see that the portfolio no longer matches the strategy. That's why C+P Consulting's Innovation transformation practice starts by linking innovation and technology strategy to business strategy. Only then does it cover idea management and technology roadmaps, followed by front-end strategy and portfolio planning.
The balance between innovation and renovation varies most from company to company. Line extensions and reformulations are cheaper and safer, so they crowd out new platforms. Mintel's figures for food and drink show that genuinely new products fell to 26% of launches in early 2024, down from 50% in 2007. Either mix is valid when chosen deliberately; the mistake is drifting into one.
This guide stays with the innovation process and the portfolio, with attention to how both are measured. PLM strategy and product data management each have their own guide. AI in product development is covered in a separate guide as well. The table below maps each sub-topic to the guide that covers it in depth.
| Sub-topic | The question it answers | Guide that covers it |
|---|---|---|
| Front end | Where do good ideas get lost before a project starts? | The front end of innovation: where the pipeline leaks |
| Idea management | How do ideas turn into funded projects? | Idea management that produces projects, not just ideas |
| Stage-gate | Why do gates slow down and stop deciding? | The stage-gate process: why it becomes bureaucracy |
| Agile hybrids | How do you keep control at higher speed? | Agile phase-gate: keeping control at speed |
| Prioritisation | How do you rank projects when everything is urgent? | Prioritising an innovation portfolio when everything is a priority |
| Governance | Who decides, and on what data? | Governance for a product development portfolio |
| Capacity | How many projects can R&D actually run? | Capacity planning for R&D: the constraint nobody models |
| Innovation rate | Which measure changes behaviour? | Measuring innovation rate in a way that changes behaviour |
| Project KPIs | How do you track one project's health? | Project KPIs for product development |
| Risk | How do you find and reduce risk before launch? | Risk management in product development projects |
Where the pipeline leaks
The pipeline leaks most at the front end, where ideas wait without an owner to define their scope and set a decision date. Losses there are expected. Stevens and Burley's cascade ran from 3,000 raw ideas to about 300 acted on. Those became 125 small projects, which narrowed to 9 significant developments and then 1.7 launches. The real problem is losing the wrong ideas for the wrong reasons, and keeping weak ones alive because nobody stopped them.
Manufacturers lose ideas and keep weak projects alive in similar ways.
NielsenIQ's Innovation Barometer reported that total sales in West Europe grew 2.1% over the year while sales from innovations fell 0.2%. New products on shelf dropped by almost 17%. Fewer launches with less revenue from each one is what a leaking front end looks like when it reaches the market.
So check two numbers before you blame creativity. Measure the wait for an idea's first decision and the share of projects at the final gate that fail a sharper first-gate assessment. The guide on the front end of innovation shows how to map these leaks one by one.
- No owner. Ideas sit in a spreadsheet or a portal with no sponsor and no date for a decision.
- Early development. Concepts go into development before anyone has tested them against the category strategy.
- Late gates. Projects unfit to pass the second gate are still using lab time at the fourth.
- No review. Launches go out without a post-launch review, so the same mistakes come back in the next cycle.
Idea management that produces projects
Idea management produces projects when every idea comes in against a stated opportunity area and has a named owner responsible for a dated decision. An open suggestion box does the opposite. It collects so many submissions that the strongest get buried, which teaches employees that nobody reads them.
A category team gets better results with a targeted challenge, such as how to cut sugar in a flagship drink without losing taste acceptance. It invites ideas for 4 to 6 weeks and then scores them against criteria it published up front. The ideas that pass get a small budget to build a concept. Teams whose ideas fail receive a short reason. That reply is what keeps people submitting the next time.
A beverage company with a fast trend cycle runs a challenge every quarter to match its pace. An ingredients supplier whose projects come from customer briefs needs a way to capture requests from the sales team instead. Either way, ideas have to come with enough context for a gatekeeper to judge them. That means describing the consumer need and the rough size of the prize, along with an explanation of the technical question that's still open.
The measure that matters is the share of ideas that become funded projects within a set period. Submission counts measure a campaign, while conversion counts measure idea management. The guide on idea management that produces projects covers scoring criteria and how to set up challenges.
Stage-gate
Stage-gate splits development into stages of work separated by gates, where a group of senior managers decides whether to advance or kill each project. The group can also hold a project or recycle it. Robert Cooper developed the model in the 1980s, and most large consumer goods manufacturers in Europe run a version of it. The gates provide value because they make the business decide deliberately whether a project is still worth its people and money.
Few companies run Cooper's original model as written. Most choose between three operating options, and the choice depends on the project type more than on company size.
As an operator, I recommend more than one track. Put renovations through a light track and new platforms through a hybrid. Keep the full model for the few projects that need a capital commitment. A single process for every project either smothers the small ones or leaves the big ones under-examined. The guide on agile phase-gate explains how sprints fit between gates when the deliverable is a formulation.
When you compare these options for your own business, check what each gate actually asks for. Then check how many projects were killed at each gate last year. If the second number is close to zero, the gates aren't making decisions.
| Option | How decisions are made | Speed and control | Evidence | Suits |
|---|---|---|---|---|
| Classic stage-gate | Fixed stages with full deliverables at every gate | High control, slower on uncertain projects | Used by an estimated 75% of major US companies | Big-bet platforms, capital-heavy launches, regulated categories |
| Agile-stage-gate hybrid | Gates kept for investment decisions, time-boxed sprints in between that produce physical prototypes | Faster response to changing requirements, control held at the gates | Early adopters reported 25% less work effort per project and nearly 20% less rework | New-to-company products with uncertain specifications |
| Scaled-down gates | 2 or 3 gates, short checklists, decisions sometimes delegated to category leads | Fastest, with the least oversight | Practice varies too much for benchmark figures | Line extensions, pack changes, simple reformulations |
Why stage-gate becomes bureaucracy
Stage-gate becomes bureaucracy when the documents at each gate keep growing while the decisions made from them stay the same. In a 2014 article, Robert Cooper listed critics' complaints that the process was "loaded with paperwork, checklists, and too much non-value-added work." He cited a short definition of bureaucracy as "work that adds no value." By that definition, a field is waste if its removal leaves the reviewer's decision unchanged.
Gate templates grow in small steps when, for example, a launch fails because of a packaging issue and a packaging section gets added. Then a regulatory surprise adds a claims section, and a supply problem adds a capacity check. None of these sections ever gets removed. After a few years, a line extension needs the same pack as a new category entry. Teams respond by delaying gates until the document is complete, and the gate turns into a formality.
In the same article, Cooper reported that J&J's Ethicon Surgery group reversed this growth as its business cases shrank from 30 to 90 pages to 4 pages. P&G's SIMPL process cut its deliverables package to six pages. Both cut the paperwork without dropping the gates.
Digitising the process can make the problem worse. When gates move into a PLM or portfolio tool, teams are tempted to rebuild every legacy form inside it. C+P works the other way round. It starts from what the platform does out of the box and deviates only for a real business reason.
To check your own process, take last year's gate decisions and list which fields the decision-makers referred to. Remove the rest. The guide on why the stage-gate process becomes bureaucracy has a field-by-field audit.
Portfolio prioritisation against capacity
Innovation portfolio management is the ongoing process of choosing which projects to fund and how fast they proceed, with decisions to stop projects as needed. Each project is judged against strategy and against the people and equipment available to run it. Benchmarking studies have repeatedly found it to be the weakest area in product innovation management. Executives admit that real go/kill points are rare and that the criteria for them don't exist.
The common result is too many projects for the resources available. Stage-Gate International describes the outcome as pipeline gridlock. Projects take longer to reach market because they queue, and teams skip the early homework because nobody has time for it. Adding more projects to a full pipeline slows every project down.
Most companies combine the four main methods for ranking projects.
The verdict for a consumer goods portfolio is to use strategic buckets to split the budget, then score projects within each bucket. Use financial figures to inform the score without letting them decide it on their own. None of these methods works until you've modelled capacity. You need the hours available by skill, such as formulation chemists or pilot plant time, against the hours the active projects need. C+P's Project and portfolio strategy practice applies agile phase-and-gate discipline to governance and prioritisation. It also covers risk and KPI management at programme and project level.
The guides on prioritising an innovation portfolio when everything is a priority and on capacity planning for R&D, the constraint nobody models, cover these decisions in more detail.
| Method | How it ranks projects | Use, per Cooper's benchmarking | Strength | Weakness |
|---|---|---|---|---|
| Financial | NPV, ROI or payback per project | 77.3% of businesses, dominant for 40.4% | Easy to compare and defend | Early-stage numbers are guesses, so they favour safe renovations |
| Strategic buckets | Budget split by strategy first, projects ranked within each bucket | 64.8%, dominant for 26.6% | Protects long-term bets from short-term ones | Needs a strategy clear enough to split the budget |
| Scoring models | Weighted scores on fit, advantage and feasibility | In use, figures vary by study | Captures value that NPV misses | Scores drift towards the sponsor's preference |
| Bubble diagrams | Risk plotted against reward, bubble size shows spend | In use, figures vary by study | Shows balance at a glance | Displays the portfolio without ranking it |
The consumer goods NPD process

The consumer goods NPD process begins with a consumer or customer insight that becomes a concept for development. Regulatory checks and scale-up precede launch, after which a post-launch review completes the process. The names of the stages vary between companies, but the work inside them doesn't change much. The differences come from the category, so this section takes the general sequence first and then looks at what changes.
The steps from insight to shelf
- Opportunity and insight. Define the consumer need or customer brief and size the opportunity within the category strategy.
- Concept and business case. Write the concept and test it with consumers. Draft the business case with volume and price targets, then set the margin target.
- Formulation and pack development. Develop the recipe or formula and the pack in parallel, with bench samples and stability tests.
- Regulatory and claims check. Confirm that the ingredients are compliant in every target market and calculate the label. Back every claim with evidence.
- Scale-up and factory trials. Move from pilot to production lines, where cost and yield are checked at volume. Check quality at that volume too.
- Launch. Agree listings with retailers before shipment to distribution, and support the launch with marketing.
- Post-launch review. Compare results against the business case at agreed points, and feed the lessons back into the front end.
Step 7 is the one companies skip, and the one that improves every later cycle. NielsenIQ data cited by industry analysts shows that growing and declining launches split as early as four weeks after launch. A review held at the end of the first year comes too late to act on.
How the process differs by category
Food and beverage follow the same sequence, with taste acceptance and shelf life dominant in steps 3 and 5. Allergen labelling makes step 4 a hard stop. In beauty care, claims substantiation and safety assessment take up more of the timeline. Ingredients and flavour houses start from a customer brief, so step 1 means qualifying the customer more than researching consumers. Specialty chemicals and coatings carry heavier hazard classification work. C+P works across all of these categories and also covers home care and tobacco products. That range is why it treats the process as a pattern to adapt and doesn't sell it as one template.
Where the process meets the system
From step 3 onward, the process creates data that later steps depend on. That data includes specifications and formulations, with nutrient or hazard values among the records. When that data lives in a specification and formulation system, the regulatory check in step 4 runs on the same records the developers used. When it lives in spreadsheets, someone retypes it, and retyped data causes recalls. The PLM strategy guide covers how to choose that system.
Measuring innovation rate
Innovation rate is the share of a company's revenue that comes from products launched within a set period. The common version is the vitality index, which 3M created in 1988. 3M reported a record 31 percent in 2010. Its method counts products launched within the previous five years.
Most companies go wrong in their choice of window; a survey reported by Design World found that 59% of companies count products as new for three years, and 21% use five. A longer window raises the percentage without any extra innovation. If the definition of "new" includes pack changes and flavour extensions, the index rewards exactly the renovation that Mintel's figures show is already crowding out new products. The AIM Institute adds that the index is lagging. It reports what already happened and gives no guidance on what to change.
To raise innovation rate, run fewer projects and finish them faster. Cut projects at the early gates so that people move to the strongest ones. Ring-fence a budget bucket for new-to-company products so that renovation can't consume it all. Then judge launches on incremental revenue. Circana reported that the top 200 US launches of 2024 generated $8.4 billion in year-one sales and 28% of overall store growth.
Pair one portfolio measure with project-level KPIs that teams can act on each week. The guides on measuring innovation rate in a way that changes behaviour and on project KPIs for product development cover both levels.
| Metric | What it measures | Best use | Watch out for |
|---|---|---|---|
| Vitality index | Revenue share from products launched in the last 3 to 5 years | Board-level trend over time | Gaming through the window length or the definition of "new" |
| Incremental revenue | Sales a launch adds after subtracting cannibalised sales of existing products | Judging whether launches grow the business | Needs consumer panel or sell-out data |
| Year-two survival | Share of launches still listed and growing in year 2 | Testing launch quality | Results arrive slowly |
| Pipeline value against target | Risk-adjusted value of active projects against the growth gap | Forward-looking portfolio health | Depends on honest probability estimates |
Governance in NPD
Governance in NPD defines who can make each decision and when, with rules for which data they use. It covers the gatekeepers for each project tier and the portfolio board that balances the whole pipeline. It also sets the escalation path for when the two disagree. Without written decision rights, decisions end up with whoever speaks loudest in the meeting.
Governance failures centre on data, as at one home and personal care manufacturer whose portfolio ran on spreadsheets that were consolidated by hand and always lagged behind reality. Every review argued about whose numbers were current. C+P digitised the underlying data flows and built dashboards for executives to review the portfolio and compliance, all with automatic refreshes from source systems. Leadership got decision data in real time and no longer had to consolidate anything by hand.
A global company divides authority between a central board for platform launches and regional category teams for renovations up to a set budget. A mid-sized ingredients business runs a single monthly board for everything. Both can work if the rules are written down and everyone uses the same numbers.
Check that each project tier has a named decision-maker and that the board sees capacity next to value. Also confirm that someone tracks decisions after the meeting. The guide on governance for a product development portfolio sets out decision-rights models.
Risk in NPD
Risk in NPD is anything that threatens a project's delivery of its business case. Consumer goods teams face commercial and technical risks, alongside risks tied to regulatory requirements and supply. Good risk management finds these risks early, when fixing them is cheap, and makes them part of every gate decision.
Regulatory risk catches out more consumer goods teams than any other group, because rules differ by market and keep changing. The European Commission's Rapid Alert System for Food and Feed (RASFF) recorded 4,695 notifications in 2023, an 8% rise on 2022. Most of them concerned pesticide residues and pathogens. The same report notes cases of mislabelling, such as unauthorised health claims on food supplements. A launch that calculates its label by hand and gets it wrong becomes a withdrawal. This is why regulatory and labelling calculation sits inside C+P's PLM scope and isn't left as a separate check at the end.
Technical risk is about whether the formula can be made at scale and still meet cost and quality targets. Supply risk covers single-source ingredients and constrained co-manufacturers. Commercial risk asks whether consumers and retailers will accept the product at the target price. Each group needs its own owner and a test that reduces the risk before the next gate.
Ask each project team for its top 3 risks and the date of the test that will reduce each one. A team that can't answer is relying on hope. The guide on risk management in product development projects covers risk registers and how to use them at gates.
Where to start
Start with portfolio prioritisation against capacity. It's the one change that improves every other part of the system. If your gates don't kill projects, a capacity model shows the cost in hours. If your innovation rate is falling, freeing up capacity is the quickest way to speed up the projects that matter. Make one honest list of active projects and the people they need, and compare it with the people you actually have. That list will tell you whether new product development in your business needs a better process or simply fewer projects. C+P Consulting helps consumer goods manufacturers connect innovation strategy and portfolio decisions to the systems that run them. It also connects the NPD process to those systems. To talk it through, book a 30-minute conversation.
FAQ
Consumer goods companies manage innovation by linking growth strategy to decisions about which projects receive funding. Teams turn insights into concepts and use development gates to decide whether work continues. Portfolio reviews keep commitments within available capacity.
More articles
PLM for process manufacturers: the complete guide
PLM for process manufacturing: how formula-based PLM differs from discrete, where ERP, PDM and PIM take over, and the signs you have outgrown spreadsheets.
Regulatory compliance in Food product development
Food information regulation explained: what must legally appear on an EU food label, which foods are exempt, and where UK requirements now differ
Packaging specifications: why they are the weakest record in the product file
Packaging specification management: what the record must hold at component level, why supplier data decays, and how the pack file drives labels and artwork.
The EU packaging regulation and the product data you will need
PPWR regulation explained: what applies from 12 August 2026, the PFAS and recyclability limits, and the packaging data behind every declaration of conformity.
Product data management for process manufacturers
Product data management for process manufacturers rests on 3 decisions. Poor data quality costs $12.9 million a year on average, per Gartner.
PLM implementation for process manufacturers: a delivery model that holds
A plm implementation for process manufacturers runs in 4 phases. A first release takes 3 to 6 months and an enterprise rollout runs 12 to 24 months.
Specification management for food manufacturers: the complete guide
This guide explains food product specification management, with a 7-step approval order and the BRCGS Issue 9 review every 3 years.
