A deep exploration of how to critically evaluate mental models — particularly organizational models used in software development. Using examples like the Spotify Model, Agile Fluency, and Team Topologies, the authors demonstrate heuristics for comparing models: understanding their underlying belief systems, identifying what they include or omit, recognizing their building blocks as attention-directing tools, and distinguishing between descriptive, prescriptive, and aspirational models. The piece argues that models impose framing and bias, and that comparing multiple models is the best way to break free from any single model's constraints. A five-step process for engaging with models is proposed: study, analyze/compare, adopt, gather feedback, and reshape.

42m read timeFrom verraes.net
Post cover image
Table of contents
Models Are WorldviewsHierarchies and NetworksHeuristicsModels DistractThe Spotify ModelAgile FluencyTeam TopologiesExplicit Building BlocksWhen the Team Gets Too Big: a Case StudyContrasting Spotify and Team TopologiesComparing Models YourselfBossy ModelsGetting Too Cosy with the ModelPrescriptive, Descriptive, AspirationalPutting the Model to WorkConclusionsEssays on Software DesignFootnotes