An architecture guild decentralizes architectural decisions, principles, and knowledge across medium and large organizations. It helps establish cross-cutting standards without creating a centralized bottleneck that slows team-level fast flow. section 15.3.2 section 15.8
The guild should fit the organization’s needs rather than follow a fixed template. Its operating model makes the motivation, roles, responsibilities, shared problems, and globally useful solutions explicit. section 15.3.2
A practical starting point defines:
- Motivation: why the guild exists, such as maintaining architectural standards while empowering teams to achieve fast flow. section 15.3.2
- Roles and responsibilities: what the guild does, including identifying shared problems and globally applicable solutions. section 15.3.2
Replacing the centralized bottleneck
A medium or large organization can use a guild instead of relying solely on a centralized architecture team or review board to establish standards affecting hundreds or thousands of engineers. section 15.3.2
Compare organizational options for distributing architect responsibilities before choosing a guild structure. section 15.3.2
