The Sponsorship Decay Problem
Most corporate innovation programmes begin with strong executive endorsement. A senior sponsor is announced. Budget is allocated. Communication is enthusiastic. Within 18 months, a familiar pattern asserts itself: the sponsor becomes less visible, budget renewals become uncertain, and the programme begins to optimise for survival rather than output.
This is not primarily a political problem. It is a measurement and positioning problem. Innovation programmes lose executive support for three consistent reasons, each of which is addressable by design.
No measurable output. When a programme cannot clearly demonstrate what it has produced — in terms that connect to business priorities, not programme metrics — executives cannot justify continued investment to a board or CFO. "We ran 14 workshops and generated 180 ideas" is not a business result. It is an activity log.
Disconnection from strategy. Programmes that operate as islands — generating interesting ideas that do not connect to the organisation's current strategic direction — are perceived as innovation theatre rather than strategic tools. Even genuinely good ideas fail to attract resources if they cannot be positioned within the strategic frame that the executive team is already accountable for.
Treatment as a cost centre. The default financial framing for an innovation programme is expense. If the programme does not produce visible outputs that can be attributed to a revenue line, a cost saving, or a risk mitigation, it sits permanently in the "discretionary spend" category — the first thing cut when conditions tighten.
What Executives Actually Need to Say Yes
Executives who sustain innovation programme investment are not optimists who believe in the intrinsic value of innovation. They are people who can answer three questions from their own leadership or board.
What did it produce? This requires quantified output: not number of ideas, but ideas that reached defined development stages, concepts that were approved for pilot, pilots that delivered measurable results, and — over a sufficient time horizon — business outcomes attributable to programme investment.
Who owns it? Programmes without a named owner with clear accountability are perceived as everyone's responsibility and therefore no one's. The executive sponsor needs a counterpart: a Programme Director with P&L accountability for the innovation portfolio, not a "Head of Innovation" whose success criteria are undefined.
What is the exit criterion? An executive who cannot answer "how will I know this is working, and what would cause me to stop it?" is making an open-ended commitment. Open-ended commitments to programmes with no measurable output are difficult to defend. An explicit exit criterion — defined in advance, as part of the programme business case — paradoxically increases executive commitment by removing the anxiety of an open-ended obligation.
Five Programme Design Principles That Maintain Buy-In
1. Design for Outcomes, Not Activities
Every programme element — every session, every workshop, every review — should be traceable to an outcome in the programme's measurement framework. If an element cannot be connected to a measurable output, it should not be in the programme.
This does not mean eliminating exploratory or learning-oriented activities. It means ensuring that even exploratory sessions have a defined output format: a set of documented hypotheses, a structured summary of competitive signals, a set of strategic questions that will be addressed in subsequent sessions.
2. Connect Every Session to a Named Strategic Priority
Each session brief should reference at least one named item in the organisation's current strategic framework. "Explore opportunities in the sustainable packaging space, with specific reference to our stated commitment to reaching 80% recyclable packaging by 2028" is a connected brief. "Explore sustainable innovation opportunities" is not.
This connection does two things. First, it ensures that session outputs can be evaluated against an existing strategic filter rather than requiring a separate "relevance assessment" after the fact. Second, it makes the session directly useful to the executive responsible for that strategic priority — who becomes a natural advocate for the programme.
3. Establish a Quarterly Innovation Review That Executives Attend Voluntarily
The quarterly review is the primary mechanism for maintaining executive engagement over time. The test of a well-designed quarterly review is whether executives attend voluntarily — not because they feel obligated to support the programme, but because the review is a useful input to their own decision-making.
A quarterly review that executives attend voluntarily has three characteristics. It is short (no more than 90 minutes). It contains new information — market signals, competitive intelligence, validated concepts — that is relevant to the executives' current priorities. And it ends with explicit decisions: resource allocations, go/no-go calls, priority shifts.
A quarterly review that becomes a programme status update — "here is what we have been doing" — fails this test and will lose executive attendance within two cycles.
4. Maintain a Live Portfolio, Not a Historical Archive
The programme's output should be visible as a live portfolio: concepts at different stages of development, with clear status, owner, resourcing, and next decision point for each. This portfolio view allows executives to understand the programme's current output without reading a report, and to intervene at specific decision points rather than receiving periodic summaries.
The psychological impact of a live portfolio is distinct from a periodic report. A periodic report describes what happened. A live portfolio shows what is happening and what decisions are needed. Executives engage differently with operational information than with historical summaries.
5. Report in Business Language, Not Innovation Language
The default reporting language of innovation programmes — "ideation sessions," "hackathons," "design sprints," "concept prototypes" — is opaque to executives whose primary accountability is to business results. Replace it.
"Three workshop sessions produced 12 concepts evaluated against strategic criteria; two have been approved for 90-day pilots with £150k combined investment" is a business statement. "We ran a design sprint and generated strong concept prototypes" is not.
This translation work is not cosmetic. Executives who understand the programme's output in their own language are more likely to engage with it substantively — and more likely to defend its budget when challenged.
Structuring the Quarterly Innovation Review
A 90-minute quarterly innovation review that executives attend voluntarily follows a consistent structure.
Opening (10 minutes): Portfolio status dashboard. Current number of active concepts, stage distribution, resource committed, stage completions since last review.
Deep dives (50 minutes): Two or three concepts at critical decision points. For each: current evidence base, specific decision required, resource implication, and risk assessment. Executive input actively solicited; these are decision meetings, not presentations.
Market intelligence (15 minutes): Three to five external signals — competitive moves, market data, regulatory developments — directly relevant to the active portfolio. This section must contain new information that executives do not already have.
Programme health (10 minutes): Input metrics, process efficiency, and any structural issues requiring executive attention.
Decisions recorded (5 minutes): All decisions taken in the meeting captured in a structured format and distributed before the end of the day.
Platforms like CoVision support the operational infrastructure of this model: structured session outputs that feed directly into the portfolio view, real-time synthesis that enables same-day reporting, and a decision record that maintains accountability between quarterly reviews. The technology does not replace the programme design — but it dramatically reduces the administrative overhead that otherwise consumes the programme team's capacity for substantive work.