Mark Seemann makes a case for selective bureaucracy in software development, arguing that some structured processes — like moving tickets, writing commit messages, and maintaining Architecture Decision Records — reduce interruptions, improve knowledge retention, and increase team bus factor. The argument draws on historical origins of bureaucracy as a fairness mechanism and applies the logic to software teams: oral-only cultures may move fast short-term but suffer long-term from knowledge loss when contributors leave. The goal isn't more bureaucracy, but trimming it to keep only the parts that genuinely help.
Table of contents
Origins of bureaucracy #Too much of a good thing #The worst system #The mature choice #Bureaucracy, the good parts #Conclusion #14.9K Impressions1 Comment