The Loonshot Transfer System
Separate innovators from operators, then actively manage ideas between them
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 98%
Organizations need artists who explore uncertain ideas and soldiers who deliver reliably on time, on budget, and on specification. Because these jobs reward opposite behaviors, forcing both into one structure causes either reckless operations or timid innovation. The solution is to separate the groups while deliberately managing the transfer between them. A leader acts as a gardener: nurturing fragile ideas, exposing them to operational scrutiny, and helping both sides translate their needs. Productive resistance is preserved rather than suppressed because operators reveal practical weaknesses while innovators prevent the franchise from becoming obsolete. Success is measured not by the number of ideas generated or labs created, but by whether promising ideas cross the boundary, improve through feedback, and reach deployment.
Origin
Extracted from Masters in Business through Safi Bahcall's account of Vannevar Bush, Bell Labs, Apple, and military innovation systems.
Core principles
- 01Innovation and execution require different operating conditions
- 02Separating innovators and operators is necessary but insufficient
- 03The transfer between groups is the most common failure point
- 04Constructive tension improves both novelty and practicality
- 05Leaders should manage the transfer rather than choose every technology
How to run it
- 1
Define the two jobs
Separate exploratory work, where failure is expected, from operational work, where reliability is essential. Give each group goals and rewards appropriate to its mission.
Pro tip Describe the groups by their jobs rather than labeling one creative and the other bureaucratic.
Watch out Do not ask safety-critical operators to experiment with the same failure tolerance as a lab.
- 2
Create structural separation
Give experimental teams enough autonomy to test ideas without routine operating pressures killing them prematurely.
Pro tip Protect early ideas until they have evidence strong enough for operational review.
Watch out A detached innovation lab without an adoption path becomes innovation theater.
- 3
Appoint credible translators
Choose people respected by both innovators and operators to carry evidence, constraints, and feedback across the boundary.
Pro tip Develop transfer leadership as a serious career path rather than an administrative assignment.
Watch out A weak liaison with no authority or technical credibility cannot resolve resistance.
- 4
Expose ideas to the field
Move promising concepts into realistic environments where operators can test cost, reliability, and usability. Expect resistance and use it to improve the idea.
Pro tip Start with controlled pilots that produce concrete learning for both groups.
Watch out Do not interpret every objection as hostility to innovation.
- 5
Manage the transfer
Keep innovators and operators engaged as the idea evolves toward scale. Focus leadership attention on the handoff rather than personally dictating the winning technology.
Pro tip Measure conversion from experiments to adopted capabilities, not raw idea counts.
Watch out Anointing projects by executive preference creates the Moses trap.
In the wild
On returning to Apple, Steve Jobs elevated designer Jony Ive and recruited Tim Cook, an extreme operational specialist. Jobs managed the relationship between original product design and disciplined production rather than doing either job alone. The iPad needed both an attractive new concept and the operational work that reduced an impractical cost to a mass-market price.
→ Apple paired ambitious product innovation with scalable, affordable execution.
Vannevar Bush created a structure that connected civilian scientists developing unusual technologies with the military organizations deploying them. His credibility across engineering, government, and military contexts helped radar and the proximity fuse reach battlefields where they changed wartime outcomes.
→ Experimental technologies crossed institutional boundaries and became decisive operational capabilities.
Common mistakes
Building an isolated innovation lab
Physical separation alone does not create adoption. Without a strong transfer mechanism, the lab produces demonstrations that operating groups never use.
Forcing both groups into one culture
Uniform incentives either punish useful experimentation or weaken operational discipline. The two jobs need different conditions.
Managing technology instead of transfer
A leader who personally anoints projects becomes a bottleneck and amplifies selection errors. Leadership attention should strengthen the system that tests and transfers ideas.
Is it for you?
Best for
It is best for growing companies, research institutions, and public-sector organizations balancing innovation with dependable execution.
Not ideal for
It is not ideal for tiny teams whose innovators and operators are still the same people.
From the transcript
“The failure point in most innovation in large companies with a public sector a private sector is in that transfer.”
“What you want to do is manage the transfer, not the technology.”
“you want to lead much more like a gardener rather than a Moses.”
From the episode
Safi Bahcall on Why You Need to Take Crazy Risks
Safi Bahcall