Facilitating Software Architecture

Chapter 4. The Architecture Advice Process

In the previous chapter, I talked about how these days decisions at scale need to be both decentralized and fast. I then showed how none of the various traditional decision processes could offer everything we needed, being either too slow or overly centralized.

In this chapter, I’ll introduce you to the architecture advice process—a simple yet powerful approach to deciding that is both decentralized and fast. I’ll explain how this process meets all four requirements for a modern decision process by involving the right number of people, optimizing the entitlement to initiate decisions, prioritizing trust, and minimizing the need to communicate decisions. I’ll also take you through two examples of it in action so that you have a better understanding of its mechanics and can see how you and others can participate in it openly and effectively. I’ll close by discussing the widespread positive impacts the advice process can have on both your software and your organization’s culture: not only removing blockers and increasing feedback but also promoting healthy, equitable communication. I’ll also show how the process delivers software architectures that evolve more fluidly and responsively. I’ve described these benefits in some detail so that you’ll know them when you come across them.

First, let’s remind ourselves why we need a faster, decentralized decision process.

The Need for a Faster, Decentralized Decision Process

There are clear challenges ...