How to Obtain Innovation Without the Inconvenience of Development cycles

Note: This paper draws on patterns observed across several industrial relationships. Company names, locations, product descriptions, job titles, transaction structures and chronology have been deliberately generalised, combined or reordered so that no individual company or relationship is identifiable. The argument concerns the mechanism, not the parties.

Research question: Why does the position of an innovator weaken in direct proportion to the success with which his knowledge is shared, and why does the same mechanism recur across unrelated relationships?

Introduction

Innovation is expensive mainly before it becomes interesting. Somebody must spend years testing ideas, changing materials, rejecting suppliers, correcting assumptions and discovering which elegant solutions fail when exposed to manufacturing, customers and reality. By the time a larger organisation becomes interested, most of that history has disappeared from view, and what remains is a functioning product that can suddenly be explained in a meeting.

This creates an attractive commercial possibility. Rather than reproduce the development cycle, an established company can cooperate with the person who has already completed most of it, and thereby obtain the result without the inconvenience of the process. This paper does not ask whether any particular organisation behaved badly, which would require evidence it does not claim to hold. It asks a more useful question: how a sequence of individually ordinary business decisions can arrive, more than once, at an outcome nobody would have proposed at the outset.

1. The Expensive Part Happens First

At the beginning of such relationships, the innovator is valued for exactly what he is. His experience is unusual, his design knowledge difficult to reproduce, and his unconventional working style is often regarded as one of the reasons the innovation exists at all. He moves quickly, changes direction when evidence requires it, tests alternatives and eliminates those that prove unsuitable. In a small technology company this is called entrepreneurship. The observation worth recording at the outset is that the behaviour is not yet being judged; it is being purchased.

The value of that behaviour lies less in the product than in the route that produced it. A finished design shows the choices that survived, not the larger number that were eliminated. Mature engineering consists in significant part of negative knowledge: knowing what no longer needs to be tested. Positive knowledge can in principle be reverse-engineered from a product, whereas negative knowledge cannot, because the product carries no trace of the routes abandoned. The most valuable thing an established organisation can obtain from an innovator is therefore the least visible, and consequently the most difficult to claim afterwards.

In a mature corporation, some of the same behaviour may later acquire a different name. That renaming is the subject of the sections that follow, because it is the step that converts a commercial transaction into a question of character.

2. Three Relationships, One Mechanism

The pattern considered here appeared in several separate industrial relationships, which have been deliberately blended. In each, an established party became interested in technology developed externally; the relationship advanced far enough for technical or commercial knowledge to move; the innovator’s value was initially recognised; and once knowledge, relationships or capability had been distributed, the position of the person who originally held them became materially less secure. Recurrence across unrelated parties is the significant fact. A failure that appears once may be an accident of personalities, but one that recurs in substantially the same form is more likely a property of the structure.

In the first relationship, discussions about broader cooperation gave an established party access to technical material and digital tools created by a smaller technology company. Commercial terms formed part of those discussions, which shows that the knowledge was not regarded as incidental. After the relationship deteriorated, people with relevant knowledge moved into other parts of the market. Whether that was anyone’s objective should not be asserted without evidence, and need not be. The observation that requires no speculation is that knowledge for which substantial value had once been contemplated could now travel by a considerably cheaper route.

The second relationship developed more explicitly. An externally developed technology was considered as an alternative to the established company’s own development programme. Samples, project information and substantial technical knowledge were shared while the parties discussed combining activities, technology and know-how within a joint operating structure, with the innovator retaining an important technical role. The relationship then progressed into a formal cooperation framework under which the established party would develop and market products using the innovator’s designs, knowledge and supply-chain access. What makes this case instructive is the timing of the later transition: criticism of the innovator increased while demand for his calculations, specifications and supplier knowledge did not immediately disappear. The contribution remained useful even as the narrative surrounding its source became less favourable.

The third relationship approached the same mechanism from the manufacturing side. A manufacturer with substantial market access became interested while broader cooperation was under discussion, and the contemplated arrangement included access to designs and know-how, possible component manufacture and routes to market. Knowledge transfer was not an accidental by-product of such a relationship; it was one of the reasons for its existence. The innovator provided engineering input, vendor involvement and assistance with market opportunities. As financial and operational difficulties accumulated, the description of that contribution shifted towards mistakes, disorder and unfulfilled promises. Some of that criticism may reflect genuine problems and should not be denied. The more interesting issue is proportionality: ordinary first-of-kind difficulties began to form part of a broader judgement of the person, while the technology and know-how remained commercially interesting.

3. Learning Renamed as Failure

The same development process can be interpreted very differently depending on when it is observed. At the beginning, rapid experimentation appears entrepreneurial; later it can be called chaotic. A change prompted by testing first demonstrates technical responsiveness and later becomes evidence that the design was immature. Development expenditure is understood first as the inevitable cost of innovation and subsequently as proof of poor management. Failure and learning are not opposites in product development but frequently the same event, viewed at different times, and the meaning assigned to it depends less on what happened than on who is now describing it.

The retrospective reading is attractive because the organisation that arrives later does not need to start where the original developer started. It has already seen the selected materials, structural principles, manufacturing logic and customer requirements, and may also know which alternatives failed. Its engineers can therefore begin several years further along the learning curve and produce a development process that appears far more disciplined than the one that preceded it. The comparison is not entirely fair, because the later organisation’s orderliness has partly been purchased with access to the earlier organisation’s disorder. If every failed component, unsuitable supplier and post-installation modification is recorded only as a failure, while the knowledge created by it is retained, the history becomes strangely asymmetric: the innovator keeps responsibility for the mistakes, and the organisation keeps the learning.

The asymmetry becomes most visible when supposedly new development revisits options the innovator rejected long ago. To a new engineering team these are legitimate alternatives worth investigating; to the innovator they are old experiments whose shortcomings were paid for years earlier. If he remains central to the process, his knowledge prevents the repetition. If his role is already being reduced, the organisation may reproduce part of the original journey and arrive, at its own expense and in good faith, at conclusions remarkably similar to those with which it began. This in turn complicates the meaning of independent development. A blank CAD file is not a blank mind: an engineer may open one already knowing the preferred materials, the configurations that failed, the capable suppliers, the required price and the customer concerns to be solved. The sheet may be blank while the engineering context is anything but.

4. The Redistribution of Scarcity

Industrial knowledge resides partly in people. An experienced product manager or engineer carries far more than appears on a résumé: supplier history, tolerances, failed solutions, customer preferences, cost structures and the memory of why particular choices were made. This knowledge resists cataloguing but relocates easily, because it travels with its holder. One company may recruit experienced employees directly; another may seek to employ people working around the innovator as part of a proposed structure; a manufacturer may build internal capability from engineers exposed to the design. Recruitment is ordinary business behaviour, and that is precisely why its cumulative effect is so rarely examined. Where knowledge is strategically valuable, hiring the people who hold it can resemble obtaining another part of the technology itself.

Customers follow the same route. An account is initially valuable because the entrepreneur built the relationship. During a proposed partnership it becomes natural to introduce other participants; technical discussions broaden, quotations circulate and customer requirements become institutional knowledge. The language moves from “your customer” to “the customer” and eventually to “our opportunity”. Suppliers undergo the same migration, from the innovator’s supply chain to the partnership’s to a contact record in procurement. If the partnership later weakens, neither the introductions nor the information acquired through them can be reversed.

The consequence is circular. As people, customers and suppliers become accessible elsewhere, less capability remains concentrated around the innovator, and his organisation may become smaller or less capable. That deterioration can then be cited as evidence that it lacked the organisation required to scale the technology in the first place. The effect of the transfer is offered as proof of the condition that supposedly justified it, and because each step was individually legitimate, the circle is rarely noticed by those standing inside it.

5. Present Disclosure, Future Intention

Chronology is more revealing than any isolated allegation. First, expertise is recognised because the larger organisation does not possess it. Then cooperation is proposed, and the expectation of a shared future encourages greater disclosure. Designs, development history, supplier relationships, technical logic, customers and sometimes people become accessible. As this happens, dependence on the original source declines, and at approximately the same time difficulties once understood as part of entrepreneurial development begin to support a new narrative in which the innovator is unreliable, chaotic or incapable of scaling the very technology that attracted the larger organisation. No coordinated conspiracy is required for this sequence to emerge, and that is the more useful conclusion. Due diligence requires information, partnerships require openness, manufacturers need specifications, companies hire experienced people and management wants systems that do not depend on one individual. None of this is remarkable in isolation; it is the direction of travel that deserves attention.

Expectations change behaviour, and that is why early understandings matter even where lawyers can later explain why they were not final contracts. Someone who believes he is supplying drawings to a customer protects information differently from someone told that his business, technology and future role will form part of a jointly built operation. A statement about a future joint structure may be legally conditional and still explain why information that would otherwise have been protected was shared. An intended licence may never be completed and still have shaped decisions made while both parties expected it to be. The significance of such commitments lies not in their legal status but in the behaviour they induced.

This produces the central asymmetry of these relationships. The innovator demonstrates trust through present disclosure; the larger organisation demonstrates trust through future intention. Technical information, once understood, cannot be returned, whereas an intention remains capable of revision. The innovator begins with something scarce, concentrated knowledge, and is encouraged to distribute it because the future is described as collaborative. Once enough has been distributed, scarcity declines, and the economic need to accommodate him on the terms originally contemplated declines with it, at precisely the moment when his ability to withdraw what he contributed has largely disappeared. The history can then be rewritten without anyone falsifying a document: the entrepreneur becomes the chaotic founder, iterative development a series of failures, a shrinking organisation proof of incapacity, and subsequent engineering independent development. What was once presented as unusual know-how gradually becomes normal engineering practice.

Reflection Box: The Same Disclosure, Structured Twice

In the 1960s the inventor Robert Kearns demonstrated his intermittent windscreen wiper to Ford in the expectation of a supply relationship. No agreement followed, intermittent wipers later appeared on Ford vehicles, and Kearns spent decades in litigation before juries found in his favour. ARM, by contrast, built its business on disclosing its processor architecture to some of the largest companies in the world. The disclosure was at least as deep, but the terms of access, licence fees and royalties were fixed before the knowledge moved. Both parties shared their most valuable knowledge with organisations far larger than themselves. Only one of them had settled what the knowledge was worth while it was still scarce.

Challenge question: in your current relationships, is your knowledge moving under terms already agreed, or under terms still being discussed?

The Double Bottom

The visible problem is that the innovator’s position weakens. The root cause, in the conventional sense, is that knowledge was disclosed before its value was secured. This diagnosis is correct but incomplete, because it describes what happened without explaining why a competent and experienced person allowed it to happen more than once. The second bottom lies in judgement. Following the Judgement Chain, the innovator interpreted behavioural signals of partnership (inclusion, praise, shared planning, urgency) as structural guarantees. That interpretation produced a question about speed, how quickly the cooperation could advance, when the question that mattered was one about withdrawal: what would remain his if it did not. Every subsequent decision was rational given that question, which is why the outcome feels unjust rather than foolish.

The Duality Principle applies to both parties. The innovator’s strengths, openness, speed and a willingness to explain why a proposal will fail, are exactly what made him valuable and exactly what made him vulnerable. The established organisation’s strength, its capacity to institutionalise knowledge, carries its own weakness: an organisation that recognises knowledge only once it has been documented internally cannot easily see what it inherited, and may sincerely believe it developed what it learned. Neither weakness requires bad faith, and both are amplified by the absence of a written answer to a question nobody wished to ask.

Conclusion

None of this proves wrongdoing by any particular company, nor does similarity between several relationships prove they were coordinated. It does expose a repeatable commercial mechanism. Knowledge can migrate through cooperation, technical disclosure, customer access, recruitment and ordinary organisational learning until the economic position of its original holder is fundamentally different from the one that existed when disclosure began. The transition is complete when the organisation’s increased capability is taken as evidence that the innovator was never indispensable. By then the origin of that capability has become difficult to see, because knowledge discussed often enough inside an organisation soon begins to feel like organisational knowledge. Innovation has been obtained, and the development cycle has been avoided, at least by the party that obtained it.

The practical implication is therefore a matter of timing. The decisive question in a technology partnership should be asked while relations are still excellent: before drawings become shared reference material, before customers become common opportunities, before suppliers are contacted directly and before people begin changing organisational address. At that moment both sides should be able to explain what happens if the promised future never materialises. If the question cannot be answered because raising it would demonstrate insufficient trust, the absence of an answer may already tell the innovator everything he needs to know.