An operating system for non-core growth

The design called for a dedicated, separately funded structure to build new businesses at arm's length from the core. That structure was not stood up. The handbook is in use; the full vehicle is not.

The brief

A corporate owner wanted its non-core growth effort to run as a system rather than a series of projects. Projects die with the people who run them; a system does not. The mandate was to design that system properly: defined stages from raw idea to first product, argued gates between them, governance, and a talent model.

What I built

A standalone operating design covering the full path from idea to first product. Stage definitions with entry and exit criteria. Gate reviews with scoring that blends machine evidence and human judgment. Governance that says who decides what, and when. Roles, incentives, and the talent model this kind of engine actually needs, which is not the same one a corporate project needs. All of it lands as a single start-to-finish handbook with the supporting templates attached, so the next team inherits the method instead of reinventing it.

Alongside the handbook sat the strategic case for the engine itself: how AI runs through the process end to end, how the innovation tools integrate into one pipeline rather than a drawer of frameworks, and why a well-run engine attracts talent a corporate programme cannot.

The real ending

The full vehicle was not stood up, and I would rather show the case with its real ending than pretend every design converts in full. What survived is what was built to survive: the client team runs its pipeline on the handbook.

One of a set of engagement and systems case studies. If a problem like this is on your desk, start with a conversation.