Andrew Harmel-Law, a tech principal from London and author of "Facilitating Software Architecture," discusses the importance of diverse participation in architectural decision-making. He argues that a broader involvement leads to richer insights and better outcomes. The conversation highlights the need for trust and engagement among stakeholders, the risks of technology attachment, and how to navigate them. Andrew stresses that embracing varied perspectives can drive cultural shifts in organizations, ultimately enhancing the architectural process.
Involving a broader range of roles in software architecture decisions can enhance collaboration and transparency within teams, preventing bottlenecks.
The advice process empowers team members to make architectural choices, fostering accountability while promoting personal growth among developers in complex decision-making.
Deep dives
Need for Evolving Software Architecture
The episode highlights the increasing necessity for comprehensive software architecture as systems continue to evolve and require more collaborative effort from various teams. Andrew Hulmer-Law shares his experience working with clients to modernize architecture and streamline software delivery. He emphasizes that traditional roles can become bottlenecks as teams optimized for continuous deployment and quality look to implement changes rapidly. His efforts to facilitate better architectural practices led to the creation of a book dedicated to exploring these dynamics.
The Advice Process for Decision Making
Andrew introduces the concept of the advice process, which allows any team member to make architectural decisions as long as they seek input from impacted parties and experts. This framework builds trust and collaborative decision-making within teams, promoting a culture where everyone is empowered to engage in architectural discussions. Transparency is key; recording these decisions and the advice received helps track accountability and encourages effective communication. This approach aims to prevent chaotic situations by ensuring that decisions are well-considered and documented.
Balancing Autonomy and Accountability
The conversation touches on the balance of autonomy granted to teams when making decisions and the need for accountability within that process. While individuals can make architectural choices, it’s crucial that they understand the consequences of these decisions and are prepared for the responsibility that comes with them. Through real-world examples, Andrew illustrates how teams can self-modulate by defining their own decisions while still consulting knowledgeable peers to avoid misguided choices. This method encourages personal growth among developers, enabling a new generation of architects capable of navigating complex decisions.
Learning Through the Writing Process
Andrew shares insights about his experience writing his book, noting the challenges and lessons learned throughout the process. He initially struggled with the concept of drafting and re-architecting his writing but eventually benefited from feedback received during the iterative writing phase. The importance of clarity through communication and the establishment of a structured approach to writing greatly influenced the final product. Moreover, he underscores that the journey of learning from feedback is similar to collaborative workflows in software development, emphasizing adaptive direction and collective intelligence.
Who should be involved in the process of making decisions about software architecture? That's a question that's been puzzling Thoughtworker Andrew Harmel-Law for some time — so much so that he decided to write a book about it. The result is Facilitating Software Architecture. Published by O'Reilly in December 2024, it's both an argument for and a guide to involving more people in the architecture decision process.
To discuss the topic and the book, Andrew joined hosts Neal Ford and Prem Chandrasekaran on the Technology Podcast. They explore why including more roles in software architecture matters today, some of the common objections to and risks of such an approach, alongside techniques and practices that can make doing it in fast-paced and dynamic organizations easier.
"It's quite magical when you see this blossoming of understanding of what it is that architects do... It's not less architecture, it's more. It's just happening in a broader sphere." — Andrew Harmel-Law
You can find Andrew's book on the O'Reilly website: https://www.oreilly.com/library/view/facilitating-software-architecture/9781098151850/
Get the Snipd podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share & Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode