An introduction and explanation of 8 guiding principles design by the Agile Coaching team for Spotify Ads R&D and how they might help you with your own change efforts

1. We are more impactful with both team-level insight AND leadership relationships;
2. We should not become operational (or at least be careful about becoming operational);
3. Focusing too much on short-term tactical wins limits the ability to have sustained impact;
4. Coach (aka change agent) collaboration is more effective than silos;
5. Results are for the short-term; systems and habits are for the long-term;
6. Involving leaders (both formal and informal) in both brainstorming and implementation makes improvement faster;
7. Coaching structure should follow coaching strategy; coaching strategy should follow product/business strategy;
8. Sharing work and successes should be intentional, not just organic.

BAPO stands for Business Architecture Process Organisation. It is Jan Bosch's more fleshed out expression of "structure should follow strategy". I recently experimented with applying this framework within Spotify Ads R&D and would like to share what worked and what didn't. Concepts expanded beyond BAPO to include product capabilities versus architecture services; overlapping product lifecycle s-curves; Simon Wardley's Pioneers, Settlers, Town Planners; and a reframing of the teaching people how to fish metaphor. Beyond sharing my successes and failures, this session will also encourage attendees to sketch how they might try this framework in their own context and anticipate what issues may appear.