Seeing like a software company
14 hours ago
- #legibility
- #software-development
- #organizational-theory
- James C. Scott's concept of 'legibility' explains how modern organizations prioritize measurable and trackable work ('legible' work) over essential but untrackable tasks ('illegible' work).
- Legibility often reduces efficiency but is favored for its benefits in planning, coordination, and large-scale operations, as seen in historical examples like German forests.
- Software companies balance legible processes (e.g., OKRs, Jira) with illegible work (e.g., tacit knowledge, interpersonal favors) to function effectively.
- Large tech companies rely on legibility for enterprise deals, long-term planning, and coordination, despite the inefficiencies it introduces.
- Temporary 'zones of illegibility' (e.g., strike teams) allow companies to handle urgent issues without bureaucratic delays.
- Backchannels and informal networks ('unsanctioned illegibility') are crucial for efficiency but are often undocumented and rely on personal relationships.
- Organizations consist of 'sociopaths' (exploiters of illegibility), 'clueless' (rule-followers), and 'losers' (those who avoid the corporate game), reflecting different engagements with legibility.
- Advocating for illegible processes is 'dangerous advice' because it challenges formal structures but is necessary for high-efficiency work and adaptability.