top of page

Why Innovation Programme Results Are Hard to Defend at Renewal

Autorenbild: Maria Ksenia Witte
Maria Ksenia Witte
vor 6 Tagen
4 Min. Lesezeit
Expanding a cohort without increasing the specialist capacity participants need creates a longer queue around the same bottleneck.

My view on success stories, innovation programme contribution and when an independent second opinion helps

Audio cover
Why Innovation Programme Results Are Hard to Defend at RenewalMaria Ksenia Witte (AI-enhanced)

In this edition:

1. A renewal recommendation needs an argument about the support worth continuing, beyond a list of successful participants.

2. Starting conditions and work already under way affect what programme results can tell you.

3. The support doing the useful work may be a specialist service or an approval that barely features in the report.

4. A justified stop can prevent a bad commitment; a test that never happened may reveal a delivery problem.

5. An independent review can give the team a documented recommendation and practical choices before the next funding or design decision.

An innovation programme’s renewal needs an explanation of the support worth funding again. A report that omits that contribution cannot support the expansion recommendation, however much successful activity it contains.


My position is to resolve that gap before committing another budget or promising a larger cohort.


If you are preparing the recommendation, the practical problem is the decision it must support. Which useful work will the next commitment protect, and can the organisation deliver it? More success stories do not answer those questions.



Why the headline result leaves questions open


Imagine a venture signs a licensing agreement during support. A buyer was already involved when the team joined. Did the programme help resolve something that was holding up the agreement, improve the terms or save time? The signature is useful news, but the contribution needs its own explanation.


The EPO’s October technology-transfer report illustrates the importance of context. It compares office outputs relative to incoming invention disclosures. In Table 3.5, six of eight comparisons between office groups are not statistically significant at 5%. The study leaves uncertainty about group differences and provides no estimate of the effect of an individual programme.


My concern is the jump from a successful participant to a larger offer of the same support. Work already under way, selection and other partners may explain part of the outcome. A review should make the programme’s particular contribution easier to understand before recommending expansion.


Two illustrative licensing situations show why the same recorded result may justify different claims about programme support.

The useful work can be surprisingly ordinary


A licensing specialist resolves a disputed clause. A partner provides a test slot. Somebody with authority approves work that had been waiting for weeks. Those contributions may be more important to a participant than the activities that dominate the brochure.


If the renewal increases cohort size without protecting the scarce service participants depended on, the programme can create a larger queue around the same unresolved task. I would want that consequence considered before describing growth as an improvement.


Make room for an honest negative result



A test that rules out an unsuitable application can prevent another year of wasted effort. I would want that result visible. A team whose test never happened because it could not get access needs a different response. Treating both as failure hides the decision the support should improve.


There is a limit: calling every stopped project learning would excuse poor delivery. The evidence needs to explain what was established and why the decision followed. Some benefits also take years to appear; a review focused only on quick sales can remove useful support too early.


The UK government’s Magenta Book guidance on evaluation recommends planning evidence collection early and considering suitable comparisons. At renewal, information about the starting position may already be difficult to recover.


The Substack analysis goes further into programme renewal choices and competing explanations. It also connects where the unresolved risk lands for investors, technology transfer offices, venture studios, founders and sponsors:



What an independent programme review should give you


If the same questions keep returning at renewal, the recommendation needs work before the next commitment. An independent assessment can bring comparisons from other commercialisation settings and give the team a documented view on what to protect or change.


A useful review provides a reasoned recommendation about what to preserve, challenge or change, with practical options that fit the assignment. A second opinion examines the current recommendation. Red teaming tests the proposed logic before commitment. Design work develops the feasible offer that should follow. The scope needs to match the decision on the team’s desk.


You should have something concrete to use in your next management or funding conversation, including reasons to protect good work. That gives the team a clearer basis for the next commitment.


My email newsletter connects sourced reality checks on innovation decisions across all stakeholders - who's affected and how.


Before the next cohort is approved

 

If the renewal paper keeps returning with questions about what to keep or change, a second opinion can test the recommendation alongside the team’s existing expertise. Relevant experience across organisations can challenge assumptions inherited from the previous design. The useful result is a recommendation on the next design work, its intended participants and the changes needed before delivery.


Kommentare

Mit 0 von 5 Sternen bewertet.
Noch keine Ratings

Rating hinzufügen
bottom of page