The long journey to an API community of practice in an old insurance company
summary
Legacy insurer with mainframe and COBOL faces APIs with the same data duplicated 14 times, mixed French/English payloads and no docs. A grassroots wiki and workshops (2015 onward) grow from 6 to 29 members, produce guidelines v1.1 on GitHub with 15 contributors, and catalog ~30 APIs. Management authorizes change so every new API requires a mandatory API design review and about 42 reviews happen to date, cutting inconsistent designs and easing rollout costs.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 5:35The community of practice
- 9:57How to add more people
- 11:45How to convince product owners
- 16:19More adoption
- 16:37Bottomup approach
- 18:06Ongoing fight
- 18:23Key numbers
related talks
25mThe API Revolution bring us to continuously change
21mIntroducing The API Lifecycle
32mThe 7 commandments for a successful API Program
26mMastering API Strategies for Digital Transformation
21mMastering API Design: Why Community Matters
35mBuilding Your API for Longevity
30mBuilding high-performance API platform teams
54mAPI team characteristics and best practices