Legible and illegible tasks in organisations

Shreyas Prakash headshot

Shreyas Prakash

I’ve been debating with my tech lead about the role of qualitative methods, continuous discovery, interviews, observational studies, in generating user insight. In his view: if we already collect vast amounts of data, isn’t it more efficient to analyse what we have rather than spend time talking to users? Quantitative data is more measurable, comparable, and easier to use as evidence. After all, what can one interview reveal that hundreds of tagged events, funnel charts, or aggregated survey scores cannot? An interview in contrast is like a needle-in-the-haystack, does it even matter when huge amounts of data is already available?

To me clearly, this was not true. In a nutshell, the reply I provided was that both “legible” and “illegible” work is important. To explain what this means, and how it applies, I need to take a long-winded detour into the world of James C. Scott, and help you see this through his eyes.

The key idea from his book ‘Seeing like a state’ translated to organisations is as follows: As companies scale, they prioritise legible work over illegible work. This makes it harder to incorporate “illegible” work through product, processes and people. Failing to incorporate the illegible leads to a lower efficiency and throughput for the organisations.

If we were to translate this into three principles:

  1. Modern organizations exert control by maximising “legibility”: by altering the system so that all parts of it can be measured, reported on, and so on.
  2. However, these organizations are dependent on a huge amount of “illegible” work: work that cannot be tracked or planned for, but is nonetheless essential.
  3. Increasing legibility thus often actually lowers efficiency - but the other benefits are high enough that organizations are typically willing to do so regardless.

The other way to put this is that “what gets measured, gets managed”, and when this company prioritises the measurable (more manageable) work, the overall efficiency of the company gets affected.

I’ll highlight some examples from the book to illustrate these points:

  • Turning a forest into a simple grid of identical trees for easier measurement: government replaced complex topologies of natural forests into perfectly measureable, easily taxeable outputs, that are more straightforward when it comes to “calculating the inventory”. But it destroys the efficiency of the forests as the (soil fungi, insects, microclimates etc) are invisible to the planners, eventually making the overall forest sickly, and low-yield.
  • The USSR experiments on agriculture: under the centralised Soviet state, agricultural produce was made fully “legible”, everything could be seen, counted, directed, and reported upon. Efficiency again collapsed as paper work mattered more than crop quality, incentives encouraged false data, and not good harvests.
  • In the 19th/20th centuries, we had Scientific Management under ‘Taylorism’ that led to reducing skilled labour into measurable, timed micro-tasks. Factory workers who had a series of jobs where measured based on how much time each job takes. The modern day counterpart for Taylorist factory management would be the excel timesheets, quite common in consultancy companies where projects are commissioned based on the “time alloted” by the team. For the sake of legibility, output was prioritised over outcome.
  • Hunter gatherers to early-agrarian societies: anthropological evidence showed that early hunter gatherers were much more well-built, less disease-prone and nourished, compared to the early-agrarian societies. What would have been the case? I was of the impression that progress to agriculture might have lead to more dietary diversity, not the other way round. The answer here also lies in James C. Scott’s key idea around legibility and illegibility. Early farmers could only cultivate 2-4 crops at scale especially carbohydrates such as wheat, barley, rice and potatoes. This made food measurable and controllable for the farmers, or the union of farmers, but dietary diversity collapsed. Again, being “easy to tax”, “easy to store”, “easy to collect”, “easy to standardise” and “easy to distribute” took preference. Being legible came at a biological cost which was ignored.
  • This applies everywhere, even the introduction of standardised units such as the S.I unit system for measurement, led to a loss in efficiency. Previously, we had local, contextual units that were applicable only to certain regions. For example, we had this unit called the “Morgen” that was defined as the area which one farmer + one ox can plough in a morning. This was replaced by “0.086 hectares”, what do you think is more efficient and applicable for the farmers of that day?

In the world of corporate-speak, organisations and softwares, this is made so visible in terms of program status update calls, bi-weekly delivery syncs, monthly OKRs, CSATs, NPS scores etc. A company that is known for certain “illegible” qualities as a startup, as it grows to be a scale-up sometimes loses them for the sake of becoming more measurable, losing itself and it’s DNA in due course. But once in a while, you might also see exceptions to this rule where organisations consciously make the illegible work more visible:

In my previous product role at Noora Health, a healthcare non-profit, we were running a program that trained patients and caregivers in maternal child care. In this case, the number of “trained patients” was legible work. This was the figure given to the grants, philanthropists and other stakeholders who were financing the program in proportion to the scale of such impact. But you also had “number of trained patients where nurse empathetically listened to the patient, and spoke to them gently” which was very illegible to measure and manage. As a consequence, this didn’t get measured, and therefore, not managed. How can you even measure “care”? But that doesn’t discount the fact that illegible work is not important (it’s important but it’s difficult to measure).. 

To ensure that the “illegible” work was still incorporated into the core program while it continued to scale and serve millions of patients and caregivers, the caregiving program had two components: an in-person component where nurses were trained to educate patients and caregivers in health facilities. And a digital component which provided just-in-time information through mobile phones for family caregiving.

If it was all about maximising “number of patients trained”, Noora Health could have very well just revamped the program focussing on JUST the digital component (as it’s easy to scale to 10s of millions this way, why bother to have an in-person component? even..). But they didn’t make that compromise, as there is a lot of “illegible work” when it comes to providing care. The way they have absorbed “illegible work” as a part of their core-program is a beautiful lesson on how it’s possible to also scale while ensuring the illegible work remains uncompromised.

Coming back to the original premise of this essay, where I was debating with my tech lead on why user interviews are important despite tons of quant data… it boils down to the same principle: illegible work should remain uncompromised.

Data can tell you who clicked on what, what they abandoned, how often an error happened etc.. but not “what users wish they could do”, “what they tried but didn’t know how”, “what workarounds were created” etc.. In that sense, data is a lagging indicator. It measures the past, and not what’s possible. What’s possible is not captured in “legible” ways. We have tacit knowledge. Lived experience. Informal behaviors. All these are “illegible”.

Data only shows the legible past. Continuous discovery makes the “illegible” work more visible, even before it becomes data. It’s not to say that this is a good replacement for quants. It merely completes it, it’s another lens we can adopt for truth-seeking, building products closer to what users really want.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. Hammock driven developmentagentic-coding
  2. Peculiar ways number three fits into our funny little brains
  3. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  4. How I write essays in 2026writing
  5. Authority in the guise of evidencecritical-rationalism
  6. Map is not the territoryphilosophy
  7. Self hypnosis as a manifestation ritualmeditation
  8. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  9. How I prepare for tough negotiations nowadaysnegotiation
  10. When should we steelthread somethingproduct-development
  11. How to become a polyglot
  12. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct-management
  13. Healthy conflict in teams have a tipping point
  14. Deslopify AI writing
  15. How I started building softwares with AI agents being non technicalagentic-coding
  16. Read raw transcriptsknowledge
  17. Legible and illegible tasks in organisationsproduct
  18. L2 Fat marker sketchesdesign
  19. Writing as moats for humanswriting
  20. Beauty of second degree probesdecision-making
  21. Boundary objects as the new prototypesprototyping
  22. One way door decisionsproduct
  23. Finished softwares should existproduct
  24. How I periodically rank my rough draftsobsidian
  25. Flipping questions on its headinterviewing
  26. Vibe writing maximswriting
  27. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  28. How I build greenfield apps with AI-assisted codingai-coding
  29. We have been scammed by the Gaussian distribution clubmathematics
  30. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  31. I was wrong about optimal stoppingmathematics
  32. Thinking like a ship
  33. Hyperpersonalised N=1 learningeducation
  34. New mediums for humans to complement superintelligenceai-coding
  35. Maxims for AI assisted codingai-coding
  36. Personal Website Starter Kitai-coding
  37. Virtual bookshelvesaesthetics
  38. It's computational everythingtrends
  39. Public gardens, secret routesdigital-garden
  40. Git way of learning to codeai-coding
  41. Kaomoji generatorsoftware
  42. Copy, Paste and Citeai-coding
  43. Style Transfer in AI writingai-coding
  44. Understanding codebases without using codeai-coding
  45. Vibe coding with Cursorai-coding
  46. Virtuoso Guide for Personal Memory Systemsmemory
  47. Writing in Future Pastwriting
  48. Publish Originally, Syndicate Elsewhereblogging
  49. Poetic License of Designdesign
  50. Idea in the shower, testing before breakfastsoftware
  51. Technology and regulation have a dance of ice and firetechnology
  52. How I ship "stuff"software
  53. Writing is thinkingwriting
  54. Song of Shapes, Words and Pathscreativity
  55. How do we absorb ideas better?knowledge
  56. Read writers who operatewriting
  57. Brew your ideas lazilyideas
  58. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  59. Compound Interest of Private Notesknowledge
  60. Conceptual Compression for LLMsai-coding
  61. Meta-analysis for contradictory research findingsdigital-health
  62. Proof of workproduct
  63. Gauging previous work of new joinees to the teamleadership
  64. Task management for product managersproduct
  65. Beauty of Zettelswriting
  66. Stitching React and Rails togetherai-coding
  67. Exploring "smart connections" for note takingknowledge
  68. Deploying Home Cooked Apps with Railssoftware
  69. Repetitive Copypromptingwriting
  70. Questions to ask every decadejournalling
  71. Balancing work, time and focusproductivity
  72. Hyperlinks are like cashew nutswriting
  73. Brand treatments, Design Systems, Vibesdesign
  74. How to spot human writing on the internetwriting
  75. Can a thought be an algorithm?product
  76. Opportunity Harvestingcareers
  77. How does AI affect UI?design
  78. Everything is a prioritisation problemproduct-management
  79. Nowlifestyle
  80. How I do product roastsproduct
  81. The Modern Startup Stacksoftware
  82. In-person vision transmissionproduct
  83. How might we help children invent for social good?social-design
  84. The meeting before the meetingmeetings
  85. Design that's so bad it's actually gooddesign
  86. Lessons learnt interview prepping for product rolesinterviewing
  87. Obsessing over personal websitessoftware
  88. English is the hot new programming languagesoftware
  89. Better way to think about conflictsconflict-management
  90. The role of taste in building productsdesign
  91. Dear enterprises, we're tired of your subscriptionssoftware
  92. Products need not be user centereddesign
  93. World's most ancient public health problemsoftware
  94. Pluginisation of Modern Softwaredesign
  95. Let's make every work 'strategic'consulting
  96. Making Nielsen's heuristics more digestibledesign
  97. Startups are a fertile ground for risk takingentrepreneurship
  98. Insights are not just a salad of factsdesign
  99. Minimum Lovable Productproduct
  100. Methods are lifejackets not straight jacketsmethodology
  101. How to arrive at on-brand colours?design
  102. Minto principle for writing memoswriting
  103. Importance of Whytask-management
  104. Quality Ideas Trump Executionsoftware
  105. How to hire a personal doctor
  106. Why I prefer indie softwareslifestyle
  107. Use code only if no code failscode
  108. Self Marketing
  109. Personal Observation Techniquesdesign
  110. Design is a confusing worddesign
  111. A Primer to Service Design Blueprintsdesign
  112. Rapid Journey Prototypingdesign
  113. Visualise detailed file structures on CLIcli
  114. Do's and Don'ts of User Researchdesign
  115. Design Manifestodesign
  116. Complex project management for productproducts
  117. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  118. Pedagogy of the Uncharted — What for, and Where to?education
  119. Future of Ageing with Mehdi Yacoubiinterviewing
  120. Future of Tacit knowledge with Celeste Volpiinterviewing
  121. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  122. Future of Equity with Ludovick Petersinterviewing
  123. Future of work with Laetitia Vitaudinterviewing
  124. Future of Mental Health with Kavya Raointerviewing
  125. Future of unschooling with Che Vanniinterviewing
  126. How might we prevent acquired infections in hospitals?digital-health
  127. The why to endure any howentrepreneurship
  128. Design education amidst social tribulationsdesign
  129. How might we assist deafblind runners to navigate?social-design