Beat a feature-superior incumbent by adding the one capability their architecture cannot copy and subtracting the friction they force on users, until you redefine the product itself.
Google Docs
Google Docs is the browser-based word processor Google built from its 2006 acquisition of Writely, the startup that first put a word processor and real-time collaboration inside a web browser. Its two defining moves run in opposite directions: it added something Microsoft Word could not do (many people editing one live document at once) and it subtracted things Word forced on users (the Save button, the local file, the installed app). Together they let a feature-inferior product redefine what a document is.
Disruptive Innovation: taming real-time collaboration with Operational Transform
The problem. When multiple people edit the same document at the same time, their keystrokes arrive at the server in unpredictable orders and over unreliable network latency. Naively applying edits as they land corrupts the text: if one person inserts a word at position 10 while another deletes at position 5, the first edit now points at the wrong place. Before Google Docs, collaboration meant emailing files back and forth and manually reconciling versions.
The approach. Google Docs adopted Operational Transformation (OT), an algorithm first conceived in the late 1980s, and made it work at production scale in the browser. Rather than send whole documents, each client sends only its small operations (insert, delete, format), and the server transforms every incoming operation against any concurrent operations before applying it, so intent is preserved regardless of arrival order. Every client effectively becomes a leader that can accept writes, with changes propagated live and folded into a single revision history.
How it solved it. OT guarantees that, as the engineering write-ups put it, "regardless of the order in which the edits are made, the final state of the document is consistent among all users." This turned multi-user editing from a merge nightmare into the varicolored cursors roaming a live page, and it became foundational DNA for the collaborative software that followed, including Figma and Notion. Google shipped it as Google Docs & Spreadsheets in October 2006, months after acquiring Writely.
Differentiation: winning by elimination, not feature parity
The problem. Microsoft Word had a decade-plus head start, near-universal installed base, and thousands of features. Competing head-on meant an endless, losing race to match every menu and dialog. Word also carried inherited friction: users had to remember to save, juggled multiple local copies with no clear "latest" version, and needed the app installed just to open a .doc file.
The approach. Instead of adding features to catch Word, Google Docs differentiated by removing whole categories of problems. It killed the Save button: every keystroke autosaves to Google Drive within seconds, eliminating lost-work anxiety. It killed the local file, making the cloud document the single source of truth (one instance that is also the only instance), backed by automatic version history and access history. And it killed the native-app requirement: sharing or viewing works in any browser, and you do not even need a Google account to view a shared document.
How it solved it. Each subtraction closed off an entire class of failure rather than patching individual cases: no "which copy is current," no "I forgot to save," no "I can't open this without Word." Google Docs never reached feature parity with Word and its adoption is nowhere near as universal, yet it introduced most people to the "cloud application" and won decisively on the first-rate features while staying second-rate on the third-rate ones. As its chroniclers put it, "in the genetics of modern software, it'd be rare to find software programs where Google Docs' DNA segments are completely absent."