Technology is Necessary, But Not Sufficient
summary
Asserts that technology alone never delivers bottom‑line gains unless it removes the real bottleneck and changes managerial assumptions; demonstrates with Encom case study (software build pipeline) and a current reality tree from Theory of Constraints, uses Kingman’s queueing insight and advocates 40% utilization / 20% learning time rather than maxing staff load, warns automation or Agile only help if they diminish the slowest stage, and shows how shifting one assumption unblocks revenue.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:50Business goals and profit
- 4:21Revenue growth vs cost
- 7:56Introducing Encom
- 10:13Bottleneck in flow
- 15:02Organizational obstacles
- 20:00Encom’s problems analyzed
- 27:01Breaking assumptions
- 31:37Where tech helps
- 35:44Tech for bottom line
- 36:25Recommended books
- 36:48Q&A
related talks
37mTechnology is Necessary, But Not Sufficient
01h 08mGetting More from Technology
42mSystems Thinking for Happy Staff & Elated Customers
43mSoftware Engineering Management at Scale with the Theory of Constraints
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
36mKeynote Speaker
39mStop Focusing on Tech Debt
25mLeading through scarcity: Building capacity in the team