Maintaining an effective rhythm has long been recognized as an attribute of successful architecture. It is easier for the many organizations involved with the architecture if there is a predictable tempo, content, and quality associated with the architecture. Rhythm is also an important quality of many agile software development methods. I define rhythm in this context as “the recurring, predictable exchange of work products within an architecture group and across its customers and suppliers.” This talk will argue that rhythm is important for establishing trust in architecture and architects. The talk will also present some ideas on how architects can establish and sustain an effective rhythm.