What a Good Platform Looks Like and How to Get There @ Large Financial Organization, Oct 2024

Slide 1

Slide 1 text

TeamTopologies.com @TeamTopologies What a Good Platform Looks Like & How to Get There Manuel Pais co-author of Team Topologies Large Financial Organization - 9 October 2024

Slide 2

Slide 2 text

Team Topologies Organizing business and technology teams for fast ﬂow Matthew Skelton & Manuel Pais IT Revolution Press, 2019 teamtopologies.com/book Over 175.000 copies sold

Slide 3

Slide 3 text

“fast ﬂow means multiple ongoing streams of value to customers via software-enriched services done rapidly, safely, and sustainably” 3

Slide 4

Slide 4 text

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

What are common Platform “problems”? 7

Slide 7

Slide 7 text

⚠ A mandated platform increases the cognitive load on teams (i.e. slows them down) 8

Slide 8

Slide 8 text

9 Ticket-based approach at odds with application scale

Slide 9

Slide 9 text

Functional silos 10 Infra CI/CD Monitoring Deployment Poorly integrated related services

Slide 10

Slide 10 text

12 Confusing APIs

Slide 11

Slide 11 text

13 Service unavailable or too slow

Slide 12

Slide 12 text

What is a Platform? 14

Slide 13

Slide 13 text

“A digital platform is a foundation of self-service APIs, tools, services, knowledge and support which are arranged as a compelling internal product.” – Evan Bottcher, 2018 15 Source: https://martinfowler.com/articles/talk-about-platforms.html

Slide 14

Slide 14 text

What Good Looks Like 17

Slide 15

Slide 15 text

Case Study 18

Slide 16

Slide 16 text

Case Study 19 https://www.youtube.com/watch?v=ARaJwB0i8Mc Circa 2020 ● Platform work linked to business results ● Apps from zero to live in 2 days (vs 6 months in the past) ● Cycle time (from commit to production) ○ 3 days → 1 minute ● Deployment frequency ○ once every 6 weeks → 3 times per day

Slide 17

Slide 17 text

Case Study 20 https://videos.itrevolution.com/watch/431737448/

Slide 18

Slide 18 text

21 Platform engineering (group) has long term funding

Slide 19

Slide 19 text

22 Photo by Tim Mossholder on Unsplash The platform acts as an engine for fast ﬂow by increasing the capacity & speed of engineering teams

Slide 20

Slide 20 text

Case Study 23 https://videos.itrevolution.com/watch/431737448/

Slide 21

Slide 21 text

24 Organized around streams / services clearly identiﬁed and owned by dedicated teams

Slide 22

Slide 22 text

Case Study 25 https://videos.itrevolution.com/watch/431737448/

Slide 23

Slide 23 text

Case Study 26 https://videos.itrevolution.com/watch/431737448/

Slide 24

Slide 24 text

27 Platform teams expected to intentionally adopt & alternate their interaction modes (with internal teams)

Slide 25

Slide 25 text

Slide 26

Slide 26 text

29 Invest in building trust early, “plant the seed” for platform adoption later

Slide 27

Slide 27 text

Case Study 30 https://videos.itrevolution.com/watch/431737448/

Slide 28

Slide 28 text

31 Internal metrics on adoption, user satisfaction, and reliability to stay on track

Slide 29

Slide 29 text

32 https://www.youtube.com/watch?v=XwaRKcjkAAo

Slide 30

Slide 30 text

33 https://www.youtube.com/watch?v=XwaRKcjkAAo BIZ LANGUAGE

Slide 31

Slide 31 text

34 Business metrics (direct and indirect) that clearly show the platform value

Slide 32

Slide 32 text

How To Get There 35

Slide 33

Slide 33 text

Case Study SAP [Enterprise Software] 36

Slide 34

Slide 34 text

Case Study “Adhering to legal regulations of over 180 countries… while running for decades at customers on-prem” 37 Dirk Lehmann - Platform Engineering XXL DevOpsDays 💖 https://devopsdays.org/

Slide 35

Slide 35 text

Case Study 38

Slide 36

Slide 36 text

Case Study “everyone from dev to delivery under one organization reduced a lot of friction (…) and we have a prod mgmt team because we are building a product” 39

Slide 37

Slide 37 text

Case Study 40 “goal of the platform is to relieve development teams from cognitive load due to common, painful tasks” 🎉

Slide 38

Slide 38 text

⏳ ⏳ Blocking Non- Blocking Security Compliance

Slide 39

Slide 39 text

Slide 40

Slide 40 text

Slide 41

Slide 41 text

Slide 42

Slide 42 text

Slide 43

Slide 43 text

Slide 44

Slide 44 text

47 5 tickets / 10 days self-serve / 2 hours

Slide 45

Slide 45 text

teams & interactions over tools & functionality adoption & engagement over mandates & standards rich customer experience over technical prowess open to change and collaborate to discover user needs unblocking internal customers via self-service patterns aiming for superlinear impact with sublinear growth Platform Manifesto platformmanifesto.is