Towards Sustainable Learning, Designing and Decision-making (Craft-Conf 2024)

Modern organizations operate in fast-moving environments with increasing demands, technological innovations, and market competition. Furthermore, they operate on more unpredictable and complex problems, so they can't use the old thinking models of experts planning and architecting up-front solutions. Instead, they must develop suitable organizational structures and architectures that can evolve sustainably to respond to those demands and challenges.

In this talk, I will explore the need for organizations to invest in structures, dynamics, and incentives to increase learning, design, and decision-making by people closest to problems and most equipped to respond to those challenges. I will also share several examples of this journey and how it changes over time.

I will show how Team Topologies can provide a foundational language for discussing the necessary organizational evolution and how Architecture Topologies can be leveraged to understand and improve how we approach learning, design, and decision-making in the different scopes of the organization.

Transcript

1. Towards Sustainable Learning, Designing and Decision-making Eduardo da Silva, PhD Independent consultant on sociotechnical systems, architecture & leadership modernization (esilva.net consulting | eduardo@esilva.net) Craft-Conf 2024, 2024/05/30
2. esilva.net 2 Sustainable Fast Flow of Change Photo by Ronaldo de Oliveira on Unsplash
3. esilva.net 3 Sustainable Fast Flow of Change Photo by Ronaldo de Oliveira on Unsplash Ability to respond fast & sustainably to the environment
4. esilva.net 4 Sustainable Fast Flow of Change ❤ Sustainable Learning, Designing and Decision-making Photo by Ronaldo de Oliveira on Unsplash Ability to respond fast & sustainably to the environment
5. esilva.net 5 Photo by Simon Berger on Unsplash
6. esilva.net 6 Photo by Simon Berger on Unsplash Learning: “learning about the problems & opportunities in the environment”
7. esilva.net 7 Photo by Simon Berger on Unsplash Learning: “learning about the problems & opportunities in the environment” Designing: “explore and design options to address the problem or opportunity”
8. esilva.net 8 Photo by Simon Berger on Unsplash Learning: “learning about the problems & opportunities in the environment” Designing: “explore and design options to address the problem or opportunity” Decision-Making: “decide on designs and take action to make things happen”
9. esilva.net In our lives, we are continuously Learning, designing and deciding …to respond to unexpected events 9
10. esilva.net 10
11. esilva.net Strange burning smell… 11
12. esilva.net 12 Learning…
13. esilva.net 13 Designing & Deciding…
14. esilva.net 14 Learning…
15. esilva.net 15 Designing & Deciding…
16. esilva.net 16 4:32 AM (first coffee)
17. esilva.net 17
18. esilva.net 18
19. esilva.net 19 9:14 AM (workshop starts at 9:30)
20. esilva.net 20 I made it (~20 min late)
21. esilva.net 21
22. esilva.net 22 Photo by Simon Berger on Unsplash
23. esilva.net ‼ Modern orgs that are not nurturing conditions for sustainable Learning, designing and decision-making will struggle to respond to their environment 23 Photo by Cole Patrick on Unsplash
24. esilva.net 24 Inspired by: Reflections: Sociotechnical Systems Design and Organization Change
25. esilva.net 25 💡Move towards org cultures, structures and incentives that allow us (particular people close to problems) to navigate and respond to the uncertain & fast changing environments we “live in” Photo by Ronaldo de Oliveira on Unsplash
26. esilva.net 🎯 Sustainable Fast Flow of Change Operating Models 🌳 26 Sociotechnical Systems Evolution & Architecture, Eduardo da Silva
27. esilva.net 🎯 Sustainable Fast Flow of Change Operating Models 🌳 27 Sociotechnical Systems Evolution & Architecture, Eduardo da Silva Learning Designing Decision- making
28. esilva.net 🎯 Sustainable Fast Flow of Change Operating Models 🌳 28 Sociotechnical Systems Evolution & Architecture, Eduardo da Silva Learning Designing Decision- making 🎯We want to continuously go fast & sustainably over this “cycle” (from ideas to value in front of the customer)
29. esilva.net 🎯 Sustainable Fast Flow of Change Operating Models 🌳 29 Sociotechnical Systems Evolution & Architecture, Eduardo da Silva Learning Designing Decision- making 🎯We want to continuously go fast & sustainably over this “cycle” (from ideas to value in front of the customer) How can we do that?
30. esilva.net 🎯 Sustainable Fast Flow of Change Operating Models 🌳 30 Sociotechnical Systems Evolution & Architecture, Eduardo da Silva “Language” to help us discuss how we organize and evolve our teams (& org) to support sustainable fast flow of change Learning Designing Decision- making
31. esilva.net ❓But, how are we understanding, discussing and improving our approaches to Learning, Designing and Decision-making (architecture)? 31 In the teams Across teams Across the org
32. esilva.net Architecture Topologies 🎯 Thinking models and practices to understand and evolve the approach to Architecture (Learning, Designing and Decision-making) in the different scopes of the organization 🔗 esilva.net/architecture-topologies 32
33. esilva.net “Language” to understand and improve our approach to architecture Architecture Topologies ❤ Team Topologies 33 “Language” to organize and evolve our teams (& org) …towards a Sustainable Fast Flow of Change Operating Models
34. esilva.net Architecture Topologies (ATs) Map 34 💡 example of visualization we can use to discuss & understand existing approaches and points for improvement ℹ this is just one example of visualization, we can use other practices, such as Team Topologies Interaction Modeling, and other things
35. esilva.net Architecture Topologies (ATs) Map 35 Maturity of Architecture Capability
36. esilva.net 36 *Would you like architects with your architecture? | images credits: Gregor Hohpe Some Categories of Approaches to Architecture* (Stefan Toth) 💡this is a gradual evolution… which will take years to develop, and will vary from team to team (Architecture Capability for Sustainable Fast Flow of Change) 💡does not mean there is no clear ownership!
37. esilva.net ❓what about “architecture” across teams, or across the org? 37 In the teams Across teams Across the org
38. esilva.net Architecture Topologies (ATs) Map 38 How are we approaching Architecture on the different scopes of the org (and across them)?
39. esilva.net Architecture Topologies (ATs) Map 39 💡people involved in these different scopes can use this sort of model to understand, discuss and identify opportunities to improve our approach to architecture
40. esilva.net Architecture Topologies (ATs) Map 40 ⚠Architecture from outside the scope Architecture Approach
41. esilva.net Architecture Topologies (ATs) Map 41 ⚠Architecture from outside the scope Architecture Approach Learning Designing Decision-making “learning about the problems & opportunities in the environment” “explore and design options to address the problem or opportunity” “decide on designs and take action to make things happen”
42. esilva.net 42 Architecture Approach Learning Designing Decision-making ℹ example of a mapping from a big org, with many teams and architects working with multiple teams
43. esilva.net 43 Architecture Approach Learning Designing Decision-making 💡different parts of the same organization have different ways of approaching architecture… and different challenges
44. esilva.net 44 Architecture Approach Learning Designing Decision-making Outcome of this collaborative mapping: ⇢ Identification of important constraints 🚫 After this, we have more conditions to: ⇢ Explore options to address constraints 📈 ⇢ Define how to continue doing this 🔁
45. esilva.net 💡having ways of improving how we approach Architecture is key… as it will be changing, as things in and around the org are changing 45
46. esilva.net 46 bol.com 1999 - 2019 Things sold Services Significant events
47. esilva.net 47 Tech Arch Org (& Way of Work) Prod & Events Tech Org (& Way of Work) bol.com 1999 - 2019 (Org + Tech + Architecture evolution) Arch.
48. esilva.net 48 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Phase 1 (1999 - ~2010): Waterfall, monoliths & centralized arch Arch. Centralized (by Architects) Prod & Events
49. esilva.net 49 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Phase 1 (1999 - ~2010): Waterfall, monoliths & centralized arch Arch. Centralized (by Architects) ⚠ “need for scaling & going faster” Prod & Events
50. esilva.net 50 Architects doing all the design & decision making
51. esilva.net 51 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Phase 1 (1999 - ~2010): Waterfall, monoliths & centralized arch Arch. Centralized (by Architects) ⚠ “need for scaling & going faster” Prod & Events
52. esilva.net 52 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Agile DevOps Teams (Micro)services ~30 ~10 Phase 2 (~2010 - ~2018): Autonomous Teams Arch. Centralized (by Architects) Teams + Archs “need for scaling & going faster” Prod & Events ⭐ these are structural changes - org + tech + arch (supported by leadership). It is not just introducing yet another process!
53. esilva.net 53 Architecture in teams done by the teams; architects doing architecture around teams
54. esilva.net 54 Architecture in teams done by the teams; architects doing architecture around teams
55. esilva.net 55 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Agile DevOps Teams (Micro)services ~30 ~10 Phase 2 (~2010 - ~2018): Autonomous Teams Arch. Centralized (by Architects) Teams + Archs “need for scaling & going faster” Prod & Events
56. esilva.net 56 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Agile DevOps Teams (Micro)services ~30 ~10 Phase 2 (~2010 - ~2018): Autonomous Teams Arch. Centralized (by Architects) Teams + Archs “need for scaling & going faster” Teams capable of iterating quickly on their scope Prod & Events
57. esilva.net 57 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Agile DevOps Teams (Micro)services ~30 ~10 Phase 2 (~2010 - ~2018): Autonomous Teams Arch. Centralized (by Architects) Teams + Archs “need for scaling & going faster” Teams capable of iterating quickly on their scope Able to deploy quickly and independently Prod & Events
58. esilva.net 58 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Agile DevOps Teams (Micro)services ~30 ~10 Phase 2 (~2010 - ~2018): Autonomous Teams Arch. Centralized (by Architects) Teams + Archs “need for scaling & going faster” Teams capable of iterating quickly on their scope Able to deploy quickly and independently Teams able to design and decide things on their scope Prod & Events
59. esilva.net 59 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Agile DevOps Teams (Micro)services ~30 ~10 Phase 2 (~2010 - ~2018): Autonomous Teams Arch. Centralized (by Architects) Teams + Archs “need for scaling & going faster” Many teams Prod & Tech Silos Prod & Events
60. esilva.net 60 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Agile DevOps Teams (Micro)services ~30 ~10 Phase 2 (~2010 - ~2018): Autonomous Teams Arch. Centralized (by Architects) Teams + Archs “need for scaling & going faster” Many teams Prod & Tech Silos Organic net of Microservices Prod & Events
61. esilva.net 61 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Agile DevOps Teams (Micro)services ~30 ~10 Phase 2 (~2010 - ~2018): Autonomous Teams Arch. Centralized (by Architects) Teams + Archs “need for scaling & going faster” Many teams Prod & Tech Silos Organic net of Microservices Architects overwhelmed & teams working on their “isolated but dependent islands” Prod & Events
62. esilva.net 62 Tech Arch Org (& Way of Work) Monoliths Tech Org (& Way of Work) Waterfall Agile DevOps Teams (Micro)services ~30 ~100 ~10 ~600 Phase 2 (~2010 - ~2018): Autonomous Teams Arch. Centralized (by Architects) Teams + Architects (anything around teams) ⚠ ⚠ ⚠ ⚠ “need for sustainable fast flow of change across teams and org” Prod & Events
63. esilva.net 63 Architects managing a lot of the “things” around the teams & teams being “isolated but dependent islands”
64. esilva.net • Team scope has all disciplines needed (⭐including “product” and “tech” => NO SILOS!) • Product scope groups teams working on related value streams (e.g., Inspire to Buy has Recommendation and Search Teams), with Enabling Product Leadership Improving Organization Structure & Architecture 64 Product Taxonomy, Ross Clanton, Amy Walters, Jason Zubrick, Pat Birkeland, Mik Kersten, Alan Nance, and Anders Wallgren
65. esilva.net 65 Teams owning architecture on their scope with clearer alignment to the multi-team scope they are part of (with Enabling Architects, PMs & EMs)
66. esilva.net 66 Teams owning architecture on their scope with clearer alignment to the multi-team scope they are part of (with Enabling Architects, PMs & EMs)
67. esilva.net 67 Tech Arch Org (& Way of Work) Monoliths Products Tech Org (& Way of Work) Waterfall Agile Product Teams DevOps Teams (Micro)services ~30 ~100 ~10 ~600 ~50 Phase 3 (~2017 - ??): Product organization Arch. Centralized (by Architects) Teams + Architects (anything around teams) Teams (+ Enabling Product Architects) Prod & Events “need for sustainable fast flow of change across teams and org”
68. esilva.net Products Waterfall Agile Product Teams DevOps Teams ~30 ~100 bol.com 1999 - 2019 68 “need for scaling & going faster” 💡change is continuous and takes time and support from leadership “need for sustainable fast flow of change across teams and org”
69. esilva.net 69 ⭐ Our business changes, and so is the way we organize our teams and systems and how we approach architecture (learning, designing and decision-making)
70. esilva.net 70 ⚠ Change & Uncertainty will not stop ✅ Embrace it & listen to it, and make sure you evolve your organization structures & approach Architecture to address that (▶ Sustainable Fast Flow Operating models) Photo by Ronaldo de Oliveira on Unsplash
71. esilva.net Thank you! Eduardo da Silva, PhD Independent consultant on sociotechnical systems, architecture & leadership modernization Team Topologies Valued Practitioner (TTVP) # esilva.net consulting # eduardo@esilva.net | emgsilva esilva.net/products ⬇ ℹmore products coming soon ℹthe topic of this talk is covered in these workshops & sessions: https://esilva.net/products/effe ctive-architecture-topologies https://academy.teamtopologies.com/ courses/effective-enabling-teams