Operating Principle
2–4 min read
A platform dependency looks free right up until the platform changes its mind. An app store shifts its fee structure. An ad network changes its algorithm. An API a product depends on gets deprecated with sixty days' notice.
None of this requires the platform to be malicious. It's simply optimizing for its own interests, which don't include protecting a specific business built on top of it. A firm built on that platform inherits its risk without ever getting a vote on its decisions.
Operating Question
Why It Matters
Firms that build core functionality on rented infrastructure are exposed to a risk that doesn't show up on a normal risk register until the platform changes. Identifying dependencies and building contingency plans before a change forces one is cheap insurance.
Supporting Evidence
General research and case studies on platform dependency risk in digital business models
Research Notes
Some platform dependency is unavoidable and worth the risk; the discipline is planning for it, not eliminating all third-party reliance. Severity varies by replaceability and switching cost.
Practical Actions
Map critical functions that depend on platforms you don't control.
Build a contingency plan for the highest-risk dependency.
Review platform risk as a standing item.
Continue Reading