APIs are Arrangements of Power. Now what?
summary
Capital One runs a platform CoE for ~9–10k developers producing thousands of APIs and seeing 3.5 billion requests and responses a day, and claims API strategy must be socio-technical not just technical. Cites Conway’s Law and the inverse Conway maneuver — Bezos’ 2003 API edict that forced AWS-style modularization and Buffer’s reorg from two monoliths into product-aligned teams as concrete wins. Recommends tactics: shrink the change and “script the critical moves,” plus reading Accelerate, Team Topologies, Thinking in Systems.
AI-written summary · about
chapters (9)
- 0:00Intro
- 4:53The Power of Organizations
- 10:52APIs are Arrangements of Power
- 14:13The inverse conway maneuver
- 16:04Change in organizations
- 21:14What is API governance
- 22:21Books
- 23:15Questions
- 26:04Conways Law
related talks
26mAPIs are the new skin of your organisation
23mLeverage APIs to Transform Your Business Landscape
38mHow APIs Change Software Development
14mAPI Strategy: Powering Digital Transformation
26mAPIs as Agent of Change
25mLayers, API Governance & Innovating w. the Principle of Least Power
26mMastering API Strategies for Digital Transformation
25mAPI, the next 10 years: Beyond the Interface
