Software architecture has evolved significantly over time, moving away from a command and control approach to a coaching and mentoring role. In this article, the authors explore the challenges of transitioning to a shared ownership model of architecture, where team-wide input is required to surface and resolve system design issues. They discuss the changing landscape and the role of architects, providing guidance to those stuck in transition and those looking to enhance and distribute their architecting. The article also delves into the changing responsibilities of an architect, how tooling advances have simplified key challenges, and how teams may be stuck in a transition towards making architecting a team capability due to lower maturity processes. This article is a must-read for anyone interested in the evolution of software architecture and the role of the architect in modern software development.
