That is, conversations include accidental and intentional informal conversations, as well as intentional (deliberate) deliberations that really work on an issue — over time (as we understand more, as things change, etc.) too.
The architect role, by whatever name, gives some organizational commitment to sustaining that system expertise, attention and relationship space — in part to provide anticipatory awareness and continuity of attention to system capabilities, properties, and challenges.
This free 146 page ebook (the foundation ideas that form the underlay to my systems design and architecture workshop), builds up the case for system design as something co-created and highly collaborative. And encourages an integrative “and” answer to “do we need architects?” (and product designers and engineering managers, ..). Where what is integrated is both: everyone plays a role and can lead, and the system design has sustained+sustaining organizational commitment.
I remembered an earlier kind mention from back in the day when we were all together, sharing, inspiring, making new connections on what used to be one of the wonders of humanity. So I dug it up, and thank you for that too @ahl