Decentralization distributes decision authority to teams closest to the relevant work. It addresses slow development, costly dependencies, and the limits of centralized teams switching between domains. section 14.2.1 section 17.1.1
Effective decentralization is socio-technical: teams aligned with business domains contribute deep knowledge, while architects and shared governance preserve security, consistency, and enterprise compliance. section 14.2.1 section 17.1.1
Use progressive discovery and alignment practices rather than treating decentralization as a one-time reorganization:
- Define domain boundaries to control scope and connect the people who understand the domain’s data sources, producers, rules, history, and evolution. section 14.2.1
- Pair decentralized domain expertise with a data architect who brings security, rules, and enterprise-wide governance. section 14.2.1
- Map domains and organizational boundaries through facilitated discovery and modeling workshops, especially where dependencies and sensitive data make autonomy risky. section 17.1.1
- Surface semantic disagreement by collecting definitions and usages asynchronously before asking teams to settle on a decision. section 17.1.1
PayFit payroll discovery
At PayFit, rapid growth made dependencies and slow product development untenable. Teams were reorganized around business outcomes and domains rather than technology layers, with platformization. A payroll workshop mapped concepts, relationships, and boundaries; an asynchronous documentation exercise then revealed that six people used “pay period” in seven different ways. section 17.1.1
