In this episode, we touch a field that we don’t explore that much, Architecture. To be more precise: Sociotechnical Architecture to maximize impact. In a way, it's strange since Peter Paul has worked as an architect for quite a while.

What this episode covers

On the website of our guest, esilva.net, it's called “co-design organizational and technical systems to maximize impact”. We think there is so much to explore in these words Sociotechnical Architecture so we asked Eduardo to join this show.

(Image: https://cdn.sanity.io/images/qxrxmo3r/techlab-prd/b1d94d3dfef08a393cc6680af37d51e839904767-1596x876.jpg)

<picture source>

We discuss what it is and also, why it is fundamental to maximize the impact of our products and the teams building & owning them. We discuss the 5 traits:

1. Conway's Law
2. Team Cognitive Load
3. Team Boundaries & Interrelations
4. Continuous Discovery & Delivery in Team
5. Understand your context & Design based on that

And to make it tangible, we discuss this topic based on the great example Eduardo uses on his website as well: 'the restaurant' and we relate to examples within the bol.com tech community.

Guests

• Eduardo da Silva; Technical Leader & Sociotechnical Software Architect at bol.com and friend of the show.

Notes

• Blog and link to Spaces Summit video on Sociotechnical Architecture
• Why and What of Sociotechnical Architecture
• Traits and Strategies of Sociotechnical Architecture

Books:

• Accelerate
• Team Topologies