Who this is for: innovation leads, product and portfolio managers, and transformation sponsors in established organisations — people who own an innovation mandate but not the organisational conditions that make it work.
Corporate innovation rarely fails for lack of ideas. It fails at the seams: between the functions that each hold one part of the problem, and between the capability the strategy assumes and the capability the team actually has.
What "interdisciplinary" means here
It does not mean “everyone in one room”. It means a team where four distinct kinds of thinking are genuinely present and able to argue with each other:
- Desirability — what people actually want, understood well enough to be evidence rather than opinion.
- Feasibility — what can be built and run, including the operational reality nobody put in the deck.
- Viability — what the business can sustain: margin, channel, risk.
- Distinctiveness — why anyone would choose this over the alternative, including doing nothing.
The Innovation SWAT capability model — the iSWAT roles of Strategist, Wizard, Activator and Technologist — exists to make this concrete: four ways of contributing to the same decision, each with its own hard skills.
Where innovation capability actually breaks
- The translator gap. Someone can sit in a design review, then an operations meeting, then a strategy conversation without needing a translator. Organisations rarely name this as a skill, so they rarely develop it.
- Evidence collapse. Early conviction gets rationalised into a business case before it has met a customer. The team is then defending a number rather than testing a hypothesis.
- Handover loss. The innovation team validates something real, then hands it to a business unit with no context and no incentive, and it dies in transition.
- Capability theatre. Innovation is measured by activity — workshops, pilots, hackathons — rather than by decisions changed.
Diagnosing before you train
Most capability programmes start with a curriculum. We would start with a diagnosis, because the same symptom — “our pipeline is thin” — has different causes: a desirability problem (weak user evidence), a governance problem (no path to approval), or a capability problem (nobody can bridge functions).
A structured audit of the innovation process, the evidence trail behind current bets, and the skills actually present usually narrows this quickly. It also gives you a baseline, which is otherwise the first thing lost when a programme is judged.
The sequence that tends to work
- Frame a real decision the organisation is already facing. Not a training case.
- Assemble across functions and give the team a shared method, so disagreement is about the problem rather than about vocabulary.
- Force the evidence step before the business case, and make the cheapest test visible.
- Build the bridge to the business unit early, not at handover.
- Name the capability you are building, and measure that — not workshop attendance.
From the Build Up series
- Abundance with architecture — why structure beats volume
- Innovation distinctions that can save millions
- Problem-solution fit — what counts as evidence
Also on this site
- The AI leadership reference, for how AI changes the governance layer of this work.
- The Innovation SWAT FAQ for the frameworks behind these terms.
Where this gets put to work
Innovation SWAT publishes the research and frameworks. Artefactx — one of Justin Tsui’s own innovation engines — delivers the interdisciplinary corporate innovation and AI leadership training, and runs the business innovation audit and consulting engagement if you want the diagnosis done independently before committing to a programme.
Frequently asked questions
What is interdisciplinary corporate innovation?
Innovation work done by a team that genuinely spans four kinds of thinking — desirability, feasibility, viability and distinctiveness — rather than by specialists handing work to each other in sequence. The value comes from the disagreement being present early, when it is still cheap.
Why do cross-functional innovation teams outperform specialist teams?
Because most innovation failures are integration failures, not invention failures. A cross-functional team catches feasibility and viability objections while the idea is still cheap to change; a sequential process discovers them only once the commitment is made.
Do we need a consulting engagement or a training programme?
If the diagnosis is genuinely unclear, start with the audit — it is faster to buy clarity than to train a team against a problem you have not located. If the gap is already known, training is the shorter route.
Can this be delivered for a single department?
Yes, though interdisciplinary work benefits from at least two functions being present. A single department can learn the method, but the seam problems usually live between departments. Artefactx can advise on the right shape.
Research note: this page summarises Innovation SWAT’s own frameworks and field work. It is written as a neutral capability reference rather than a sales page. The hands-on delivery sits inside Justin Tsui’s own interdisciplinary innovation engines, linked above.