The role of a software architect has a broad range of interpretations. Most likely an architect is seen as someone who makes decisions regarding the software architecture, is responsible for the quality of software, or even enforces technical standards, tools, and platforms. On the other side, to gain speed in development and releasing software, the movement from functional teams towards cross-functional and autonomous teams blurs the lines of responsibilities and decision-making capabilities. How can a software architect facilitate the idea of autonomous teams? This talk is an experience report elaborating on different ways how to integrate an architect into an organization with multiple development teams, what we learned, and how we continuously improved to avoid friction in the process of developing software.