Brief: Across this six-issue arc, the same gap has surfaced under five names: innovation theatre, zombie pilots, portfolio drift, resource asymmetry, and governance that runs a beat behind. All trace to one structural absence. No function is accountable for converting a validated signal into a structural commitment. This issue names that function, the Venture Operator Function, defines it through two tiers and four capabilities, sets the three conditions that separate a real function from a node with a title, and explains why most organisations do not hold it even where they assume they already do. It closes with a six-question self-diagnostic you can run on your own portfolio.

Subscribe now

Across this series, the same gap has surfaced under five different names.

Innovation theatre persists because activity is often the only signal that governance instruments can read, and no one is accountable for converting activity into ventures. Pilots and experiments zombify, as the authority to stop them cannot be exercised across forums and no one holds it. Portfolios stay collections because resources never move to the strongest signal, and no one owns reallocation. Resources arrive on the wrong clock at the wrong scale because the enterprise runs on the calendar while the portfolio runs on the signal, and no one holds the bridge between them.

Five issues, five patterns with one structural absence beneath them all.

The diagnosis was never a shortage of ideas, strategy, or talent. Corporate innovation functions have invested heavily in the front end, in ideation, exploration, the pilots that prove a signal exists, and even early-stage startups. What they have not built, or have not matured to the same degree, is the layer that sits between a validated signal and a structural commitment, the layer accountable for making the system reorganise around evidence. The signal has been read, but the reorganisation does not follow. The work falls into the space between knowing and acting, and that space has no owner.

This is the final issue in the series, and its task is to name the thing that occupies that space when it exists and is missing when it does not. Both Issue 10 and Issue 11 pointed here. The capability Issue 11 said the corporation has to build is not a process or an instrument. It is a function. This issue defines it.

The function and its two tiers.

The Venture Operator Function, “the function” for short, for this issue, is the conversion layer between a validated signal and a structural commitment. It is the part of the system responsible for ensuring that when evidence demands a change, the structure actually changes.

It is defined by an altitude, not by a person or a title. The function has to sit close enough to the work to read a signal at the resolution at which the signal arrives, and high enough above the work to move resources across ventures and stop them when the evidence turns. Many corporate innovation roles hold one of the two positions. The function requires both at once.

It has two tiers, because the work operates at two altitudes.

The upper tier is Opportunity Authority. It is accountable for a hypothesis about where value exists, across the full lifecycle of that hypothesis. It opens the hypothesis, tests it across a set of options, concentrates resources on the options that prove out, evolves the hypothesis as evidence reshapes it, and retires it when the evidence no longer holds. The unit it governs is the opportunity area, the bounded space a hypothesis defines. Inside that space, exploration spans build, buy, invest, and partner, because at the point of exploration, the vehicle the answer takes is not yet known. Opportunity Authority is therefore vehicle-agnostic. Its objective is the hypothesis, not any single option.

The four capabilities live at this tier, in their portfolio form. Signal ownership is reading which options in the set are crossing the commitment threshold. Scope is narrowing the set. Resource movement is concentrating capital and talent on the options that are compounding and pulling it off those that are not. Stop operates at two levels: ending an individual option when its bet is failing, and retiring an entire opportunity area when its hypothesis has been falsified or has exhausted its allocation without producing a strong signal.

The lower tier is Option Authority. It is accountable for executing a single option to its proof point, running the build, stewarding the investment, managing the partnership, and managing the option as it evolves from one vehicle to another over time, for example, an early-stage investment that later becomes a broader partnership. Option Authority is vehicle-specific by definition, because executing a build and stewarding an investment are different work. Its objective is the option’s own milestone, not the area, and it holds no authority over the hypothesis itself.

The function is the relationship between the two tiers. Execution distributes to Option Authority. Conversion concentrates at Opportunity Authority.

The asymmetry is the point. The capability that must distribute is the execution of each option, because a central node running every venture is its own failure mode. The capability that cannot distribute is conversion across options, because the moment it scatters, you get duplicated bets, budget contests, and local optimisation, which is the portfolio illusion at the level of the operating model. Option Authority cannot stop its own option or retire its own area, for the same structural reason in both cases. No one kills the frame that justifies their own existence. Stop has to sit above the work it stops, or it never gets exercised.

The function presupposes the mandate; it does not set it. It assumes the upstream decisions described in Issue 9 are already made: that innovation has a defined mandate, that the instrument types in scope are named, that the risk appetite is set, and that there is a venturing strategy to execute against.

The presupposition is deliberate, because conversion is a different problem from definition, and collapsing the two leads to mistaking the function for the strategy function and waving it away. This issue addresses the ongoing execution and refinement of venturing within that boundary, not the drawing of the boundary itself. Where the mandate is too loose to execute against, the function does not redraw it; rather, it surfaces the gap, because conversion failures expose definitional ones. That is the feedback Issue 9 described, running from portfolio performance back into strategy.

This is where the disciplines the series has been building become accountable to something. Structural discipline, decision rights, stop authority, and resource reallocation have, until now, been conditions a system should meet. The Venture Operator Function answers the question those conditions leave open: who they are accountable to. The function provides structural discipline for a given node.

Why the function is unheld.

The capabilities are not missing. In most corporate innovation functions, and in corporates more broadly, all four exist somewhere. Different partiesm may hold them, and the organisational chart is designed to keep them apart.

• Signal interpretation sits within an innovation team that closely reads the market and has no capital authority.

• Resource movement sits with finance, whose mandate is to protect known-return lines on the profit-and-loss statement.

• Scope and stop sit with business-unit heads, whose incentive is to defend their own allocations.

Each holder is behaving rationally inside its own incentive structure. The innovation team cannot move the capital it can see is needed. The finance function will not allocate capital to an unproven return when a proven one is competing for it. The business-unit head will not stop a venture that carries headcount and standing. This is the same logic Issue 11 traced through the “not wanting to act off-cycle” example. The behaviour is not a failure of will. It is the system producing the behaviour it is structured to produce.

The scatter is the design, not an oversight. And a capability set that is distributed across functions whose incentives point away from conversion cannot convert. Each holder optimises locally, and conversion is the one thing no local optimisation produces. These functions were also built for steady-state operation, not for execution under constraint and uncertainty, so each applies a steady-state test to a venture decision. That is the deeper reason no single existing function can hold conversion authority. It would have to cut across all of them at once, against the grain of what each was built to do.

The scatter is the first factor. The second is the altitude, the tier itself. The point at which conversion would occur is unoccupied.

Corporate strategy functions operate at a high and abstract level. They set intent, assign a number to a theme, optimise compliance costs, determine an acquisition, enter adjacent markets, and build a digital channel, without owning the work that executing the theme implies. Execution is pushed down to divisions, which interpret the theme locally through their own remits, build their own versions, and compete for the same budget. Between the altitude that sets intent and the altitude that executes it, there is no node accountable for the opportunity area itself, casting across options, concentrating on evidence, retiring what fails.

The shape of the failure is consistent: in many cases, a venture, regardless of instrument, needs a strategic rationale to clear the gate above it and divisional buy-in to secure adoption below it. The two gates share neither a clock nor an objective. The strategic gate moves in step with the parent’s planning cadence and judges the venture’s fit with the theme. The divisions move on their own delivery commitments and judge the venture by whether they can absorb it, which they often cannot, because each division carries a different innovation remit and a set of incumbent projects already competing for attention and budget. The venture moves at the pace of the slowest gate, and in the shape the gates will tolerate, not the shape the evidence calls for. No one owns conversion across that altitude, so the signal never becomes a commitment. It dies in the space between intent and execution.

The third factor is the sharpest, and most clearly marks the function as absent.

The hardest of the four capabilities has no owner anywhere in most structures. Option-level stop exists in weak form, because someone can usually cancel a project. Area-level stop rarely exists, because retiring an opportunity area means declaring that an entire theme, one that leadership endorsed and funded, is no longer worth pursuing. That is the most politically expensive decision in the system. It requires telling the people who championed the theme that the evidence has gone against it. No standing role is accountable for making it, so it is not made. Areas persist long after their hypothesis has been falsified, or continue to consume resources without producing a strong signal, still generating fresh options against a claim the evidence and the appetite have already closed. The opportunity area becomes the zombie pilot one altitude up.

A capability with no owner is not a capability the system has. It is a gap the system has learned to route around.

The candidate roles each hold a portion and none holds the whole. Signal proximity without capital authority. Capital authority over investments but not across builds and partnerships. Delivery coordination without stop authority on evidence. Each is real, and each is a genuine role in its own right. None is the Venture Operator Function, the accountable consolidation of all four capabilities at the conversion altitude, which is what no existing role carries, and which the exemptions return to.

What makes the node the function.

Consolidating the four capabilities into a single node is necessary but not sufficient. A node can hold all four on paper and still not be the function. Three conditions convert a node that holds the capabilities into the function rather than a person who is temporarily behaving like it.

The first is that the authority must be backed, not tolerated.

A node can be named and still routed around. The organisational chart records the authority, but in practice every decision it makes is revisited. The test of backed authority is whether a decision holds once it is made, or whether it must clear a strategic gate above and divisional buy-in below before it takes effect, and can be relitigated at the next forum. Tolerated authority is authority that is revisited until it dissolves, the decision is named, and then quietly unmade.

Issue 11 showed why this happens: acting off-cycle marks the operator as undisciplined, so the institutional cost of exercising authority falls on the individual who exercises it. The function inverts that cost. It institutionalises the authority, so that exercising it is following the protocol rather than breaching it. Backed authority is the difference between a node that converts signals and a node that proposes conversions for others to ratify.

The second condition is that the incentives must be consistent with venture pace.

The corporate operator running a venture lacks both halves that drive pace in an independent venture. The upside is absent, because compensation is a fixed package decoupled from the venture’s outcome. The downside is also absent, because, as Issue 10 established, ventures can be funded at the level required to stay alive and not compound. A slow venture does not die; it zombifies, and continues to pay its operator either way. Enterprise pace is therefore the rational default. It is not a character failing of the people involved. It is the predictable result of an incentive structure that has removed both the reward for moving fast and the penalty for moving slowly.

Behind the individual incentive sits the enterprise’s own. A listed parent answers to shareholders on a quarterly cadence and, in regulated sectors, carries exposure that rewards caution over speed, so the institution’s default setting is already slower than venture pace before any individual operator is considered.

The function only behaves like the function if its accountability is tied to the hypothesis and insulated from the operating-profit tradeoff, the same separation Issue 10 built into the structure of the venture pool. A node accountable to an operating line will protect the operating line. A node accountable to the hypothesis will move on the evidence. The structural design of the accountability, not the disposition of the individual, sets the pace.

The third condition is that the function must be durable.

Personal authority dies at the next leadership transition. Issue 10 documented this directly in the Australian corporate venture vehicles, several of which were structurally well designed and then unwound when the sponsor changed, or cost pressures rose. The structures that survived longest were those whose continuation did not depend on a single decision-maker’s continued backing. Authority that exists only because a particular individual currently chooses to operate it is not yet a function. It is a person doing the work of one, and the capability leaves when they do. The same fragility runs through the fast-track, which requires a sponsor to invoke it, and the off-cycle move, which requires an individual to spend personal capital. Durability is what separates a function from a role. A person holds a role. A function endures across the people who occupy it.

Consolidated authority that is tolerated, misaligned, or sponsor-dependent is not the Venture Operator Function but a node with a title. The function is consolidated authority that is backed, incentive-aligned, and durable.

The structural implication follows from the argument rather than decorating it. A function that meets these three conditions is hard to build from within an incentive structure designed to prevent it, because the system is built for steady-state operation. The authority is the one the hierarchy is least willing to delegate; the incentives are the ones the compensation system is least built to provide; the durability is the kind that depends on outlasting the sponsor who created it. None of this means the function must be external. It means it must be designed so that authority, incentives, and durability are properties of the design, not of whoever holds it. However it is staffed, the design carries the function, but the person does not.

The Venture Operator Self-Diagnostic.

The practical question is whether the function exists within a given organisation, and, if not, where the gaps lie. The self-diagnostic below surfaces it, quickly. It is built to be run on a real function, not in the abstract.

The first four questions test whether each capability is held by a single accountable node at the opportunity-area altitude. Write down the name of the person who holds each one today.

The act of writing the names is where the diagnosis lands.

Reading the pattern. Look at the four names written for Questions 1 to 4.

One name across all four, holding on Question 5 and surviving on Question 6, means the function exists as a structure. This is rare, and it is worth examining for what is enabling it, because the enabling conditions are usually deliberate.

One name performing the work informally, hostage on Question 5 and failing on Question 6, means the function is being performed and not held. It will leave at the next transition.

Four different names, or “the committee,” or “no one,” means the capabilities are scattered across functions with conflicting incentives, and no node is accountable for conversion. This is the default state, and it is the state this series has spent five issues describing from five angles.

The exemptions.

Four arguments are commonly raised to explain why a given organisation already has the function, or does not need it. Each carries some legitimacy, and each is worth testing against the altitude and the capability set.

A word on terms before the four, because it matters here. Several of the roles below are functions in their own right, often senior ones with teams and real mandates. The question is not whether they are functions. It is whether they are the Venture Operator Function this issue names, the vehicle-agnostic conversion accountability at the upper tier. Where this section says a role is not the function, it means it is not that one. It does not mean the role is not a function in its own right.

One pattern runs under several of these objections, so it is worth stating once. Within whatever mandate the enterprise has set, the vehicle should be selected against the hypothesis, not defaulted to by whoever holds authority over a particular vehicle. A vehicle-scoped role will often show two biases inside its mandate. It defaults to the vehicle it runs rather than choosing among the permitted vehicles on the evidence. And it is likely to underuse the instrument it does hold, taking its primary value and leaving the rest.

A deliberately bounded mandate is legitimate, the case Issue 9 made. An enterprise that scopes innovation to internal build and spin-out, for strategy and risk reasons, has made a real decision, one the function works within, not against. The critique is not that a role declines a vehicle the enterprise has ruled out. It is that, among the in-scope vehicles, the choice is too often made by remit rather than by evidence.

“We have a head of innovation who owns this.”

The head-of-innovation role is legitimate, and its remit varies widely, from narrow internal initiatives to broad cross-vehicle mandates. The point is scope, not competence. The exemption fails where the remit is bounded, which is the common case. Many heads of innovation are scoped to internal experimentation and build: run the experiment, prove the concept, roll it out within the existing business. That is a real and useful remit, and a fraction of what the function requires. It is one vehicle where the function works across whichever vehicles the mandate permits; where the mandate allows both build and spin-out, the build-scoped role tends to default to building rather than choosing between them on the evidence. And it is one phase where the function owns the whole hypothesis lifecycle, the comparative judgement across options and the retirement of the area. A remit built around experimentation tests a chosen solution. Discovery casts across options to find which vehicle proves the hypothesis at all.

In the two-tier language, the bounded role sits at Option Authority altitude for a single vehicle, yet is described as the whole function. That is why a strong, well-run head of innovation can still leave the conversion gap open: not because the role is limited, but because its scope sits below the conversion altitude by design. Where the remit genuinely spans all vehicles and the full lifecycle, the role is not an exemption. It is the function under another name.

“We do this through our governance committee.”

A committee cannot be the function, for two reasons the series has already established. It meets on the parent’s cadence, so it cannot act between forums, and exposure does not wait for the calendar. And it decides by consensus, so it optimises for proportionality across its members’ interests rather than conviction on a single signal. A committee that must keep every function comfortable cannot allocate capital to one option at the expense of the others. The committee is frequently the structural reason the four capabilities are scattered, not the mechanism that consolidates them.

“Our culture handles this informally. We do not need the structure.”

Informal handling is the durability failure stated as a virtue. If the function is performed informally, it is done by a person and leaves with that person. It works while a capable individual is present and willing to spend the personal capital that off-cycle action costs. It does not survive their departure, a reorganisation, or a change of sponsor. A function that depends on the goodwill of a particular individual is exposed at exactly the moments the organisation most needs it to hold.

“This is just a chief venture officer by another name.”

This is the most important exemption, because it directly threatens the category, and the chief venture officer role is a senior and legitimate one. Here too the point is scope and objective, not competence. As usually constituted, the role owns investment activity, sits on the parent’s capital cadence, and is accountable for a portfolio of deals. That bounds it twice: the vehicle is usually investment, where the function is vehicle-agnostic, and the objective is usually financial return, where the function is mandated to enterprise value.

Enterprise value is the wider concept, and financial return is one of its forms. The others are the ones an investment mandate is not built to register: a product capability built internally, an adjacency entered through partnership, a near-term gain in competitiveness, a simplification that strengthens the core. Most do not resolve into a position with a return, so a mandate measured on investment outcomes cannot see them. This is the strategic-versus-financial distinction Issue 11 drew, where the strategic position is the harder cost to see because it does not appear on the quarterly report. A chief venture officer can do excellent work against an investment mandate and still not be the function, because the function asks what the best way is to pursue this opportunity for the enterprise. In contrast, the mandate asks what the best return is on this position. The first question contains the second.

There is a second form of underuse, within the investment itself. A sanctioned position is an instrument, not only a bet. It can open a commercial or partnership relationship that strengthens the core now, a product capability, a better customer experience, an adjacency, an internal optimisation, rather than only a return at exit. A mandate measured on portfolio return underweights this, because the value accrues to the business, not the fund, and the fund is not accountable for it. The one vehicle is used for less than it could return.

Like the head of innovation, the bounded chief venture officer is a vehicle specialist at the option tier, here for investments. Where the mandate genuinely spans the in-scope vehicles and is measured on enterprise value rather than investment return alone, the title is the function under a finance-led name, not an exemption. Where it is not, naming the function is not relabelling the role. It is identifying an accountability that the existing roles, together, do not hold.

Closing the arc.

The series has traced one absence through five forms.

• The activity that never becomes a venture.

• The pilot that never gets stopped.

• The portfolio that never reallocates.

• The resource that never arrives in time.

• The governance that never keeps pace.

In each case, the missing element was not insight; the signal is read. What was missing was a function accountable for converting the reading into a structural commitment, and for owning the hypothesis from the moment it opens until the moment it is retired.

Abundant capital hides the failure. When resources are plentiful, the cost of slow conversion is absorbed by the surplus, paid quietly out of the slack, which is part of why the gap has been survivable for so long. Constraint removes the slack. The option that should have been concentrated on cannot be funded when there is nothing spare to move, and the area that should have been retired is now consuming capital a live bet needs. The gap was always there.

Constraint only makes it legible, and expensive. So when an organisation cuts the innovation function, it usually cuts the visible half and leaves the conversion gap intact, because the gap was never in the front end. It then pays market rates to acquire what it could have built, the pattern Issue 10 traced through ventures bought rather than grown, in a thin domestic capital market that makes the fallback more expensive here than in deeper economies.

The series has carried a running line. A portfolio without kill discipline is a list. A portfolio without resource velocity is a list with a budget.

This issue adds the final clause.

A portfolio no one is accountable for converting is a list with a budget and a sponsor. The budget keeps it funded.

The sponsor keeps it endorsed. Neither converts a signal into a commitment, nor does either survive the sponsor’s departure. The function is what remains when the budget and the sponsor are not enough, which is most of the time.

This is Issue #12, the sixth and final issue in the Corporate Venturing Under Constraint series. Issue 11 named the capability the corporation has to build to govern exposure on the signal’s cadence rather than the calendar’s. This issue has named the function that holds it: the accountable conversion layer between a validated signal and a structural commitment, defined by two tiers, four capabilities, and three conditions, and tested by a six-question self-diagnostic. The self-diagnostic is designed to be run on your own function. Save it, and run it against the opportunity area in your portfolio that carries the most weight right now.

References & Further Reading

This issue is the capstone of a six-issue arc. The structural arguments rest on the patterns developed across the full series, listed here in sequence as a single index.

• The Venture Operator. “Issue #7: When Nothing Changes.” Put Ideas To Work, 16 March 2026. Available at: https://www.putideastowork.com/p/when-nothing-changes

• The Venture Operator. “Issue #8: Zombie Pilots.” Put Ideas To Work, 9 April 2026. Available at: https://www.putideastowork.com/p/issue8-zombie-pilots

• The Venture Operator. “Issue #9: The Portfolio Illusion.” Put Ideas To Work, 21 April 2026. Available at: https://www.putideastowork.com/p/issue-9-the-portfolio-illusion

• The Venture Operator. “Issue #10: Resource Asymmetry.” Put Ideas To Work, 5 May 2026. Available at: https://www.putideastowork.com/p/issue-10-resource-asymmetry

• The Venture Operator. “Issue #11: When Exposure Outpaces Governance.” Put Ideas To Work, 20 May 2026. Available at: https://www.putideastowork.com/p/issue-11-when-exposure-outpaces-governance

The durability evidence referenced in the section on what makes the node the function, including the Australian corporate venture vehicles that were correctly structured and later unwound at sponsor or leadership transitions, is documented with full primary sources in the References section of Issue 10.

It is also not the most useful structural reading.

The Budget did something more consequential than introduce a CGT change. It pulled in two directions at once. The institutional venture capital layer was expanded, while the operator layer was compressed. Both moves sit inside the same package. The policy framing treats them as separate questions.

They are not. They are the same question seen from two ends.

The institutional layer, expanded.

For the first time since its introduction, the venture capital tax incentives have been substantially enlarged. From 1 July 2027, the VCLP investee asset cap rises from $250 million to $480 million. The ESVCLP investee cap rises from $50 million to $80 million. The ESVCLP tax exemption cap rises from $250 million to $420 million. The maximum ESVCLP fund size rises from $200 million to $270 million.

The ESVCLP investee cap has sat at $50 million since its inception in 2007. The VCLP investee cap has sat at $250 million since the Venture Capital Act 2002. In one Budget, the Government has materially enlarged the addressable universe for institutional venture capital deployment into Australian companies. Growth-stage businesses that previously sat above the threshold now sit inside it.

Furthermore, loss carry-back becomes permanent for companies with turnover up to $1 billion from the 1 July 2026 tax year. Loss refundability arrives for sub $10 million startups in their first two years from 1 July 2028, capped at the value of FBT and PAYG withholding on Australian wages. The R&D Tax Incentive has been restructured, with core offset rates lifting by 4.5 percentage points and the refundable offset threshold rising from $20 million in turnover to $50 million in turnover.

Overall, the Australian institutional venture capital has gained meaningful tax-architecture support that it has not had for two decades.

That support sits primarily though at the fund-vehicle level. The ESVCLP and VCLP regimes retain their existing tax treatment. Eligible returns to ESVCLP investors remain tax-exempt, and foreign limited partners in VCLPs retain flow-through with capital gains character preserved. Fund managers receiving carried interest, however, face the new CGT regime on realisation.

The institutional layer has three sub-layers: the funds gain capacity, the most tax-advantaged investor returns are preserved, and fund managers face the same CGT change on their carry as the operator cohort below.

The operator layer, compressed

From 1 July 2027, the 50% CGT discount is replaced with inflation indexation and a 30% minimum tax floor on capital gains. The change applies to all CGT assets held by individuals, trusts and partnerships, with transitional apportionment for assets held across the boundary. Further out, from 1 July 2028, discretionary trusts will be subject to a 30% minimum tax at the trustee level, with three years of rollover relief for those who choose to restructure. And, the Eligible Venture Capital Investor program closed to new applications at 7:30 p.m. on Budget night.

For founders with a near-zero cost base, exiting at the top marginal rate roughly doubles the effective tax on the gain. Standard Ledger has estimated the shift from around 23.5% under the old discount to 47% under the new regime, with Baker McKenzie’s published analysis confirming the structural impact on equity awards and start-up concession holdings. Inflation indexation provides almost no relief because there is little cost base to index. The 30% minimum floor is rarely binding for the founder cohort because their marginal rate sits above it.

For startup employees holding shares acquired under employee share schemes, the impact is structurally similar. Baker McKenzie’s published analysis is clear: for ESS-acquired shares held beyond the deferred taxing point, “the discount will no longer be available”. The startup ESS concession retains the deferral mechanism but loses the terminal benefit. The shares defer until disposal. On disposal, there is no longer a 50% discount waiting.

For angel investors, the EVCI closure removes a structural pathway that family offices and direct investors used to claim the venture capital CGT exemption without going through a limited partnership. From Budget night, that channel is shut to new applications.

For founders holding equity through discretionary family trusts, the trust changes apply in addition to the CGT change. Many Australian founders structure their holdings through family discretionary trusts at the time of company formation; the structure has long been the default practitioner advice. When the changes take affect, those structures face a 30% trustee-level minimum tax that compresses the planning value that has historically made the structure attractive.

The three-year rollover relief from 1 July 2027 is a real concession for those willing to restructure, but the restructuring itself is expensive, and the underlying CGT change still applies to the gain on disposal.

The four measures intersect at the operator layer.

Each addresses a different policy concern; when applied together, they shift the after-tax return for the cohort of people who carry the early risk in Australian venture-stage companies.

Why is this a structural issue

The Government’s framing of the CGT change is to rebalance a tax system that treats assets more generously than labour. In the venture compensation stack, that framing is structurally inverted. The 50% discount was, in operating terms, a partial recognition that startup equity is a labour substitution mechanism.

• Founders take it instead of competitive salaries.

• Senior employees take it instead of competitive cash compensation.

• Angels deploy it as personal capital with operational involvement.

The discount brought the asset-side tax treatment closer to what it would have been if the underlying compensation had been paid as wages under a 7-year deferral.

Removing it without an ESS. specific concession treats this cohort as passive investors, which they are not. They are the people whose unpaid labour and personal capital make the institutional venture deployment work in the first place.

Looking at this from the operator’s vantage, three consequences are visible.

• A senior operator considering a 40 to 60% cut in cash compensation to join a Series A startup has historically accepted that cut in exchange for equity, which carries favourable tax treatment on exit. The discount, in operating terms, was the Government’s contribution to making that trade-off rational. Removing it without an offsetting concession changes the math.

• A founder considering whether to start a venture at all now faces a lower expected payoff against the same opportunity cost of forgone competitive employment.

• An existing operator inside a startup, holding ESS shares at or near the deferred taxing point, now faces a different decision again: dispose before 1 July 2027 under the old discount, or hold through to a worse regime.

Each of these decisions rests with an individual, not with an institutional capital allocator and the budget’s framing appears to treat these as the same kind of decision that the allocator makes.

Across all three cohorts, the upside threshold that justifies the trade-off has likely risen.

• The senior operator needs either a larger equity grant or a higher exit multiple.

• The founder needs a bigger expected windfall.

• The ESS-holder facing the 1 July 2027 boundary needs the same.

Additionally, marginal ventures and modest-return investments lose potential investability at every layer of the stack simultaneously.

This is the structural shape of the Budget. The supply side of venture capital was enlarged, but the demand side, the founders, senior operators and angels who absorb the risk that lets the supply side deploy, was compressed.

The Strategic Examination, partially adopted

The Government’s venture-related measures are described in the Budget Papers as the first stage of its response to the Ambitious Australia: Strategic Examination of Research and Development final report, released in March 2026 by the panel chaired by Robyn Denholm.

The panel made 20 recommendations, with the Budget adopting the ESVCLP and VCLP cap expansions and parts of the R&D Tax Incentive restructure.

However, recommendations include the Premium Startup Stream, the quarterly R&D Tax Incentive offset payments for early-stage companies, the Early Stage Innovation Company reform, the production tax credit for advanced manufacturing, the innovation voucher program, or the superannuation mobilisation toward venture capital.

The panel warned against partial adoption. The report’s framing was that the package operates as an integrated whole and that adopting only parts will produce “incremental changes and band-aid solutions.” The Budget delivered the supply-side recommendations and left most of the demand-side ones for later.

The venture-specific argument sits inside a broader policy direction as the CGT discount removal applies to all CGT assets, not just venture equity. The discretionary trust changes apply across all discretionary trusts, not just founder-held structures. The broader implications of this are beyond the scope of this article, but the Government is using tax instruments to rebalance the treatment of asset income relative to labour income across the system. In the venture compensation stack, one domain where that rebalancing meets a structural mismatch is because the asset-labour distinction breaks down inside venture. Owner-operated small business equity, family enterprise succession, and senior employee equity compensation outside venture sit in similar territory. Each absorbs the policy with different specific consequences.

The pattern is wider than venture.

Australia’s Economic Accelerator program shows the same pattern of disaggregation at a smaller scale. Established in 2022 to bridge the research commercialisation gap, wound down in the same Budget. The funding has been redirected to CSIRO sustainability and to a new National Resilience and Science Council. The architecture survives in a different form, but the funding does not.

Institutional supports are reshaped while the underlying commitments thin.

The consultation is the test.

The consultation is no longer in the future.

Two formal consultation sessions have already occurred with the Tech Council of Australia and the Australian Investment Council. Speaking on ABC Insiders on 17 May, Treasurer Chalmers explicitly stated that the Government recognises that startups and venture capital have different cost bases, hardening the language from the initial Budget framing.

The Productivity Commission has separately added institutional weight, with chair Danielle Wood publicly flagging that the CGT reforms risk unintended consequences for the startup sector. The consultation itself and the speed with which the Government moved to acknowledge the sector’s circumstances within 24 hours of Budget night are genuine recognition of the demand side. Whether the recognition produces a structurally adequate response is the question that has not yet been answered.

The Australian Financial Review has reported that the Government is reluctant to create carve-outs from the broader CGT reform but is considering changes to the cost-base calculation for startup founders and investors. These are not equivalent positions. Retaining the discount is one thing. Adjusting the cost-base calculation is a much narrower concession that reaches founders with structurally low cost bases but does not reach ESS paid employees on disposal of vested shares, does not reach angels who used EVCI, and does not reach discretionary trust holders.

Multiple groups inside the Australian startup ecosystem are organising around the consultation. The Tech Council of Australia is one voice, with its CEO, Kate Cornick, stating publicly that there is “work to do to ensure Australia’s startup community doesn’t become collateral damage” from the proposed CGT changes. Founders and VC networks are mobilising separately, concerned that the larger institutional voice will not represent the smaller end of the sector.

On 20 May, a group of Australian founders under 40, including Linktree co-founder Alex Zaccaria, me&u CEO Kim Teo, Bastion founder Jack Watts, and Cyber Revolution co-founder Adam Hewitt, launched an open letter to Prime Minister Albanese, framing the CGT changes as an “aspiration ambush” that reaches beyond tech startups to every growing business in Australia.

The consultation outcome determines whether the two directions in the Budget align or remain opposed. A meaningful concession that reaches ESS holders, angels, and founders would narrow the asymmetry. A narrow technical fix, in the cost-base form the Government appears to favour, would not. Expanded institutional capital would then flow into a venture economy where people taking the risk on the ground keep materially less of the upside than before.

The consultation is active, the recognition is real, and the structural question is whether the response treats the asymmetry as a single problem or as a series of separate technical concerns.

What this leaves operators with

The Budget did real work on the supply side of Australian venture capital. The ESVCLP and VCLP cap lifts will be felt over the next two cycles. Loss carry-back will help operationally resilient companies. Loss of refundability will subsidise the earliest stage of Australian PAYG hiring in young startups.

What it did not do was acknowledge that the operator layer it is compressing is the one that carries the risk, allowing the institutional layer to deploy. Australian venture policy continues to be delivered through tax instruments rather than through the underlying decision-rights architecture.

Tax instruments can enlarge or shrink the financial environment in which ventures operate. They cannot, on their own, ensure that the people building those ventures retain enough of the upside to keep building them.

For operators, the current position is to engage in the consultation directly. Not just through the Tech Council or the institutional VC associations. Through founder and senior-operator voices specifically, because the cost-base adjustment route the Government appears to be considering does not by itself reach the cohort most exposed.

The consultation outcome matters, but the Budget sits inside a venture environment that was already structurally constrained.

Growth capital at Series B and beyond remains thin enough that Australian companies still consider relocating to access US institutional rounds, regardless of how generous the ESVCLP expansion now reads.

Senior operator pipelines into venture-stage roles were already shallow before the Budget compressed the equity economics that made those moves rational.

Australian venture exits remain dominated by trade sales to US acquirers rather than domestic IPOs, and the 1 July 2027 CGT boundary now adds tax-timing pressure on top of that pre-existing structural pull.

The absence of a Chapter 11 equivalent, raised already by David Burt on LinkedIn, sits entirely outside the Budget and remains a constraint the Government has not engaged with.

The Budget reshapes some of these constraints, worsens one of them specifically, and leaves most untouched. Reading the Budget as a whole environment, rather than as a single variable within it, risks overstating what the consultation can achieve and understating what remains structurally unresolved.

The two directions can still be brought into alignment.

The package, as it stands, does not do that. The institutional layer expanded. The operator layer is compressed. If they remain opposed, the consequences compound past the consultation moment: founder formation thins, senior operators migrate offshore, and the institutional layer’s expanded envelope deploys into a venture economy that has been narrowed at the layer that produces it.

More money to invest in a thinner stack of high-conviction bets is not the venture economy Australia needs.

Written 25 May 2026. The consultation on startup treatment under the new CGT regime is active and specifics may continue to move. This article reflects the structural state of the Budget package and the consultation as of the date of writing."

References & Further Reading

• Commonwealth of Australia. Budget Paper No. 2: Budget Measures 2026-27. Delivered 12 May 2026. https://budget.gov.au/content/bp2/

• Commonwealth of Australia. Budget 2026-27: Tax reform. Theme page summary of CGT, negative gearing, discretionary trust, and venture capital measures. https://budget.gov.au/content/04-tax-reform.htm

• Australian Government, Department of Industry, Science and Resources. Ambitious Australia: Strategic Examination of Research and Development. Final Report. Released 17 March 2026. Panel chaired by Robyn Denholm, with Emeritus Professor Ian Chubb AC, Winthrop Professor Fiona Wood AO, and Dr Kate Cornick.

• Treasury Ministers. Press conference, Cabramatta, Sydney, by Treasurer Jim Chalmers. 13 May 2026. Transcript covering ongoing consultation on CGT implementation for the start-up sector. https://ministers.treasury.gov.au/ministers/jim-chalmers-2022/transcripts/press-conference-cabramatta-sydney

• Treasurer Jim Chalmers, ABC Insiders interview, 17 May 2026. Public statement that the Government recognises startups and venture capital have a different cost-base calculation. Two formal consultations confirmed with Tech Council of Australia and Australian Investment Council.

• Baker McKenzie. Australia: Budget Bites — Equity Awards. May 2026. Analysis of CGT changes and impact on ESS-acquired shares, including start-up concession holdings. https://www.bakermckenzie.com/en/insight/publications/2026/05/australian-federal-budget-2026-2027

• Baker McKenzie. Australia: Budget Bites — CGT Discount and Negative Gearing. May 2026. https://www.bakermckenzie.com/en/insight/publications/2026/05/australia-budget-bites-cgt-discount-and-negative-gearing

• Standard Ledger. Discretionary Trusts for Australian Startups After the 2026 Budget: Should You Still Use One? May 2026. Practitioner analysis of trust restructuring decisions for founders. https://www.standardledger.co/article/discretionary-trusts-for-australian-startups-after-the-2026-budget-should-you-still-use-one

• Gilbert + Tobin (GTLaw). The new rules of the game: what the 2026-27 Federal Budget means for private capital in Australia. May 2026. Worked example of the CGT regime impact on private equity and venture capital returns. https://www.gtlaw.com.au/insights/the-new-rules-of-the-game-what-the-202627-federal-budget-means-for-private-capital-in-australia

• Corrs Chambers Westgarth. Australian Federal Budget 2026-27: Corporate Tax Measures. May 2026. https://www.corrs.com.au/insights/australian-federal-budget-2026-27-corporate-tax-measures

• Bloomberg. Australia Capital Gains Tax Reform Risks Startups, PC Chief Says. 13 May 2026. Reports Productivity Commission chair Danielle Wood publicly flagging that the CGT reforms risk unintended consequences for the startup sector.

• Capital Brief. Jim Chalmers ‘recognises’ startups and VC need special consideration amid CGT change. 18 May 2026. https://www.capitalbrief.com/briefing/jim-chalmers-recognises-startups-and-vcs-need-special-consideration-over-cgt-changes-90244feb-b086-4614-af95-376156ad29b3/

• Capital Brief. Startup founders scramble for a seat at Chalmers’ table for talks over CGT carveout. May 2026. https://www.capitalbrief.com/article/startup-founders-scramble-for-a-seat-at-chalmers-table-for-talks-over-cgt-carveout-91b09dcd-b31d-4c7f-9788-a1d7c35fad0d/

• SmartCompany. Labor considers startup CGT changes after founder backlash. May 2026. https://www.smartcompany.com.au/federal-budget-2026/labor-startup-cgt-tweaks-founder-backlash/

• Startup Daily. Budget 2026: Startup sector praises R&D reforms but warns on CGT overhaul. 13 May 2026. https://www.startupdaily.net/topic/politics-news-analysis/budget-2026-startup-sector-reaction-cgt-rd-tax-reforms/

• Startup Daily. Government signals rethink on startup CGT rules amid backlash. May 2026. https://www.startupdaily.net/topic/politics-news-analysis/government-signals-rethink-on-startup-cgt-rules-amid-backlash/

• Startup Daily. Why Chalmers’ housing fix is about to break the Australian startup economy. Opinion piece predating the Budget; provides early framing of the founder-zero-cost-base argument. https://www.startupdaily.net/advice/opinion/why-chalmers-housing-fix-is-about-to-break-the-australian-startup-economy/

• InnovationAus. Chalmers works towards CGT fix for startups and VCs. May 2026. Coverage of the consultation moment and the Ambitious Australia adoption gap. https://www.innovationaus.com/chalmers-works-towards-cgt-fix-for-startups-and-vcs/

• Airtree Ventures. What Aussie startups need to know about the Delaware Flip. 2026. Context on the structural pattern of Australian startups relocating to access US capital. https://www.airtree.vc/open-source-vc/aussie-startups-delaware-flip-up

• MA Financial. Investment Outlook 2026, Private Equity and Venture Capital. February 2026. Context on Australian IPO and exit activity continuing to lag the US through 2025. https://mafinancial.com/insights/2026-investment-outlook/private-equity-and-venture-capital

• William Buck. Dealmaking Insights Report 2026. April 2026. Foreign buyer share of Australian transactions at decade-highs. https://williambuck.com/tools/dealmaking-insights-report-2026/

• David Burt. LinkedIn post raising the case for a US-style Chapter 11 process for Australian startups. May 2026. https://www.linkedin.com/posts/david-burt-_startups-share-7461989438043332608-jEUQ/

• Tech Council of Australia, 12 May 2026, Media Release - Tech Council welcomes nod to RD&I in Federal Budget, concerned with CGT changes, https://techcouncil.com.au/newsroom/media-release-tech-council-welcomes-nod-to-rdi-in-federal-budget-concerned-with-cgt-changes/

This issue is Part 5 of a 6 issue arc on Corporate Venturing Under Constraint.

A corporate venture validates. The market signal is clear. Early commercial metrics move in the right direction. The team is engaged. The sponsor is talking about it in executive forums. And then, somewhere between the fourth and the seventh month after validation, momentum stalls.

The team has not changed. The market has not shifted. The product has not failed. The venture has done what it was set up to do. It has produced a signal that warrants commitment. And yet the commitment does not come. What looks like a venture losing momentum is most often a governance system that cannot keep pace with the cadence the portfolio’s exposure now requires.

A corporate innovation portfolio is rarely a single venture. It is a collection of internal builds, partnerships, minority investments, spin-outs, and acqui-hires, each carrying different exposure profiles and changing at different cadences. The single venture that stalls is the visible failure. The portfolio held inside the same governance system is the structural condition.

A note on scope. The argument here addresses corporate innovation portfolios that are actually executing innovation through one of the five vehicle types named above. Functions that wear an innovation label but operate as technology programmes, R&D rebrands, or transformation initiatives are a different organisational pattern.

The two rhythms operating at odds with each other.

An enterprise and its portfolio run on different rhythms, and many corporate governance systems are built to operate on only one of them.

The corporation runs on a calendar rhythm: quarterly reporting cycles, annual budget rounds, half-year reviews. Board cadence aligns with the listed company calendar, and capital allocation occurs in scheduled rounds. Decision rights are exercised at convened forums. Risk is assessed at periodic intervals. The rhythm is metronomic, and the instruments of governance are calibrated to it. They were built that way for good reason. A mature business produces predictable outputs, and the governance system that holds it can run on predictable cycles.

The portfolio runs on a different rhythm. Its exposure changes when signals change, and each vehicle in the portfolio carries a different exposure profile.

• Internal builds carry exposure that compounds slowly and accelerates around validation. The cadence shifts from quarterly-acceptable to weekly-critical at the point the venture proves commercial signal.

• Spin-outs carry exposure that concentrates around separation events. Decision rights, capital structure, and IP arrangements all become exposure-rich at moments when the parent’s governance system was not designed to handle on short notice.

• Minority investments and corporate venture capital positions carry exposure driven by the portfolio companies and the broader funding environment. Follow-on rounds, down rounds, and bridge financings happen on the cadence of external markets. The parent’s standing capital review cycle cannot respond to the cadence external rounds require.

• Partnerships carry exposure from counterparty behaviour. A partner reorganisation, a strategic shift, or a key personnel change can transform the partnership’s risk profile within a week. The governance instruments built for partnership review run on quarterly cycles at best.

• Acqui-hires carry exposure in the integration window. Talent retention, integration scope, and IP harvesting decisions are high-exposure decisions for the first eighteen months. The parent’s standing M&A governance is built for the deal, not necessarily for the eighteen months after it.

Five vehicles.

Five exposure rhythms.

One governance system that runs on the corporation’s calendar.

When a corporate innovation portfolio is held within the parent’s governance system, every vehicle’s exposure rhythm must align with the parent’s calendar rhythm. The mismatch is not visible in early exploration because exposure is low and the governance system has time to respond. It becomes visible the moment any of the five vehicles generates exposure. Validation produces it for internal builds. Counterparty change produces it for partnerships. A follow-on round produces it for CVC positions. The trigger varies. The structural failure is the same, but exposure does not wait.

The enterprise runs on the calendar. The portfolio runs on the signal. Governance must run on the signal.

Three structural causes

Cause 1: Instruments calibrated to the parent’s reporting cycle

The first layer is the instruments themselves. The templates, the review forums, the approval forms, the risk registers, the business case formats. These are designed for steady-state business units that produce predictable data on predictable cycles.

When a venture is asked to operate within these instruments, it is expected to produce data that does not yet exist, at a cadence that does not match the rate at which the venture’s reality actually changes. The quarterly review requires an internal build to show variance against the forecast. The build has not been alive long enough for the forecast to be meaningful. The annual capital review asks a CVC team for a three-year fund return projection. The fund’s strongest current evidence is a follow-on round that closed last week. The partnership review asks for milestone progress against a contract written eighteen months ago. The contract no longer reflects either party’s reality. The instruments produce confidence in domains where the portfolio has none, and silence in the domains where the portfolio has a signal.

The governance system ends up reading a version of the portfolio that does not match the actual portfolio.

Cause 2: Decision rights held at the parent’s forums

Even if the instruments could be modified to carry venture-grade evidence, the authority to act on that evidence sits at forums that meet on the parent’s cadence. The quarterly executive committee, monthly steering group, half-yearly capital allocation board, or the annual strategic review.

A portfolio’s exposure can change in a week. The next forum that holds the relevant decision authority is six weeks away. By the time the decision is made, the exposure has shifted again, and the decision is responding to a state that no longer exists.

BCG’s 2024 survey of ~1,000 senior corporate executives on large-scale technology programmes found that two-thirds of those programmes fail to deliver on time, budget, or scope, with respondents identifying governance models that fail to empower teams to act between forums as one of the most common causes. The finding is not specific to innovation portfolios, but the mechanism is identical across them. When the authority to act on emerging conditions resides exclusively in scheduled forums, execution decays in the gap between them.

At portfolio scale, every vehicle’s exposure-driven decision has to wait.

• A CVC follow-on opportunity that closes in nine days is held until the next capital committee.

• A partnership that needs scope renegotiation after a counterparty change waits for the next review cycle.

• An internal build that has been validated and now requires a step-change in capital and authority waits for the annual round.

The decision-makers are not the failure. The cadence at which they can convene is.

Cause 3: Capital allocation moves through processes designed for steady-state deployment

The slowest layer can often be capital. Even if the instruments carried the right evidence and the forums met on the right cadence, the capital itself cannot move at portfolio speed. Reallocations between cost centres require business case redevelopment. Off-cycle commitments need executive sponsorship that itself takes time to assemble. Movement between portfolio positions runs through finance processes calibrated for predictability, not responsiveness.

This is where exposure-responsive moves commonly fall short. A signal strengthens on an internal build. The diagnosis is correct. The instruments record it. The forum is willing to act. And the capital cannot be moved within the cadence the signal requires.

A partnership renegotiation becomes time-critical after a counterparty restructure. The capital committee meets in eight weeks. The window in which the renegotiation has leverage closes in twelve days. The position was lost not because the parent did not want it, but because the parent could not act on it in time.

The empirical picture on CVC longevity has two parts. Song Ma’s research, published in The Review of Financial Studies in 2020 and drawing on a long historical dataset, documented that the median life of a corporate venture capital division was approximately 4 years, with a mean of 6 years, compared with independent venture funds that run on 10- to 12-year cycles. More recent industry data from Global Corporate Venturing’s 2024 review suggests CVC longevity has been improving, with more than 60 per cent of tracked CVC units surviving beyond their first three years. The headline numbers have shifted; however, the mechanism behind closure has not.

The CVC units that closed in 2024 did so for reasons that confirm rather than contradict the original finding. Industry analysis, completed by Global Corporate Venturing’s 2024 review, of those closures is attributed to parent-company restructuring following share-price pressure, parent-company cost-cutting drives, takeover defence, and breakdowns in the relationship between the CVC and the parent’s core business. In each documented case, the CVC’s own portfolio performance was not the trigger. The triggers were parent-company dynamics operating on the parent’s calendar. Several units that had closed had been performing strongly by external rankings at the time of closure.

So the pattern holds, whether the median life is four years or longer, the vehicle is closed when the parent shifts, not when the venture work is done.

Capital allocated to corporate innovation is structurally short-tenure relative to the work it is being asked to do. Internal builds that require five-year horizons sit within governance frameworks that revisit allocation annually. CVC positions designed for ten-year cycles operate within parent vehicles whose continuation depends on the parent’s strategic mood. Acqui-hire integration windows of eighteen months sit within M&A governance that resets quarterly.

The willingness is there, but plumbing can be uplifted.

The three layers have a compounding effect.

• Instrument failure produces a governance system that is blind to exposure.

• A failure in decision rights results in a governance system that is slow to respond to exposure.

• Capital failure produces a governance system that is structurally incapable of acting on exposure.

Where all three are present, the governance system observes the portfolio rather than governs it.

Why the challenge persists

The structural mismatch has been visible to senior corporate operators for at least a decade. BCG’s 2024 study explicitly notes that 10 years had passed since its 2015 large-scale study of the same pattern, with no measurable improvement over that period. The question is not whether the mismatch exists. The question is why corporations have not corrected it. There are two likely conditions that can explain the persistence.

The first is short-termism. Exposure-cadence governance is built to act on signals that pay out over timeframes longer than the parent can wait. A commit-harder move in response to a strengthening signal might require capital today and produce returns over three years. The capital is real but the return is unprovable. The governance system is held by people whose own incentives run on shorter cycles than the venture’s payout cycle. Patience is a cost the company has not been built to absorb, and exposure-responsive governance requires patience the parent lacks. The CVC closures 2024 take this shape. CVCs close when the parent comes under cost or strategic pressure, not when the CVC has completed its work. The vehicle’s calendar is set by the parents’ circumstances, not by the venture’s logic.

The second is the official permission. The instruments to act off-cycle exist nominally in many corporations. Board chairs can pull forward executive forums. CFOs can authorise off-cycle capital moves. Executives can order unscheduled portfolio reviews. They are also institutionally rationed. Using them off-cycle marks the user as undisciplined. Calling an executive committee six weeks in advance reads as poor planning. Moving capital outside the budget round reads as failure to forecast, triggering a portfolio review without a scheduled trigger reads as panic.

The CFO who can authorise an off-cycle capital move and does not is behaving rationally. The system is producing the behaviour it is designed to produce.

The governance system is structurally capable of exposure-cadence governance and institutionally constrained against it. The instruments are present. The willingness to use them is not. What appears to be cultural reluctance is, in fact, a rational response to institutional incentives. The individual operator bears the cost of using exposure-responsive governance. The portfolio bears the cost of not using it.

These two conditions do not cause the mismatch, but are part of the environment that makes it persistent.

Surfacing the governance-exposure mismatch

The first practical question is whether the mismatch exists in any given innovation portfolio and, if so, where it is concentrated. The diagnostic that follows surfaces the key items to consider when answering it. It can be run against a single venture or applied across a portfolio. For a single venture, each question tests one dimension of governance cadence for that venture. For a portfolio, the same questions are answered across all vehicles held, and the read is the aggregate. A portfolio that fails the diagnostic on internal builds but passes on CVC positions reveals where the structural mismatch is concentrated.

A governance system can be elegant on paper and structurally late in practice; this diagnostic seeks to test the latter.

At a high level.

Six ‘yes’ answers could indicate a governance system operating at the exposure cadence. This is rare and worth examining for what is enabling it.

Three to five yes answers indicate a partial match. Governance responds to some exposure changes but not all of them. Established corporate innovation portfolios commonly sit here. The system works for the exposure changes it has been designed to anticipate, but fails for those it has not.

Two or fewer yes answers may indicate a structural mismatch. The parent’s calendar is governing the portfolio, not its own exposure. From this position, four predictable failure modes could follow.

• Innovation theatre, where governance instruments record activity because activity is the only signal they can read. https://www.putideastowork.com/p/when-nothing-changes

• Zombie pilots, where projects survive because the stopping authority cannot be exercised between forums. https://www.putideastowork.com/p/issue8-zombie-pilots

• Portfolio drift, where reallocation cannot keep pace with the required cadence. https://www.putideastowork.com/p/issue-9-the-portfolio-illusion

• Resource asymmetry, where capital flows lag signals of change. https://www.putideastowork.com/p/issue-10-resource-asymmetry

Looking for the exemption

Four arguments are commonly raised against the cadence-mismatch thesis, each of which carries some legitimacy. The size argument reflects real questions about portfolio scale. The stage argument reflects real concerns about premature formalisation. The separate-track argument reflects a structural response many corporations have actually made. The feature-not-bug argument reflects a financial discipline view that slow capital protects against overcommitment. The question is whether each one holds when tested against the rhythm at which the portfolio’s exposure actually moves.

“We have a separate governance track for innovation.”

The most common exemption. The corporation has designed an innovation committee, an innovation board, and an innovation steering group. The structure is new. The reader points to it as evidence that the problem has been solved.

The structure is new. The cadence is the same. A separate governance track that meets quarterly is still quarterly. The instrument was duplicated. The rhythm was not changed. If the innovation board meets every twelve weeks, exposure-cadence governance is still impossible. The track is decorative.

“Our portfolio is too small to need this level of discipline.”

The escape via size. The reader argues that exposure-cadence governance is for portfolios of scale. Their portfolio has three positions. The complexity does not warrant the discipline.

Size does not reduce the requirement. It concentrates it. A portfolio with three positions has more exposure per position than a portfolio with thirty. The cost of governance lag on a single position is higher, not lower, when the portfolio is small. The smaller the portfolio, the less it can afford the lag.

“We are at an early stage. Formal governance would slow us down.”

The escape via stage. The reader argues that exposure-cadence governance is for mature portfolios. Theirs is still exploratory. Formality would suppress the experimentation the portfolio currently needs.

Governance maturity is not a function of stage. It is a function of exposure. An early-stage internal build with a regulatory commitment carries real exposure. A first CVC position in a fast-moving sector carries real exposure. A partnership that signs a partnership agreement with a counterparty undergoing its own structural change carries real exposure. The exposure does not wait for the portfolio to feel mature enough to govern it. The stage is calendar-driven. Exposure is signal-driven. The conflation between the two is the trap.

“Slow capital is a feature, not a bug. It forces conviction before commitment.”

Sometimes in place for a rational reason initially, but a somewhat sophisticated exemption, and the one held most strongly across senior corporate leadership. The argument is that the parents’ slower capital cadence is a deliberate check on venture enthusiasm. Corporate ventures fail at high rates. Slowing capital movement forces the venture team to demonstrate conviction with evidence rather than urgency. The lag is in the governance.

The financial discipline tradition that underwrites this argument is one of the most valuable institutional safeguards corporations have. The structural argument here is not that the discipline is wrong. It is that the discipline is being applied to a cost it was not designed to address.

This argument has empirical weight on financial grounds and is worth taking seriously. A meta-analysis by Haslanger, Lehmann, and Seitz published in The Journal of Technology Transfer in 2023, synthesising 32 studies and more than 105,000 observations, found no significant relationship between CVC investments and financial performance. The CFO who is sceptical of CVC financial returns is reading the empirical literature correctly.

The same meta-analysis, however, also found that CVC investments are positively associated with strategic performance outcomes, such as patent citations and product introductions. The strategic value is real and measurable. The financial return is not. Which means the cost of governance lag in a CVC portfolio is not paid in lost financial returns. It is paid for a lost strategic position. The strategic position is the harder cost to see, because it does not appear on the next quarterly report. It eventually appears in a competitor’s product launch.

The same structure applies across the other four vehicle types. Slowing capital movement on an internal build does not preserve financial discipline. It surrenders the market window. Slowing down decisions on a partnership does not produce better counterparty negotiation. It cedes terms to the partner’s faster process. Slowing reallocation on an acqui-hire integration does not protect against integration risk. It guarantees talent attrition during the period when retention is most fragile.

The conviction-before-commitment argument confuses two different costs. Slow capital protects the parent from financial overcommitment. It does not protect the venture portfolio from strategic underperformance. The two are different decisions, and the governance system that mistakes one for the other is governing on the wrong dimension.

What to consider, if relevant.

The structural answer to the governance-cadence mismatch is a capability many corporations do not currently hold in the form the exposure cadence requires. That capability will take time to build, and it is the subject of the next issue. But the portfolio cannot wait for it. Four moves can be considered at the portfolio’s existing governance level, without redesigning standing instruments, that will close part of the gap.

These moves assume the portfolio is genuinely pursuing innovation and venture work that the company depends on. Where it is not, the structural pressure to make them does not exist.

Define off-cycle review triggers in advance. For each vehicle in the portfolio, name the conditions that would warrant pulling governance forward. A regulatory shift on a partnership. A down-round on a CVC position. A churn signal on an internal build’s pilot customers. A counterparty change on an acqui-hire integration. The point is not the list. The point is that the conditions are written down before they fire.

Pre-named triggers do two things the institutional system cannot otherwise accommodate. They convert off-cycle actions from individual escalation into institutional protocol, shifting the cost of acting from the individual operator to the system. The CFO who acts on a pre-named trigger is following the protocol, not breaching it. They also make the off-cycle move auditable in retrospect. The corporation that asks why an off-cycle review was triggered can be shown the document. Institutional permission constraints commonly dissolve when the action has a paper trail that predates the event.

The cost of not making this move: every off-cycle review depends on someone willing to spend personal capital to call it. In many quarters, no one is.

Name a single decision-maker between forums for each vehicle. Stop authority, scope-narrowing authority, and re-commitment authority should rest with a named person who does not have to wait for the next forum to act. This is not about creating a new role. It is about resolving an ambiguity left open by the existing governance structure.

In many corporate innovation portfolios, between-forum authority is held collectively, meaning no one person holds it. The portfolio lead can recommend a stop. The committee chair can endorse it. The capital committee has to confirm it. The actual decision floats between three people, none of whom has unilateral authority and all of whom can defer to the next meeting. Decisions accumulate in the gap. Some never resurface. Naming a single person with explicit authority converts a diffuse decision-rights problem into a clear escalation pathway. The named person does not need new powers; they need the authority they already have to be documented and unambiguous.

The cost of not making this move: between-forum decisions that should take minutes take six weeks, and many never get formally taken at all.

Pre-authorise reallocation thresholds with the capital committee. Have the conversation with the CFO or the capital committee chair about the size of reallocation that can be moved between portfolio positions without a new business case. Five hundred thousand. Two million. Whatever number the corporation can absorb without it triggering a full review. The number matters less than the threshold’s existence.

Corporations often already have an informal version of this. The CFO who quietly approves a small reallocation between two portfolio positions is exercising the discretion the role already carries. The problem is that discretion is rationed by institutional permission, which means it is used reluctantly and only when the operator is confident the move will not be questioned. Formalising the threshold converts ambiguous discretion into protocol. Protocol is cheap to use. Discretion is expensive. The same move that costs the CFO personal capital under the informal arrangement costs nothing under a documented threshold.

The cost of not making this move: every reallocation, however small, has to wait for the next capital committee, which compounds capital paralysis across the portfolio.

Audit the highest-exposure vehicle against the diagnostic before the next board cycle. Run the six questions against the vehicle in the portfolio carrying the most exposure right now. Not the whole portfolio. The single position with the highest exposure.

The reason to start narrow is structural. A portfolio-wide audit produces a long list of governance gaps, none of which has institutional urgency. A single-vehicle audit of the highest-exposure position produces a short list of urgent governance gaps. The conversation with the board changes from “we have governance debt across the portfolio” to “this specific position has these specific governance gaps before its next exposure event.” The first conversation is a strategy paper. The second is a decision the board has to make.

The cost of not making this move: the governance gap that will most likely lead to the next failure remains invisible until it blows up.

These are not the structural answers. The structural answer may require a capability that the corporation currently lacks or does not have the risk appetite for. But the cost of waiting for the structural answer while ignoring the operational moves is high. Each board cycle that passes with the mismatch in place compounds the cost.

• A position is lost.

• A pilot zombifies.

• A signal goes unread.

The losses are not catastrophic in any single cycle.

They are continuous, and they accumulate.

If the parent’s standing instruments are designed for the calendar rhythm, and the failure modes traced above are downstream of that fact, then the parent’s standing capabilities cannot be the answer. The corporation’s existing functions are built for the rhythm the corporation runs on. They are structurally incapable of carrying the exposure-cadence work the portfolio requires. The instruments are not adequate. The forums do not meet often enough. The capital does not move fast enough. And no individual operator, however skilled, can carry out this work as a side responsibility alongside a role designed for steady-state oversight.

The capability needed is something the corporation has to build. What it looks like, how it sits within the corporate, and what discipline it requires are the subjects of what follows.

Closing out.

Governance does not mature with age. It matures with exposure.

References & Further Reading

• Ma, Song. “The Life Cycle of Corporate Venture Capital.” The Review of Financial Studies, Volume 33, Issue 1, January 2020, pages 358-394. Summary posted on the Harvard Law School Forum on Corporate Governance, 15 April 2019. Available at: https://corpgov.law.harvard.edu/2019/04/15/the-life-cycle-of-corporate-venture-capital/

• Haslanger, Patrick, Erik E. Lehmann und Nikolaus Seitz. “The Performance Effects of Corporate Venture Capital: A Meta-Analysis.” The Journal of Technology Transfer, Volume 48, Issue 6, December 2023, pages 2132-2160. Open access. Available at: https://link.springer.com/article/10.1007/s10961-022-09954-w

• Hurford, Stephen. “These CVC Units Didn’t Make It to 2025, and the Reasons Aren’t Always Easy to Understand.” Global Corporate Venturing, 19 December 2024. Available at: https://globalventuring.com/corporate/cvc-units-closed-2024/

• Grebe, Michael, Vanessa Lyon, Michael Harnisch, Abhik Chatterjee, Steven Alexander Kok and Jon Brock. “Most Large-Scale Tech Programs Fail, Here’s How to Succeed.” Boston Consulting Group, 13 November 2024. Available at: https://www.bcg.com/publications/2024/most-large-scale-tech-programs-fail-how-to-succeed

• Brock, Jon, Sesh Iyer, and Tamim Saleh. “Large-Scale IT Projects: From Nightmare to Value Creation.” Boston Consulting Group, 20 May 2015. Available at: https://www.bcg.com/publications/2015/technology-business-transformation-technology-organization-large-scale-it-projects

What was actually withdrawn was not $800 million. As the announcement states, the existing cohort will have funding towards their individual outcomes, whether successful or not. What was withdrawn was the stability of a stage-gated commercialisation signal that applicants, industry partners, and university research offices had been planning against. Stage-gated funding from proof-of-concept to proof-of-scale exists in every credible deep-tech system globally because the risk profile and time horizon do not always correspond to the needs of private capital. That is a structural market function, not market failure. When the signal goes, the planning architecture built against it goes with it.

Two questions follow from that. Was the ending appropriately governed? And is the system AEA operated inside actually designed to convert funding into commercial outcomes at all?

The ecosystem conversation is mostly running on the first. The second is the one that matters more.

A question on governance.

Innovation and commercialisation are a long game. The final outcome of a given venture may occur long after the initialisation of a commercialisation program.

Ending a research commercialisation program can be a defensible call as portfolios concentrate, priorities shift, and new mechanisms supersede old ones. The question is not whether programs should ever end. It is whether the ending is governed by architecture or by discretion.

The contrast with comparable systems is what makes this sharp.

The United States

The United States runs the Small Business Innovation Research program, established in 1982 and operating across eight presidents and both parties. The SBIR is not discretionary as it is a statutory set-aside of 3.2% of any federal agency’s extramural R&D budget above $100 million. It is also codified at 15 U.S.C. 638, and eleven federal agencies are obligated to run SBIR programs under that set-aside. The program has sunset provisions and requires periodic legislative reauthorisation.

Its authority lapsed on 30 September 2025, and the program sat in legal limbo for five months, with companies burning through reserves and tech transfer offices pausing negotiations. Then, in March, Congress passed bipartisan reauthorisation, which was signed into law in April, extending the program through fiscal year 2031.

The point is not that SBIR is untouchable. It can fall over like all programs, but the point is how it falls over. It falls over through a visible legislative process, with public debate, against a structural architecture that resumes operation when authority is restored. The funding is not subject to discretion because the set-aside is in statute.

The European Union and the United Kingdom

The European Innovation Council sits within Horizon Europe, established under Articles 173 and 182 of the Treaty on the Functioning of the European Union, and operates within the EU’s Multiannual Financial Framework.

Innovate UK is a statutory council within UK Research and Innovation, established under the Higher Education and Research Act 2017. UKRI operates at arm’s length from government as a non-departmental public body. Both have funding levels that flex with budget cycles, but neither has institutions that can be unwound by executive decision, and neither can have its core funding removed without a legislative or budgetary process running its course.

The architecture sits in primary legislation. The funding mechanism is built into the architecture.

Australia

Australia’s Economic Accelerator had a different structure. The program was created by the Higher Education Support Amendment (Australia’s Economic Accelerator) Act 2023, which established a statutorily mandated Advisory Board, a research commercialisation strategy, and an annual investment plan, all of which are prescribed under Division 42 of HESA.

What it lacked was a statutory funding set-aside. The $1.6 billion ten-year envelope was an administrative commitment, not a legislative floor. Funding could be withdrawn by executive decision because the envelope was never anchored in statute. The Advisory Board, the strategy, and the investment plan remain in place. The funding does not. The program’s architecture presumability was built into the legislation. The architecture for continued funding was not.

The structural read is not that AEA should have continued. It is that AEA could only ever end this way, through the funding mechanism, because it was never anchored in legislation. As a result, the program survives, but the funding does not.

A harder question.

The harder question is whether additional funding within the current architecture yields more commercialisation outcomes.

The international comparisons have something Australia does not, and it is not more money; they have system coordination.

• The SBIR is structurally coupled to federal procurement, with the agencies that fund Phase I and II frequently serving as buyers in Phase III.

• The EIC Accelerator pairs grants and equity with the Business Acceleration Services layer to support regulatory navigation and investor access.

• Innovate UK sits within UKRI alongside the seven research councils and Research England, with a coordinated regulatory architecture across the Medicines and Healthcare Products Regulatory Agency, the British Standards Institution, and the Catapult network.

In each system, funding is one instrument inside a coordinated commercialisation architecture.

Australia funds, but the rest of the architecture is partial or absent. AEA was a funding instrument inserted into a system that was not designed to receive it efficiently.

There is data that paints a contrasting picture, worth sharing directly. The widely cited framing that Australia ranks last in the OECD for industry-research collaboration draws on OECD data series going back to the mid-2010s and has been repeated in ecosystem commentary for nearly a decade. More recent Australian Government tracking suggests improvements in adjacent metrics, with Australia ranking 7th out of 39 in the 2023 OECD innovation survey on the share of innovation-active businesses.

All in all, signalling that the trajectory for Australia is not flat.

The numbers that hold across both readings are the input-output gap and the cluster picture.

Australia ranks 16th globally on innovation inputs and 27th on innovation outputs in the 2025 WIPO Index, with the gap most pronounced in Knowledge and technology outputs, where Australia ranks 29th. The 2025 WIPO cluster ranking shows Australia with two clusters in the global top 100, down from three in 2024. Strong inputs, weaker outputs, particularly in knowledge and technology commercialisation, narrowing cluster footprint.

The pattern is consistent regardless of which collaboration metric is preferred.

The point is not that Australia is uniquely broken, but even with improving collaboration metrics and a respectable overall innovation ranking, the conversion of research investment to commercial output continues to lag. Funding is not the only constraint, which indicates that the surrounding system architecture and market appetite also need attention.

Signals do not execute themselves; systems do. The kill-switch frame that emerged from the corporate venture capital wind-downs of the last 24 months applies here without modification. A program that sits inside the wrong system architecture is fragile by default and can be unwound by the next budget cycle, the next leadership shift, or the next reprioritisation.

Having a kill switch should not be considered a flaw in the program. It is the system letting the program be the only thing carrying the load. Consideration of building a durable architecture, and funding levels that can flex without the system or the program collapsing. Without architecture, the program becomes the architecture, and the architecture ends when the program does.

What should the next program consider?

If the next attempt is going to do different work, three structural design choices matter more than the funding number attached to it.

• The first is statutory architecture rather than departmental discretion. A program established under primary legislation, with an arms-length body owning it institutionally, can have its funding levels flexed without the institution itself unwinding. Durability of architecture is what allows funding to flex without the system collapsing. International comparisons all share this property to varying degrees, and the evidence is consistent: the institution survives because the architecture survives.

• The second is coordinated system design rather than standalone funding. The regulatory pathway, the IP framework, industry partnership norms, procurement’s willingness to absorb new technology, and capital follow-on are not background conditions; they are key inputs to the commercialisation system. A program that funds in isolation will likely produce the conversion rate AEA produced. A program designed within a coordinated system could do better.

• The third may matter more than its position in the list suggests. Portfolio logic should be defined at design time. Some programs operate as open-stage, gate-controlled funnels, in which every applicant can, in principle, progress. Others run as concentrating portfolios where the cohort narrows deliberately, with reserves and follow-on rules visible from the start. Both are defensible.
  
  What is not defensible is starting one and ending up as the other through an external decision. Applicants can plan against either logic, but they cannot plan against an undeclared logic.

What should we watch for?

The signal worth watching over the next 12 months is whether the successor mechanism is announced with or without statutory architecture.

A multi-year departmental envelope is the same program with a different number attached. A program established under primary legislation, sitting inside coordinated commercialisation architecture, is a different proposition entirely. The framing of the announcement will tell the ecosystem which one is on the table.

For operators within the system, the move is to stop planning against single instruments. Stage-gated funding from a discretionary program is a fragile input. Consideration needs to be given to planning against architecture, not against the program. Where the architecture is coordinated, the work can compound. Where it is not, expect the rug to move, even without any early market indications.

Australia does fund research at scale. However, it has not yet been asked whether Australia is willing to build the architecture that converts funding into outcomes. Until that conversation starts, the kill switch will keep firing.

References & further reading

1. Australian Government, Department of Education. Australia’s Economic Accelerator - Program Update. https://www.aea.gov.au/australias-economic-accelerator-program-update

2. Capital Brief. Commonwealth government axes $800m research commercialisation program. https://www.capitalbrief.com/briefing/commonwealth-government-axes-800m-research-commercialisation-program-39051371-d3ee-440e-b2a6-5d5c7c49e10b/

3. InnovationAus. ‘Sends the wrong signal’: Research sector blasts AEA axing. https://www.innovationaus.com/sends-the-wrong-signal-research-sector-blasts-aea-axing/

4. Science and Technology Australia. Federal Budget “savings” create more uncertainty without a plan. https://scienceandtechnologyaustralia.org.au/federal-budget-savings-create-more-uncertainty-without-a-plan/

5. AEA Advisory Board. 2024-25 Annual Report on research translation and commercialisation. https://www.aea.gov.au/download/813/aea-advisory-boards-annual-report-2024-25/384/annual-report/pdf

On international governance architecture

United States:

• SBIR / STTR Congressional Research Service. Small Business Research Programs: Overview and Issues for Reauthorization in the 119th Congress. https://www.congress.gov/crs-product/IF12874

• Congressional Research Service. Small Business Research Programs: Selected Issues for Reauthorization. https://www.congress.gov/crs-product/R48629

• CSIS. SBIR and STTR Reauthorization and the Future of Small Business Innovation. https://www.csis.org/analysis/sbir-and-sttr-reauthorization-and-future-small-business-innovation

• SBIR.gov. The History of the SBIR and STTR Programs. https://www.sbir.gov/tutorials/program-basics/tutorial-5

European Union:

• EUR-Lex. Horizon Europe - the framework programme for research and innovation. https://eur-lex.europa.eu/EN/legal-content/summary/horizon-europe-the-framework-programme-for-research-and-innovation-laying-down-its-rules-for-participation-and-dissemination.html

• European Commission. Horizon Europe - Research and Innovation. https://research-and-innovation.ec.europa.eu/funding/funding-opportunities/funding-programmes-and-open-calls/horizon-europe_en

• European Innovation Council. EIC Accelerator. https://eic.ec.europa.eu/eic-funding-opportunities/eic-accelerator_en

• European Parliament Fact Sheets. Multiannual Financial Framework. https://www.europarl.europa.eu/factsheets/en/sheet/29/multiannual-financial-framework

United Kingdom:

• Legislation.gov.uk. Higher Education and Research Act 2017. https://www.legislation.gov.uk/ukpga/2017/29/notes/division/3/index.htm

• GOV.UK. UKRI Framework Document 2025. https://www.gov.uk/government/publications/ukri-framework-document-2025/ukri-framework-document-2025

• UKRI. Our relationship with the government. https://www.ukri.org/who-we-are/how-we-are-governed/our-relationship-with-the-government/

Australia's Performance

Current data (2024-2025)

• Australian Government, Department of Industry, Science and Resources. How is the Australian innovation system tracking in 2024? https://www.industry.gov.au/news/how-australian-innovation-system-tracking-2024

• Australian Government, Department of Industry, Science and Resources. What do international indicators say about innovation? https://www.industry.gov.au/news/what-do-international-indicators-say-about-innovation

• WIPO. Global Innovation Index 2025: Australia. https://www.wipo.int/edocs/gii-ranking/2025/au.pdf

• WIPO. Global Innovation Index 2025: Cluster ranking. https://www.wipo.int/web-publications/global-innovation-index-2025/en/cluster-ranking.html

Historical Context

• Public Sector Network. State of the Australian Innovation System. https://publicsectornetwork.com/insight/state-of-the-australian-innovation-system-how-government-industry-academia-connect-innovation

• Australian Government. Research Translation and Commercialisation Agenda. https://www.education.gov.au/research-translation-and-commercialisation-agenda

• OECD Economics Department. Boosting Productivity in Australia (Working Paper No. 1025). https://www.oecd.org/content/dam/oecd/en/publications/reports/2013/02/boosting-productivity-in-australia_g17a224d/5k4c0vt9xhf3-en.pdf

• Deloitte Access Economics. The path forward for commercialising university research. https://www.deloitte.com/au/en/services/financial-advisory/perspectives/the-path-forward-commercialising-university-research.html

Research commercialisation system design

• OECD. University-Industry Collaboration. https://www.oecd.org/en/publications/university-industry-collaboration_e9c1e648-en.html

• Australian Government. Action Plan to supercharge research commercialisation. https://www.minister.industry.gov.au/ministers/taylor/media-releases/action-plan-supercharge-research-commercialisation

The signal that arrived too late.

A corporate venture team identifies a strong signal in Q2. The signal indicates retention is compounding, and that a customer segment is emerging that the team did not anticipate but cannot ignore. They need to commit resources to it now, while the signal is still hot.

The annual budget was set in November. Headcount was approved in January. The next planning cycle begins in nine months.

By the time the resources arrive, the window has narrowed. Sometimes it has closed. The venture continues, but the version of the venture that gets resourced is not the one the signal called for. It is the one the budget could accommodate.

This is not bureaucratic resistance. The CFO is not the antagonist. The planning team is not obstructing innovation. Each part of the system is doing what it was designed to do. The system itself was built for a different job.

Corporate ventures do not fail from under-funding. They fail because the resource system is running on the wrong clock at the wrong scale.

This pattern holds whether the venture is built internally, spun out as an independent entity, invested in through corporate venture capital, acquired through M&A or acqui-hire, or pursued through partnership.

The execution path changes. The structural condition does not.

This is a different argument from the one most readers expect as many discussions about innovation funding focus on volume. Addressing questions such as how much capital is allocated, what proportion of revenue is committed, and where the budget sits in the organisational chart. That conversation matters, but it is the second-order question. The first-order question is whether the resource system can move at all when evidence demands it. Volume without velocity is the most expensive failure mode in corporate venturing. It produces big and late.

The deeper diagnosis.

Issue #9 named the absence of reallocation as a portfolio-level failure. A real portfolio redistributes resources when signals strengthen. Most corporate innovation portfolios do not. That essay left a question unresolved. Even when the portfolio decides to reallocate, can the underlying resource system enforce the decision? The answer, in most cases, is no.

The reason is upstream of any particular budgeting failure. Most resource problems in corporate venturing trace to a single structural decision. Innovation is treated as a contained function with a fixed allocation, rather than as a distributed capability with a claim on enterprise resources. The innovation team has its budget. The ventures within it compete for that budget. They do not have a structural mechanism to draw from elsewhere when signals justify it.

Once that classification is made, four downstream conditions follow. Two govern cadence. Two govern volume. Together, they produce the asymmetry the title names.

Cause 1: Ventures are governed on Calendar Time, not Venture Time

Corporate planning runs on calendar time. There is an annual budget with an annual headcount plan, all being managed through quarterly reviews. The calendar is a rhythm imposed for reasons of accountability, forecasting, and governance. Those reasons are legitimate for established business units operating on year-over-year improvement cycles.

Ventures do not operate on calendar time. They operate on venture time, a composite of three distinct rhythms.

There is “evidence time,” when signals strengthen, and the venture has new information about what should happen next. Evidence cycles run in weeks or months, not years. A retention curve that compounds in Q2 is information the team did not have in Q1. Acting on it in Q4, after the next budget cycle, is acting on a snapshot of a market that has moved.

There is an “opportunity time”. When external windows open and close on market clocks, the corporation cannot influence them. A venture round worth participating in. A target available for acquisition. A partnership that becomes possible because a particular configuration of buyers, suppliers, and competitors has briefly aligned. Opportunity time is the world telling the venture when it must move. The corporate calendar is irrelevant to it.

There is an “ad-hoc” time component. Unscheduled but consequential moments. A spin-out is succeeding faster than expected and needs additional staff before the next hiring round. A partnership requiring fast technical resourcing to meet a contract milestone. A pilot showing enough signal that a step-change investment is warranted before the next gate review.

Calendar time is one rhythm, but Venture time is three. The mismatch is not occasional; it is constant. The corporate planning cycle was never designed to accommodate any of the three, because the operations it governs do not require them.

Cause 2: Talent lock-in once deployed

The first cadence problem is about putting resources in. The second is about moving resources between ventures once they are in.

Capital can be reallocated faster than people. A venture that needs less can have its budget trimmed at the next quarterly review. A venture that earns more can have funding lifted. The money moves quickly once the decision is made.

People do not move on the same clock. Once a person is deployed onto a venture, redeploying them onto a stronger signal elsewhere in the portfolio requires unwinding a network of arrangements. Performance reviews are linked to the current scope. Manager relationships have been built. Career narratives have been constructed around the current venture. HR systems treat redeployment as a re-hire process, not a reallocation. Even when the portfolio decides to concentrate talent on the strongest signal, the system makes the decision unenforceable on any timeline that matters.

This is the second clock, and it is often slower than the first. A portfolio with fast capital reallocation and slow talent reallocation is still a portfolio that can change its slide deck but not its execution. The same dynamic applies in spin-outs, where pulling additional people into a successful spin-out from the parent often runs through the parent’s HR cycle. The spin-out’s capital independence does not extend to the flow of talent.

Cause 3: Resource competition with the core business (the floor)

Cadence is one face of the asymmetry. Volume is the other.

When ventures sit inside the corporate budget process, they compete with established business units for resources from the same pool. Every additional dollar to a venture is a dollar removed from a known-return P&L line. The CFO does not need to oppose innovation. The budget structure does it for them.

The rational response, given that comparison, is to set the venture allocation low. Low enough that it does not threaten any meaningful business unit line item. Low enough that approval is uncontested. Low enough that no individual decision-maker has to defend a transfer of capital from operations to experimentation.

This produces a structural floor where ventures get just enough to keep going, never enough to compound. The result, the venture does not have the funding the signal would justify. In CVC structures, the same pattern appears at the deal level. A corporate venture fund weighing follow-on participation in a hot round against operating returns will write a smaller cheque than the round requires. The fund is in the room. It is not in the round at the level of strategic interest it warrants.

Cause 4: No concentration mechanism for compounding signals (the ceiling)

The volume problem has both a ceiling and a floor. Even when a venture earns the right to more resources through evidence, there is no mechanism to concentrate capital on it excessively.

A venture that doubles its retention curve does not automatically receive double the budget. A spin-out that signs a major customer ahead of plan does not automatically secure step-change follow-on capital from the parent. An acquisition target whose strategic value has become obvious does not automatically jump to the top of the M&A queue. Each of these requires a fresh approval against the same competing claims as before. The system can fund maintenance. It cannot fund conviction.

This is the structural difference between a venture portfolio and a venture system. A portfolio decides which bets to make. A system decides which bets to concentrate on as evidence accumulates. Without a concentration ceiling, every venture in the portfolio is funded as if it had the same compounding probability, regardless of the evidence.

The cumulative cost

Each cause is bearable in isolation. A venture operating under all four conditions is not. The system funds these ventures at exactly the level required to keep them alive and exactly nothing more, which is the slow accumulation of stalled ventures, Issue #9 named.

The four resource states

Cadence and volume are not coequal. Cadence is upstream. Volume is downstream. A fast clock with thin volume can still read signals and place small bets. A slow clock with heavy volume produces capital that arrives after the signal has decayed. The 2x2 below maps the four states corporate innovation functions occupy.

Most corporate innovation functions live in the top-left quadrant. Some, after a budget increase that did not include a cadence redesign, move to the bottom-left and discover that more money on a slower clock produces larger zombie pilots, not better ventures. A few, usually structurally separated from the parent, sit in the top-right. The bottom-right is where venture-grade execution actually happens. It is also where most corporate innovation functions claim to be.

The four exits

Most readers will already be reaching for reasons their organisation is exempt from this argument. Four exits, in order of how often they are used.

• We have a fast-track process for urgent resourcing.
  Many fast-track processes are political escape valves, not structural mechanisms, depending on a senior sponsor invoking them. They run on relationship capital, not governance design. A fast-track that requires a leader to personally champion each invocation is not a system. It is a workaround that works once or twice a year, then collapses. A real cadence correction does not require anyone to champion it. The default cadence is the fast cadence.

• We have an innovation fund. That is our pre-authorised pool.
  Named innovation funds are often accounting re-classifications of the same annual budget. The capital lives within the pool, but the cadence and volume rules governing its release remain unchanged. The pool cannot be deployed without going back through the business unit planning cycle, without a quarterly committee, or without an exception process that takes longer than the signal allows. A pool you cannot deploy on venture time is not a venture pool. It is a labelled bucket inside the existing system.

• We have a governance committee that can make resource decisions.
  A quarterly meeting committee cannot operate on venture time. A committee that requires consensus cannot concentrate capital on a single signal at the expense of others. A committee whose members each represent a different function will optimise for proportionality rather than conviction. The committee is not the answer to absent decision rights. It is often the structural reason that decision rights are absent.

• The real problem is we just need a bigger innovation budget.
  This is the most expensive exit. Volume without velocity is dead capital. BCG’s 2024 research found 83% of leaders rank innovation as a top-three priority, while only around 30% feel ready to execute. Adding to the volume side cannot close that gap while cadence remains untouched. A larger budget on the wrong clock does not produce more ventures. It produces more zombie pilots with bigger headcount lines.

What changes

The fix is structural, not procedural. A faster approval process inside the existing architecture will not produce venture-grade resourcing. The architecture itself has to change, with a mechanism that enables the venture pool to sit outside the annual planning cycle. This is not a labelled bucket. A genuinely separate structure with its own governance, its own decision rights, and its own deployment triggers.

Governance

The pool is governed by a small group with explicit authority to deploy capital and assign talent on evidence triggers, without requiring approval from the next BU planning round. The group is structurally separated from the operating P&L, which means its decisions cannot be vetoed by line-of-business managers protecting their allocations. The group’s accountability is for the ventures that pool resources, not for the operating revenue lines those resources might have served instead.

This structure is not unfamiliar. It is roughly how independent venture firms operate: a partner group with capital deployment authority, evidence-based decision triggers, and accountability to a portfolio rather than to an operating P&L. The novel work in a corporate context is making the structure compatible with the rest of the organisation without surrendering its independence.

Triggers

The pool deploys on evidence triggers, not on calendar triggers. A retention curve crossing a defined threshold. A customer concentration signal exceeding a stated level. An external event such as a competitor move, a regulatory change, or the availability of a target. A spin-out hitting a milestone that warrants follow-on. The triggers are documented, monitored, and acted on without requiring fresh approval each time.

This does not mean the pool deploys without evaluation. It means the judgment runs on the venture’s clock, not the corporation’s. A trigger fires, causing a decision within the pool’s governance. Capital and talent move. The annual planning cycle does not need to be known in advance.

Size

The pool needs to be large enough to fund concentration, not just continuation. If the pool can support only N ventures at the maintenance level, the concentration ceiling remains unchanged. The pool must carry headroom for a step-change investment in the strongest signal, meaning it must be sized as if at least one venture will require multiples of its initial allocation. A typical starting frame: pool size equal to two to three times the sum of initial venture allocations, with explicit reserves for follow-on concentration.

The pool fixes cadence first. It also creates the structural conditions for volume to flow to the strongest signals, because there is somewhere for that volume to go without contesting BU allocations.

The pool addresses capital cadence. Talent cadence requires a parallel structure, with pre-authorised talent slots that are reassignable on evidence triggers, and HR treating venture redeployment as strategic rather than a re-hire. Without that, the pool can move money but not people.

Diagnosing Resource Velocity

Six questions. Three on cadence. Three on volume. Each has a named failure mode. Apply this to your own innovation function. Answer honestly.

Cadence

1. When was the last time your innovation function reallocated capital outside the annual planning cycle? If the answer is “in the last quarter,” you have a working cadence. If the answer is “during last year’s reset,” or you cannot recall, you do not.
   Failure mode: You have a calendar, not a clock.

2. If a venture team identified a strong signal next month, how long until additional capital and headcount could be deployed in response?
   Measure the answer in weeks. If the answer is in quarters, the signal will have decayed by the time the resourcing arrives.
   Failure mode: signal-to-deployment lag is measured in quarters, not weeks.

3. What evidence threshold triggers an out-of-cycle resource decision in your governance system?
   If you can name the threshold, you have evidence-based cadence. If the answer is “when the CEO asks,” you have political cadence.
   Failure mode: there is no threshold, only a calendar.

Volume

1. When a venture demonstrates compounding evidence, can it secure step-change resourcing without joining the next BU planning round?
   If yes, you have a concentration mechanism. If no, the venture is graded on a curve set by the core business.
   Failure mode: Ventures are evaluated against operating returns, not venture returns.

2. Is there pre-authorised capital sitting in a venture pool, or does every increment require fresh approval against competing BU bids?
   A pool you cannot deploy without re-approval is not a pool.
   Failure mode: Venture capital is contested capital.

3. Is there a defined ceiling on how much a single venture can absorb when signals justify concentration, or does every dollar above baseline require an exception?
   If your strongest venture cannot draw step-change resources without exception treatment, your system is designed to maintain ventures, not to bet on them.
   Failure mode: your system can fund maintenance but not conviction.

Reading the pattern

Five or six yes answers: you have venture-grade resourcing. Confirm by reviewing how the system performed under pressure in the last 24 months.

Three or four yes answers: one axis is functioning while the other is broken. Identify which. Cadence-strong / volume-weak organisations make many small bets quickly, but cannot concentrate when one of them works. Volume-strong / cadence-weak organisations have meaningful capital that arrives after the signal has decayed. Both states are unstable.

Less than three positive answers: you are operating in stalled-and-starved territory. The portfolio is on the wrong clock at the wrong scale. The structural fix is upstream of any particular budget conversation.

The Australian context: A capital constrained ecosystem.

The cost of resource asymmetry compounds in capital-constrained ecosystems. Australia is one such ecosystem, and four features make the structural argument harder to escape locally.

A decade of mixed venture outcomes

The most publicly documented Australian evidence sits in corporate venture capital, because external investments leave a paper trail and external structures attract external commentary. The same structural conditions apply to internal builds, spin-offs, M&A, and partnerships, but those failures are usually invisible outside the organisation. The CVC story below is illustrative, not definitional. The same patterns play out across every execution path.

Over the last ten years, each of Australia’s major banks built corporate venture vehicles. Their structural designs differed materially.

• Some were internal funds governed under the parent’s financial architecture.

• Some were spun out into independent entities with the parent as sole funder.

• Some were externally-managed funds with the parent as one limited partner among several.

• Some were venture scalers with partial separation: a separate legal entity and technology stack, but inside the parent’s strategic gravity.

The outcomes have not divided cleanly along the lines most people would predict. Externalisation alone has not been the answer. Internal models have not always failed. The variable that better explains durability is something more specific: how robust the structural separation was, and how much it depended on the parent’s continued willingness to fund and not interfere.

• One of the major banks set up an internal innovation and investment arm. Close to a decade later, it had evolved and was spun out into an independent entity, to operate outside the “gravitational pull” of the parent entity. Thereby, driving improvements across delivery speed, agility, lower costs, and easier talent recruitment. The entity ran for several years. with several meaningful investments, including a position in one of Australia’s most successful fintechs. In late 2025, under new leadership and amid a broader restructure, the bank closed the entity. The remaining portfolio was folded back into a non-operating holding company. The structural fix had been correctly implemented and then unwound.

• A different bank ran an internal fund for several years and approximately $100M of deployed capital before substantially slowing its activity. The fund still exists and still has a public-facing investment process and a portfolio, however new investments have dropped from its peak. The structural separation was real. The funding potentially was not over time.

• A third, took a different mode, operating a venture scaler, with partial separation, that started with a stated ambition of 25 ventures by 2025. It has since re-positioned to scaled back on volume, to fewer but larger bets. It too more recently has extended its model through a partnership with an external fintech fund.

• And a fourth, the earliest mover, structured its CVC as an externally-managed fund with the bank as a limited partner. That fund made early bets that produced material returns, including a position in a US crypto exchange that yielded a reported $500M-plus windfall on listing. It ran three funds. Ahead of its fourth fund, it decoupled from the bank, partly because the bank was reluctant to back the categories the fund manager wanted to pursue. The fund continues to operate. It is no longer a pure corporate venture vehicle solely for its parent entity.

Two patterns matter in this evidence.

The first is that the durability of separation explains more than the presence of separation. Independent entities funded solely by the parent have a weaker form of structural separation than independent funds with diversified limited partners. The kill switch is in different hands. When the parent’s leadership changes or its cost pressure rises, the parent-funded entity is exposed in a way the diversified-LP fund is not.

The second is that even correctly implemented structural fixes are not durable unless they are institutionalised beyond any single leadership team. The structural argument the essay has made operates over decision cycles measured in months. Corporate leadership cycles run on multi-year clocks. A venture architecture that depends on the goodwill of a particular CEO will be vulnerable at the next transition, regardless of how well it was designed.

The lesson is not that externalisation is the answer. It is that resource architecture is the binding constraint; the architecture has to be designed for durability rather than initial separation, and the durability has to be earned over time and across leadership transitions, not just established at inception. The structures that survived longest in the Australian evidence were those whose continuation did not depend on any single corporate decision-maker continuing to back them.

The same pattern, less visible: internal builds and spin-outs

The CVC examples above are documented because external investments leave a paper trail. The much larger pool of evidence sits in internal builds, where the structural pattern is identical but the failures are visible only inside the organisations that own them.

The pattern is recognisable. An internal venture is launched with a strategic mandate. It receives an annual allocation that is rational by core-business standards but starves it by venture standards. It runs for several years. Customer acquisition is steady but slow. Headcount lifts incrementally. The product roadmap moves at the cadence permitted by the parent’s planning cycle. Years later, when the organisation needs to accelerate to keep up with a market that has moved, the internal venture cannot. The acceleration option chosen is usually external: a competitor neobank is acquired, an external partnership is signed, a fintech is bolted on. The structural problem the internal build was designed to solve is eventually solved by paying market rates for someone who was free to operate on venture time.

One Australian example sits in plain view. A major bank launched an internal direct bank in 2008. Roughly thirteen years later, with a customer base that had grown but had not kept pace with newer entrants, the parent bought a younger competitor folded it into the original venture, taking the competitor’s technology platform and team alongside the original brand.

The internal build was not a failure. It worked, by every measure the parents’ planning cycle had set for it. It was simply unable to meet the market’s timeline. The acceleration had to be purchased externally because the parent’s architecture could not generate it.

That is the structural pattern at the internal-build level. The venture had funding for over a decade. What it did not have was the cadence and concentration mechanism to compound. The eventual fix was not to redesign the resource architecture. It was to acquire what the architecture had failed to produce. That works once. It does not work as a system.

The acquisition pattern reveals the same condition from a different angle. When organisations cannot resource at venture velocity internally, they buy. The acquired venture often arrives with the velocity intact, only for the integration process to destroy it. Bain’s M&A research has found that talent retention is the second-largest contributor to acquisition deal success, behind only deal thesis. Acquired venture teams that operated on venture time before acquisition find themselves slowed to the parent’s pace within the first integration cycle. The volume problem has been solved by the acquisition price. The cadence problem has not.

If an organisation repeatedly chooses to buy what it cannot build internally, the binding constraint is not capability or talent. It is a resource architecture. The pattern may repeat every five to seven years.

A capital ecosystem that compounds the cost.

The Cut Through Venture and Folklore Ventures State of Australian Startup Funding 2025 report shows the structural shape of local capital. $5.48 billion was raised across 390 deals in 2025, but the top 20 deals captured 58% of the total. Series B remains a bottleneck, and 66% of all 2025 deals included at least one international investor, up from 57% in 2024. At Series A and beyond, offshore participation is now the norm rather than the exception.

For corporate ventures, this matters because the fallback option after missing an internal resourcing window is much narrower than in deeper capital markets. A US-based corporate venture that misses its parent’s funding window can usually find domestic bridge capital. An Australian corporate venture that misses its parent’s window often cannot. Internal cadence is not just a governance question. In Australia, internal cadence often is the capital availability for corporate ventures.

A concentrated corporate landscape.

our banks. Three miners. Two insurers. Annual planning cycles in these organisations are not just embedded, they are load-bearing. The structural mismatch between calendar time and venture time is therefore especially costly here, because the organisations most likely to operate corporate venture functions are also the ones with the most deeply entrenched planning architectures.

The Australian innovation ecosystem cannot fix the cadence problem from the outside. The fix has to come from inside the organisations that hold the largest balance sheets, and the design of that fix is the structural question this issue has tried to name.

A doctrine close.

Volume without velocity funds zombie pilots. Velocity without volume funds experiments. Ventures need both.

A corporate venture system running on the wrong clock at the wrong scale is not a venture system. It is an operational system with a venture label. The label provides cover. The structure produces the outcomes the structure was designed to produce. Calendar time and contested volume produce stalled ventures. Venture time and pre-authorised concentration produce ventures.

Issue #9 ended on the line that a portfolio without kill discipline is just a list. Issue 10 extends that argument one structural layer down. A portfolio without resource velocity is just a list with a budget.

Closing note

This is Issue #10, the fourth or six in the Corporate Venturing Under Constraint series. Issue #9 named the absence of reallocation as the portfolio-level failure. Issue #10 has named the resource architecture that makes reallocation unenforceable.

Still to come:

Issue #11 takes up the question this issue leaves open: who, inside the organisation, holds the authority to design and operate this architecture in the first place. Governance maturity. Decision rights. The role that does not yet exist in most corporate innovation functions.

Issue #12 closes the series by naming the function itself. The Venture Operator Function a category that this body of work has been describing.

If you found this useful, the diagnostic above is designed to be run on your own function. Save it, screenshot it, share it with someone who needs to see it. The structural conversation is easier to have when both parties are looking at the same diagnostic.

Subscribe now

References & Further Reading

1. Bain & Company. (2022). Reimagining Talent in M&A: 2022 M&A Report. https://www.bain.com/insights/reimagining-talent-m-and-a-report-2022/

2. Boston Consulting Group. (2024). Most Innovative Companies 2024: Innovation Systems Need a Reboot. https://www.bcg.com/publications/innovation-strategy-delivery-insights

3. Capital Brief. (October, 2024). x15 Ventures celebrates first major ‘exit’ as Unloan graduates into CBA division. https://www.capitalbrief.com/article/x15-ventures-celebrates-first-major-exit-as-unloan-graduates-into-cba-division-40a3cdc7-fd35-4b61-8cbe-cf996c92780d/

4. Capital Brief. (October, 2025). ‘Makes sense’: ANZ confirms 1835i closure. https://www.capitalbrief.com/newsletter/makes-sense-anz-confirms-1835i-closure-4c965396-a6f1-45ee-bd68-3df1167291f5/

5. Capital Brief. (December, 2024). ‘Pleased it’s over’: Ubank CEO on the 86 400 merger and the neobank’s future at NAB. https://www.capitalbrief.com/article/pleased-its-over-ubank-ceos-on-the-86-400-merger-and-the-neobanks-future-at-nab-649af10e-6eab-4e2a-aa91-adb62100144f/

6. Capital Brief. (August, 2024). From Reinventure to reinvention: Westpac’s mutating VC journey. https://www.capitalbrief.com/article/from-reinventure-to-reinvention-westpacs-turbulent-vc-journey-418322dc-ff80-4f50-954b-917e6330831f/

7. Collective Campus. Corporate Venture Capital in Australia: Fueling Innovation and Growth. https://www.collectivecampus.io/blog/corporate-venture-capital-in-australia-fueling-innovation-and-growth

8. Cut Through Venture and Folklore Ventures. (February, 2025). State of Australian Startup Funding 2025. https://www.cutthrough.com/insights/state-of-australian-startup-funding-2025

9. iTnews. (June 2022). CBA’s x15ventures switches focus from build to benefits. https://www.itnews.com.au/news/cbas-x15ventures-switches-focus-from-build-to-benefits-580793

10. Mi3. (December, 2023). Fewer, bigger bets: CommBank’s X15 ventures doubles down on scaling winners. https://www.mi-3.com.au/05-12-2023/banking-deeper-tech-integration-and-innovation-drive-customer-loyalty-well-commercial

11. Startup Daily. (October, 2025). ANZ bank has killed off its venture arm, 1835i. https://www.startupdaily.net/topic/venture-capital/anz-bank-has-killed-off-its-venture-arm-1835i/

Now consider how most corporate innovation functions use the word “portfolio.”

They mean: the things we are currently doing.

That is not a portfolio. That is a collection. And the distance between those two words is where most innovation value gets destroyed.

The Collection Problem

Most organisations arrive at their “innovation portfolio” the same way. Individual initiatives get proposed, evaluated, and approved through separate business cases. Each one clears its own hurdle. Each one gets its own budget line. Each one reports on its own progress against its own milestones.

At some point, someone assembles a slide that shows all of these experiments, options, ventures or initiatives on a single page. Maybe they get sorted into horizons. Someone may draw a 2x2 with risk on one axis and strategic fit on the other. The slide gets presented at a quarterly review. Everyone nods. The word “portfolio” is used.

But nothing about that process constitutes portfolio management. No one asked whether these ventures, taken together, represent a coherent set of strategic bets. No one assessed whether the risk is concentrated or distributed. No one has the authority to move resources from one initiative to another based on relative performance. No one is measuring return at the portfolio level.

What exists is a collection of individually approved projects that are visible on the same slide. The slide creates the appearance of portfolio thinking without any of the underlying mechanics.

Why the Gap Exists

The collection-to-portfolio gap is not an oversight. It is a structural consequence of how many organisations set up their innovation functions. The gap has at least four root causes, and they compound.

The mandate is undefined.

Before you can construct a portfolio, you need to answer a question that most organisations skip entirely: what is the role of innovation in this organisation’s strategy, and what methods are in scope?

This is a scoping decision that sits upstream of everything else. It determines which instruments are available to the innovation function or functions and which belong elsewhere. An organisation might decide that its innovation mandate covers internal venture building and spinouts, but that partnerships and strategic investments sit with corporate development. Another may include invest-to-partner models within the innovation remit. A third might limit the scope to incremental improvements within existing business lines.

None of these choices is inherently wrong. An organisation that says “we build from within and occasionally spin out” has made a legitimate strategic decision. It narrows the option set but creates clarity about what the portfolio can contain, what capabilities are needed, and what a return looks like.

The problem is when this scoping decision never gets made. Innovation becomes whatever anyone decides it is. Different business units pursue different types of activity under the same label. Some run small incremental projects. Some attempt genuine ventures. Some call process improvements “innovation” because the word carries budget protection.

Without a mandate, there is no boundary. Without a boundary, there is no portfolio. There is just accumulation.

The instruments are treated as interchangeable.

Even where a mandate exists, most organisations fail to recognise that different types of innovation activity are fundamentally different instruments.

Building a venture from within the organisation is not the same as investing in an external startup. A spinout operates under different constraints than a partnership. An invest-to-partner model, where you take a position in an external company with the intent of integrating capability over a three to five-year horizon, looks nothing like a twelve-month internal build.

In finance, no one would manage equities, fixed income, and options as if they were the same thing. The portfolio exists precisely because these instruments are different, and the value comes from how they interact as a set.

Most innovation functions treat every initiative as the same type of bet. The same stage-gate process. The same milestone structure. The same quarterly reporting cadence. This flattening erases the very differences that portfolio construction is designed to exploit.

The structural design prevents portfolio-level decisions.

How the innovation function is organised determines whether portfolio management is even possible.

In a centralised model, a single team owns the innovation mandate. This creates the possibility of portfolio-level authority: someone who can see the full set of bets and make trade-offs across them. But centralised models often lack proximity to the business context where ventures need to operate.

In a decentralised model, each business unit runs its own innovation activity. This provides business context but eliminates portfolio-level visibility. No one can see all the bets. No one can reallocate resources across the set. Each unit optimises locally, and the organisation’s total innovation spend is just the sum of uncoordinated parts.

The hub-and-spoke model is the most common attempt to resolve this tension. A central hub holds processes, standards, budget, governance, and capability. Spokes in business units run execution closer to the operating context. Larger or cross-cutting bets escalate to the hub. Day-to-day innovation stays in the spokes.

In theory, this combines centralised coherence with decentralised proximity. In practice, it drifts. The hub becomes administrative rather than strategic, running reporting cycles and stage-gate reviews rather than making portfolio decisions. The spokes diverge in their methods and definitions, each developing its own view of what counts as innovation. Decision rights between hub and spoke become contested. The quarterly review becomes a status update rather than a governance forum. And no one is confident about where portfolio-level authority actually sits, because in practice, it sits nowhere.

This is also where Issue 8’s stop authority problem becomes a portfolio-level problem. If no one in the structure has the authority to kill an individual initiative, no one can rebalance the set. Stop authority at the project level is a prerequisite for portfolio management. Without it, the portfolio can only grow. It can be difficult to reshape.

The structural design choice matters less than whether the chosen structure enables someone to manage the portfolio as a whole. If no one has authority over the set, the set cannot function as a portfolio regardless of how it is organised.

There is no connection to strategy.

A portfolio without an investment thesis is just a scatter plot.

In finance, the thesis determines the construction: which sectors to overweight, which risks to accept, and which time horizon to optimise for. The portfolio is the execution layer of the thesis.

In corporate innovation, the equivalent is the connection between the innovation portfolio and the organisation’s strategic plan. The portfolio should be the set of strategic options the organisation is actively pursuing to create future value. Each position should trace back to a strategic question the organisation needs to answer or a capability it needs to develop.

Not every bet needs to map neatly to an existing strategic priority. A well-constructed portfolio includes exploratory positions: deliberate, bounded investments in areas where the organisation has no current thesis but wants to develop one. Adjacency plays. Emerging technology watches. Genuine moonshots where the organisation is spending to learn whether a space is relevant to its future.

The critical distinction is that exploratory positions are still deliberate. They are in the portfolio because someone decided to allocate resources to that space, not because they drifted in through an enthusiastic business unit. They still carry a return expectation, even if that return is defined as “develop enough understanding to make a strategic decision within eighteen months.” Exploratory does not mean exempt from rigour.

When innovation operates as a standalone function with its own strategy, disconnected from the organisation’s strategic planning process, the portfolio becomes self-referential. It serves the innovation function’s goals rather than the organisation’s strategic needs. This is how you end up with innovation teams that can demonstrate impressive activity metrics while the organisation’s strategic gaps remain unaddressed.

The connection needs to run in both directions. Strategy should inform what the portfolio contains. And the portfolio’s performance should inform strategic planning, updating the organisation’s view of which options are maturing, which are failing, and where new bets are needed.

To put it plainly, many innovation functions have no defined boundary around what they are responsible for, treat fundamentally different types of bets as if they were interchangeable, are structured in ways that prevent anyone from managing the set as a whole, and operate with little or no connection to the organisation’s strategic plan. Any one of these gaps would prevent real portfolio management. Most organisations have all four. That is not a portfolio with room for improvement. It is a collection with a label.

Before You Diagnose: The State of Play

Before applying any diagnostic, there is a prior step that most organisations skip. And it is broader than most expect.

You need an inventory. Not of what the innovation function is currently running, but of everything the organisation is doing that could constitute innovation or venturing activity, anywhere, under any label.

This means looking beyond the innovation team’s pipeline. Corporate development might be running invest-to-partner plays that are functionally innovation bets but governed as transactions. A business unit might have a skunkworks project that nobody reports centrally. The strategy team might be funding exploratory research that never touches the innovation function’s pipeline. M&A might be doing acqui-hires that are capability bets dressed as deals.

The broad state of play needs to capture each activity’s type, stage, committed resources, expected return, and the strategic question it is intended to answer. It also needs to note where the activity currently sits organisationally and who governs it.

Most organisations cannot produce this on demand. When they try, the exercise itself becomes revealing. Initiatives surface that no one at the centre knew were running. Committed resources turn out to be higher than anyone estimated because costs are spread across business unit budgets that are never consolidated. Several initiatives turn out to be pursuing overlapping objectives with no coordination between them. Activities that one function calls “innovation”, another calls “business development” or “continuous improvement,” and the definitional inconsistency is itself a finding.

The broad inventory matters because it inverts the usual sequence. Most organisations define the mandate first and then inventory what falls within it. This is circular; you end up scoping around what is already visible rather than what should be managed. The stronger sequence is to see the full landscape first, then draw the boundary. The mandate becomes a decision informed by evidence rather than a top-down decree that inherits whatever definitional problems already exist.

Once the mandate is defined, the state of play narrows to the portfolio boundary. But it does not become a one-time exercise. It is the foundation of portfolio governance: updated regularly, reviewed against strategic priorities, and used as the basis for rebalancing decisions. If you cannot produce an accurate state of play, you cannot manage a portfolio. You are navigating without an inventory.

The Portfolio Reality Diagnostic

Six questions to help determine whether what the organisation has is a portfolio or a collection.

1. Can you define the mandate?

Write down, in one paragraph, what your innovation function is authorised to pursue and what methods are in scope. If you cannot do this, or if the answer is “it depends on the business unit,” you do not have a portfolio boundary. You have an accumulation.

2. Can you produce a state of play?

List every activity across the organisation that could constitute innovation or venturing, not just what the innovation function manages. Include its type, stage, committed resources, and expected return. If you cannot produce this list within a week, if the exercise reveals activities no one at the centre knew were running, or if different functions cannot agree on what counts, you do not have portfolio visibility. You have fog.

3. Can you name the instruments?

Take that list and categorise each initiative by type: internal build, spinout, partnership, investment, invest-to-partner, exploratory position, or other. If every initiative is the same type, your portfolio has no diversification. If you cannot categorise them because the types have never been distinguished, your portfolio has no composition logic.

4. Can you state the expected return (desired outcomes) for each position?

For each initiative, articulate the return the organisation expects and the time horizon. The return does not have to be financial. It can be strategic optionality, capability development, or market learning. But it must be defined. If most initiatives have no stated return expectation, you have no basis for portfolio-level measurement.

5. Can one person or body rebalance the portfolio?

Identify who has the authority to move resources between initiatives, accelerate one at the expense of another, or kill a position based on the portfolio’s overall performance. If the answer is “no one” or “it would require separate approvals from each business unit,” you have a collection governed by its parts, not a portfolio governed as a whole.

6. Can you trace each position to a strategic question?

For each initiative, identify the strategic question it answers or the strategic capability it develops. This includes exploratory positions, which should trace to a question the organisation is actively trying to answer, even if the answer is not yet clear. If many initiatives cannot be connected to the organisation’s strategic plan or to a deliberate exploration thesis, the portfolio is self-referential. It serves the innovation function, not the organisation.

Reading the pattern: If you answered “no” to one or two of these, you have specific gaps to close. If you answered “no” to three or more, what you have is not a portfolio in any meaningful sense. It is a collection of individually approved activities that share a label but lack the connective tissue that enables portfolio management.

But We Are Different

Two versions of this argument appear reliably when portfolio discipline is proposed.

This inverts the logic. Uncertainty is precisely why portfolio discipline exists. Financial portfolios are not built for environments of certainty. They are built because individual positions are unpredictable, and the portfolio is the mechanism for managing that unpredictability across a set of bets. Diversification, rebalancing, and position sizing all exist because no one knows which individual bet will pay off.

The same principle applies to innovation. Individual ventures are uncertain. That is not a reason to abandon portfolio logic. It is the reason you need it.

A 2022 study published in Production and Operations Management by Si, Kavadias, and Loch at Cambridge Judge Business School found that the results of innovation portfolio management processes remain widely perceived as unsatisfactory, but not because the problem is too uncertain for structure. The root cause they identified was an overemphasis on generic individual project selection, without connection to the organisation’s specific strategy. The problem is not too much rigour. It is the wrong kind of rigour, applied at the wrong level.

McKinsey has consistently found that while more than 80% of executives say innovation is among their top three priorities, fewer than 10% are satisfied with their organisation’s innovation performance. That gap has persisted for nearly a decade. BCG’s 2024 Most Innovative Companies report tells the same story at scale. The report surveyed more than 1,000 senior innovation executives globally and found that the readiness gap is widening. In 2022, 20% of companies qualified as “innovation ready” on BCG’s maturity benchmark. By 2024, that figure had fallen to 3%, even as 83% of companies ranked innovation as a top-three priority. Only 12% of executives reported a strong link between their business and innovation strategies. BCG described the emerging pattern as “zombie” innovation systems: organisations going through the motions without a clear strategy to focus their efforts. The parallel with Issue 8’s zombie pilots is not coincidental. The same structural absence, no one with the authority or mandate to make hard decisions, produces the same outcome at every level: activity without accountability.

McKinsey’s late-2024 survey of over 1,000 C-level executives across 99 countries reinforced this. Most organisations struggle to make trade-offs between short- and longer-term initiatives or among projects with different risk profiles. That is not a description of organisations with too much structure. It is a description of organisations with no portfolio-level decision-making at all.

Complexity is not an exemption from portfolio logic. It is the reason you need it.

Large organisations with multiple business units, geographies, and innovation models will never have a simple portfolio. But the alternative to a single portfolio view is not to have no view; it is multiple uncoordinated views that no one can reconcile. Without a portfolio-level view, the organisation cannot see concentration risk, identify duplication, or make trade-offs across the set.

The operational challenge is real. Constructing a portfolio view across a complex organisation requires shared definitions, consistent categorisation, and a governance layer with authority over the whole. That is difficult. But the difficulty of construction is not an argument against the necessity. It is a description of the work that needs to be done.

The Real Cost of the Illusion

The danger of the portfolio illusion is not just that it is inaccurate. It creates false confidence.

An organisation that knows it has a collection of ad hoc innovation projects at least understands what it is working with. The constraints are visible. The lack of coordination is acknowledged.

An organisation that believes it has a portfolio may assume it is diversified, even though it may be concentrated. It assumes it has strategic coverage when it may have gaps. It assumes someone is managing the set, even though no one has that authority.

The portfolio’s language creates a governance assumption that the structure does not support.

This is how organisations find themselves with twenty innovation initiatives and no strategic options. Activity is high. The slide looks full. But nothing in the collection is constructed to deliver portfolio-level returns, because no one is managing it at that level.

What a Portfolio Actually Means

A portfolio is a deliberately constructed set of strategic options, scoped by mandate, composed across instruments, governed as a whole, measured against return, and connected to strategy.

A portfolio you never rebalance is just a list you approved. And collections do not compound.

References & Further Reading

Si, H., Kavadias, S. and Loch, C. (2022) ‘Managing Innovation Portfolios: From Project Selection to Portfolio Design’, Production and Operations Management.
Available at: https://onlinelibrary.wiley.com/doi/10.1111/poms.13860

Boston Consulting Group (2024). Innovation Systems Need a Reboot: The 2024 Most Innovative Companies Report.
Available at: https://www.bcg.com/publications/2024/innovation-systems-need-a-reboot

McKinsey & Company (2025) ‘Investing in Innovation: Three Ways to Do More with Less’, McKinsey Global Survey on Innovation.
Available at: https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/investing-in-innovation-three-ways-to-do-more-with-less

This article is based on the author's professional experience and interpretation of publicly available information. It is provided for general informational purposes only and does not constitute advice. Any views expressed are the author's own and do not refer to any specific organisation, program, or individual.

This is Issue 9 of Put Ideas To Work, a biweekly newsletter currently discussing corporate venturing under constraint. If this issue was useful, consider sharing it with someone who manages an innovation function. The diagnostic works best when it prompts a conversation, not just a self-assessment.

Issue 8 explored stop authority and why corporate pilots rarely get killed. Issue 9 extends that logic to the portfolio level: stop authority is necessary but insufficient if no one has authority over the set.

The ecosystem’s capital stack was thin, its infrastructure underdeveloped, and its policy support inconsistent. If you wanted to build a large technology company, the common wisdom was that you would eventually need to go offshore.

But over the past eighteen months, a series of seemingly unrelated developments suggests something more structural may be happening.

Australia’s innovation ecosystem is quietly rewiring itself.

Not through a single policy announcement or a blockbuster funding round, but through a gradual expansion of the institutions, capital sources, and infrastructure that support innovation.

Individually, these developments appear to be incremental progress. Taken together, they point toward a more mature ecosystem emerging.

The capital stack is expanding.

Historically, venture capital has carried a large segment of the burden of startup financing in Australia. In doing so, it created a structural weakness. When venture markets slowed, as they did through 2022 and 2023, the ecosystem slowed with them.

Now new layers of capital are beginning to appear.

International venture debt and private credit providers are increasingly targeting Australian technology companies, offering non-dilutive financing to startups that have already demonstrated revenue traction. HSBC launched a dedicated venture debt offering in Australia in late 2023, initially allocating A$228 million to loans of A$10 million to A$30 million to late-stage venture-backed companies.¹ In August 2025, the bank expanded this with the launch of HSBC Innovation Banking in Australia, which HSBC described as the first specialised banking offering in the country dedicated to venture-backed businesses.²

More significantly, in March 2026, Silicon Valley growth lender Partners for Growth announced a new, later-stage technology private credit strategy with commitments exceeding A$250 million.³ The PFG Income Fund provides growth debt, asset-backed financing, and structured credit to later-stage Australian technology-enabled businesses, fintechs, and alternative lenders. Partners for Growth has operated in Australia since 2007 and has backed more than 85 local companies, including Employment Hero, Koala, and Bridgit.

This is a meaningful shift. Venture debt and private credit have not traditionally been common funding instruments for Australian tech startups chasing growth capital. As Partners for Growth noted, founders are becoming more deliberate about financing as their businesses scale, and many are incorporating structured private credit to support growth while preserving ownership and business flexibility.

At the same time, universities are launching their own investment vehicles designed to fund research spinouts at the earliest stages. In February 2026, UNSW committed A$35 million to research commercialisation, including a A$25 million Pre-Seed Fund for early-stage spinouts and a A$10 million investment in High Street Ventures, an independent venture capital fund supporting companies as they grow.⁴ The University of Sydney has also launched a A$25 million spinout fund.⁵ More than half of Australia’s 43 universities now have access to an investment fund that can help commercialise academic research. This is a penetration rate that surpasses both the United States (33%) and Europe (40%).⁶

Meanwhile, governments are entering the earliest stages of risk capital through commercialisation grants and sector-focused funds. The National Reconstruction Fund has allocated A$15 billion overall, with A$1 billion directed toward priority areas including renewables, medical technology, and advanced manufacturing.⁷ The Western Australian Government recently launched a A$45 million venture capital initiative expected to leverage A$150 million in new VC funds for local startups.⁸

The result is that Australia’s startup capital stack is beginning to look less like a single pipeline and more like a layered system. Founders now have access to a variety of grants, university-backed funds, venture capital, and increasingly, venture debt rather than only venture capital.

It is a subtle change over time, but an important one.

A maturing innovation ecosystem is defined not just by the presence of capital, but also by its diversity.

Infrastructure is becoming strategic.

Another shift underway is the expanding emphasis on technological infrastructure. In the early days of the startup ecosystem, the focus was almost entirely on founders and venture funding. Infrastructure rarely entered the conversation.

That is beginning to change.

Governments are increasingly directing capital toward data centres, compute infrastructure, and advanced technology capabilities. In June 2025, Amazon Web Services announced a A$20 billion investment in Australian data centres. This is one of the largest technology investments in the nation’s history.⁹ Microsoft had previously committed A$5 billion in late 2023 to broaden its footprint to 29 centres across Sydney, Melbourne, and Canberra.¹⁰

In March 2026, the National Reconstruction Fund Corporation made a A$200 million hybrid investment in ASX-listed Macquarie Technology Group to support the development of sovereign cloud services, AI-enabled cybersecurity capability, and new sovereign data facilities.¹¹ It was the NRF’s largest single technology sector investment to date. The funding is meant to support the accelerated use of sovereign cloud and AI by Australian government agencies, the Department of Defence, the defence industry, and critical infrastructure sectors. As NRF CEO David Gall noted, the investment fits squarely within the fund’s mandate by “building the country’s digital industrial capability.”

Meanwhile, global AI firms are signalling serious interest in Australia. In late March 2026, Anthropic signed a memorandum of understanding with the Australian government and announced it was “exploring investments in data centre infrastructure and energy throughout the country.”¹² The company, which confirmed Sydney as its fourth Asia-Pacific office following openings in Tokyo, Bengaluru, and Seoul, cited Australia’s renewable energy potential and pledge to AI safety as reasons for the partnership.

These investments are frequently framed through the lens of national security or economic resilience, but they likewise play an important role in shaping the innovation ecosystem. The Clean Energy Finance Corporation estimates the Australian data centre industry will attract between A$85 billion and A$135 billion in investment over the next decade.¹³

In March 2026, the Australian Government took the next step by releasing its expectations for data centre and AI infrastructure developers as part of the National AI Plan.¹⁴ The framework specifies five expectations covering national interest, energy transition, water sustainability, skills investment, and strengthening research and innovation. Critically, it expects hyperscalers to make compute available to Australian startups wanting to create Australian AI and to partner with the local innovation ecosystem.

In other words, innovation policy is increasingly appearing less like startup support and more like industrial strategy.

This raises an important question for the ecosystem: is Australia building a platform for AI creation, or is it primarily presenting itself as an AI consumer? The answer likely depends on whether the infrastructure investments translate into meaningful access for local startups and researchers, or whether they primarily serve the regional operations of global players.

That shift mirrors developments in the United States, Europe, and parts of Asia, where governments have begun to treat advanced technology infrastructure as an important asset.

Australia appears to be moving in the same direction.

Universities are becoming venture studios.

One interesting structural shift is taking place within universities.

or decades, universities have been central to the country’s research output but peripheral to its startup ecosystem. Commercialisation pathways were often slow, fragmented, or dependent on external venture capital. The current model is beginning to evolve.

Universities are now creating venture funds, incubators, and startup studios designed specifically to transform research into companies. UNSW, which describes itself as Australia’s leading entrepreneurial university based on spinout volume, launched 25 new spinout companies in 2025 and topped the Knowledge Commercialisation Australasia Survey of Commercialisation Outcomes from Public Research Report for the fourth consecutive year. ¹⁵

Uniseed, one of the world’s oldest university venture funds, covers more than 20% of Australian universities and has established a track record of converting academic research into commercially viable ventures. In 2025, its incoming CEO, Alastair Hick, called for more streamlining of venture capital investment to accelerate dealmaking following a spurt of new funds forming in the country.¹⁶ In Victoria, the state government’s A$2 billion Breakthrough Victoria fund is partnering with universities including Deakin, La Trobe, Monash, RMIT, and Swinburne to set up dedicated commercialisation funds. ¹⁷

This reflects a broader global trend in which universities increasingly operate as entrepreneurial platforms rather than purely academic institutions.

If this trend continues, the origin point for many of Australia’s most significant startups may shift from garages and coworking spaces to research laboratories.

That could be particularly important for deep-tech sectors such as artificial intelligence, advanced materials, climate technology, and biotechnology, where the underlying intellectual property often originates in academic research.

Australia has long had world-class research institutions. The challenge has always been translating that research into commercial outcomes.

University-backed venture programs may finally start to close that gap.

Global capital is still decisive.

Although these encouraging structural changes, one constant remains: international investors still drive the largest growth rounds in Australian startups.

According to the State of Australian Startup Funding 2025 report by Cut Through Venture and Folklore Ventures, 66% of all deals in 2025 included at least one international investor, up from 57% in 2024. At Series A and beyond, offshore investor participation has become the standard rather than the exception. Global firms, including Andreessen Horowitz, Bessemer Venture Partners, and Lightspeed Venture Partners, all backed Australian-founded companies during 2025.¹⁸

The pattern continues into 2026. In March, stablecoin payments platform KAST, while not Australian-headquartered, raised US$80 million in Series A funding led by US investors QED Investors and Left Lane Capital, with participation from Peak XV Partners, HSG, and DST Global Partners.¹⁹ Founded by former Circle executive Raagulan Pathy, the Singapore-based company illustrates the wider pattern: the round valued it at US$600 million, casting it as a potential unicorn. KAST, which has scaled to more than one million users and processes nearly US$5 billion in annualised transaction volume, expects its annual revenue run rate to reach US$100 million in 2026.

Founders cited larger cheque sizes, deeper follow-on capacity, and support for global expansion as the primary reasons for seeking international capital.

This pattern is not necessarily a weakness. In many cases, global capital accelerates growth and connects companies to international markets. Australia’s major domestic venture firms, including Blackbird Ventures, Square Peg Capital, and Airtree Ventures, continue to raise significant funds and often co-invest alongside international partners. In February 2026, Square Peg completed the first close on its Fund 6 and Opportunities Fund 3, locking in A$650 million from institutional investors.²⁰

But it does highlight an ongoing challenge for the ecosystem.

Australia has become increasingly effective at producing promising startups. Australian startups raised A$5.4 billion across 390 deals in 2025, a 31% increase year-on-year and the third-largest funding year on record.²¹

The harder question is whether the ecosystem can consistently support those companies through the scale-up phase without relying on external capital.

The expanding capital stack may eventually help address that challenge, but it is still early.

The fragmentation question

The optimistic reading of these developments is that Australia is building a more mature, diversified innovation ecosystem. But there is a less comfortable interpretation: the ecosystem may be diversifying without integrating.

Consider the evidence of continued stress beneath the headline numbers. According to the State of Australian Startup Funding 2025 report, 46% of investors surveyed saw at least one portfolio company shut down during the year. 77% reported layoffs across their portfolios. Bridge rounds remained common as companies extended their runways rather than raising full-priced rounds during the recovery period.²²

These figures show the delayed effects of the 2022-2023 funding contraction. Companies that raised at elevated valuations during the boom and then struggled to grow into those valuations continued to face difficult choices throughout 2025.

More structurally, the report reveals a two-speed market. A small number of mega-rounds lifted headline totals, while median deal sizes rose partly because fewer very early-stage rounds are happening. The pre-seed and seed funding pipeline, which produces tomorrow’s Series A companies, has shown weakness for four consecutive quarters.²³

Capital is also concentrated by sector. AI-at-the-core companies commanded valuation premiums and sharper competition, while non-AI deals were priced within tighter, more disciplined bands. 15 of 25 tracked sectors saw a fall in capital raised compared to 2024.²⁴

Meanwhile, the proliferation of new capital sources, university funds, government programs, venture debt providers, and state-backed commercialisation vehicles creates coordination challenges. Uniseed’s incoming CEO, Alastair Hick, identified this directly, highlighting that syndicates are forming with multiple investors. Each brings different investment committees, decision-making procedures, and views on commercial and legal terms. The result is friction that slows dealmaking precisely when the ecosystem needs speed. ²⁵

The risk is not that any single initiative fails. It is that Australia builds multiple parallel systems, university spinout programs here, government infrastructure funds there, private credit vehicles elsewhere, without the connective tissue to move companies fluently from one stage to the next.

A diversified capital stack is valuable. A fragmented one is not.

A quiet transition

None of these developments, on their own, represents a dramatic turning point.

There has been no single moment where the Australian startup ecosystem suddenly became more mature or globally competitive.

Instead, the transformation appears to be happening through a series of incremental shifts.

New forms of capital are entering the market. Universities are becoming more entrepreneurial. Governments are investing in strategic technology infrastructure. Global companies are expanding their presence locally. According to IMARC Group, the Australian venture capital market reached US$4.5 billion in 2025 and is projected to reach US$10.3 billion by 2034, exhibiting a CAGR of 8.74%.²⁶

Taken together, these signals suggest that Australia’s innovation ecosystem may be entering a new phase.

The first phase of the ecosystem involved proving that world-class startups could emerge from Australia. The next phase may be about building the institutions, capital markets, and infrastructure required to sustain them.

If that transition succeeds, the defining characteristic of the Australian startup ecosystem will no longer be that its best companies eventually leave.

It will be so that they can scale where they started. And that would denote a significant evolution in how Australia turns ideas into work.

A final thought

The signals are there. The capital stack is broadening. Universities are stepping up. Infrastructure is becoming strategic. But whether these shifts connect into a coherent system or remain a collection of parallel initiatives is still unfolding.

So I will leave the question with you:

Notes & Sources

1. HSBC, “HSBC launches venture debt offer for Australian scaleups,” November 2023

2. HSBC, "HSBC Innovation Banking launches in Australia," August 2025

3. Partners for Growth / Australian FinTech, "Partners for Growth launches A$250m+ growth debt fund for Australian tech and fintech companies," March 2026

4. UNSW Sydney, "NSW Treasurer praises UNSW spinouts at fund launch," February 2026

5. University of Sydney, "$25m fund helps bring research from the lab to market," April 2025

6. Global Venturing, "Half of Australian universities have a spinout fund, ahead of US and Europe," August 2025

7. The Investor Standard, "Australia Startup Funding Surge, 2026 Grants and ASX Implications," February 2026

8. Inspirepreneur Magazine, "Top Venture Capital Firms in Australia 2026," March 2026

9. Australian Stock Report, "Australia's Data Centre Boom: ASX Stocks Powering the AI Revolution," December 2025

10. Microsoft, "Microsoft announces A$5 billion investment in computing capacity and capability to help Australia seize the AI era," October 2023

11. National Reconstruction Fund Corporation, "National Reconstruction Fund invests in Macquarie Technology Group to strengthen Australia's sovereign cloud and cybersecurity capabilities," March 2026

12. Australian Financial Review, "AI giant Anthropic says 'exploring' Australia data centre investments," April 2026

13. Pinsent Masons, "Australian government unveils prioritised support for 'national interest' data centres," April 2026

14. Australian Government Department of Industry, Science and Resources, "Expectations of data centres and AI infrastructure developers," March 2026

15. UNSW Sydney, “NSW Treasurer praises UNSW spinouts at fund launch,” February 2026

16. Global Venturing, "Australia needs to move faster on spinning out companies – Uniseed new head Hick," November 2025

17. Global Venturing, "Half of Australian universities have a spinout fund — ahead of US and Europe," August 2025

18. Cut Through Venture & Folklore Ventures, “State of Australian Startup Funding 2025,” February 2026

19. CoinDesk / KAST, "Stablecoin payments platform KAST raises $80 million Series A at $600 million valuation," March 2026

20. Capital Brief, "Square Peg locks in $650m as new fund vintage hits first close," February 2026

21. Cut Through Venture & Folklore Ventures, “State of Australian Startup Funding 2025,” February 2026

22. Cut Through Venture & Folklore Ventures, "State of Australian Startup Funding 2025," February 2026

23. Cut Through Venture & Folklore Ventures, “State of Australian Startup Funding 2025,” February 2026

24. Cut Through Venture & Folklore Ventures, "State of Australian Startup Funding 2025," February 2026

25. Global Venturing, “Australia needs to move faster on spinning out companies – Uniseed new head Hick,” November 2025

26. IMARC Group, "Australia Venture Capital Market Report 2025-2034

This article is based on the author's professional experience and interpretation of publicly available information. It is provided for general informational purposes only and does not constitute advice. Any views expressed are the author's own and do not refer to any specific organisation, program, or individual.

Most corporate innovation portfolios contain at least one idea, one venture, one initiative that everyone privately acknowledges is not working, but no one stops it.

Sometimes it is the quiet kind. Modestly funded, never celebrated, simply persisting. Quarter after quarter, it appears on the slide, absorbs a small allocation, and generates just enough activity to avoid the question no one wants to answer.

But there is a second variant that is harder to name and more expensive to ignore. This one is not starved of resources. It has dedicated headcount, meaningful budget, and sometimes even executive sponsorship. The team is busy. The updates are polished. And yet nothing has structurally moved. No market validation has landed. No revenue has materialised. No one has narrowed the scope or made a commitment that would actually put the initiative at risk of being tested by reality.

The resources keep flowing, not because the evidence justifies them. They continue because the commitment was made publicly. Now the sponsor’s credibility is attached to its continuation. The larger the investment, the harder it becomes to determine whether it is still warranted. This version of the zombie pilot does not appear to be neglected. It looks like conviction. That is what makes it dangerous.

Both are zombie pilots.

One starves quietly in the margin while the other feeds comfortably at the centre. Neither is alive in any meaningful operational sense. Neither is dead because no one has the authority, incentive, or structural mechanism to kill it. Together, they represent the most common and least discussed failure mode in corporate innovation governance.

The interesting question is not why these pilots fail. It is why they do not stop.

This is not a small problem. IDC’s research with Lenovo found that for every 33 proofs of concept launched across enterprise environments, only 4 reached production. The rest were not cancelled. They had not progressed. They existed in what the researchers described as a permanently provisional state, consuming budget and eroding executive confidence without ever reaching a clear resolution. That description is precise. It is also a description of a governance failure, not a technology failure.

Built to start. Not built to stop.

The obvious explanation is sunk cost. Someone invested political capital to launch the pilot, and stopping it publicly means writing off that investment. But sunk cost is a psychological explanation. It is incomplete. The deeper problem is structural.

Most innovation governance systems are designed to do one thing well … approve. It might not always be as efficient as operators would like, but of there are clear stage gates for funding. They have review boards for launch. They have sponsors who champion initiatives through internal resistance. The entire architecture is oriented around getting things started.

In Issue #7, I examined why well-resourced innovation functions still fail to produce ventures. Systems designed around activity metrics rather than execution outcomes create what amounts to “innovation theatre”. The zombie pilot is a specific expression of that same structural condition. The function can start things. It can run things. What it cannot do is stop things, because the stop authority was never built into the governance architecture.

Stop authority, the clearly assigned right to kill an initiative, is the most absent governance capability in corporate innovation. Not because leaders lack courage, but because the system was never designed to require it. There is no stage gate for cessation. No review trigger that asks “should this still exist?” No role whose explicit accountability includes recommending termination.

Multiple research programmes have identified the same gap from different angles. What researchers at RT Insights, Bain Capital Ventures, and others independently describe as an “ownership vacuum,” where the experiment has a sponsor but the outcome does not have an owner, is the structural condition that allows zombie pilots to persist. Without an owner accountable for the outcome, there is no one with the standing to recommend cessation. The vacuum is not an oversight. It is a predictable result of governance systems that were designed to launch initiatives, not to resolve them.

Without a stop authority, the default state of any initiative is continuation.

This matters because continuing is not neutral. Every zombie pilot, whether it is starving in the margin or feeding at the centre, consumes more than its line-item budget. It occupies a portfolio slot that signals “we are already doing something in that space.” It absorbs management attention, even if only the attention required to avoid deciding it. And it provides cover for the sponsor who launched it, the executive who approved it, and the team that would otherwise need redeployment.

The well-funded variant compounds this. The scale of investment creates its own justification, and the more the organisation has committed, the harder it becomes to ask whether the commitment is still warranted. At some point, the sunk cost becomes the strategy.

The zombie pilot does not survive because it is succeeding. It survives because the cost of stopping it is borne by an individual, while the cost of continuing the venture is distributed across the organisation. Stopping requires someone to raise their hand, absorb the political risk, and trigger a process that probably does not exist.

Continuing requires nothing. It is the organisational equivalent of leaving a subscription running, because cancelling it means finding the login details.

Courage is not the fix.

The implication is not “be braver about killing pilots.” That is a mindset recommendation disguised as strategy, and it misses the point entirely. If stopping required only courage, organisations with strong leaders would never have zombie pilots. They do.

The implication is that stop authority must be designed into the governance system with the same rigour as start authority. It needs to be structural, not heroic.

This means several things in practice.

1. Every pilot approved should have a pre-committed termination trigger.
   Not a vague milestone review, but a specific condition under which the default shifts from persistence to cessation. The question at review should not be “is there a reason to stop this?” It should be “has this earned the right to continue?” The burden of proof matters enormously. When continuation remains the default, evidence of failure must accumulate to an extraordinary threshold before anyone acts. When cessation is the default, even modest initiatives must periodically demonstrate that they deserve the resources they consume.

2. The stop authority must be assigned to a role rather than left to emerge.
   Someone in the governance structure needs the explicit right, and the explicit expectation, to recommend kills. Not as a punishment. Not as a failure of sponsorship. As a routine function of portfolio discipline. The absence of this role is why zombie pilots cluster. No one’s job includes the line item “identify initiatives that should no longer exist.”

3. The cost of continuation must be made visible.
   Zombie pilots persist partly because their cost is illegible. The budget line looks modest. But the portfolio slot they occupy, the strategic space they block, the opportunity cost of the team’s time, the signal they send about what the organisation tolerates. However, none of this shows on a dashboard. Making the full cost of continuation visible is a governance design choice. It does not happen by accident, and its absence is not neutral.

The deeper pattern here extends well beyond innovation portfolios.

Organisations are generally better at creating than at ceasing. They are better at launching than at landing. The muscles for initiation are well-developed. The muscles for termination are atrophied, not because of disuse, but because they were never built.

Having a stop authority is not an optional governance refinement. It is a structural prerequisite for portfolio discipline. Without it, every portfolio will accumulate drag. Not because the people are wrong, but because the system makes stopping harder than continuing.

And in any system where stopping is harder than continuing, things that should stop will not.

The Stop Authority Diagnostic

The pattern described above can be diagnosed. Pilots that persist not because they are succeeding but because stopping them is structurally harder than continuing. It does not require a transformation programme or a governance overhaul to identify. It requires five questions.

These questions are not designed to evaluate whether a specific pilot is good or bad. Rather, they are designed to assess whether your governance system has the structural capacity to stop anything.

Is a stop authority assigned?

For any active initiative or venture in the portfolio, can you name the person whose role includes the explicit authority to recommend termination?

Not the sponsor.

Not the executive who approved it.

A role with the standing to say “this should no longer exist” without that statement being read as a political act. If you cannot name that person, the stop authority is absent. It does not matter how strong your leaders are. The capability has not been built.

Where does the burden of proof sit?

When an initiative comes up for review, what is the default?

Does the team need to demonstrate that the pilot has earned continuation, or does someone need to build a case for stopping it?

If the burden of proof sits with cessation, if you need a reason to stop but not a reason to continue, the system is architecturally biased toward accumulation.

Zombie pilots are the predictable result.

Do termination triggers exist before launch?

When the pilot was approved, was there a pre-committed condition under which it would end?

Not a milestone.

Not a KPI target.

A specific observable condition: “if X has not occurred by Y, the default is termination.” If the answer is no, the pilot was launched with an open-ended claim on resources.

Every venture pursued without a termination trigger is a future zombie candidate.

Is the full cost of continuation visible?

Can you see, on a dashboard, in a review pack, anywhere, the total cost of an active pilot beyond its budget line?

The portfolio slot it occupies. The strategic space it blocks. The management attention it absorbs. The opportunity cost of the team assigned to it. If only the direct budget is visible, the cost of continuation remains illegible, and illegible costs cannot drive decisions.

When was the last kill?

Not a pivot. Not a “strategic redirection.” Not a quiet de-funding that let something expire without anyone acknowledging what happened.

An explicit, deliberate decision to stop an initiative and communicate that decision as a governance outcome. If you cannot point to one in the past twelve months, the stop muscle has not been exercised. It may not exist.

Understanding the pattern

These five questions do not produce a score, but rather they produce a structural picture.

If you answered “no” to three or more, your governance system lacks functional stop authority. You have a system that can start things, but cannot stop them. Your portfolio will accumulate drag, not because of bad judgement, but because the architecture makes continuation the path of least resistance.

Each gap the diagnostic reveals maps to a specific governance design choice: assigning the authority, shifting the burden, pre-committing the trigger, or surfacing the cost. These are not cultural goals. They are built decisions.

The fix is not about becoming more “ruthless” or “disciplined” in the abstract. It is about building the specific governance capabilities that make stopping as operationally routine as starting.

The muscles that were never built

Zombie pilots are a symptom of a bigger issue. Organisations have spent decades improving the architecture of initiation with stage gates, investment committees, innovation sprints, accelerator programmes and even venture boards. The infrastructure for starting things is sophisticated, well-resourced, and culturally celebrated. However, the infrastructure for stopping things barely exists.

This asymmetry is not limited to innovation portfolios. It appears in product lines that no longer serve the strategy. In committees that outlived their purpose. In reporting structures that persist because no one has the standing to dissolve them. The inability to cease is an organisational condition, and innovation portfolios are where it becomes most visible, because the gap between activity and value is hardest to ignore.

Scott Kirsner observed in Harvard Business Review that when a CEO reveals a major innovation initiative, you should mark your calendar. Three years later, many of these ventures will have quietly expired without an obituary. That quiet expiry is the zombie pilot’s final form. Not a dramatic failure. Not an explicit decision. Just a slow fade that no one is accountable for, because the system never assigned accountability for cessation in the first place.

I have written separately about how this pattern is playing out across Australia’s government, enterprise, and venture portfolios, where audit bodies and digital transformation agencies have documented the same structural failure for years.

The language varies, including “Pilotitis” or “Pilot purgatory.” The underlying condition is identical, that systems that can start things but cannot force a scale-or-stop decision once a pilot has done the job it was meant to do.

Execution discipline is not only about doing things well. It is about stopping things cleanly.

When stopping an initiative is structurally harder than persisting with it, the portfolio does not have a performance problem. It has a governance problem.

References & Further Reading

• IDC, research undertaken in partnership with Lenovo, CIO Playbook 2025: 88% of AI proofs of concept fail to reach production. https://www.cio.com/article/3850763/88-of-ai-pilots-fail-to-reach-production-but-thats-not-all-on-it.html

• Scott Kirsner, The Stage Where Most Innovation Projects Fail, Harvard Business Review, 2017. https://hbr.org/2017/04/the-stage-where-most-innovation-projects-fail

• SoftwareSeni, The Enterprise AI Pilot Purgatory Problem: What the Statistics Actually Tell Us, 2026. Synthesises research from IDC, MIT NANDA, McKinsey, BCG, RT Insights, Bain Capital Ventures, and others on the “ownership vacuum” pattern. https://www.softwareseni.com/the-enterprise-ai-pilot-purgatory-problem-what-the-statistics-actually-tell-us/

• The Venture Operator, Observation: Australia’s Zombie Pilot Problem, Put Ideas To Work, 2026. https://www.putideastowork.com/p/observation-australias-zombie-pilot

• The Venture Operator, Issue 07: When Nothing Changes, Put Ideas To Work, 2026. https://www.putideastowork.com/p/when-nothing-changes

This article is based on the author's professional experience and interpretation of publicly available information. It is provided for general informational purposes only and does not constitute advice. Any views expressed are the author's own and do not refer to any specific organisation, program, or individual.

This is Issue 08 of Put Ideas To Work. It builds on the structural patterns explored in Issue 07: When Nothing Changes, which examined why well-resourced innovation functions still fail to produce ventures. If the Stop Authority Diagnostic is useful, share it with someone who runs a portfolio review. It takes five minutes and the pattern will be obvious. And if you are not yet subscribed, Put Ideas To Work publishes biweekly. Each issue builds a diagnostic framework for venture execution under constraint.

Six weeks later, nothing has structurally changed.

No capital moved. No initiative received dedicated resourcing. No decision rights shifted. The teams are still operating on the same budgets, with the same headcount, inside the same reporting lines.

The showcase was a success. The innovation program is active, but nothing has happened to change the trajectory of a single venture within the organisation.

This is not a failure of effort or intent. It is a structural condition. It is innovation theatre.

Activity without consequence

Innovation theatre occurs when innovation functions are designed around activity metrics rather than execution outcomes.

The activity is real. Ideas are generated, workshops are held, pilots are built, and teams prepare status updates on schedule. But the structural indicators of execution remain unchanged.

No additional capital has been reallocated, authority and decision rights have not shifted, and scope has not narrowed. In summary, nothing has stopped or significantly changed to double down on the bets made.

The innovation function exists inside the organisation’s communication layer, presentations, updates, reports, showcases, but outside its decision layer. It does not influence how budgets are constructed, how resources are deployed, or how strategic priorities are adjusted.

Steve Blank identified this pattern in Harvard Business Review in 2019, describing how organisations adopt innovation activities, hackathons, workshops, and design sprints, that produce the appearance of innovation without its structural consequences. He distinguished between organisational theatre, innovation theatre, and process theatre. What he named as a behavioural tendency is, more precisely, a governance design problem. The activities are real. The structural authority to act on what they produce is not.

This creates a peculiar dynamic. The function appears healthy on the surface. Internally, the teams running initiatives often sense that something is missing, but struggle to articulate exactly what.

What is missing is execution authority.

Innovation without execution authority is not a program, nor a priority. It is a marketing newsletter.

Why does the system reward appearance?

Innovation mandates are often issued by leadership but not structurally empowered. A CEO or board declares that innovation is a strategic priority. This leads to the formation of a team or teams and the issuance of mandates, but the organisation’s decision architecture does not change to accommodate it.

The innovation operation receives permission to explore, but not the authority to execute. It can generate ideas, run experiments, and build prototypes. But it cannot reallocate capital, reassign talent, narrow the portfolio, or stop initiatives that are not working.

This is not a personality problem. It is an incentive and governance design problem.

Innovation teams are typically measured on:

• Number of ideas generated or submitted.

• Number of workshops and hackathons were conducted.

• Pilots launched, or partners engaged.

• Presentations delivered to leadership.

• Internal participation and engagement rates.

• Progress is reported as stakeholder alignment, strategic conversations, or engagement quality, measures that are difficult to challenge precisely because they are difficult to define.

These are activity metrics that measure the function’s performance, not the performance of the ventures it pursues.

Execution metrics look different and operate on two levels. The first level measures whether the system has reorganised. Whether signals actually changed how the organisation behaves:

• Capital reallocated based on evidence.

• Initiatives stopped when signals decayed.

• Decision rights assigned to venture leads.

• Resources concentrated on compounding signals.

• Scope narrowed as conviction increased.

The second level measures whether that reorganisation produced results:

• Ventures that generated measurable commercial outcomes, revenue, customers acquired, contracts signed, or return on invested capital.

• Time from validated signal to resourced commitment, the speed at which the system converts evidence into structural action.

Most innovation functions track neither level. Some may track the first without the second, which creates structural movement without accountability for outcomes. The combination is what matters; did the system reorganise, and did that reorganisation produce a venture, regardless of whether the method used was build, invest or partner, worth the resources it consumed?

In most corporate innovation functions, no one is measured on either. And what is not measured is rarely prioritised.

The result is a system that rewards the appearance of innovation without requiring its structural consequences or its commercial outcomes.

A Structural Disconnect

There is a pattern I have seen repeated across large organisations, in financial services, resources, government-linked enterprises, and increasingly inside universities, establishing venture mandates.

An innovation team identifies a genuine opportunity with promising signals identified early. The team is motivated, and the work is credible. But when the initiative reaches the point where it needs structural support, dedicated capital, decision authority, and talent reallocation, the organisation does not respond.

Not because leadership disagrees or the evidence is weak, but because the system is not designed to convert innovation signals into structural decisions when consequences start to matter, to the executive sponsors and the organisation broadly.

The triple mandate.

Corporate innovation functions are often expected to operate across multiple roles simultaneously. In a startup ecosystem, these functions are typically separated: capital allocators decide where funding flows, venture builders build ventures, and operators execute under uncertainty. Within a corporate innovation function, one team often handles all three. They allocate “budgetted” capital across a portfolio of initiatives, build internal experiments/ventures, and are expected to deliver execution discipline that turns signals into structural commitment.

That triple mandate creates a specific governance tension. When the same team is responsible for funding decisions (within a stated risk tolerance), exploration venture creation, and execution oversight, the execution layer almost always suffers. It is the least visible of the three roles and the least rewarded. Capital allocation decisions get board attention. New ventures get showcased. Execution discipline, narrowing scope, stopping initiatives, and reallocating resources happen quietly, if at all.

Given the matrixed structure of most large organisations, this problem compounds. Even where innovation teams have capable people and clear intent, the decisions required to convert a validated signal into a resourced venture do not rest solely within the innovation function. They are distributed across the organisation.

Capital reallocation requires finance and strategic planning approval. Governance sign-off involves a separate committee with its own cadence and risk appetite. Legal review follows its own timeline. Risk assessment introduces additional conditions. Procurement, if an external partner or vendor is involved, adds another layer. Each of these functions operates with different incentives, different timelines, and critically, no shared accountability for venture outcomes.

The innovation team may have identified the signal, built the business case, and demonstrated early traction. But the decisions required to act on that evidence are scattered across five or six organisational functions, none of which are measured on whether the venture succeeds. Each can slow or stop progress, as none has the mandate to accelerate it.

This is not bureaucracy for its own sake. These functions exist for legitimate reasons: risk management, capital stewardship, and legal compliance. The problem is that they were designed to govern established business operations, not to coordinate around new-venture timelines for unexpected, uncertain opportunities where speed and evidence-based resource allocation are critical.

Budget cycles are annual, and headcount is planned and allocated twelve months in advance. Governance committees meet quarterly, and legal review queues are measured in weeks. The venture’s signal is compounding now.

By the time the system responds, the window may have narrowed or closed.

And so the innovation team continues to operate in the margin. It can run experiments. It can present results. But it cannot trigger the structural changes that would turn a promising initiative into a funded venture with execution authority, because those changes require coordination across functions that were never designed to move at venture speed.

This is the structural disconnect at the heart of innovation theatre. The front end of innovation, ideation, exploration, and experimentation, is well resourced and largely contained within the innovation function. The back end, commitment, resource movement, and governance escalation are fragmented across the organisation, operating on fundamentally different rhythms.

The evidence supports this. McKinsey has reported that nearly two-thirds of organisations remain stuck in pilot mode, unable to scale projects across the enterprise. The framing is often about technology adoption or digital transformation. Still, the structural pattern is identical: organisations that are effective at launching experiments but are unable to convert them into scaled execution. The bottleneck is not the front end. It is the transition from exploration to structural commitment, a transition that requires organisational coordination, which the system was not built to handle.

The front end of corporate innovation is well built and largely self-contained. The back end, where signals become structural commitment, is fragmented across the organisation. That is where ventures stall.

The Quiet Cost

Innovation theatre does not produce dramatic failures. That is part of why it persists.

There is no crisis point, no public failure, no sudden loss. The function continues, and updates are positive. Activity is sustained, and from the outside, everything appears functional. The cost is quieter and cumulative.

BCG’s 2024 Most Innovative Companies report quantified this gap. Eighty-three per cent of senior executives now rank innovation among their top three priorities. Yet only 3 per cent of companies qualified as innovation-ready, a sharp decline from 20 per cent just 2 years earlier. The aspiration has been rising, but the ability to execute has been falling. A lack of ideas or investment does not explain that divergence. It is explained by the structural gap between innovation activity and the authority to execute.

Talent attrition is the earliest signal. High-capability operators inside innovation teams eventually recognise the structural ceiling. They leave, not because they are disengaged, but because they have learned that the system will not convert their work into execution. The organisation loses its most execution-oriented people first.

Organisational credibility erodes next. When successive cohorts of initiatives fail to produce structural outcomes, leadership begins to question the function’s value. External credibility follows. Startup founders and partners who engage with corporate venturing functions learn quickly which organisations have execution authority and which are performing the function without it. In ecosystems like Australia, where the corporate innovation community is relatively concentrated, this reputation moves fast.

The cumulative cost is not the money spent on the function. It is the ventures that were not built, the talent that left, and the organisational patience that is consumed without producing structural change.

From Communications to Execution

The shift is not about running fewer initiatives or generating fewer ideas. Exploration has genuine value. The shift is about what the organisation measures and what authority the innovation function holds.

The diagnostic question is simple:

What capital, authority, or resources moved because of this initiative?

If the answer is nothing, the function produced content, not execution. The initiative may have generated learning, relationships, or internal visibility. Those are not worthless, but they are not venture creation.

For corporate innovation functions to produce ventures rather than activity, three conditions need to be present:

Execution authority must exist within the function. Someone within the innovation function must be able to recommend capital reallocation, talent movement, or scope narrowing. That recommendation must connect to a decision-maker who can act on it within the venture’s timeline, not the organisation’s planning cycle.

Measurement must shift from activity to structural consequence. If the function is measured by how many ideas it generates, it will generate ideas. If it is measured by how many initiatives received dedicated resources, had their scope narrowed, or were stopped based on evidence, it will produce execution discipline.

The stop authority must be safe. Innovation theatre persists partly because stopping is politically expensive. Ending a pilot, deprioritising an initiative, or narrowing the portfolio creates visibility. If that visibility is punished rather than rewarded, the rational response is to continue everything. The system must make stopping as structurally safe as starting.

Let’s Execute

This is not a strategy exercise. It is a structural audit you can run this week.

Answer these five questions about your innovation function. Answer them honestly, not optimistically.

1. Does anyone inside the innovation function have the authority to recommend resource reallocation?

Not in theory. In practice. Has it happened in the last twelve months? If the answer is no, the function operates inside the communication layer, not the decision layer.

2. When was the last time an initiative was stopped based on evidence?

Not paused. Not “deprioritised.” Stopped. If nothing has been stopped, the function lacks kill discipline. Every active initiative is consuming resources that could be concentrated on stronger signals.

3. What changed structurally after your last showcase or review?

Did capital move? Did headcount shift? Did decision rights change? If the answer to all three is no, the review is a communication event, not a decision event.

4. How is the innovation function measured?

List the metrics. Separate them into two categories: activity metrics (ideas generated, workshops held, pilots launched) and execution metrics (capital reallocated, initiatives stopped, resources concentrated). Count each column. The ratio tells you what the function is designed to produce.

5. If your strongest initiative needed dedicated resources next month, could the system deliver them?

Not next budget cycle. Next month. If the answer is no, the organisation’s resource clock runs on a fundamentally different cadence from its venture clock. That mismatch is where promising initiatives stall.

If three or more of these answers reveal structural gaps, the function is not yet designed to produce ventures. It is designed to produce activity.

That is not a judgement of the people running it. It is a description of the system they operate within.

A Closing Thought

Corporate innovation functions inside large organisations are often staffed by capable people doing credible work under significant constraints. The problem is rarely effort, intent, or even the quality of ideas.

The problem is that the system around them was not designed to convert their work into structural change.

Execution authority is not a reward for proving yourself. It is a precondition for the production of ventures. Without it, even the strongest signals remain observations rather than decisions.

Ideas do not scale. Execution does. And execution begins when something in the structure actually moves.

What’s coming next? Execution authority is one structural gap. But even when functions have some authority, individual initiatives can persist long past the point where signals justify continuation. The next issue examines the most common expression of this: the corporate pilot that cannot die. Not because it is succeeding, but because stopping it is structurally harder than continuing.

This article draws on patterns observed across corporate venturing and innovation functions, startups, venture studios, and university commercialisation environments. Individual context matters.

For example, imagine a seed-stage SaaS startup. Growth has been uneven for months; churn is unpredictable, and the team is trying out several acquisition channels at once. The product roadmap remains broad to keep options open.

Then things start to change. One customer segment renews at much higher rates. Expansion revenue shows up without much extra effort. Support tickets from this group drop while their engagement goes up.

It is not a dramatic shift, but it is steady. The signal is clear.

The temptation is to notice the signal but keep running all current projects, hold onto every option, hedge your bets, and keep experimenting in parallel. But a signal only counts if it leads to action, like narrowing your focus, moving capital, or shifting your team’s attention.

• Low-performing acquisition experiments are shut down.

• Product capacity is concentrated around this segment.

• Marketing spend is redirected.

• Other feature bets are paused.

Making a commitment raises your exposure and changes how you handle risk.

This applies both when you are deciding whether to commit resources based on market signals and when you are following through on that commitment.

The tougher question comes next: If making commitments in uncertain times is the real work, who’s responsible for making sure it’s done well?

Signals Do Not Execute Themselves

Signals are open to interpretation, but execution depends on the structure.

• A customer cohort responds.

• Retention stabilises.

• Unit economics improves.

These are just inputs; they do not automatically reorganise teams, change budgets, or clarify who’s in charge. Many early-stage startups and innovation teams think that once something is validated, disciplined execution will just follow.

But that is not the case.

The market can change, but systems will not adapt unless someone actively reconfigures them.

If you do not reorganise your structure, commitment just becomes a story you tell, which leads to drift over time.

Signals do not turn into action on their own. Systems make execution happen.

Venture Operator as a Function

The Venture Operator is not just a job title. It’s about having someone accountable for structure when exposure grows faster than certainty in how capital is allocated. This role is responsible for making the necessary changes.

This responsibility might fall to a founder, a venture lead, a general manager, a board member, or a capital partner. When it’s clearly defined, escalation is straightforward. When it is missing, things get more ambiguous.

This role exists to turn a signal into real action:

• What narrows?

• What stops?

• What moves?

• Who decides?

• When is it reviewed again?

Without decision authority, this function becomes mere coordination.
Without a “stop” authority, it defaults to optimism.
Without capital reallocation power, it is reduced to an advisory role.

This is not just general management. It comes into play at key turning points, when spending goes up before you have certainty. Discipline won’t remove uncertainty, but it makes sure you deal with it on purpose.

With this structure, commitment turns into real action. Without it, commitment is just for how.

Commitment Lacking Re-organisation

Commitment increases burn against uncertainty. Exposure rises immediately, whether the system changes or not. The risk is not that commitment is wrong. The real risk is that you start spending faster, but your structure is still set up to keep all options open.

That is when dilution starts, not equity dilution, but structural dilution. This means your capital gets spread out, and decision-making becomes less clear. In short, you start to drift.

Drift usually is not caused by bad signals. It happens because structural changes are too slow.

• Scope stays broad.

• Resources remain spread thin.

• Decision rights remain unclear.

• Governance remains informal.

• Cadence is inconsistent.

• And capital moves faster than structure.

In this setup, good news can make you overconfident, while bad news makes you defensive. Neither leads to disciplined changes. Reorganising is the price you pay for making a commitment.

If you do not tighten your structure, your conviction is just for show.

The Cost of Over-Optionality

Keeping your options open is often seen as smart, especially early in the process. But too much optionality just makes things more complicated.

• Every active initiative increases coordination cost.

• Every preserved option dilutes signal precision.

• Every deferred decision slows capital movement.

Optionality can make you feel comfortable, but it rarely guarantees results. In environments where capital is tight, too much optionality is costly. It spreads your resources thin, muddies accountability, and slows down changes needed.

Focusing on your efforts is not about being aggressive, it is about being disciplined.

Incentive Asymmetry

Structural fragility is usually not an accident. In many systems, it feels easier to let things drift than to make changes. People fear losing status, being blamed, or admitting something isn’t working, and these emotions create strong barriers. Leaders often avoid tough decisions, hoping new evidence will appear and save them from the discomfort of making a visible stop or reallocation. The system keeps moving, not because the evidence is unclear, but because changing direction feels emotionally costly.

• Stopping creates visibility.

• Narrowing the scope creates risk.

• Reallocating capital creates political exposure.

• Ending an initiative creates reputational friction.

• Continuation appears safer.

This imbalance explains why it’s rare for someone to have the authority to stop things, and why optionality lasts longer than it should. Mature governance solves this by making disciplined changes safer than letting things drift.

Capital Depth Changes Consequence

Structural discipline matters in any venture environment. It cannot make up for a weak market, but it does prevent avoidable structural fragility.

The amount of capital you have affects the outcome.

In ecosystems with plenty of late-stage capital, inefficiency can be absorbed. Optionality can last longer. Governance immaturity can survive for a few more quarters.

Australia has less follow-on capital despite its ambition. The domestic market is smaller, with tighter error margins and stronger signaling effects. When startups face a big change in capital, like FinTechs relying on international funding that suddenly dries up, their cash runway shrinks fast, forcing a year’s planned growth into just a few months. In these conditions, missing even one milestone can mean the difference between recalibrating and shutting down.

In this environment, letting things drift burn through your runway even faster.

Structural discipline doesn’t guarantee success, but without it, capital-constrained systems will always be fragile. This isn’t just an opinion; it’s a fact about how capital works.

When there’s less follow-on capital than ambition, your ability to adapt quickly becomes a key advantage.

Structural Discipline at Inflection

Inflection points are rarely dramatic. Usually, there are quiet shifts as evidence builds up.

• Retention stabilises.

• CAC improves.

• Pipeline quality sharpens.

• Sales cycles compress and so on.

Just interpreting signals does not drive change. Structural discipline at inflection needs five things:

1. Clear signal ownership

2. Defined decision rights

3. Visible resource movement

4. Explicit stop authority

5. Fixed cadence for evidence interpretation

Without these, an inflection point turns into a discussion instead of a decision.

What Must Exist for Productive Execution

Disciplined execution depends on the structure. It shapes how capital and authority move, and how teams behave. Clear structure sets the culture for decisiveness, transparency, and accountability. Over time, these habits define the team’s identity. As discipline grows, confidence and clarity spread. When structure and culture align, results and progress come faster, making disciplined execution a shared standard.

At inflection points, five conditions need to be in place.

1. Clear Signal Ownership

• Who defines the threshold?

• Who declares it crossed?

• Who initiates escalation?

• If ownership is collective, exposure is diffused.

2. Defined Decision Rights

• Who can narrow the scope immediately?

• Who can reallocate capital inside the cycle?

• Who can override sunk cost logic?

• Governance maturity is decision clarity under pressure.

3. Visible Resource Movement

Conviction must concentrate capital and talent.

• If budget lines don’t change in the next allocation window, conviction is just talk.

• If headcount doesn’t shift, optionality still dominates.

• Moving resources is proof of real structural change.

4. Explicit Stop Authority

Stopping is structurally harder than starting.

• Who can terminate?

• What threshold triggers review?

• How quickly are resources reclaimed?

If stopping something requires political bargaining, governance isn’t mature yet.

5. Fixed Cadence for Evidence Interpretation

Ad hoc interpretation favours narrative. Disciplined systems establish cadence:

• Weekly evidence review.

• Monthly capital checkpoint.

• Quarterly scope revalidation.

Cadence reduces bias, while irregular interpretation amplifies it. Evidence without cadence becomes opinion.

Let’s Execute

If commitment has been declared, the structure must already reflect it.
Answer these without narrative.

Signal

• Who owns the conviction signal?

• What threshold defines continuation?

• When was it last formally reviewed?

Authority

• Who can narrow the scope without consensus?

• Who can reallocate the budget immediately?

• Who can stop this?

Capital

• What stopped when conviction increased?

• Which budget line lost funding?

• Which initiative was deprioritised?

Cadence

• Is evidence interpreted on a fixed rhythm?

• Or only when tension rises?

If these answers are unclear, commitment increases risk without increasing discipline. Execution is not just effort; it is reconfigured under uncertainty.

Governance Maturity

Many early-stage founders resist the word governance. It sounds like a process.

It sounds like oversight. It sounds like something that slows innovation and gets in the way of the “scrappy” approach many founders want to be.

Early on, informality is an advantage, enabling faster decisions, flexible scoring, and concentrated authority. This flexibility is a strength, but inflection points change the equation. As burn increases, headcount grows, outside capital comes in, and conviction deepens; exposure goes up. The informality that once made things fast can start to hide risk.

Governance maturity is not bureaucracy. It is exposure management.

It answers a simple question: As risk goes up, does clarity go up too?

Mature governance:

• Tightens decision rights as exposure increases

• Aligns capital deployment with evidence density

• Protects the stop authority from politics

• Narrowing the scope as conviction strengthens

It does not slow down innovation. It keeps innovation from drifting, of course.

It does not reduce ambition. It makes sure ambition is funded intentionally.

Structural discipline cannot compensate for a weak market.

But it does help prevent avoidable structural problems.

In capital-constrained places like Australia, this matters even more. There is less follow-on capital; error margins are tighter, missed signals compound faster, and there are fewer ways to recover.

In this context, mature governance gives you an even bigger advantage. It increases reconfiguration speed.

• It reduces capital waste.

• It sharpens decision clarity under pressure.

Where authority remains ambiguous, inflection dissolves into committee.

Where stop authority is politically unsafe, optionality persists past its value. Governance maturity isn’t about adding more processes. It ensures that as exposure increases, the system becomes more precise, not more scattered. In thin capital environments, that precision isn’t just for show. It’s protective.

A Closing Thought

Scale does not fix weak structure; it makes it worse. Structural discipline cannot make up for a weak market, but it does prevent avoidable fragility.

Committing when things are uncertain increases your exposure, which means you need to reconfigure.

In ecosystems with little follow-on capital, the cost of being imprecise compounds quickly. In a capital-constrained environment, scale doesn’t reward enthusiasm; it rewards structural discipline.

Disclaimer

This article reflects general observations drawn from venture and operating environments. It is provided for informational purposes only and does not constitute legal, financial, or investment advice. Any application should be considered in light of your specific circumstances.

This is where many ventures lose momentum.

Signal identification is essential.
But it is not the end.

Effective early stage venture building relies on distinguishing real signals from noise. This discipline is critical as pursuing the wrong signals misdirects resources. More critically, not making a decision and chasing every signal concurrently will fragment focus and exhaust a venture’s limited capacity.

Strong venture builders will test early, disprove quickly, and use evidence to narrow the options in front of them.

But it is after the signal are validated that breakdowns will occur as escalation or prioritisation is deferred to preserve flexibility, because “everything is important” or “we are still not certain.”

This will shift optionality from being an asset to a liability.

When optionality because structural risk.

Options are valuable early, permitting rapid learning and low-cost course correction.

Beyond a certain point, however, preserving options becomes a substitute for making a decision. Teams focus on keeping paths open rather than advancing decisively in one direction.

This may seem familiar:

• “We need slightly more data.”

• “It may be too early to escalate.”

• “Let’s sustain parallel paths for now.”

Individually, these positions are reasonable. Collectively, they create an environment in which retaining the status quo feels safer than committing.

The compounding cost of delay.

Delay consumes optionality rather than preserving it, particularly as signals lose strategic value faster than most organisations assume.

When commitment is deferred, consequences accumulate:

• Opportunity windows narrow as markets, partners, and competitors move.

• Strategic alternatives degrade as attention is divided.

• High-calibre talent disengages in the absence of directional clarity.

• Capital continues to burn without proportionate return, eroding confidence.

• Decision debt accumulates, making future escalation heavier and slower.

These costs are rarely confined to a single startup, venture or initiative.

If action is delayed too long, ventures do not just miss opportunities but also weaken the capital, talent, and conviction required for decisive action.

Translation requires decision exposure

Turning a signal into a strategy requires action, not just analysis.

A signal matters only when it produces decisions that change behaviour. In practice, those shifts should be visible:

• Scope narrows.

• Capital is reallocated.

• Talent is added, redeployed, or removed.

If these changes do not occur, the signal has been observed but not absorbed.

Many ventures stall at this point; the analysis is sound, the deck is coherent, and the evidence is defensible. But the system is not designed to internalise the consequences of commitment, making strategy just documentation rather than direction.

Why this pattern persists.

This failure rarely stems from weak thinking or poor intent.

Often it is reinforced by structural conditions, such as:

• Incentive structures that reward preservation instead of resolution.

• Diffuse accountability for escalation.

• Unclear decision rights.

• Execution capability is assumed rather than deliberately built.

In environments like these, optionality is not simply preferred; it is safer.

And so ventures drift, not because they lack insight, but because commitment is culturally and structurally harder than continuation

Let’s execute, even if under partial certainty.

Decision then subsequent execution does not require full certainty. Nor should it be expected to. It requires directional commitment based on a sufficient signal.

Disciplined translation from signal to action involves:

1. Clearly articulating the signal
   What has changed and why it matters now?

2. Explicitly narrowing the field
   Strategy is defined as much by exclusion as by pursuit.

3. Forcing a near-term commitment
   Time-box the decision and make it visible.

4. Realigning resources immediately
   Capital and talent must reflect the chosen direction.

5. Maintaining reversibility without tolerating drift
   Direction can change, but indecision cannot persist.

Discomfort at this stage is not a warning, nor a negative.
It is evidence that translation is occurring.

The operating gap.

At this stage, a deeper pattern emerges. Ventures stall not only because signals are absent, but because accountability for translating validated signals into execution remains unclear.

Recognition occurs.

Discussion expands.

Commitment diffuses.

This is not primarily a strategic deficiency; it is an operating gap.

Addressing that gap does not always require a new title or structure. It does need explicit ownership.

In strong founding teams, one person typically assumes responsibility for narrowing options and driving commitment.In others, defined mechanisms, clear escalation triggers, decision rights, and resource alignment rules exist.

Where neither exists, discussion proliferates and execution fragments. Momentum slows not from lack of insight, but from lack of disciplined translation.

The gap between signal and structured commitment is often a more significant contributor to venture stagnation than weak ideas alone.

A closing thought.

The ability to recognise signals is table stakes. But the ability to act on them, consistently, visibly, and under uncertainty is what differentiates ventures that compound traction from those that stall.

That distinction is not conceptual. It is operational.

What is coming next? In the final issue of this series, we will deal with the implications directly. If commitment in conditions of uncertainty is the real work, who is accountable for operating it well?

Disclaimer

This article reflects general observations drawn from venture and operating environments. It is provided for informational purposes only and does not constitute legal, financial, or investment advice. Any application should be considered in light of your specific circumstances.

Pilots do not fail. They linger.

They generate activity, updates and learning decks, similar to any corporate project, long after learning has stopped compounding. A pilot continues to receive funding (to a point), remains staffed, and is regularly reported on, yet it never quite crosses the threshold into real operational commitment. The point where experimentation stops and implementation starts.

This is frequently framed as an innovation problem. But it is not.

What Australia is experiencing, across government, enterprise, and venture portfolio, is a decision failure. Specifically, a failure to force scale-or-stop decisions once a pilot has done the job it was meant to do.

That is why expressions such as “pilotitis” and “pilot purgatory” are no longer simply hallway language. They are explicitly named in Australian contexts because the pattern is persistent and recognisable.

When a pattern gets a name, it is already widespread.

Australian enterprise and technology commentary has increasingly used the term “pilot purgatory” to describe promising proofs of concept that never graduate to implementation. This does not refer to experiments that collapse or receive a timely stop decision when hypotheses are disproved through rigour. This refers to experiments that continue, as no one ever defines what “good enough to scale” actually means. Experiments that have no entry criteria, no exit criteria and no moment when continuation has to be actively re-earned.

Australia’s Digital Transformation Agency used the term “pilotitis” in the context of AI and digital government, referring to initiatives that demonstrate feasibility but stall before wider implementation and adoption.

When a central digital authority adopts this language, it signals that the issue is not about capability or creativity; it is about how decisions are structured.

The audit trail tells the same story.

Australia’s audit bodies have been documenting this failure mode for years. The Australian National Audit Office has been clear about the purpose of pilots: they exist to inform adoption decisions. Monitoring and evaluation are not box-ticking exercises; they are meant to support judgments about impact, efficiency, and whether something should scale, change, or stop.

Yet the recurring finding is that evaluation is often not designed to force a decision.

Performance reporting focuses on activity rather than effect. This means the reporting is focused on reporting outputs and the tracking of milestones. However, outcomes are not framed in a way that compels a material commitment or a clean stop.

The same theme appears again in audits of performance statements across major government entities, where reporting describes what was done rather than what was achieved in terms that would justify scaling. Or even the inverse: a quick, efficient stop decision. Both are valuable.

At the state level, the NSW Audit Office has identified similar issues, particularly the lack of effective planning to scale successful pilots. When scale is not planned for, pilots do not fail. They simply remain pilots.

How zombie pilots are created

It is this environment where zombie pilots thrive:

• Enough activity to look legitimate

• Enough ambiguity to avoid hard calls

• Enough sunk cost to make stopping uncomfortable

As a result, effort stays high, but learning plateaus and continuation get quietly re-approved. This is not because the case is strong, but because stopping carries consequences that someone has to own up to.

But you can also usually tell a zombie pilot by how it is talked about.

Often, the update is jam-packed, full of activity, and increases over time, and the team is always engaged and ready for the next iteration of the experiment. But when someone asks the simple question -

“So are we actually committing to this?” 

the room goes quiet. Not because people do not care, but because no one is quite sure who is meant to answer. That pause is the tell. The pilot is not blocked by technology or talent. It is blocked by ownership.

This is not a flaw in the people involved. It is a predictable outcome of systems in which decision rights are diffuse and risk is asymmetric.

AI did not create this problem. It exposed it.

AI has become the most effective stress test of these decision systems, as pilots are being launched faster than governance frameworks can absorb them. They touch regulated data, workforce impact, reputational risk, and external examination simultaneously, and scaling them is no longer a technical decision; it is an organisational one, raising the stakes.

AI pilots often succeed on activity metrics:

• models trained

• vendors engaged

• proofs delivered

• workshops run

But they avoid outcome-based measures that would force the real question:

Are we equipped to operationalise this, or should it stop?

This is exactly what the Digital Transformation Agency was pointing to. AI does not tolerate fuzzy ownership or vague decision rights. It exposes them.

Why is this flaring now

This pattern is strengthening as Australia’s innovation and funding environment has rebounded in aggregate terms. Experimentation is still encouraged. Pilots are still funded. Venture and innovation activity continues. But governance has not kept up.

As capital tightens and tolerance narrows, continuation bias increases. It is often easier, politically, operationally, and personally, to extend a pilot than to terminate it. Especially when stopping means reallocating people, admitting uncertainty, or absorbing short-term discomfort.

In the end, pilots persist, not because they are winning, but because the system makes stopping expensive.

The issue underneath

Strip away the language and the decks, and the same three unanswered questions appear again and again:

1. What must be true for this pilot to move to production?
   Not “what did we test,” but what evidence would justify real commitment.

2. Who owns the operational and reputational risk if it does scale?
   Technical risk is easy to discuss. Organisational risk is not.

3. Who is explicitly authorised to stop it when learning plateaus?
   Not slow it. Not reshape it. Stop it.

Until those questions have owners, pilots will continue to build up without compounding value.

This is what leads to an unwelcome truth:

The blocker is rarely the pilot itself. It is the cost of being the person who turns it off.

A final observation

Australia may not necessarily have an innovation problem, but there are indications of a decision problem. And until continuation has to be actively re-earned, zombie pilots will remain a rational outcome of an irrational system.

This is not an interesting observation. It is a solvable problem, but only if decision-making and outcomes, not ongoing experimentation, become the focus.

References / Further Reading

• Australian National Audit Office, Evaluation of Australian Government Pilot Programs
  https://www.anao.gov.au/work/performance-audit/evaluation-of-australian-government-pilot-programs

• Australian National Audit Office, Performance Statements of Major Australian Government Entities: Outcomes of the 2024–25 Audit Program.
  https://www.anao.gov.au/work/performance-statements-audit/performance-statements-of-major-australian-government-entities-outcomes-of-2024-25-audit-program

• NSW Audit Office - Their futures matter (program evaluation and scale challenges)

  https://www.audit.nsw.gov.au/our-work/reports/their-futures-matter

• Digital Transformation Agency, Global leaders come together in Australia to shape the future of digital government and AI

  https://www.dta.gov.au/articles/global-leaders-come-together-australia-shape-future-digital-government-and-ai

• Australia’s startup funding outlook / ecosystem commentary, SmartCompany

  https://www.smartcompany.com.au/startupsmart/australia-startups-2025-funding-report/

Disclaimer

This article is based on the author’s professional experience and interpretation of publicly available information. It is provided for general informational purposes only and does not constitute advice. Any views expressed are the author’s own and do not refer to any specific organisation, program, or individual.

Work continues, roadmaps are revised, and additional capital is allocated. Updates commonly assert the idea remains plausible, without confirming or disproving its validity.

However, a systemic shift occurs when signals that formerly guided direction and priority stop compounding.

This is not failure, but non-compounding drift. The venture continues, yet learning, traction, and strategic clarity no longer accelerate.

This state persists not from lack of discipline or intent, but due to continuation bias: the tendency to extend time and capital simply because the idea remains plausible.

Issue #4 examines when stopping is most difficult, not because the venture has failed, but because continuing is no longer justified.

Non-compounding drift:
When movement replaces progress.

In the early stages of a venture, learning compounds with each experiment and action. All contributing towards reducing uncertainty, sharpening direction and ability to make clearer decisions.

However, when this situation reverses, non-compounding drift starts to set in.

• Experiments repeat common patterns.

• Progress increasingly requires justification rather than genuine insight.

• Decisions feel harder, not clearer.

• Activity remains high while insights plateau.

Nothing is fundamentally broken, and at this point, nothing has failed.

The venture stops improving meaningfully and enters stagnation or perpetual pivots.

Why rational teams persist.

In non-compounding drift, continuation bias is the main driver of persistence.

Continuation bias is the tendency to allocate additional time and capital after signals stop compounding, simply because the idea remains plausible.

This bias does not stem from ignorance or poor intent, but from plausibility serving as a rationale to continue.

As long as an idea has not clearly failed:

• Founders can justify their continued commitment.

• Corporate venture teams can justify sponsorship and priority.

• Investors can justify follow-on exposure.

Two phrases reliably appear at this point:

We just need more time.

We just need more capital.

Both statements may seem reasonable, but they frequently delay addressing the same unresolved question:

What, specifically, would need to change for continuation to be justified, and is that change actually underway?

When this question is not answered, continuation becomes the default and bias replaces disciplined decision-making.

When time and capital no longer enable progress.

At the early stages, time and capital are meant to buy learning.

When signals compound:

• Time increases clarity

• Capital increase optionality

When non-compounding drift takes hold, their roles reverse.

Time becomes a strategic distraction as attention moves to a venture that no longer improves quickly enough to justify exclusive focus.

Capital turns into commitment escalation, with funding used to preserve continuity rather than enhance competitive advantage.

Nothing dramatic occurs, yet opportunity quietly narrows.

The unreported loss.

Opportunity cost rarely appears in venture updates, burn rates, or runway charts, and it does not trigger alarms.

It accumulates quietly with every additional month spent on a venture in non-compounding drift carrying a further cost:

• Another idea not explored.

• Another market not tested.

• Another strategic option was not considered or pursued.

For founders, opportunity cost appears as a strategic distraction, with attention monopolised by a venture that no longer deserves full commitment.

For corporate venture teams, it appears as portfolio crowding, where plausible initiatives consume resources that could support more viable opportunities.

For investors, it appears as capital inertia, with follow-on funding maintaining existing positions rather than increasing expected value.

Opportunity cost becomes visible only when teams are forced to articulate what they would pursue instead.

The most significant opportunity cost is not financial, but the loss of alternative pursuits that could have been undertaken by stopping earlier.

When persistence stops creating leverage -
(A Founder’s Lens)

Founders feel this situation viscerally.

You are still working hard. Your team is still engaged. And, Nothing has failed.

However, the shift has occurred, and leverage dissipates with each pivot yielding less new information.Efforts to influence the narrative begin to rival the focus on product development. And, decisions demand more justification, not less.

What appears externally as resilience usually feels internally like unfocused effort.

Founders lose optionality not by stopping too soon, but by persisting past the point of diminishing returns.

The limit to productive pivoting.

Founders are often advised to pivot, and this is sometimes appropriate. However, the effectiveness of pivoting diminishes over time.

Initially, pivots help narrow the hypothesis space. Later, they may perpetuate ambiguity.

It is important to take into account that each pivot consumes:

• Team belief,

• External credibility

• Strategic consistency

• Learning bandwidth

Eventually, pivoting stops generating new understandings and only delays necessary decisions and the underlying drift remains.

Learning has diminishing returns.

Failure can generate insight, but only up to a point.

What is often missed is that learning becomes finite and incurs costs.

Early learning is reinforcing, but depending on tactics, it can later plateau. Often during non-compounding drift, saying “we are still learning” becomes a justification rather than an objective observation.

Continuing to learn is only rational when:

• The learning still reduces meaningful uncertainty.

• And the cost of extracting it is justified by what it enables next.

When these conditions are no longer met, continued learning does not justify further action and only postpones the decision it was meant to inform.

Disciplined teams prioritise stopping before extracting learning. This process is explicit and bounded, focused on generating transferable findings rather than repairing the narrative.

When exploration turns into inertia -
(A Corporate Venture’s Lens)

In corporate venturing, continuation bias often hides within governance.

Ventures persist because:

• They remain sufficiently aligned with the strategy or mandate.

• They have internal sponsors.

• They avoid political friction.

Over time:

• strategic relevance weakens

• Narratives become harder to sustain

• Capital is used to maintain appearances rather than to create strategic options.

“More time” becomes one more reporting cycle.

“More capital” avoids a difficult internal call.

The main risk is not direct loss, but the displacement of better opportunities while maintaining an illusion of progress.

In a corporate setting, an essential factor is the design of incentives and roles.

In many corporate innovation models, roles, reporting structures, and success metrics are tied to the survival of individual programs rather than portfolio outcomes. Teams are organised around specific ventures, progress is reported by initiative, and career advancement depends on sustaining ongoing projects.

In these conditions, stopping a venture is no longer only a deliberate decision. It can seem like the removal of a mandate, a team, or a career path.

Continuation becomes rational, even when signals stop compounding.

Discipline becomes less about individual resolve and more about separating continuation decisions from initiative-based incentives. This allows cessation free of personal, political, or career consequences.

When follow-on becomes default -
(An Investor’s Lens)

From an investor’s perspective, this is when discipline erodes.

The venture does not fail quickly enough to warrant termination, nor does it succeed enough to justify further investment. As a result, follow-on capital is often rationalised as:

• Supporting the founder

• Protecting the initial position

• Preserving optionality

However, optionality is not maintained by default continuation. It is preserved by relative improvement versus alternatives.

Capital allocated to ventures in non-compounding drift is unavailable for investments with higher return potential.

This is not pessimism. It is portfolio discipline.

Discipline without performance

Discipline is sometimes mistaken for managing external perceptions.
Shutdown announcements, retrospective clarity, and lessons-learned narratives emerge later.

Real discipline is quieter. It is seen as:

• Re-earning continuation, not extending it

• Treating time and capital as conditional

• Accepting that plausibility is not progress.

• Allowing outcomes without identity defence

Legitimate decisions to cease operations are justified by evidence and process, not by external approval. Stopping does not require recognition to be valid.

Let’s execute.

A founding team, corporate venture group, or investment committee can use this diagnostic when reviewing continuation.

Answer the following questions directly and concisely.

1. What is the present-tense justification for continuing this venture?

2. Which signals have strengthened in the last 90 days, reducing uncertainty?

3. If no additional capital were available, what would materially change?

4. If this venture did not exist, what would this team focus on instead?

5. What decision is being deferred by asking for more time or more capital?

If these questions cannot be answered clearly, the ambiguity is a critical signal.

A closing thought.

Most ventures do not end because the case for stopping is clear.

They end because the case for continuing is never re-earned.

Walking away is not a loss of belief, resilience, or ambition. It is the result of disciplined action, applied when signals stop compounding and opportunity cost outweighs potential gains.

Stopping creates space, not for reflection or narrative repair, but for better decisions in other areas.

The work does not end when the venture stops. It begins again with greater clarity about what deserves commitment going forward.

What’s coming next? Stopping is one side of discipline. Deliberate continuation is the other. The next issue will examine actions taken once signals become clear, including:

• How disciplined teams translate evidence into strategy?

• How do they choose what to double down on?

• and how continuation remains deliberately re-earned?

This series and perspectives draws on patterns observed across startups, corporate ventures and innovation decision-making. It is not a checklist to be blindly followed. 

Most of the signals people rely on to judge progress are misleading.

Activity. Interest. Pilots. Positive conversations. Narratives of early traction. Each may seem convincing, yet all can be misleading.

Once this becomes clear, a predictable pattern often follows.

Teams rarely change direction immediately. They do not stop. They do not suddenly become more disciplined. They hesitate.

This leaves two questions:

1. If existing signals are unreliable, what should teams focus on instead?

2. How can progress continue without substituting one set of weak signals for another?

At this stage, teams often seek additional information. More data. More validation. More conversations.

This is not to clarify the decision, but to delay making it. The problem is rarely a lack of signals. The problem is a lack of signal strength.

This issue focuses on recognising that distinction and will guide you through how to differentiate among signals as you decide what matters most. Before exploring the types of signals, it’s important to understand why typical responses to early uncertainty often fall short.

Not all signals are equal.

A common mistake among founders, venture builders, and corporate innovation teams is treating all signals as equally significant. They are not.

Some signals are noisy, some are fragile and some exist only while attention is actively applied to them. Others however compound.

The strongest signals rarely appear clearly. They do not arrive with certainty and often seem unremarkable at first. On their own, they may not feel decisive. What distinguishes them is what happens next.

They reappear.

They reinforce each other.

They begin to narrow the range of reasonable options.

Over time, they start to force decisions even when no one is explicitly pushing for one. Some signals need constant explanation. Others do not. Most teams do not miss this because they are not paying attention. This occurs because early signals often feel urgent to those closely involved.

Why “more data” is rarely the answer?

When confidence in existing signals erodes, the instinctive response is measurement. I have observed multiplying dashboards, perpetual pilot extensions and repeating research or discovery loops.The work becomes busy, structured and defensible.

However, it often the venture begins to feel stagnant. There are more updates, but fewer decisions. More evidence, but no change in direction. More activity, without a corresponding shift in commitment.

This is often described as rigour. In practice, there is usually hesitation.

Weak signals benefit from ambiguity. They survive when interpretation remains optional, and decisions can be deferred.

Alternatively, strong signals behave differently, they will often have an impact on the decision to be made. They reduce ambiguity. They make trade-offs harder to avoid. They narrow the space between “interesting” and “necessary.”

The question is not whether you have signals. It is whether those signals are compounding or quietly fading.

Compounding vs decaying signals

The difference between weak and strong signals rarely shows up in a single moment. It happens up over time.

Decaying signals tend to remain isolated and require repeated explanation. Their urgency fades unless someone actively sustains it. When attention shifts, they disappear.

Compounding signals behave differently. They resurface without effort. They create secondary effects. They start interacting with other parts of the system.

Often, the distinction becomes clear only in retrospect, when it is evident that some signals required ongoing support to remain visible, while others persisted independently.

This is not about optimism or skepticism.
It is about accumulation.

What real demand looks like in the wild?

This issue is not about tools, steps, or validation techniques. It is about learning to observe what is already occurring.

Across startups, spin-outs, and corporate innovation programs, a small number of patterns recur where real demand exists, long before success is obvious.

Behaviour that costs something

Real demand shows up where people are already paying a price.

For founders, that price is often personal or financial. Time is lost. Manual workarounds persist. Resources are committed earlier than they feel comfortable. People accept inconvenience rather than revert to the status quo.

For corporate innovation leaders, the currency is different. The cost is organisational.

Exceptions are made. Standard pathways are bypassed and work happens unofficially because the alternative is worse. Leaders tolerate risk they would normally deflect.

This is often uncomfortable to observe, particularly when it becomes clear that people are solving the problem independently rather than due to your involvement.

Where people consistently pay a price, demand is rarely theoretical.

Workarounds that scale socially

One workaround proves very little. The same workaround appearing independently across customers, teams, or parts of an organisation is a different signal.

For founders, this repetition is usually external: similar spreadsheets, parallel hacks, familiar patterns emerging across different buyers.

Inside large organisations, repetition is often hidden. The same problem is solved badly in multiple places. Shadow systems appear and local fixes replicate quietly because no one is rewarded for surfacing them.

When many people independently arrive at the same imperfect solution, the underlying problem is usually real.

Escalation without prompting

Weak signals need chasing. Strong signals escalate on their own.

For founders, escalation often moves outward. Introductions happen without asking. Conversations expand. Procurement or finance enters earlier than expected. Questions begin to imply consequences rather than curiosity.

Inside organisations, escalation moves upward. Senior leaders ask how this fits with strategy. Risk and compliance surface implications. Ownership becomes unclear.

At this stage, the situation often feels less contained.

For founders, escalation creates opportunity.
For corporates, it creates accountability.

In both cases, it signals that the work is no longer optional.

Decisions forced by success

Positive outcomes are often mistaken for strong signals.

A pilot that performs well but allows everyone to defer a “buy or do not buy” decision is weak. A prototype that works but doesn’t challenge an existing process is weak.

Strong signals create consequences.

For founders, success collapses optionality. Pricing must be set, contracts negotiated and resources are reallocated.

For corporate innovation teams, success creates friction. Existing systems are challenged. Ownership becomes contested. Funding conversations move out of innovation budgets and into the business.

Within organisations, a lack of friction following success is often a warning sign.

Compression of time

One of the most reliable indicators of real demand is what happens over time.

For founders, this often shows up as shortened cycles. Decisions happen faster and follow-ups occur without chasing.

Inside organisations, time compression looks different. Deadlines appear suddenly. Executive updates are pulled forward. Decisions that were expected later become uncomfortable to delay.

This is not urgency for its own sake. It is exposure. When time compresses within a system, it is usually because delay has become risky.

The quiet pressure of real demand

At this point, many teams begin to sense a shift, even if they struggle to articulate it. Nothing dramatic has happened and there is no single breakthrough moment.

Yet, continuing as before begins to feel misaligned.

The work still moves forward, but with less effort. Certain conversations keep resurfacing and certain questions refuse to stay contained.

At the same time, other things fade.

Updates that once felt important stop changing anything. New information no longer alters the picture. Momentum appears to be assumed rather than actively generated.

At this stage, experienced teams often realise how much they have relied on narrative rather than evidence.

Strong signals do not demand attention. They create pressure.

They do not ask to be believed. They make delays harder to justify.

Strong signals accumulate, driving necessary decisions and making delays hard to justify. Weak signals require explanation, fade without support, and produce activity without real progress.

Recognise which type you have prioritise compounding signals, act decisively, and avoid relying on plausibility alone. The key is to focus on signals that reinforce themselves, force decisions, and compress time. These are the indicators of real demand.

A decision fork in the road.

This is usually the moment teams underestimate. This is not due to subtlety, but rather because it is inconvenient.

By the time you reach this point, you rarely lack information. What is often missing is the self-granted permission to act on what the signals already indicate.

The decision point does not announce itself. There is no sudden deadline or failure. Instead, it becomes clear that nothing new is emerging.

Conversations repeat.
The same signals and justification are repeatedly cited.
The same explanations are repeated to justify maintaining the current course.

At this stage, most teams do not continue because they believe the idea is right.
They continue because the idea is still plausible.

Plausibility sustains the narrative. It keeps options open and makes delay appear responsible rather than evasive. But plausibility is not momentum.

The decision point is where you determine whether you are responding to compounding evidence or maintaining decaying justification.

When signals compound, continuation becomes structurally obvious. Venture builds should be able to observe, resources shifts, clearer ownership and trade-offs being accepted rather than debated. Continuing may not feel easy, but it feels necessary.

When signals decay, something else happens. The work continues, but the pressure disappears. Energy is maintained through explanation rather than through tangible consequences. Progress becomes something described rather than experienced.

This is where many capable teams linger.

Not because they are careless.

Not because they lack discipline.

But because stopping feels disproportionate when nothing has failed.

Walking away from a failing idea is straightforward. It is much more difficult to walk away from a good idea supported by weak signals. That is why this fork matters.

It is not a test of optimism.

It is  not a test of resilience.

It is a test of whether you are willing to treat the absence of momentum as meaningful information.

For founders, delaying this decision quietly consumes runway and credibility.
For corporate innovation leaders, it consumes political capital and organisational patience.

In both cases, the cost is real, though deferred.

The decision fork is not able certainty. It is about recognising when continuing no longer improves the quality of your information. Once you reach this point, continued activity is no longer a neutral choice.

It is a choice.

Let’s execute

This is not a growth exercise.
It is a recognition exercise.

This process is more challenging than it appears, not due to complexity, but because it eliminates places to hide.

Set aside an hour to complete this exercise independently.

1. List the signals you are currently relying on.

   For each, ask yourself the following:

   1. Has this signal strengthened or weakened over time?

   2. Did it escalate without prompting, or require chasing?

   3. Did it force a decision, or allow deferral?

   4. Did time compress or stretch?

Now group them into two columns:

1. Compounding

2. Decaying

Do not debate the categories.

If you need to justify why a signal belongs in the first column, it likely does not.

Finally, answer one question honestly:

• If you removed all decaying signals, would you still continue?

This exercise is intentionally designed to be uncomfortable.

It quietly distinguishes those building genuine progress from those simply maintaining activity.

A closing thought

Strong signals do not guarantee success.
Weak signals almost guarantee drift.

The role of a venture operator, founder, or corporate innovation leader is not to create artificial confidence. It is to interpret evidence and make timely decisions.

Most people can generate activity.

Fewer can recognise momentum.

Very few are willing to act when signals indicate it is time to stop.

Whats coming next? The next issue will look to address the decision most teams avoid. Not when the idea fails, that part is straightforward. When the idea remains plausible, work continues, but the signals do not compound.

It will examine:

1. Why teams stay longer than they should?

2. What discipline looks like in practice, without becoming performative?

3. How to disengage without turning it into a personal narrative that requires justification?

Because the ability to stop is not a personality trait. It is an operating capability.

This series reflects patterns observed across startups, corporates, and research-led ventures, not a checklist to be blindly followed.

The last event I went to last year finished in a way that felt quietly important.

On stage, a founder spoke about their journey so far. Not only the highlights, but the reality of it. The reality of the venture and the reality of life. What stayed with me most was how often the conversation came back to resilience.

Resilience here was not just about optimism or toughness. It was about being able to keep going when you do not have all the information, resources are limited, and the next steps are not clear.

How you think about resilience matters. That framing matters.

In early-stage ventures, you rarely have enough data to make perfect decisions. Most of the time, you are making the best decision you can at that moment, with partial evidence, limited resources, and pressure coming from multiple directions. Some of that pressure comes from the venture itself. Some of it comes from life.

Founders do not operate in a vacuum. Life events can and will often intervene, your capacity changes, momentum can break, and your energy will drop. At the same time, the venture still asks for progress.

Demand signals are weak, evidence is noisy, and what you hoped would validate the direction often refuses to cooperate. Or, it can say something that you do not want to hear.

Resilience, in that context, is the ability to stay engaged despite the challenges.

Sometimes that means working with what you have rather than what you planned for. Sometimes it means trusting your judgement before the data has fully caught up, and being willing to live with the consequences. And sometimes it means being stubborn enough to continue. Not blindly, but deliberately, because the goal still matters even when the route keeps changing.

This is also where some of the hardest choices show up.

Resilience is tested when founders realise the team they started with may not be the team they need to continue. When roles need to change. When co-founders need to step back. When the founding group needs to grow. These decisions are rarely clear, rarely clean, and almost never arrive at a convenient time.

Avoiding them often feels easier in the short term. Making them is usually what keeps the venture moving forward.

Resilience is also about time. Staying in the game long enough for signals to mature, for evidence to accumulate, and for second-order effects to reveal themselves. And sometimes, for the mind and body to recover.

This is where resilience connects directly to demand, evidence, and coherence.

Without it, teams optimise for relief. They reach for cleaner stories, safer tests, and smaller decisions that reduce discomfort but avoid the harder questions. Teams with resilience stay with those questions long enough for weak signals to either strengthen into real evidence or disappear entirely.

Resilience is not about ignoring evidence. It is about staying engaged until the evidence is strong enough to justify change, or clear enough to know when to stop.

Across founders, venture builders, and spin-out teams, the pattern is consistent. The ventures that progress are not defined by certainty or uninterrupted momentum. They are defined by their ability to hold things together while making imperfect decisions under pressure.

That is not inspirational.

It is operational.

And without it, you cannot keep going.

This observation prompted by an article from Global Corporate Venturing (linked below) maps high activity and capital flows, providing insight into how various corporate investors engage the market. It notes that “artificial intelligence continues to absorb the lion’s share of corporate venture capital,” but also emphasises that the landscape reflects “increasingly strategic and diversified capital deployment,” not just “AI exuberance.”

This perspective is useful and raises important questions.

The investor landscape is diverse, including infrastructure leaders such as NVIDIA, established venture arms like GV and Salesforce Ventures, and crypto-native firms like Coinbase and Animoca Brands.

This diversity shows where corporates are focusing their attention.

However, activity alone can be an ambiguous signal for founders. High deal volume may reflect strategic clarity or alternatively ongoing uncertainty and hedging. While calling this “strategic and diversified” is reasonable at the capital-allocation level, it raises the question of how often this activity leads to real changes in decision-making, integration, or execution within the parent organisation.

From an operator’s perspective, this capital deployment suggests that venture investing may serve as a strategic input. In practice, this can involve exploring adjacencies, preserving optionality, and informing build, buy, or partner decisions. However, the article does not assess whether or how often these signals are acted upon.

That distinction is especially relevant for founders.

A CVC’s presence on a “most active” list does not guarantee that, for a founder:

• Your solution, and more importantly, the specific problem it addresses, is already recognised internally rather than just aligned with a priority theme,

• real demand exists inside the organisation, or

• pilots will convert into contracts, revenue, or integration.

Regardless of a corporate investor’s activity level, founders must clearly define the problem they are solving and identify where genuine demand exists.

This requires clarity regarding:

• Who experiences the problem today, and who controls the budget?

• Whether demand is demonstrated through actions, such as budget ownership, workaround adoption, or active engagement, rather than narrative, and

• What specific decision would the corporation need to make if the solution is successful?

CVC activity does not create demand. But it can amplify clarity when demand is already real.

There are examples where corporate venture activity leads to internal decisions, integration, and long-term value creation. Achieving this is rarely straightforward and often depends on factors beyond the investment itself, including organisational readiness, incentive alignment, and execution capacity. The variability means that activity alone is not the complete signal unless viewed alongside how each individual corporation actually leverages and acts on its venture investments.

The key takeaway for founders is that investment volume and thematic momentum indicate where attention is focused. Ultimately, effectiveness depends on whether this activity leads to changes in decisions or execution.

Source: Global Corporate Venturing, “Most active CVC units of 2025”

This issue examines the critical gap between demand signals and their interpretation.

A True Failure

Rarely do teams skip validation. New venture founders and teams conduct customer interviews, they pilot solutions, they collect feedback and encouragement.

Despite following best practices, many early ventures still stall, rarely due to a lack of effort but from misjudgement. Teams misread signals or mistake early interest for validation, progressing through presentations, workshops and even pilots. However, they eventually fail when tested against actual behaviour.

To recap The First Test is not only a method for validating solutions; it serves as a filter to determine whether a problem is worth pursuing. A problem without a real demand signal, no actual behaviour should be avoided.

The problems to avoid.

Three types of problems often emerge and should be avoided.

• Problems that are theoretical. They exist in strategy documents and future-state narratives, align with trends, and make sense intellectually. But they do not appear in workflows, budgets, or daily behaviour. If a problem exists only in abstraction, there is no demand signal to address.

• Problems that are aesthetic. They sound reasonable, such as “It would be nice if…” or “I wish we had a cleaner way to…”. While they may feel modern, they rarely prompt action. Aesthetics create preference, not pull, and pull drives adoption.

• Problems that are low velocity. Even if real, they occur too infrequently to create urgency. Low frequency leads to low recall and low priority, causing ventures to stall before execution.

The most successful ventures address problems that are frequent, costly, and difficult to ignore. They have found urgency and repeated impact when evaluating opportunities.

A quick reminder on innovation

When a venture stalls or even fails, many teams are often given a familiar explanation.

“Maybe it is just too new. Maybe demand has not formed yet.”

This explanation is rarely accurate.

Innovation succeeds by solving existing problems more effectively, not by inventing new ones. When there is no existing behaviour, workaround, compensation, effort, or cost, then urgency has not been established, indicating a weak signal of demand.

Novel solutions succeed. Novel problems rarely do.

Recognising patterns in failed ventures helps prevent future mistakes. Accurate signal interpretation protects against wasting resources on weak problems.

Beware the false positives.

Finding a strong demand signal is encouraging, but some signals collapse under scrutiny. These traps create the illusion of demand that founders, corporations, and professionals misread.

Interest is not intent. A stakeholder may say, “Yes, we would use this,” yet nothing changes: workflow stays the same, no contract is signed. People often love new ideas in conversation. They enjoy sounding supportive. However, a verbal endorsement is not a commitment.

Enthusiasm is not urgency. A pilot meeting may be energetic, and the demo well received, but if no budget is allocated, no deadlines shifted, and no risk is accepted, there is no urgency. Urgency always involves a cost, even for unproven solutions. Energy is not evidence.

Imagination is not truth. In interviews, people may describe what they would do, but in practice, they continue to use spreadsheets, manual checks, and long-standing workarounds. Often, this is driven by the interviewer, who asks leading questions about future behaviour. The questions often sound like

“If this existed, would you …”

“In theory, could this help you … “

“Would you use a tool that … “

As a result, they imagine rather than report reality. They talk about hypotheticals project where as real demand needs to exist in the present.

Persona pain is not real pain. A presentation may claim the CFO struggles, but analysts absorb the burden. The system suffers, but the persona is unaffected. Personas point to pain but do not prove its existence.

Corporate sponsorship is not adoption. An innovation lead may champion an idea, and leadership may align with it. But if procurement stalls, legal hesitates, or operations deprioritises it, the organisation supports change without enacting it.

Socially convincing demand signals may seem strong, but only those that withstand testing result in real action. Always look for practical proof, not appearances.

A necessary clarification on pilots

Pilots exist at the boundary between genuine signals and illusion.

Pilots can be valuable and often represent the first serious engagement with a new idea or capability. However, they are typically low cost, low commitment, and low risk, making them easier to approve. This is especially true when dealing with large organisations.

However, a pilot does not prove demand; it demonstrates permission to explore. Pilots can be misleading if they lack clear success criteria, a defined path to scale, a pre-allocated budget, or an accountable business owner. In these cases, pilots generate learning rather than commitment.

Pilots are meaningful when they are designed to inform a clear buy-or-not-buy decision, address a specific operational problem, are sponsored by someone directly affected, and are linked to an existing cost line.

The intent behind a pilot matters more than the pilot itself. True demand is revealed by commitment, not just participation.

When Demand Hides

Even good tests can mislead if you do not know where to look.

These are situations in which demand exists, but the signals are more complex to discern. Not because the problem is not real, but because the behaviour that expresses it is obscured, fragmented, or absorbed into other parts of the system.

Some signals are invisible at first. Teams often hide their hacks in workarounds, shadow systems, manual checks, and “temporary” fixes that persist. If you ask only how the process should work, you will miss how it does. Real demand lies between policy and practice.

Sometimes the pain is carried by someone else. Executives feel nothing while front line teams compensate daily. If a downstream operator quietly compensates for a broken process, the problem may appear small from above, even when it is structurally significant. This is common in corporates and regulated environments. You may not find the signals in the boardroom. You may find them where the work happens.

Sometimes behaviour is fragmented across roles. One team wastes time; another absorbs cost; a third manages risk; a fourth cleans errors. Individually, the signal looks weak. Collectively, the behaviour is loud. The First Test still applies but must be performed at the system level.

And sometimes long-standing pain disappears into tolerance. People adapt. They stop complaining. Resignation replaces expectation. But overall tolerance is not satisfaction.

How the operator can distort the signals

When The First Test appears to fail, it is rarely because the test is flawed. It is because assumptions distort what is being observed.

One distortion is being too broad. “Improve efficiency” is not a problem. Real problems are concrete enough to be recognised in context.

Another distortion is smuggling the solution into the problem. When language shifts to solutions, observation gives way to justification.

The First Test only works when problems are expressed in human terms: what breaks, who compensates, and what it costs.

Interpreting signals depends on your perspective.

The First Test is universal. However, how signals are misread depends on your role and incentives. Though the failure is shared, the blind spots are not.

Founders often mistake encouragement for inevitability. Early interest feels like momentum, but without workflow, budget, or priority change, the signal is social, not economic.

Investors can confuse activity for evidence. Busy pipelines and strong pilots feel reassuring. But capital amplifies clarity; it does not create it. When signals are weak, funding extends false momentum.

Corporate innovation leaders most often confuse alignment with adoption. If stakeholders agree and governance is satisfied, it feels like progress. But alignment is permission, not demand. Adoption begins when a business unit owns the problem and absorbs the cost.

Advisors and operators are in a challenging position. Their primary risk is assuming clarity exists when it does not. The operator’s role is not to create confidence, but to ensure consequences are addressed.

In essence, actions that demonstrate behaviour, cost, and decisive choices are the most reliable indicators of real demand. Use these as your guideposts.

Finding Real Demand Signals Matter

The First Test exists to prevent a specific, expensive mistake by building on belief rather than behaviour. Passing it does not guarantee success, but misreading it almost guarantees waste.

Most teams do not fail because they did not test. They failed because:

• They trusted the wrong signals.

• They mistook politeness for pull.

• They mistook activity for urgency.

• They mistook permission for commitment.

Identifying demand signals through the First Test does not protect you from failure; it helps to protect yourself from self-deception.

Let’s Execute

Pressure test the signal, not the story.

In Issue 01, you executed the First Test. This time lets challenge early demand signals before committing resources beyond what is necessary.

Let’s apply the First Test discipline immediately without waiting for a solution, a product, or adoption. This matters most in early ventures, where demand must be inferred before workflows change or budgets move.

1. Pick the signal you are currently relying on and downgrade it

Choose one signal you have been treating as traction, a pilot approval, a supportive conversation, a warm intro, positive feedback, or an investor interest.

Now ask a harder question:

What cost is someone already paying because this problem exists?

If the answer is no time wasted, no risk absorbed, no workaround created, then you are not looking at demand. You may be looking at politeness. In early ventures, cost precedes solutions. If no one is paying a price today, they will not pay for relief tomorrow.

2. Translate “workflow change” into early-stage reality

Early ventures often get stuck because they interpret “no workflow change” as failure. Before a solution exists, the workflow change shows up as:

• unofficial workarounds

• spreadsheets next to systems

• manual checks

• duplicated effort

• fragile processes people babysit

Ask:

What are people already doing despite not having a solution?

Those compensations are the early signal. No workaround usually means no urgency.

3. Translate “budget movement” into early-stage cost

Before money moves, time and effort move.

Ask:

Who is spending hours fixing this?

Who is double-checking outputs?

Who is absorbing the risk when it breaks?

Who is cleaning up the downstream impact?

Time is the first currency people spend on real problems. If no one spends time today, the budget will not move later.

4. Force a decision, even without a product

Early founders often default to “more discovery” when signals are weak.

Instead, force clarity:

• If this problem were removed tomorrow, whose job would materially change?

• If the answer is vague, distributed, or hypothetical, the signal is weak.

You are not looking for agreement; you are looking for a consequence.

5. Pause if the signal never strengthens, even if the idea is good

Most wasted effort does not come from bad ideas.

It comes from continuing when the same conversations repeat, the same enthusiasm shows up, but no additional cost or urgency appears.

Stopping is not failure. Continuing without strengthening signals is.

A closing thought

Demand signals can be misread and then defended.

• Encouragement was treated as inevitability.

• Activity was mistaken for urgency.

• Permission was confused with commitment.

• The First Test was passed but not interpreted.

Before solutions exist, demand does not announce itself politely. It shows up as compensation, friction, risk, and workarounds. It costs something, even when no one is paying yet.

Your job is not to prove the idea deserves to exist. It is to decide whether the signal is strong enough to earn execution.

Reflection: When demand never strengthened

One of the earliest mistakes I made as a founder was not building too soon.

It was waiting for a signal to strengthen that never did. I had a prototype and early users engaged with it. Corporate innovation teams were supportive and happy to stay involved.

Interest never disappeared and conversations kept happening, but feedback became repetitive and consistent. What never happened was effort. I noticed no one stayed late to make it work. No one chased it internally. No one felt exposed if it failed. Every conversation sounded like progress, but each one reset back to the same place.

At the time, I told myself this was what “early” looked like. In hindsight, it was repetition without urgency.

The mistake was not building a prototype. It was mistaking recognition and politeness for demand.

That experience is why I now watch for behaviour before belief, not because ideas are fragile, but because founder time is.

What’s coming next? The next issue will focus on signals that do not need defending, those that compound, force decisions, and make momentum inevitable rather than hoped for. Execution does not reward belief. It rewards judgment.

This series reflects patterns observed across startups, corporates, and research-led ventures, not a checklist to be blindly followed.

Before you build anything, test the problem, not the solution.

Here is the fastest way to know whether an idea deserves your time.

The Familiar Failure

Many of us who work with, advise, or invest in founders have seen this pattern.

A founder presents an early-stage venture deck or a polished working prototype.

There is a thoughtful UI. Clean logic. Weeks of work evidenced. And sometimes even $40K spent.

They have spoken to people.
They have had meetings.
They have heard encouraging feedback.

“This is interesting!”

“I’d definitely use something like this.”

Two weeks later, the idea is dead, if they are lucky. Some continue for months or even years. Not because the solution was wrong. Not because the execution was poor.

But because the problem was not real.

What it means for a problem to be NOT real?

A problem is not real when there is:

• No workaround.

• No urgency.

• No repeated behaviour.

• No signal anyone cared enough to act.

The founder did not misread their idea. They misread the problem. It was not worth pursuing, at least not yet.

That is where The First Test begins.

A Venture Operator’s First Test

If you want to know whether an idea is worth pursuing, start with one question:

Is this a problem people are already expending effort to deal with today?

Not could, should or might once a product exists.

But what people are actually doing right now, in the absence of a good solution.

Across technology, sector, healthcare, deep tech, and research-led domains, real problems create observable behaviour.

That behaviour may look different by domain, but it always exists when demand is real.

Reading demand signals in the wild

In practice, demand shows up as people paying a price to cope.

That price may include:

• manual effort and workarounds including spreadsheets, scripts, shadow systems, repeated manual tasks

• risk, delay, and mitigation including interim protocols, monitoring regimes, acceptance of known limitations

• a form of spend such as time, money, external consultants, political capital, compliance overhead

The form varies by domain.
The signal does not.

Where behaviour exists, there is demand.
Where behaviour does not exist, there is no evidence of urgency.

Assessing signal strength

To make this concrete, ask:

• Is the problem active, are people taking action today?

• What is the workaround? Every real problem produces one.

• How painful is it? Pain drives urgency, adoption, and willingness to pay.

• What is the cost of the workaround? Time, money, risk, delay, frustration, compliance overhead … all count.

• How frequently does this behaviour occur? Recurring pain compounds. One-off pain rarely does.

If there is sustained behaviour, there is an initial signal the idea may be worth exploring. If there is no behaviour, you have noise.

The diagram is not a maturity model. It is not a funnel. And it is not a scorecard designed to make weak ideas feel better.

It is a simply a way to visualise how demand shows up in the real world.

As you move up the levels, you are not moving toward sophistication. You are moving toward observable reality.

At the bottom (Levels 1-2), signals are cheap. People talk, they speculate, they express interest. Nothing changes in how work gets done.

In the middle (Level 3), pain becomes visible. The problem show sup repeatedly. It causes friction, delays,m error or inefficiency. But action is still inconsistent. People tolerate the pain rather than actively compensate for it.

At the top (Levels 4-5), behavior changes. People start doing something about the problem, even if the solution is imperfect. They build workarounds, add manual step, bring tools or external help, therefore spend time, money, political capital or accept the risk to cope.

This is the point where the problem can be considered initially investable.

The diagram is intentionally simple because the judgement it supports is simple:

if people are not already expending effort to deal with the problem, you do not yet have evidence of demand. 

How strong does the signal need to be?

To justify investment, even your own time, you should be aiming for a signal strength of 4 or 5. Anything below that is speculation.

If the world is not already expending effort to deal with the problem, it will not magically start when your solution appears.

This is not about optimism or belief.
It is about observable reality.

A common objection

This does not apply to healthcare, biotech, or deep tech.
People cannot solve the problem yet, that’s why the innovation is needed.

This objection usually comes from a good place.

In regulated or science-led domains, the final solution genuinely may not exist yet.
But that does not invalidate the test.

It clarifies what kind of behaviour you should be looking for.

What the test is really asking?

The First Test is not about whether the problem can be fully solved today.
It is about whether people are already paying a price to live with it.

In the areas of Medtech, Biotech, Deep Tech and other research-led sectors, that price often appears long before a new solution exists.

For example:

• In MedTech, clinicians adapting procedures or workflows to compensate, increased monitoring, manual checks, or secondary confirmation steps or even hospitals absorbing higher operating costs to manage the limitation. These are behavioural signals, even if no one can “fix” the problem yet.

• In BioTech or Therapeutics, where there is no effective treatment for an illness or condition, off-label use of existing drugs, multi-drug regimens to manage symptoms imperfectly or funding flowing into adjacent or partial solutions. Again, these are cost-bearing behaviours, not hypotheticals.

• For research-led or deep tech domains, even when the core breakthrough does not exist yet, you may still see, organisations investing heavily in mitigation rather than resolution or policy, compliance, or safety layers added to manage known risk. If people are reorganising work, absorbing risk, or allocating capital around the problem, the signal is real.

If people are reorganising work, absorbing cost, or accepting risk around a problem, the signal is real.

“Unsolvable today” does not mean “not urgent.”

“No workaround” usually means “no urgency.”

Why the Demand Signals Matters

Different audiences. Same failure mode.

The First Test is universal because the mistake it prevents is universal: building before understanding.

However, its value appears differently depending on who you are.

• For the founder, it prevents months of building something elegant, impressive and irrelevant. Many early-stage failures are not execution failures; they are problem-selection failures. The First Test forces founders to earn the right to build.

• For the corporate innovator, it cuts through internal enthusiasm, political sponsorship and innovation theatre. Internal alignment is not external demand. The First Test recentres the conversation on reality rather than narratives.

• For researchers or Universities, it bridges the gap between technical novelty and real-world application. The question shifts from “What could this technology do?” to “Where is the world already struggling without it?

• For the investor, it helps to focus on a team that understands markets, not just ideas. It is a fast, cheap initial filter for your pipeline.

That shift is the difference between publications and impact.

Let’s Execute

No workshops. No frameworks. No theatre.

You do not need permission, funding or a team to run The First Test. You need curiosity and discipline.

1. Write the problem once.
   One sentence. Plain language. No solutions.If you cannot do this, stop.

2. Hunt for behaviour.
   Look for where the problem already shows up, in workflows, reports, budgets, complaints, manual effort, workarounds, etc. If you cannot find three real examples, you do not yet have a problem.`

3. Validate one workaround.
   Talk to the person doing the work. Not what they think. Not what they believe. What they do. Ask them to show you what they actually do. Behaviour rarely lies.

4. Score what you see.
   Not emotionally. Not optimistically. But honestly

   1. How often does this occur?

   2. How painful is it?

   3. What does it cost?

   4. What happens if nothing changes?

High scores earn progress. Low scores earn restraint.

5. Decide.
   Proceed, reposition, or pause. Most teams drift. Operators decide.

A Closing Thought

Innovation begins with observation, not invention.

The market leaves breadcrumbs everywhere.

Follow the behaviour. If people are not already solving the problem today with time, money, or effort. It is improbable that people will suddenly start once your product appears. Developing an understanding on this will help you to choose problems that justify your scarce time, capital, and focus.

Novel solutions win. Novel problems do not.

What coming next?

Passing The First Test does not guarantee you are right, or will be successful.

In the next issue, we will look at why even strong-looking demand signals are often misread, how enthusiasm, pilots, sponsorship and alignment can create the illusion of traction.

We will unpack most common false positives, the signals that quietly matter more to help minimise time, capital and credibility are wasted.

If you are building a startup or a new venture within a corporation, you have probably been told that failure is part of the process. But let's be honest - knowing that does not make rejections, pivots, or financial struggles feel any less brutal.

• The sleepless nights.

• The rejections from investors.

• The pivots feel like starting over.

• The overwhelming question: "Am I wasting my time?"

But (most likely) every founder who has succeeded in their mission has been where you may be today.

The difference? They did not stop.

You will never have everything right the first time when building something new from scratch.

You need to get just one big thing right. And that one big thing maybe something unexpected and never planned for. Potentially directly from your friends, your customers, or potential investors, not necessarily directly from your head.

Stay in the game.

Some may think that a founder's success comes from a series of perfect decisions, but history tells us a different story.

• Airbnb was rejected by many investors.

• Slack started as a gaming company. They spent years building a game but noticed their internal messaging tool was useful. That "failure" turned into a billion-dollar business.

• WhatsApp was just another messaging app. But they focused relentlessly on simplicity, privacy, and zero ads. That single insight made them indispensable, leading to one of the most significant acquisitions in tech history.

While luck is a factor, you can’t always control it. Yet, these ventures, teams, and founders showed unwavering determination. Through continuous learning, iteration, and adaptation, they discovered a game-changing move.

And that's the game you're playing. Not perfection. Not overnight success. But the constant search for that one move.

Why failure is just data in disguise?

Let’s reframe failure.
Failure is not a dead end—it is market feedback.
Every misstep is actually giving you invaluable information:

• Customers not paying at your pricing point? Now you know what does not work.

• Did your MVP flop? Now you know what is missing.

• Investors passed? Now you know where your pitch needs improvement.

Every “failure” is a step forward if you’re paying attention.

The best founders, leaders and teams aren’t avoiding failure—they’re using it as a learning tool.

That pivot, that one move that changes everything.

Many desired unicorns and successful ventures often no longer look like their original idea.

• Instagram started as Burbn, a location-based check-in app. However, users only cared about the photo-sharing feature. So, the founders scrapped everything else.

• PayPal originally built encryption software before pivoting into digital payments. If they had never pivoted from their initial intent, the early success of online auctioning and shopping may have looked very different.

Your first idea is rarely your best idea, but like wine can get better over time.

What matters is whether you're listening, iterating, and willing to adapt when the proper insight appears.

The Founder Mindset Shift: Play the Long Game

If you are struggling at work and thinking about quitting, take a deep breath, pause and reflect. Here’s how to shift your mindset:

• Done is better than perfect. Stop overthinking and get something into the hands of real users. The best insights come from the market, not from your own head.

• Failure is an experiment, not an ending. Every setback is a data point. Ask yourself: What did I learn? What should I try next?

• Flexibility is your greatest asset. If users love one unexpected feature—double down on it. If investors give consistent feedback,—adjust your pitch.

• Small wins compound. You do not need to build a billion-dollar company overnight. Just land one great customer, one key investor, one small validation. That’s how you build momentum and gain traction.

Keep pushing. Keep iterating. Keep believing.

In startups and new ventures, you do not always need to be right; sometimes, you need to be right once. It could be the next thing you try.

Interesting Content Found:

1. Airbnb's Early Rejections: In 2008, Airbnb co-founders Brian Chesky and Joe Gebbia sought to raise $150,000 at a $1.5 million valuation, offering a 10% stake in their company. They approached seven investors, five of whom sent rejection emails, while two did not respond.
   https://medium.com/%40bchesky/7-rejections-7d894cbaa084

2. Slack's Pivot from a Failed Gaming Company: Slack originated as an internal communication tool used within Stewart Butterfield's company, Tiny Speck, during its work on the development of "Glitch," an online video game. After realizing the game's lack of profitability, Butterfield decided to repurpose the communication tools into what became Slack.
   https://techcrunch.com/2019/05/30/the-slack-origin-story/

3. WhatsApp's founders, Jan Koum and Brian Acton, emphasised simplicity and user privacy as core principles. They deliberately avoided advertisements and prioritised a straightforward, user-friendly interface, which contributed to the app's widespread adoption and eventual acquisition by Facebook.
   https://www.wired.com/story/whats-app-owner-founder-jan-koum-facebook/
   https://www.fastcompany.com/40459142/whatsapps-cofounder-on-how-it-reached-1-3-billion-users-without-losing-its-focus

Let's skip the fluff before we start the echo chamber to each other, "This is my year," let the dust settle, embrace recovery and regeneration with friends and family and set yourself up for success.

Start with Gratitude

The first and most crucial step is to take stock of what happened in 2024. Because if you are anything like me, last year was a ride - some interesting wins, some glorious fails and a lot of figuring it out as we went.

Building something from scratch is not a simple task, and here's the truth: no one does it alone. Think about it beyond what worked and what did not, and ask yourself:

• Who was there when you wanted to quit?

• Who made you laugh when it all felt too heavy?

• Who gave you the push you needed—or just quietly believed in you?

For me, multiple people, family, friends, mentors, fellow founders and clients played a role in my 2024 journey, providing support, guidance, skills, and even renewed belief in continuing to pursue those crazy challenges despite the obstacles and criticisms. Before diving into 2025, I recognise the people who had my back last year. The ones who were there when it was not pretty. Because no matter how hard we grind, no one builds anything worthwhile entirely on their own.

Now, let's talk about goals.

2025 may still feel like a blank canvas, but let's not just throw paint on it and call it a masterpiece. Whether you are still pre-seed and flying solo or getting ready to raise your Series B capital investment. Let's get intentional. Ask yourself some tough questions.

• What's the one bold move you were holding off because of the fear of failure?

• Where do you want to be by this time next year—and what's the first step to get there?

• Who do you need to surround yourself with to make it happen?

Irrespective of your goal or goals for your venture in 2025, stay focused, make them specific, avoid burnout, build support, and revert to your original why when things get tough.

Five Quick Tips for setting goals up for success.

1) Be Focused:

Many things will probably pull you in different directions throughout the year. Remember, you cannot do everything, and you cannot be everything to everyone. I did state one intentionally as you do not need 20 goals; you need a few right ones—Prioritise quality over quantity. Focus on what matters most and break it down.

Any big goal can feel overwhelming, but breaking it into smaller, actionable steps makes it manageable. Instead of saying, "I want to grow my startup," try, for example:

• Q1: Launch the MVP

• Q2: Establish a sales pipeline.

• Q3: Onboard my ten first-paying clients.

2) Be Specific:

Nothing fancy. Make your goals specific and measurable.

"Get better at marketing" is not a goal; some say this would be a vague wish. Try, instead: "Run three paid ad experiments and measure return on investment at the end of March."

When goals are clear, they are easier to track, achieve, and learn from. Break them into smaller milestones to track how far you have come. Celebrate the wins—even the small ones—and learn from the stumbles. Achieving traction and progress is better than finding perfection.

3) Avoid Burnout / Avoid the noise

Do not do everything simultaneously. Focus your own and your team's energy on where it counts. It is okay to say no to projects, ideas, or tasks that do not align with your core vision.

4) Build Up your Goal Support

Encircle yourself with a reference group that provides support. Find your people: mentors, co-founders, advisors, or a community of peers who'll challenge and cheer for you. The right people will keep you accountable and remind you why you started.

5) It is all about the Why

Above all, remember the "why." When the going gets tough (and it will), reconnect with why you started. Your "why" is the anchor that keeps you grounded and instils the culture and mindset needed in your team to push forward and achieve progress.

Lastly, Growth

And let us not forget growth; growth is not just about hitting milestones—it is about learning, adapting, and becoming a better version of yourself, even when it becomes uncomfortable and life throws you an impressive curveball. Growth happens in the messy middle, so embrace it.

Now, thank and recognise those who got you through 2024, and here to a 2025 jam-packed packed with big and scary goals, achievable outcomes, showing up for the people who matter and embracing the messy but beautiful journey of growth and venturing.

Comment below what you’re grateful for from 2024 and your number one goal for 2025! Let’s inspire each other to grow and thrive.