Do Busy Right - The Task and Attention Management Podcast · Larry Tribble, Ph.D.

The Modern Productivity Paradox, What Should Knowledge Workers Do? - DBR 072

·50 min·3 clips
Systems theory says optimizing a sub-process can sub-optimize the whole process.
1. Do Busy Right: The Task and Attention Management Podcast uses 'The Modern Productivity Paradox' to examine why IT spending does not automatically raise productivity. 2. Larry Tribble is the host and speaker, and he grounds the episode in his attention-compass approach to task, information, and attention management. 3. The episode asks whether knowledge workers, solopreneurs, and managers are buying software that helps output or only feels productive. 4. Tribble revisits the 'productivity paradox,' a 1990s term for the mismatch between heavy IT spending and flat national productivity statistics. 5. He links the discussion to the Y2K era and the dot-com bust, when IT spending was redirected and the paradox faded from attention. 6. He says the question is returning because software spending is rising again, including current enthusiasm for AI. 7. Tribble argues that organizations often buy IT as point solutions for individual tasks instead of as support for an entire process. 8. He gives the example of different departments buying different CRM systems and then forcing centralized IT to support all of them. 9. He says vendors are constrained by economics because they must make software that sells, not only software that is best for productivity. 10. He cites Nicholas Carr's 2003 Harvard Business Review article 'IT Doesn't Matter' and compares IT to commodity technologies like railroads, electricity, and smartphones. 11. He ties that argument to the resource-based view of strategy, where competitive advantage depends on resources that are rare, valuable, and not commodity-like. 12. Tribble says systems theory suggests businesses should optimize processes, not just routine tasks, because sub-process optimization can hurt the whole system. 13. He references Eli Goldratt's The Goal and the theory of constraints, where the bottleneck governs overall throughput. 14. He uses a 10-step wood-to-sculpture example to show that speeding up the wrong step only creates inventory before the bottleneck. 15. He says there is a 90% chance of optimizing the wrong step if you do not identify the bottleneck first. 16. He warns that more tools create more data movement between subsystems and more support burden for organizations and users. 17. The tone is explanatory and argumentative, with Larry Tribble talking directly to listeners and pausing to correct himself on systems theory. 18. The format is a solo teaching episode that moves from historical examples to practical action steps and a coaching offer. 19. People responsible for software choices, process design, or personal productivity will get the most value. 20. Listeners wanting a light overview without systems thinking or management theory may skip it.
Listen to the show on