Require that every API carry a reuse score that measures how widely and effectively it is being reused across teams and how much it duplicates existing capabilities. I want reuse assessed with a consistent, published method so we can reward APIs that serve many consumers and surface redundant efforts before they multiply. Reuse scoring turns a vague ideal into a governable signal that guides investment, retirement, and discovery decisions. An API portfolio that is never scored for reuse drifts toward sprawl and duplication, so I hold applied reuse scoring as a production-grade governance requirement.
Reuse Scoring Applied
Strategies
APIs Are Evaluated Before Adoption
I want us to evaluate an API before we build on it, because the cheapest time to discover a bad dependency is before it is wired into production. That means running third-party APIs through a procu...
Experiences
Reuse
The reuse of APIs in applications and integrations, but also in the producing of APIs plays an important part in the overall experience of teams who are producing and consuming APIs. The reuse of A...
Reusability
Reusability is the experience of finding and applying an existing API instead of building the same capability again. It depends on discovery, consistent design, and clear documentation that make an...
Lifecycle
balance Governance Production
Governance is how everything on this lifecycle stays aligned as an operation scales. Policies, rules, and standards applied consistently across teams are what keep APIs coherent without slowing eve...
travel_explore Discovery Production
Discovery is how APIs get found and reused instead of rebuilt. APIs.json, catalogs, and search make the APIs I operate visible to the people who need them. Good discovery is what turns a pile of AP...
