Centralized decision-making places architectural authority with a person or group outside the development teams. It can help when teams are paralyzed by indecision, but risks poor decisions, delays while teams wait for answers, and weak buy-in when decisions are imposed. Moving decisions to teams avoids this bottleneck. section 3.4.2
Figure 3.18 The four options for who does architecture: benevolent dictator, architect in the team, architecture done by team members, and implicit architecture - image from https://architectelevator.com/architecture/organizing-architecture/
Compare centralized decisions with embedded architects, team-member decision-making, and implicit architecture. section 3.4.2

