Many believe that software architects primarily structure software and make technical decisions. But in reality, it’s about much more: your ideas and decisions must be implemented by the team and aligned with all stakeholders. Moreover, the organization itself has a significant influence on the architecture.
That’s why it’s so important for architects to be effective - both within the organization and in the architecture itself. This talk demonstrates how to achieve that in practice, drawing on years of experience as an architect and architecture consultant.

Devoxx

A conference talk by Eberhard Wolff arguing that software architecture is fundamentally a people business, not just a technical discipline. While hard skills matter, surveys and interviews consistently show communication is the most important skill in IT. Wolff makes the case that architects should focus on influencing rather than overriding management, supporting developers rather than positioning themselves as superior, and enabling team autonomy in decisions. He covers practical strategies including the 'Fearless Change' pattern catalog for introducing ideas into organizations, socio-technical architecture reviews that focus on team dynamics over slide decks, and facilitation techniques like liberating structures to enable parallel participation. He closes by acknowledging that communication is imperfect and failure is normal.

Team and Software: Making an Impact as an Architect by Eberhard Wolff