Sources of Innovation & the Innovation Process
Global Innovation Management - TUHH Institute for Technology & Innovation Management · part of my Technology Management MBA · study notes for revision.
Chapter 1 asked what innovation is. This chapter asks two very practical follow-ups: where do the ideas come from, and once you have one, how does it actually travel from a rough hunch to a shipped product? The first half is about sources - the places a smart firm goes hunting for the seed of the next big thing. The second half is about process - Cooper’s Stage-Gate model, the assembly line that turns those seeds into launched products without betting the company on a hunch.
1 · Two perspectives on where innovation comes from
Section titled “1 · Two perspectives on where innovation comes from”If you brainstorm “sources of innovation” cold, you’ll list the obvious ones: R&D labs, competitors, market research. That’s the corporate view. But there’s a second, richer view - the user view - and a lot of this chapter lives there.
- Watching the competition and the wider market
- Looking for a solution that’s relevant to many customers at once
- Diffusion happens through the firm’s own sales channels
- Starts from the user’s own need
- Combines usage knowledge with solution knowledge
- Spreads by word of mouth and user communities
The corporate lens is broad and safe - it aggregates demand. The user lens is sharper and stranger - it starts with one person who has a specific, unmet problem. And that’s exactly why the user lens is so valuable for radical innovation: the person feeling the pain first is often the person inventing the fix first, long before the market as a whole even notices there’s a problem.
2 · Lead users - customers who live in the future
Section titled “2 · Lead users - customers who live in the future”The single most important idea in the “user” camp comes from Eric von Hippel: the lead user.
A lead user is not your average customer. They are people who - because of who they are and what they do - sit far ahead of the mainstream market. They feel a need now that most people won’t feel for years. And crucially, because no product exists to solve it yet, they’re held back in their own work and often build the solution themselves.
That last box is the magic. Because a lead user has already hacked together a fix, they hand you two things at once: knowledge of the need and knowledge of a solution. A normal market survey gives you only the first, and usually only for needs people already recognise. Lead users signal what von Hippel calls trend quality - their needs today are a preview of the mass market’s needs tomorrow.
2.1 How to actually find them
Section titled “2.1 How to actually find them”Lead users don’t fill in your survey - they’re too far out on the edge. You have to go looking. Four practical routes:
| Approach | What you do | Why it works |
|---|---|---|
| Extreme users | Seek out the people with the most demanding, most advanced requirements | Their needs are the mainstream’s needs, dialled up |
| Analogous markets | Look in other fields facing a similar problem in a harsher form (“analogue lead users”) | A problem you’re just meeting may be old news - and solved - somewhere else |
| Grouping & networking | Connect these scattered advanced users to each other | Ideas compound when edge-case users compare notes |
| Joint development | Co-develop, cooperate, or license their solution | Turns their private hack into your product |
3 · Jobs-to-be-Done - sell the hole, not the drill
Section titled “3 · Jobs-to-be-Done - sell the hole, not the drill”The second big user-centred idea is Jobs-to-be-Done (JTBD), associated with Clayton Christensen (from The Innovator’s Solution, 2003). It’s a reframing so simple it’s easy to underrate.
The claim: customers don’t really buy products. They “hire” a product to get a job done. The product is just the current best tool for the job - and tools get fired and replaced all the time, while the job stays put.
The sharpest illustration is the Walkman. As a product, the Walkman is dead and gone. But the job it was hired for - “let me listen to my music, privately, on the move” - never went anywhere. That job simply got re-hired: to the iPod, then to the smartphone, then to streaming earbuds. A firm fixated on “making a better Walkman” missed the whole story. A firm focused on the job saw the future.
And here’s the strategic kicker: change the job, and you change the market - including who your competitors are.
- The apple 🍏
- The orange 🍊
- Competitors: other fresh, wholesome foods
- The apple 🍏
- The bagel 🥯
- Competitors: anything fast & portable
Notice the apple appears in both sets, but its rivals change completely depending on the job. If you thought you competed only with other fruit, the “quick snack” job just told you that you’re actually up against bagels, granola bars and vending machines. That’s JTBD earning its keep.
4 · Innovative analogies - borrow a principle from somewhere else
Section titled “4 · Innovative analogies - borrow a principle from somewhere else”A third source is beautifully lateral: the innovative analogy. The move is to take a form, structure, functional principle or technology that already works in one area and transfer it to a completely different problem.
Two things are true of any good analogy at once: the source and target are similar in the aspect you care about (a function, a structure), and different in the aspects you don’t. You’re borrowing the useful bit and leaving the rest behind. Analogies come in three flavours, ordered by how far afield you reach:
| Type | Source of the idea | Classic example |
|---|---|---|
| Near | The same industry as you | Adapting a rival’s proven mechanism to your product line |
| Bionic | Nature - millions of years of R&D, free | Termite-mound cooling → building air-conditioning |
| Cross-industry | A totally different sector | Formula 1 race-car engineering → Nike Shox cushioning |
The termite mound is the showcase. Termites keep the inside of their towering mounds at a near-constant temperature using a passive system of airflow - no power, no compressor. Architects borrowed that principle to ventilate and cool buildings, reportedly cutting air-conditioning costs by up to 90%, delivering continuous fresh air, and producing a genuinely “green” innovation - a whole new architecture copied from an insect. The Nike Shox cushioning system, meanwhile, took its inspiration from the springs and suspension logic of a Formula 1 race car - an idea living in an industry with nothing to do with running shoes.
5 · Open Innovation - nobody has a monopoly on good ideas
Section titled “5 · Open Innovation - nobody has a monopoly on good ideas”So far every source has one thing in common: the good idea is often outside your own four walls - in a lead user, in another industry, in nature. Henry Chesbrough turned that observation into a whole paradigm in 2003: Open Innovation.
His starting line says it all: “good ideas are widely distributed today - no one has a monopoly on useful knowledge any more.” The old model was closed: invent everything in-house, guard it, ship it yourself. Open Innovation says that’s leaving value on the table in both directions.
Chesbrough defines it as the use of purposive inflows and outflows of knowledge - deliberately letting ideas cross the company boundary both ways:
- Pull in external ideas alongside your own internal ones
- Accelerates your internal innovation - you’re not starting from scratch
- Let ideas that don’t fit your strategy be used outside
- Use both internal and external paths to market
The picture that makes this concrete is the innovation funnel. Imagine your development pipeline - idea generation → evaluation/selection → development → production - but now draw the company boundary as porous instead of solid:
The two arrows across the corporate limit are the whole point:
- Integrate in: absorb promising external ideas into your development pipeline.
- Exploit out: rather than let a good-but-off-strategy idea die in a drawer, license it, spin it out, or partner it so someone captures its value.
6 · From idea to launch - Cooper’s Stage-Gate® model
Section titled “6 · From idea to launch - Cooper’s Stage-Gate® model”Great - you’ve now got sources spilling ideas at you. That’s a problem as much as a gift: most ideas are bad, good ideas can still fail in execution, and every stage of development costs real money. You need a disciplined process to move projects forward and to kill the losers early. That’s the Stage-Gate® model, developed in the 1980s by Dr. Robert G. Cooper.
Cooper describes it as a conceptual and operational map for moving new-product projects from idea to launch - a blueprint for running product innovation more effectively (doing the right projects) and more efficiently (doing projects right). The structure is exactly what the name promises: stages where work happens, separated by gates where decisions happen.
6.1 What a stage is
Section titled “6.1 What a stage is”A stage is a chunk of work, and it has four defining properties worth memorising:
- Each stage exists to gather data and drive down the project’s unknowns before the next decision
- There is no “R&D stage” or “Marketing stage” - every stage involves Marketing, R&D, Production, Engineering together, working in parallel
- Each stage costs more than the last - but each step also cuts the unknowns, so you only spend big once risk is small
- Each stage bundles activities that research has shown separate winning products from failures
Mechanically, a stage runs as: activities (the team gathers data) → integrated analysis (they interpret it) → deliverables (packaged information) → which feed the Go/Kill decision at the gate. Then the whole loop repeats at the next stage.
6.2 What a gate is
Section titled “6.2 What a gate is”A gate is a meeting - a quality-control and Go/Kill checkpoint standing at the entrance to each stage. Gates are the reason Stage-Gate isn’t just a to-do list: they’re where projects get funded, paused, or mercifully killed. They’re staffed by senior managers from different functions - the people who actually own the resources the project needs next. Cooper calls them the gatekeepers.
Every gate has the same three-part structure:
-
Deliverables - what the project leader and team must bring to the meeting (the results of the completed stage’s activities). These come off a standard menu for each gate and are agreed at the previous gate, so nobody’s surprised - management’s expectations are crystal clear in advance.
-
Criteria - how the project is judged. Two kinds:
- Must-meet / knock-out questions - a yes/no checklist designed to reject misfit projects fast. Fail one, you’re out.
- Should-meet criteria - desirable factors that are scored and added up (a point-count system) to prioritise the survivors against each other.
-
Outputs - the decision and what happens next: Go / Kill / Hold / Recycle, plus an approved action plan for the next stage (people, money, person-days, a timeline) and the agreed list of deliverables and date for the next gate.
7 · Why new products win - Cooper’s 7 success drivers
Section titled “7 · Why new products win - Cooper’s 7 success drivers”Stage-Gate didn’t come from a whiteboard; it came from studying what actually separated winning products from flops. Cooper distils that research into seven success drivers - and they double as a checklist for any product project:
| # | Driver | What it means in plain English |
|---|---|---|
| 1 | Superior product | A genuinely unique, differentiated product with a compelling value proposition - not a me-too |
| 2 | Customer focus | Build in the voice of the customer; a market-driven process, not an engineering-driven one |
| 3 | Front-end loading | Do the homework - proper due diligence before development starts |
| 4 | Sharp product definition | Nail the product/project definition early; avoid scope creep and shifting specs, which slow you down |
| 5 | Spiral development | Build → test → get feedback → revise; put something in front of the customer often to get it right |
| 6 | Well-executed launch | A solid marketing plan at the heart of a properly resourced launch - the product doesn’t sell itself |
| 7 | Speed | Accelerate - but never at the expense of quality of execution |
8 · The fuzzy front end - where projects are quietly won or lost
Section titled “8 · The fuzzy front end - where projects are quietly won or lost”Look back at the pipeline. Everything before development actually kicks off - Discovery, Gate 1, Stage 1 Scoping, Gate 2, Stage 2 Business Case - is what researchers call the fuzzy front end (FFE): the early, ill-defined, pre-development phase where the idea is still soft and the numbers are still guesses.
It’s tempting to treat this messy stretch as “not real work yet.” That’s a mistake. Research by Verworn (2003) found that how well you design and manage these early phases has a real, measurable payoff - in two ways at once:
So what actually happens in that first real stage? Stage 1 (Scoping) is a quick, internal look - deliberately not a deep investigation, just enough to decide whether the idea deserves the heavier Stage 2 business case. It runs three fast assessments plus a recommendation:
- Quick scope of market prospects - potential, acceptance, requirements
- Desk & detective research only - readily available and in-house sources, no full market study
- Conceptual read on feasibility, probable solution, technical risks
- Manufacturability / supply, IP issues, check for partners
- A quick business sanity check of the rationale
- Rough payback period - no spreadsheets or NPV calculations yet
The mindset is: spend a little effort to decide whether to spend a lot. That’s incremental commitment (from §6.1) showing up right at the start line - and it’s why a well-run fuzzy front end quietly does so much of the work of a successful launch.
Revision summary
Section titled “Revision summary”Next: Globalization & Megatrends → - zooming out from the firm to the forces reshaping the whole world economy.