Innovation fails when leadership funds the technology but leaves the surrounding capability system underdeveloped.
A board can approve an innovation budget in an afternoon. Building an organisation that can repeatedly absorb, adapt and scale new ideas takes much longer.
This difference is easy to underestimate. Innovation is often represented as a pipeline of projects: identify an opportunity, fund a pilot, prove the concept and scale it. That model is useful but incomplete. A technically sound idea can stall because the organisation lacks finance for deployment, suppliers cannot support it, operators do not have the skills, information does not reach decision-makers, regulation creates uncertainty, or the commercial incentive is too weak to justify change.
The project may appear to have failed. In reality, the surrounding innovation ecosystem may never have been capable of carrying it.
The Strategic Context
Wakeford and colleagues examined this problem in a 2017 study of green industrialisation in Ethiopia's cement, leather and textile sectors. Their work combined nine semi-structured interviews with policy and industry actors and a survey of 117 firms.
The researchers found relatively low rates of green product and process innovation across the combined sample. Firms identified high technology costs, inadequate finance and limited information among the important barriers. Improving competitiveness, expanding markets and reducing unit costs were stronger innovation motivations than reducing environmental impacts or meeting environmental requirements. The study also emphasised interactions among firms, government, development partners and sector institutions as part of the innovation system.
Those findings belong to the specific national and sectoral context studied in 2016 and should not be universalised. But the architecture is highly transferable.
Innovation does not occur inside a laboratory or digital team alone. It occurs inside a network of actors, incentives, information flows, finance, rules, skills and market expectations.
For executives, the implication is clear:
Innovation capacity is an organisational and ecosystem capability, not a line item in the R&D budget.
What Leaders Commonly Misread
The first misread is confusing invention with innovation.
A prototype can be technically novel without becoming operationally useful. Innovation requires adoption, diffusion and value creation. That means the organisation must move beyond proving that something works to proving that it can be integrated, funded, governed and used.
The second misread is assuming money is the only missing input.
Capital matters. But funding cannot compensate indefinitely for missing skills, weak supplier capability, fragmented decision rights, unclear regulation or poor access to information.
The third misread is treating innovation as a central-team responsibility.
A dedicated innovation function can coordinate and accelerate work, but it cannot substitute for operating ownership. If production, commercial, procurement, IT, finance and risk functions do not have the capability or incentive to adopt the innovation, the central team becomes a pilot factory rather than a transformation engine.
The fourth misread is assuming environmental or strategic importance will motivate adoption by itself.
Wakeford and colleagues found competitiveness and cost-related motives stronger than environmental motives among the surveyed firms. The broader lesson is that a leadership objective does not automatically become an operating incentive. People respond to the economic, operational and institutional signals they actually experience.
Reframing the Issue
Innovation strategy should not begin with a list of technologies.
It should begin with a capability question:
What must be true in our organisation and ecosystem for valuable ideas to move reliably from evidence to adoption?
This changes the unit of analysis.
The unit is no longer the pilot. It is the innovation system.
That system includes internal actors such as engineering, operations, finance, procurement, legal, data, risk and commercial teams. It can also include universities, suppliers, regulators, investors, customers and industry bodies.
The strength of the system depends on the quality of the interfaces between these actors, not merely the competence of each one individually.
Related article: Sustainability Capability Is Built in Layers, Not Added as a Target
Strategic Analysis: The Six Capabilities Behind Repeatable Innovation
1. A credible demand signal
Innovation accelerates when the problem is economically and strategically real.
Teams need to know what outcome matters, who values it and how success will be recognised. A vague instruction to "innovate with AI" or "find greener technologies" creates activity, not direction.
A credible demand signal defines the customer or operational problem, the strategic value and the constraints that matter.
2. Access to capital across stages
Different phases require different forms of funding.
Exploration should be cheap and reversible. Demonstration requires enough capital to create credible evidence. Scale-up may require significant infrastructure, working capital and operating change.
A common failure is to fund experimentation but create no pathway for industrialisation. The pilot succeeds, but the business cannot cross the gap between demonstration and deployment.
3. Knowledge and information flow
Wakeford and colleagues found limited information to be an innovation barrier in the studied sectors, and highlighted the role of actor interaction.
Inside enterprises, information fragmentation produces the same effect. Engineering may know what is technically possible while finance understands investment limits, procurement knows supplier capability and operations knows the real failure modes. If those views meet only at final approval, the organisation learns too late.
4. Absorptive capability
An organisation needs the ability to understand external knowledge, adapt it and integrate it into operations.
This is why buying advanced technology does not guarantee advanced performance. Equipment, software or intellectual property must be translated into procedures, skills, data, maintenance, governance and operating routines.
The weakest part of many innovation strategies is not invention. It is absorption.
5. Institutional and governance support
Rules shape innovation behaviour.
Approval thresholds, procurement methods, cybersecurity rules, technical standards, safety requirements, intellectual-property arrangements and budget cycles can either enable responsible experimentation or make it prohibitively slow.
Good governance is not the absence of control. It is a control architecture matched to the maturity and reversibility of the decision.
6. Commercial and operating incentives
If the people expected to adopt an innovation carry the operational risk while someone else receives the benefit, resistance is rational.
Adoption is more likely when the incentive system recognises productivity, reliability, customer value or cost improvements that the innovation can create.
This is particularly important when environmental innovation requires near-term cost or disruption but creates benefits elsewhere in the enterprise.
The Portfolio Implication
Innovation portfolios should therefore be balanced across more than technologies.
A portfolio filled with pilots but lacking capability-building initiatives is structurally weak.
Leadership may need to fund:
- technical experiments;
- shared data infrastructure;
- operator training;
- supplier development;
- regulatory engagement;
- test environments;
- commercial partnerships;
- change and adoption capability.
These initiatives can look indirect when reviewed project by project. At portfolio level, they are the enabling architecture that allows multiple innovations to succeed.
Opportunity cost also matters. Funding ten small pilots can feel diversified, but if none can cross the adoption gap, the portfolio is consuming attention without building enterprise capability.
Decision Framework
ERANORTH recommends a seven-part Innovation Ecosystem Test before scaling a material innovation.
1. Strategic pull
What problem, customer need or strategic objective creates genuine demand for the innovation?
2. Technical evidence
What has been proven, under what conditions, and what remains uncertain?
3. Capital pathway
Is there a credible funding path from pilot through deployment, including operating and working-capital implications?
4. Knowledge pathway
Who must understand, transfer and retain the knowledge? Where can information become trapped?
5. Adoption capability
Do operators, customers, suppliers and support functions have the skills and capacity required to use the new system?
6. Institutional fit
Which rules, approvals, standards or contractual arrangements could prevent or materially delay adoption?
7. Incentive alignment
Who bears the cost, who carries the risk and who receives the benefit? Are those incentives aligned enough to support adoption?
If several of these conditions are weak, leadership should treat the gap as part of the innovation program rather than blaming the technology alone.
From Strategy to Execution
Immediate action: review the active innovation portfolio and classify each initiative by its main adoption dependency. Identify projects that have technical funding but no scale-up owner, no deployment budget or no operating adoption plan.
Medium-term capability building: establish cross-functional mechanisms for knowledge transfer and early challenge. Bring finance, procurement, operations, risk and engineering into innovation governance before designs harden.
Long-term strategic positioning: build repeatable absorption capability. The enterprise advantage is not the ability to discover one new technology. It is the ability to learn faster than competitors, integrate external knowledge and convert it into reliable operating performance.
Related article: Technology Is a Means, Not a Strategy
Signals to Monitor
Watch the ratio of pilots to scaled deployments; time between proof of concept and operating adoption; percentage of pilots without named business owners; repeated procurement or regulatory delays; lack of supplier alternatives; innovation spending concentrated on technology but not training or integration; operating teams receiving innovations late; and benefits that depend on behavioural change without funded adoption work.
Another warning sign is a portfolio in which the same barrier appears repeatedly across unrelated pilots. Recurrent finance, data, approval or skills constraints indicate a system problem, not a collection of project problems.
Questions for the Leadership Team
- Which part of our innovation system fails most often: ideas, evidence, funding, integration or adoption?
- Are we financing pilots without financing the path to scale?
- Which external actors are essential to our innovation strategy, and how strong are those relationships?
- Where is critical knowledge trapped between functions or organisations?
- Do our approval and procurement rules distinguish reversible experiments from irreversible commitments?
- Who carries the operating risk of adoption, and who receives the benefit?
- What enterprise capability would allow several innovations to succeed rather than improving only one project?
Closing Perspective
Innovation is frequently managed as a search for better ideas. Mature organisations manage it as a system for turning ideas into adopted capability.
That system needs capital, but capital is only one input. It also needs knowledge flow, institutional support, operating capacity, incentives and relationships strong enough to move technology across organisational boundaries.
The strategic question is therefore not "How much do we spend on innovation?"
It is:
What system have we built that makes valuable innovation repeatedly possible?
Source basis: This article is an original ERANORTH synthesis principally informed by Wakeford et al. (2017), Innovation for green industrialisation: An empirical assessment of innovation in Ethiopia's cement, leather and textile sectors, Journal of Cleaner Production, volume 166. The study's country- and sector-specific findings are used as evidence for system relationships, not as present-day universal benchmarks.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.