I found myself revisiting 'Journey to Product Teams' from @johncutlefish earlier today, and noticed how 'Run' seems to be essential to get into the 'more product team shaped' half of the infographic

ime owning 'Run' allows the team to add probes to capture and visualise product usage (which is a kind of parallel observability to traditional ops), and is a huge step forward if a team has never had this capability

https://amplitude.com/blog/journey-to-product-teams-infographic

See The Journey to Product Teams (Infographic) | Amplitude

Check out the infographic we use at Amplitude to describe different product team structures and approaches to collaboration.

Amplitude

I drew a thing some time back to illustrate the journey towards sense and respond from a linear 'dev team' - again the key thing was getting feedback from 'Run' ('the world' here)

the final form (not shown here) is the team owning the model and the sense and respond 'legs' of the loop