Virtual Domain-driven design The paradox or polarity between decentralised and centralised decision-making
Oct 16, 2025
This discussion dives into the intricate balance between centralized and decentralized decision-making in software teams. It highlights the trust challenges that arise when teams are given autonomy. Insights reveal how centralized control can stifle creativity, while decentralization fosters empowered teams and sustainable solutions. Key topics include the importance of decision transparency, handling biases, and practical steps for achieving decentralization. An interactive session using Miro boards enhances engagement, allowing participants to collaboratively explore these concepts.
AI Snips
Chapters
Transcript
Episode notes
Define Decision Styles Before Debating Centralization
- 'Decentralized' and 'centralized' are ambiguous without a decision-style model like autocratic, delegation, consultative, consent, democratic, consensus.
- Use clear categories (e.g., Andrew's decision styles) to diagnose which mode you're actually using.
Architects Can Unintentionally Recentralize Knowledge
- Architects often become knowledge sinks who block team flow by centralizing system context.
- This creates team dependency that undermines the goal of decentralized architecture by teams.
Enable Teams, Don’t Make Decisions For Them
- Treat platform and architect teams as enablers who teach teams to do architecture themselves.
- Shift platform work from making decisions to coaching, mentoring, and short-term collaboration.