Philip Evans, 2013

“Data is transforming the boundaries of the firm.”

Strategist Philip Evans used his 2013 TED@BCG talk to explain how falling communication costs and expanding data challenge long-standing assumptions about scale, vertical integration, and competitive advantage. The quote points to a structural change: information can move across organizational boundaries more easily than physical assets. Partners, platforms, customers, and specialized suppliers can coordinate in arrangements that older strategies could not support. The enduring management question is which decision the idea changes and what evidence would show that the interpretation is wrong. The point is to make judgment observable without reducing a complicated human system to one convenient number.

Leaders can map where proprietary control still creates value and where open interfaces or partnerships would improve speed and reach. Data rights, standards, and decision authority should be designed before dependency grows. A useful principle should improve a choice before it becomes a retrospective slogan. Qualitative evidence, operational data, and direct experience should be considered together before expansion.

Ecosystems can concentrate power even while appearing open. Privacy, security, interoperability, supplier bargaining power, and exit options require governance so efficiency does not create an irreversible or exploitative lock-in. That requires attention to incentives, affected people, and the conditions under which the idea stops applying. This prevents the loudest advocate or most polished presentation from defining reality for everyone else.

Cloud services, APIs, and artificial intelligence have accelerated the pattern Evans described. His idea matters because strategy must consider who controls information flows, not only who owns factories or customer contracts. Map one product’s information chain from customer need to delivery. Identify a boundary that technology has made obsolete, test a partnership or interface, and define portability, consent, security, and failure responsibilities first. Recording the decision and its limits gives future teams knowledge they can inspect rather than a success story they are asked to repeat. Scaling should follow demonstrated value and clear safeguards, with enough flexibility to pause when new evidence changes the balance. A practical decision record should preserve the expected mechanism, the strongest alternative explanation, and the point at which leaders would stop or redesign the work. This makes accountability useful instead of punitive and helps a future team see which parts depended on conditions that may no longer exist. The record should be short enough to revisit and specific enough that another person could challenge its assumptions. Clear ownership then turns reflection into a scheduled management responsibility. A concise public note should show colleagues which observation changed the decision and when the next review will occur.