
Sign up to save your podcasts
Or


Jason introduces the concept of latency, the delay before action takes place, and explains why teams that decide or correct issues under 5 hours have dramatically higher success rates. Traditional project management (CPM) has only a 26% success rate with 21% failures, while Scrum/agile systems achieve 42% success with only 8% failures. The difference? Latency in seeing and acting on problems. A CPM expert called Jason to defend CPM, saying they noticed something felt wrong and caught it two months later via Power BI dashboards. Jason's response: "You just proved my point, with Takt or Scrum, you would have found that in days or hours, not months." Everything must be visual, bring problems to the surface immediately, show clearly what the problem is to everyone, and be easily understood, checked, actionable, fast, and reliable. Put scheduling systems in the hands of people at the place of work doing the actual work.
What you'll learn in this episode:
Latency = the delay before action takes place (decision-making, removing roadblocks, recovering projects)
5-hour decision window: Teams that decide/correct issues under 5 hours have higher success rates
Traditional project management success rates: 26% success, 21% failures, 53% challenged
Scrum/agile success rates: 42% success, 8% failures, 50% challenged (26% to 42% is a huge improvement)
CPM expert story: Took 2 months to notice the problem via Power BI dashboards, which proved Jason's point
Takt systems show problems in days/hours, not months
Takt uses 1/12th of the scheduling resources: No scheduling department needed, repurpose them as lean experts
Process not people principle: Blame processes and behaviors, not people, shame targets for who they are, accountability targets for what they do
Visual systems requirements: Must bring problems to the surface immediately, show clearly what the problem is, be easily understood/checked/actionable/fast/reliable
Gemba = the actual place of work where work is taking place
Put scheduling in the hands of people at the place of work, doing actual work
Reduce latency. See at the gemba. Decide under 5 hours. On we go.
If you like the Elevate Construction podcast, please subscribe for free, and you'll never miss an episode. And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two 😊).
Also, here are links to our YouTube Channels:
· Jason Schroeder YouTube Channel: https://www.youtube.com/channel/UC4xpRYvrW5Op5Ckxs4vDGDg
· LeanTakt YouTube Channel: https://www.youtube.com/c/leanTakt
· LeanSuper YouTube Channel: https://www.youtube.com/channel/UCzQDevqQP19L4LePuqma3Fg/featured
· LeanSurvey YouTube Channel: https://www.youtube.com/channel/UC-Ztn3okFhyB_3p5nmMKnsw
By Jason Schroeder4.9
139139 ratings
Jason introduces the concept of latency, the delay before action takes place, and explains why teams that decide or correct issues under 5 hours have dramatically higher success rates. Traditional project management (CPM) has only a 26% success rate with 21% failures, while Scrum/agile systems achieve 42% success with only 8% failures. The difference? Latency in seeing and acting on problems. A CPM expert called Jason to defend CPM, saying they noticed something felt wrong and caught it two months later via Power BI dashboards. Jason's response: "You just proved my point, with Takt or Scrum, you would have found that in days or hours, not months." Everything must be visual, bring problems to the surface immediately, show clearly what the problem is to everyone, and be easily understood, checked, actionable, fast, and reliable. Put scheduling systems in the hands of people at the place of work doing the actual work.
What you'll learn in this episode:
Latency = the delay before action takes place (decision-making, removing roadblocks, recovering projects)
5-hour decision window: Teams that decide/correct issues under 5 hours have higher success rates
Traditional project management success rates: 26% success, 21% failures, 53% challenged
Scrum/agile success rates: 42% success, 8% failures, 50% challenged (26% to 42% is a huge improvement)
CPM expert story: Took 2 months to notice the problem via Power BI dashboards, which proved Jason's point
Takt systems show problems in days/hours, not months
Takt uses 1/12th of the scheduling resources: No scheduling department needed, repurpose them as lean experts
Process not people principle: Blame processes and behaviors, not people, shame targets for who they are, accountability targets for what they do
Visual systems requirements: Must bring problems to the surface immediately, show clearly what the problem is, be easily understood/checked/actionable/fast/reliable
Gemba = the actual place of work where work is taking place
Put scheduling in the hands of people at the place of work, doing actual work
Reduce latency. See at the gemba. Decide under 5 hours. On we go.
If you like the Elevate Construction podcast, please subscribe for free, and you'll never miss an episode. And if you really like the Elevate Construction podcast, I'd appreciate you telling a friend (Maybe even two 😊).
Also, here are links to our YouTube Channels:
· Jason Schroeder YouTube Channel: https://www.youtube.com/channel/UC4xpRYvrW5Op5Ckxs4vDGDg
· LeanTakt YouTube Channel: https://www.youtube.com/c/leanTakt
· LeanSuper YouTube Channel: https://www.youtube.com/channel/UCzQDevqQP19L4LePuqma3Fg/featured
· LeanSurvey YouTube Channel: https://www.youtube.com/channel/UC-Ztn3okFhyB_3p5nmMKnsw

14,296 Listeners

4,424 Listeners

30,870 Listeners

32,856 Listeners

7,216 Listeners

12,154 Listeners

14,031 Listeners

1,139 Listeners

2,294 Listeners

2,633 Listeners

4,025 Listeners

2,230 Listeners

50 Listeners

382 Listeners

7 Listeners