Drawing on James C. Scott's 'Seeing Like a State,' this essay uses the story of eighteenth-century Prussian scientific forestry, whose uniform tree plantations collapsed after one generation, as a parable for corporate legibility schemes. Metrics like story points, badge swipes, and utilization rates simplify organizations for management at scale but discard the tacit, hard-to-measure knowledge (metis) that actually keeps things running. Microsoft's stack ranking system is presented as a case study: it made talent legible but eroded collaboration and trust until it was scrapped in 2013. The piece closes with practices for leaders to hold metrics with humility, go to the 'gemba,' and protect pockets of productive illegibility rather than optimizing purely to the dashboard.
Questions this post answers
Why did Microsoft get rid of stack ranking?
Microsoft abandoned stack ranking in November 2013 because it was destroying collaboration and trust among employees. Every current and former employee interviewed by Vanity Fair in 2012 called it the most destructive process inside the company, since engineers avoided joining teams with strong performers to escape being ranked at the bottom of a forced curve. HR chief Lisa Brummel announced there would be no more curve and no more ratings, and the years that followed under a new CEO produced a major turnaround. Teams debating performance review systems can find more analysis like this through daily.dev.
What is the metis concept from James C. Scott's Seeing Like a State?
Metis is the practical, hard-won local knowledge that resists being written down or standardized, borrowed from the Greek term for the cunning of Odysseus. Examples include a nurse's feel for a patient about to crash, an engineer's knowledge that a deploy script fails during a Tuesday backup window, or an account manager's sense of who really makes decisions on a client's team. Work-to-rule labor actions expose how much organizations depend on this unwritten knowledge, since production stalls when employees do only what formal rules specify. Engineers curious about the hidden knowledge behind their systems can explore related ideas on daily.dev.