Custom Governance: The Cure for Innovation Antibodies

Ask why a capable, well-run company keeps failing to produce radical or transformative innovation and the honest answer is uncomfortable: the same organization that runs the core business superbly is quietly rejecting anything that doesn't look like the existing core business. We call these forces the innovation antibodies, and it helps to be fair to them, because they are there for a good reason. Rejecting whatever doesn't fit is how the core stays focused, efficient, and disciplined; the antibodies are the organizational immune system that keeps unproven bets and distractions from diluting a business that already works. The important thing about them is that they behave like gravity. You can't see them directly, they act on everything all the time, and you can't switch them off by wanting to. A review that wasn't designed for this kind of uncertainty, a shared resource the venture can't get prioritized to access, a progress metric it was never positioned to hit: each is reasonable on its own in the core business, but together they surround and slowly smother the innovation work.

If the antibodies are the organization operating exactly as designed, and doing something valuable while they do it, then trying harder inside that design won't beat them. The cure is to give the innovation work a different operating model, designed for its unique purpose. That is what custom governance is. The trouble is that "custom governance" usually gets hand-waved as "just give the team some autonomy," or "create a new or dedicated org unit," and that under-specification is exactly why it so often fails. Designing it is concrete work at two levels, calibrated to how far the work sits from the core, and it includes a transition that most prescriptions skip and that a venture's own early success can quietly sabotage.

First, a precondition

Governance design does nothing on its own. It needs a real strategic mandate for innovation, with accountability for defined outcomes, and active leadership sponsorship behind it. Without those, any exemption you carefully design is simply ignored the first time it is inconvenient. Mandate and sponsorship are their own subject, and we treat them separately in what a successful new-business innovation capability actually requires. The reason they matter here is the bridge into everything below: sponsorship and leadership accountability are the will to protect the new work, and governance is what makes that will durable and institutional, rather than dependent on one champion's vigilance that vanishes the day they change roles.

With that in place, be precise about what custom governance is and isn't. It is not an open playground, and it is not just an off-books unit flying under the radar. If anything, the original Skunkworks is the prototype of custom governance done right: an operating model deliberately designed for a purpose distinct from the core. The term has since been watered down to mean little more than "an autonomous team," which drops the part that actually matters, governance purpose-built for the work. Real custom governance operates at two levels, and it is a different job at each.

Governance Level one: the innovation portfolio operating model

The first level is the operating model for the innovation portfolio as a whole, set deliberately against the company's default corporate governance rather than borrowed from it. This is systems design, and it turns on a handful of decisions.

The most consequential is how the work is funded. A core business is funded on the calendar, an annual budget set against forecasts. Innovation should be funded against evidence, in staged, cash-like increments released as a venture earns the right to the next one. Investment is timed to evidence-readiness, never to the budget cycle. Alongside funding sit the evaluation criteria, deliberately designed to differ by how far a bet sits from the core rather than applied uniformly, plus clear decision rights and exit criteria, and metrics and cadences fit for uncertain work instead of the core's reporting rhythm.

The tell that a company lacks this level is the per-project carve-out grind: every venture has to fight for the same exceptions, one at a time, winning them by force of a sponsor's personality and losing them the moment that sponsor's attention moves on. Custom governance replaces that grind with institutionalized exceptions, decided once and applied by design. And a defining responsibility of this level is that it has to frame and facilitate the second one: the portfolio operating model exists partly to make good project-level governance easy to grant, so each new venture isn't a fresh negotiation from zero.

One honest caveat belongs here. This structure makes a Stop economically real, because staged funding means stopping a venture actually frees resources to redeploy rather than triggering a fight over a committed annual budget. But making a Stop possible is not the same as calling it. That still takes a decision culture willing to act on the evidence, which governance can enable but cannot supply.

Governance Level two: calibrating the individual project or venture

The second level is where the portfolio model meets a specific venture, and it is an equal and equally demanding job, just a different one. Here the question is concrete: which of the core's synergies will this venture actually use, and which of the core's rules will it be exempted from? Connect it to the distribution, brand, technology, and capital that justified building it inside, and exempt it from the processes and thresholds that would sand the distinct and new innovation off it.

The primary variable that should drive those choices is adjacency, meaning how far the venture sits from the core's Resources, Processes, and Priorities (its RPP). Adjacency is the first-order driver of how much custom governance a venture needs. A near-core initiative shares most of the core's RPP and needs only light exemption; a far-adjacency bet violates most of it and needs a great deal, and if you judge that far bet by core-business criteria it will always look bad, right up until you have killed it. Calibrating exemption to adjacency, venture by venture, is what keeps a promising far bet from being quietly conformed to death, and it is precisely the portfolio-level framework from level one that makes this calibration repeatable rather than a heroic act each time. (Where a venture's evaluation lands on Continue, Pivot, Pause, or Stop is the vocabulary we use for those staged decisions; the point here is that the criteria behind them are calibrated to adjacency, not applied uniformly.)

The governance transition most prescriptions skip

The move that generic "give them autonomy" advice at the project level leaves out, and the most distinctive part of getting this right, is the transition. A venture doesn't only need protected governance early. It needs a deliberately designed transition out of explore-mode governance and toward the scale-and-optimize-mode governance the established business runs under, the graduation we've explored in our work on scaling transformation. This is not necessarily a move between organizations. It is a deliberate change of the rules, metrics, and cadence the venture lives under.

The trigger for that transition is usually traction, and traction is also where the instinct goes wrong. When a venture starts posting real results, the temptation is to treat those positive indicators as proof it is ready and hand it straight back into the core's standard governance. That often kills it, because the traction depended on custom-governance attributes the core doesn't have, or actively works against. The right read is the opposite: traction is the signal that transitional governance is now needed, to begin aligning the venture with the core where and when that genuinely helps, while deliberately preserving the custom attributes it still uniquely needs.

So the transition is rarely a single step. It can hold several stages within a shared, transitional governance phase, and the movement between them should be triggered by predefined criteria and conditions the venture actually meets, not by a calendar or an arbitrary timeframe. Skip the design and this is exactly where promising ventures crash: they clear the early gates, the hand-in to normal operating governance is undesigned, and the antibodies that were held off at the start finally get their shot on a venture now big enough to be worth attacking. Designing this transition belongs in the governance from the beginning; it cannot be improvised once the venture is winning.

It has to be engineered, and maintained

Everything above is deliberate organizational system engineering, not encouragement, and that is the whole point. The moment innovation rests on willpower or on winning exceptions one fight at a time, the antibodies come back, because the default operating model never actually changed. The maturity curve runs from that per-project carve-out grind, through institutionalized exceptions, to a complete alternative operating model that runs wherever innovation lives and is measured and continuously tuned as the company learns what works. If you want an honest read on where your organization's governance sits on that curve, and on the other conditions that decide whether good innovation work survives, our Innovation Capability Assessment scores exactly this.

Getting there is design work, and it is a large part of what we do. BRI consulting designs the operating model with your team: the portfolio governance, the adjacency-differentiated criteria, the decision and exit rights, and the transition. Growth Forge® Software then institutionalizes and scales that model, so the differentiated criteria and evidence-timed cadence become how the system runs rather than something a champion has to defend by hand.

The companies that reliably produce radical innovation didn't out-will their antibodies. They stopped asking a system built to run the core to also incubate radical ventures on the core's terms, and they designed a different operating model for the work: at the portfolio level, at the level of each venture, and across the transition between them, tuned deliberately over time. That design is the cure.

BRI Associates helps companies grow by drawing on decades of practitioner experience in corporate innovation and new business development — practitioners, not pundits or academics — through direct consulting, training workshops, and Growth Forge® Software, built for the unique requirements of corporate innovation and growth organizations.