Legibility and Illegibility for Operators is a 10-part series. Use this page as the table of contents and read the posts in order.
Read the series in order
- The Operator’s Legibility Problem
- Legibility Is Translation, Not Exposure
- When to Make Work More Legible
- When Illegibility Is a Feature
- The Dashboard That Flattened the Work
- Tacit Knowledge Does Not Survive Full Documentation
- Trust Is an Illegible Operating System
- Experimentation Needs a Fog Bank
- The Dark Side of Illegibility
- The Legibility Audit for Operators
Start with The Operator’s Legibility Problem. If you want the practical diagnostic, jump to The Legibility Audit for Operators.
