“Create more value than you capture.”
Tim O’Reilly offered this line in an O’Reilly Media principle described in his publishing talks. O’Reilly connected the motto with publishing, open-source communities, and technology platforms. A healthy ecosystem can generate far more benefit for readers, developers, customers, and complementary businesses than one company could keep for itself. The documented setting keeps the line attached to real work rather than turning it into a floating slogan.
Value creation and revenue are not identical. A durable organization can earn money while designing knowledge, interfaces, and opportunities that let others build, learn, and prosper beyond the original transaction. That interpretation makes the quotation useful as a decision rule rather than merely as inspiration. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
Capturing too little can make maintenance impossible, and appeals to community value can be used to justify unpaid labor. The balance must fund the people and infrastructure responsible for the shared resource rather than privatizing gains and socializing costs. Keeping that boundary visible prevents a memorable sentence from becoming an excuse for simplistic policy or design. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Platform companies and AI vendors shape entire downstream markets. O’Reilly’s principle offers a practical metric: after the business succeeds, do users and partners retain new capability, portability, and bargaining power, or has most of the value been converted into dependence? The enduring lesson is to connect technical ambition with evidence, participation, and responsibility for outcomes. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Tim O’Reilly offered this line in an O’Reilly Media principle described in his publishing talks. O’Reilly connected the motto with publishing, open-source communities, and technology platforms. A healthy ecosystem can generate far more benefit for readers, developers, customers, and complementary businesses than one company could keep for itself. The documented setting keeps the line attached to real work rather than turning it into a floating slogan.
The source record connects the wording to an O’Reilly Media principle described in his publishing talks, which is the context used for this post.
Value creation and revenue are not identical. A durable organization can earn money while designing knowledge, interfaces, and opportunities that let others build, learn, and prosper beyond the original transaction. That interpretation makes the quotation useful as a decision rule rather than merely as inspiration. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
The interpretation focuses on a decision or design principle that readers can test against actual systems.
Capturing too little can make maintenance impossible, and appeals to community value can be used to justify unpaid labor. The balance must fund the people and infrastructure responsible for the shared resource rather than privatizing gains and socializing costs. Keeping that boundary visible prevents a memorable sentence from becoming an excuse for simplistic policy or design. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
Platform companies and AI vendors shape entire downstream markets. O’Reilly’s principle offers a practical metric: after the business succeeds, do users and partners retain new capability, portability, and bargaining power, or has most of the value been converted into dependence? The enduring lesson is to connect technical ambition with evidence, participation, and responsibility for outcomes. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.