Technology is Necessary, But Not Sufficient
summary
Claim: technology helps only when it reduces the true throughput constraint. Using a fictional washing‑machine repair firm “ncom” and current reality tree cause‑and‑effect mapping (Theory of Constraints), the slowest step is field engineers failing to fix on first visit, so efficiency targets increase rework and backlog. Concrete levers are changing metrics to timeliness and right first time, improving triage/parts loading and adding self‑service or routing tech; tech alone fails, but paired with those social changes it reduces the bottleneck and raises revenue.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:27Profit as business goal
- 3:53Cost vs revenue focus
- 8:03Identifying business bottlenecks
- 10:29Case study: Incom’s challenges
- 12:22Cause and effect analysis
- 23:36Breaking assumptions with creativity
- 28:12Technology’s role in improvement
- 32:27Invalidated assumptions in management
- 33:52OpenCredo’s approach and books
- 34:13Q&A: Experience vs assumptions
related talks
44mTechnology is Necessary, But Not Sufficient
42mSystems Thinking for Happy Staff & Elated Customers
43mSoftware Engineering Management at Scale with the Theory of Constraints
01h 07mTechnical Neglect
31mImproving engineering effectiveness: A journey for the entire organization
17mOptimizing Tech Throughput
31mEngineering Effectiveness: Achieving your goals with less
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
