The innovation engine

Where strategy becomes something you can hold.

A working week that ends with an artefact. Your team arrives with a challenge and leaves with something tested — not a photograph of a wall and a deck assembled afterwards by whoever had the least to do.

Five days · one arc · senior-led throughout

01The format

Every depth runs through here.

Catalyst Labs is not a separate offer sitting beside the engagement ladder. It is how the ladder is delivered. An Ignition can be a single Lab. A Liftoff is usually one. A Transformation is a sequence of them, spaced against the decisions they serve.

The format holds whatever the question, which is what makes a five-day week predictable enough to put senior people in the room for all of it.

Day 01

Frame

What decision is being made, who signs it, and what would change it.

Day 02

Gather

Evidence assembled against the frame, graded and dated, gaps named as gaps.

Day 03

Fold

Options built and stress-tested. Disagreement invited onto the record.

Day 04

Test

Reviewed against the gates, with the people who own the evidence present.

Day 05

Hand over

The artefact, the reasoning, and the structure — in your tenant, usable without us.

02Lab instances

Same arc, different room.

Each instance is the format tuned to a domain — the questions in Day 01, the evidence pathways in Day 02, and the gates on Day 04 differ. The week does not.

Future Lab

Strategic foresight and scenario design for an uncertain market. The delivery vehicle for a PULSE engagement.

Launch Lab

Launch readiness and sequencing, with what fails first ranked rather than reported by workstream.

Access Lab

Market access and payer strategy worked through tangibly, against the objections a payer will actually raise.

Patient Lab

Patient journey and access barriers — mapped with each barrier owned by someone who can remove it.

Discovery Lab

Where an AI or operating-model question gets scoped honestly before anyone commits budget to it.

More on request

The instance list grows as practices do. If yours is not here, the arc still applies — the tuning is the work.

03Why it works

Three things a workshop usually cannot do.

01

The environment produces structure, not artefacts of attendance

Sessions run inside the working environment rather than a meeting room, so what comes out is captured as it is made. Nothing has to be reconstructed on Monday by someone who was not in the argument.

02

Disagreement is scheduled, on Day 03

A workshop tends to surface dissent by accident, late, and treat it as a problem. Here it is the point of a day — because a recommendation everyone agreed with is usually one nobody stress-tested.

03

The week ends with a handover, not a promise of one

Day 05 is not a readout. It is the transfer of the artefact and the structure that produced it, in a form your team can re-run.

04Delivery

Senior-led throughout.

The person who scopes the Lab runs the Lab. There is no facilitation team and no handover to delivery — the week is short precisely because it is expensive to staff properly, and staffing it any other way removes the reason it works.

Labs run in the SmartLab environment, delivered with Ludic Group. Ludic supplies the environment; the Labs we build in it, and everything inside them, are ours and yours.

Contact us