Ep.332 - And then a Miracle Happens!

Jason shares Keith Cunningham meme from Tony Robbins Business Mastery: chalkboard shows math on left, "and then a miracle happens" in middle, results on right, professor says "I think we need some more detail around step two." Point: can't say "1 plus 2 plus miracle equals financial success", need optics, measurement, numbers to make good decisions. Same applies to construction scheduling: when variation occurs, can't dissolve logic in P6/Asta/Microsoft Project and fake a plan, that's wishful thinking. Must intelligently adjust following production laws: Little's law, law of bottlenecks, law of effect of variation, Kingman's formula, Brooks's law. Concrete production example from Weston Woolsey at Oakland: smaller batch sizes, smaller crew sizes. Key question: when variation happens on decks, do you just shift deck schedule or shift everything together (columns, walls, decks)? Analyzes through each law, Kingman's formula says keep cycle times consistent in rhythm; law of bottlenecks says isolating deck schedule increases variation so you can't see/optimize bottlenecks; law of variation says changing just deck schedule creates different handoffs, crane schedules, procurement, manpower cycles; Brooks's law says shifting manpower between areas slows production. Learned from Germans (Yanosh and Marco): sometimes better to move everything together in variation and keep workflow/trade flow/logistical rhythm consistent instead of creating little ripples of variation and inconsistent handoffs. Patton: "A good plan violently executed today is better than a perfect plan tomorrow"—but he didn't say "no plan violently executed." Final message: anything that increases variation will increase project duration.

What you'll learn in this episode:

• Keith Cunningham's miracle meme: chalkboard with math on left, "and then a miracle happens" in middle, results on right, professor says "need more detail around step two"; can't rely on wishful thinking in finances or schedules

• Why dissolving logic in scheduling software is like saying "1 plus 2 plus miracle equals success"—must show reality of impacts, then make plan following production laws, widen circle, get help

• The critical concrete scheduling question: when variation hits decks, do you shift just deck schedule or everything together? Most people shift decks alone, but that violates production laws

• How isolating deck schedule fails Kingman's formula: need consistent cycle times in rhythm, but shifting only decks breaks rhythm for columns/walls/decks working together

• Why shifting decks alone violates law of variation: creates different handoffs, different crane schedules, different procurement times, different manpower cycles—moving crews everywhere causes context switching losses

• The German insight from Yanosh and Marco: sometimes better to move everything together in variation and keep workflow/trade flow/logistical rhythm consistent instead of creating ripples throughout system

• Patton's principle correctly applied: "A good plan violently executed today is better than a perfect plan tomorrow", but he didn't say no plan violently executed; everything requires a plan

"Anything that you do that increases variation will increase your project duration."

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