The Next Next Common Sense
Consider how technology company Microsoft's early attempt to mea- sure developer productivity through lines of code actually incentivized unnecessary complexity. Only when Microsoft shifted to more nuanced measures combining quantitative technical debt metrics with qualitative code review assessments did it create a measurement system that actually enhanced quality. Pure quantification can create three significant problems: Proxy measure displacement. When organizations optimize for metrics rather than the underlying qualities they represent, coherence suffers. Healthcare systems that measured physician productivity through patient volume found that increasing "efficiency" by this metric often un- dermined the actual health outcomes they ultimately sought. System gaming behavior. When metrics become targets, they cease to be good measures as people optimize for the measurement rather than the intention behind it. Financial services company Wells Fargo discov- ered this painfully when its aggressive cross-selling metrics led to wide- spread unauthorized account creation. Complexity reduction bias. Quantitative measures tend to simplify complex phenomena to make them countable, often losing critical nuance in the process. Education systems that focus exclusively on standardized test scores typically undervalue the complex skills—creativity, critical thinking, collaboration—most essential for student success. These limitations don't mean abandoning quantification but rather complementing it with qualitative approaches that capture what numbers alone cannot.
Narrative-based assessment
Qualitative assessment through structured narratives provides in- sights into complexity dynamics that metrics miss. These approaches capture the context, relationships, and emergent patterns essential for understanding complexity mastery.
331
Made with FlippingBook. PDF to flipbook with ease