OS/2: The IBM-Microsoft Platform Investment That Lost the Desktop War
IBM and Microsoft jointly funded OS/2 as the successor to DOS, but divergent incentives and Windows momentum turned the ambitious platform into a strategic loss.
OS/2 was funded because DOS looked increasingly inadequate
Microsoft records an August 1985 agreement with IBM for joint development of operating systems and systems software. Both companies expected more capable PCs to need a more modern software foundation. From an investment perspective, the important point is that money was being used to convert a technical possibility into an organization that customers could trust. The return depended on complementary investment by customers, developers, suppliers, and employees rather than on one isolated product sale. That made execution, timing, and ecosystem formation as important as the underlying engineering.[1]
Joint development spread cost and split authority
Two companies could pool engineering resources, but every architecture choice also had to satisfy two business models. The smaller decision mattered because it changed who else was willing to commit time or capital to the platform.
The 1987 announcement positioned OS/2 as the next platform generation
Microsoft’s 1987 chronology records the April announcement of OS/2 as a major result of the joint development agreement. IBM announced the PS/2 family at the same time. From an investment perspective, the important point is that money was being used to convert a technical possibility into an organization that customers could trust. The return depended on complementary investment by customers, developers, suppliers, and employees rather than on one isolated product sale. That made execution, timing, and ecosystem formation as important as the underlying engineering.[2]
Software risk became tied to IBM’s hardware strategy
Customers could interpret the platform as part of IBM’s effort to regain control over the PC architecture. The smaller decision mattered because it changed who else was willing to commit time or capital to the platform.
The technical target moved while Windows improved on the installed base
OS/2 pursued protected memory, multitasking, and a new graphical environment while Windows offered a more incremental path from DOS. That difference changed migration economics for users and developers. From an investment perspective, the important point is that money was being used to convert a technical possibility into an organization that customers could trust. The return depended on complementary investment by customers, developers, suppliers, and employees rather than on one isolated product sale. That made execution, timing, and ecosystem formation as important as the underlying engineering.[3]
Compatibility made delay rational
A developer could reach more existing customers through Windows without making the deeper OS/2 commitment. The smaller decision mattered because it changed who else was willing to commit time or capital to the platform.
Presentation Manager arrived but network effects were already decisive
Microsoft records IBM and Microsoft releasing OS/2 1.1 with Presentation Manager in 1988. From an investment perspective, the important point is that money was being used to convert a technical possibility into an organization that customers could trust. The return depended on complementary investment by customers, developers, suppliers, and employees rather than on one isolated product sale. That made execution, timing, and ecosystem formation as important as the underlying engineering.[4]
Developer time was the scarce capital
The partnership could pay engineers, but it could not command independent software firms to prioritize OS/2. The smaller decision mattered because it changed who else was willing to commit time or capital to the platform.
IBM and Microsoft monetized different layers of the stack
IBM depended heavily on systems and enterprise relationships, while Microsoft’s economics increasingly favored licensing software across the broad compatible-PC market. From an investment perspective, the important point is that money was being used to convert a technical possibility into an organization that customers could trust. The return depended on complementary investment by customers, developers, suppliers, and employees rather than on one isolated product sale. That made execution, timing, and ecosystem formation as important as the underlying engineering.[5]
Duplicated platform investment became strategic conflict
Microsoft’s 1990 chronology still describes joint efforts around OS/2, DOS, and Windows, but Windows had stronger momentum and increasingly different strategic value for Microsoft. From an investment perspective, the important point is that money was being used to convert a technical possibility into an organization that customers could trust. The return depended on complementary investment by customers, developers, suppliers, and employees rather than on one isolated product sale. That made execution, timing, and ecosystem formation as important as the underlying engineering.[1]
The loss still produced useful engineering knowledge
OS/2 advanced protected-memory, multitasking, graphical, and enterprise operating-system practices even though it failed to dominate the desktop. A strategic loss can still generate transferable capability. From an investment perspective, the important point is that money was being used to convert a technical possibility into an organization that customers could trust. The return depended on complementary investment by customers, developers, suppliers, and employees rather than on one isolated product sale. That made execution, timing, and ecosystem formation as important as the underlying engineering.[2]
Why OS/2 belongs in the investment history of software
OS/2 shows that capital, talent, and market access are insufficient when governance and ecosystem incentives diverge. IBM and Microsoft funded a technically serious platform, but the lower-friction migration path accumulated stronger outside investment. From an investment perspective, the important point is that money was being used to convert a technical possibility into an organization that customers could trust. The return depended on complementary investment by customers, developers, suppliers, and employees rather than on one isolated product sale. That made execution, timing, and ecosystem formation as important as the underlying engineering.[3]
Works Cited
- 01Microsoft Learn — History of Microsoft 1985 learn.microsoft.com
- 02Microsoft Learn — History of Microsoft 1987 learn.microsoft.com
- 03OS/2 Museum — OS/2 1.0 os2museum.com
- 04Microsoft Learn — History of Microsoft 1988 learn.microsoft.com
- 05Microsoft Learn — History of Microsoft 1990 learn.microsoft.com
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead