Many techniques for software architecture are designed to support reviews and approvals, rather than ongoing development and evolution.
This makes perfect sense when we're in a Desert company, where we are optimizing for ease of management. It often doesn't serve the needs of Forest companies, where we care more about building value.
We can do better.
How might engineers surface our designs to technical and non-technical stakeholders for validation? How can leaders communicate our goals and set engineers up to delight us? How do we build a company-wide practice of modular, testable design?
From flip books to sumi-e to rules sets, Beth draws on Domain-Driven Design, experience engineering and hir background in technical theater to creatively build cross-team alignment on what software goes where.
This talk will prepare attendees to agilely support ambitious architectural evolutions, one small, safe step at a time. Tested in high-trust technical cultures, these techniques scale to address the essential complexity of design as teams grow.
The talk will include examples of at least four specific patterns: One Arrow, Flip Book, Follow The Rules, and Architecture Forum
It does not cover Decision Records, Technical Design Documents or other governance techniques. Instead, it focuses on tools that help every engineer come to tell the same story about what they are building together.