Innovation Activity ≠ Innovation Outcomes
Updated: Sep 30
“Around 3,000 different people built this yacht.”
This comment stood out during a tour onboard the 111m Oceanco LEVIATHAN because it highlights something broader than one project.
Yachting is an extraordinary multidisciplinary brain trust. Designers, naval architects, engineers, shipyards, specialist suppliers, project teams, crew, brokers, managers, lawyers and regulatory bodies bring very different expertise, requirements and perspectives together to deliver exceptionally complex projects.
There is clearly no shortage of capability. Yet different conversations around innovation repeatedly returned to the difficulty of turning good ideas into useful outcomes.
There is also an important tension at the heart of the subject. Innovation requires tolerance for ambiguity, experimentation and failure. Yacht projects are generally structured around the opposite: certainty of cost, programme, performance and reliability.
Not every client wants to be an early adopter, nor should every project seek to push boundaries. For many, a proven solution with lower risk and less friction is entirely rational.
The question is therefore not simply how to enable more innovation, but where innovation creates enough value to justify the uncertainty it can introduce.
Where it does, five challenges seem to recur.
Silos
Innovation naturally starts with what people know and can directly influence. Engineers see engineering opportunities, designers approach them through design, commercial teams through cost and risk, technology companies through their systems and crew through operation.
Such specialist depth is a strength, but the consequences rarely remain within one discipline. A technical improvement may affect design, weight, power, integration, cost, compliance, maintenance and operation.
Innovation may start vertically, but adoption requires looking horizontally.
Interfaces
A shipyard acts as prime contractor, but specialist capability is distributed across manufacturers, integrators, suppliers and subcontractors.
Innovation opportunities can exist between systems, disciplines or contractual scopes, where ownership is unclear.
Who develops it? Who integrates it? Whose scope does it belong to?
Incentives
Technical merit alone does not determine whether an innovative idea progresses.
Different companies operate within their own delivery deadlines, budgets, margins, contracts, intellectual property and warranty obligations. A better solution might require one party to fund development, another to integrate it and somebody else to carry the risk.
This is amplified by low volumes and high levels of customisation in yachting. Development costs and integration risk may be carried for a single project, while the opportunity to repeat the solution elsewhere is not guaranteed.
Who pays? Who integrates? Who carries the risk? Who benefits?
If these answers point in different directions, a technically good idea can quite rationally stall.
Complexity
Innovation is often associated with adding capability: more functionality, integration, automation and data.
But every addition can also introduce friction, dependencies, training, maintenance and potential failure. Individually sensible decisions can accumulate into an overly complex system.
This is critical for an asset expected to operate reliably and independently, often far from immediate technical support. Novelty has to justify the integration, maintenance and operational risk it introduces.
Innovation has to earn its place. Does it make the yacht, system or experience meaningfully better?
Continuity
Yachting’s project-based structure creates another challenge. Teams coalesce around individual projects before people move between yachts, yards, suppliers and client teams.
Some learning remains within organisations and some moves with individuals.
This can fragment institutional memory, but it can also create valuable cross-pollination as experience from one project finds an application elsewhere.
Is knowledge captured and applied, or rediscovered on the next project?
Activity ≠ Outcomes
None of this suggests yachting lacks innovation. There is activity across research, partnerships, prototypes, new technologies and experimentation onboard yachts.
Individual clients can also provide the ambition and capital to push technology beyond normal commercial constraints. This can make yachts useful demonstrators, but proving something on one exceptional project is different from establishing repeatable adoption.
All of this activity can be valuable, but activity is not the same as outcomes.
A prototype can demonstrate that something works. A yacht can demonstrate that something is possible. Neither necessarily demonstrates adoption, repeatability or lasting value at scale.
Equally, an experiment that fails can produce a valuable outcome if the learning changes the next decision.
Lastly, not all innovation activity represents the same level of maturity. Basic research, experimental technologies, demonstrators and production-ready solutions require very different approaches to funding, risk and adoption.
The opportunity is therefore not simply to generate more ideas or pursue more innovation. It is to identify where innovation creates genuine value, then improve the conditions that allow the right ideas to progress from insight to practical adoption.
Silos need connection.
Interfaces need integration.
Incentives need alignment.
Complexity needs clarity.
Continuity needs learning.
Many of the answers may already exist within the sector’s considerable brain trust. The harder task is connecting the expertise, organisations and incentives required to turn them into outcomes.
Which leaves one useful question whenever something is described as innovative:
What actually changed?
Comments