Good architecture shouldn't need a carrot or a stick (5 minute read)
Traditional architecture governance creates friction through approval boards and embedded architects, while a "paved road" approach provides pre-approved, ready-to-use solutions that make compliance the easiest path.
What: The article contrasts three architecture governance approaches: the "stick" (approval boards that review and block projects), the "carrot" (assigning architects to guide teams), and the "paved road" (providing pre-built, approved solutions for common needs). Netflix and Spotify use the paved road model, which eliminates most governance overhead by making the compliant path also the fastest path.
Why it matters: Most teams avoid architecture processes by either going shadow IT or disguising new work as existing projects. By making pre-approved solutions handle security, logging, and legal automatically, organizations can achieve compliance through convenience rather than enforcement, while projects naturally follow standards because they're the path of least resistance.
Takeaway: If you're building platform or architecture teams, focus on creating ready-made, opinionated solutions for common patterns rather than review processes. If you're on a development team, advocate for standardized templates and tooling over board approvals.
Deep dive
- Traditional architecture boards create a "stick" approach where teams must prepare extensive documentation and face approval processes that can block projects indefinitely, leading to shadow IT and workarounds
- The "carrot" approach of embedding architects in projects reduces governance burden but adds meetings and a team member whose role is to say "yes, but" at every decision
- Paved road architecture flips the model by offering pre-built, fully approved solutions that handle cross-cutting concerns like security, logging, and legal compliance automatically
- From a project perspective, using paved roads means skipping multiple approval boards and getting part of your implementation done for free, directly accelerating timelines
- When the standard doesn't fit, teams only need to discuss adaptations rather than justify the entire foundation, dramatically reducing negotiation scope
- Projects naturally follow the path of least resistance, so making compliance the easiest route drives adoption without enforcement or heavy governance overhead
- Teams that deviate from paved roads must justify the extra time and risk of carving their own path, creating organic deterrence without policies
- The approach doesn't eliminate governance entirely—architecture still validates decisions—but shifts enforcement from late-stage approval to early-stage design of reusable components
- "Architecture à la carte" extends this further with modular plug-and-play blocks where teams answer simple questions (expected users, lifespan, preferences) to generate validated architectures
- Innovation isn't hindered because dedicated innovation projects can update and evolve the paved roads themselves, ensuring strategy evolves at one central point rather than fragmenting across teams
Decoder
- Paved road architecture: Providing pre-built, pre-approved technical solutions as the default path, making compliance easier than custom implementations
- Shadow IT: When teams build or buy technology without going through official approval processes to avoid bureaucracy
- Architecture board: A governance body that reviews and approves (or rejects) technical proposals before projects can proceed
- Artefacts: Documentation and diagrams required by architecture boards to evaluate projects
- Path of least resistance: In project management, the natural tendency to choose options that minimize risk, effort, and timeline impact
Original article
Good architecture shouldn't rely on enforcement or heavy guidance, because both create friction and resistance from internal teams. Instead, a “paved road” approach—providing ready-made, approved solutions that are the easiest path—naturally drives adoption and aligns projects without heavy governance overhead.