Experimenting with BAPO
summary
Applied BAPO inside Spotify Ads R&D to translate strategy into a straw‑man C4-style architecture and a product capability map, then validated with a senior engineer, product leads and mission leads. Services get classified as commodity/hygiene, differentiating, or innovation and team headcounts are overlaid to reveal misalignment. Change tactics use existing artifacts, person‑by‑person buy‑in and experiments; outcome: narrative adoption succeeds but the model does not reshape the target operating model, partly because level‑3 leaders need conclusions not fishing lessons.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:46Problem Context
- 2:58Framing Question
- 9:37General Idea
- 10:35Principles
- 11:53The Approach
- 17:47Conclusion
related talks
41mCombining Product Thinking & Spotify’s Backstage
05mUsing A B testing to rebuild the UI used by 1 5 million users a day
53mA Case For Outside-In Design
26mFrom friction to function: Strengthening the product-engineering alliance
29mA/B and see: Improving User Experience with Experimentation
28mBeyond A/B: Test automation approaches for web variants from A to Z
24mBusiness Value Over Architecture?
30mHow to make better modernization decisions