Issue #12: The Venture Operator Function
The function that converts signals into structural commitment.
This issue is Part 6 of a 6-issue arc on Corporate Venturing Under Constraint.
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.
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.
A note on what this is not, because it is the first objection the structure invites. The two tiers are accountabilities, not headcount. Importantly, they do not create a requirement for two new layers of management. In a small innovation portfolio, one person may hold both Opportunity Authority and Option Authority, and the model still holds, because the accountabilities remain distinct even when the same person carries them. What cannot happen is the two collapsing into each other, so that the person executing an option is also the person deciding whether to stop it.
The separation is of decision rights, not of organisational chart boxes.
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.
Question 1. Signal ownership. Within an opportunity area, is there a single named node accountable for deciding when an option’s evidence has crossed the threshold for increased commitment, with the authority to act before the next scheduled forum? Name them.
Failure mode: Signal limbo, the threshold is crossed and recorded, but no one is authorised to convert the reading into commitment until a forum convenes. The signal decays in the gap.
Question 2. Scope authority. Within an opportunity area, is there a single named node that can narrow the option set or redirect an option on emerging evidence, without assembling cross-functional consensus? Name them.
Failure mode: Scope drift, the option set only ever widens. Bets accumulate because no one can cut, and the area loses focus as it adds rather than concentrates.
Question 3. Resource movement. Is there a single named node that can move capital and talent across the option set, onto options whose evidence is strengthening and off those decaying, between planning cycles and across vehicle types? Name them.
Failure mode: Allocation lock, resources move only at the planning cycle’s cadence and only within their original vehicle, regardless of what the evidence is doing across the set.
Question 4. Stop authority. Is there a single named node that can stop an individual option when its bet is failing, and also retire an entire opportunity area when its hypothesis no longer holds, redirecting what either frees, without requiring the agreement of the people running the option or the leadership that endorsed the area? Name them.
Failure mode: Stop by attrition at both levels; therefore, options are starved rather than stopped, and areas persist long after the hypothesis has been falsified, because retiring a leadership-endorsed theme is the most expensive and least-owned decision in the system.
Question 5. Backed authority. When the node makes a call on the evidence, does the decision hold, or must each commitment still clear a strategic gate above and divisional buy-in below before it takes effect, and can it be reopened at the next forum? Name what the decision has to pass through.
Failure mode: Authority on paper but vetoed in practice. The node is named, but its decisions are re-litigated upward and downward until 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.
Question 6. Durability. If the current sponsor or leadership changed tomorrow, would the function persist, or does it exist only because a particular individual currently chooses to operate it? Name what the function depends on.
Failure mode: Sponsor dependence, as the function is being performed, not held. It survives as long as its occupant does and leaves with them.
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.
Ideas do not scale. Execution does. And execution requires a function accountable for structure, not a sponsor who believes in it.
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.
This essay 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.
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.