Mega-project Questions – part ‪1‬

The Project Team That Came to Work Scattered to Desks and Never Huddled Four Months Behind

There is a project in serious trouble. Four months behind schedule. No flow. Work piling up everywhere. Crews stumbling over each other. Roadblocks multiplying daily. And the project management team arrives every morning, walks past each other, goes straight to their desks, opens laptops, starts working. Alone. Isolated. Each person fighting their own fires. Superintendent dealing with trade coordination issues. Project engineer buried in RFIs. Assistant superintendent chasing permits. Project manager handling owner changes. Quality manager addressing punch list explosions. Safety manager responding to near-misses. All working hard. All skilled professionals. All committed. But never aligned. Never huddled. Never coordinated as team. So when the superintendent needs engineer help with an RFI blocking concrete pour, the engineer is already committed to structural coordination meeting. When project manager needs assistant superintendent input on schedule recovery, the assistant is already chasing inspections across town. When quality manager discovers mock-up issues requiring immediate design clarification, the team has no forum to address it collectively. Everyone busy. Everyone productive individually. But the team is not rowing in same direction. Not clearing path for field. Not removing roadblocks systematically. Just reacting independently to chaos. And the project stays four months behind. Getting worse daily. Until someone calls for help. Jason arrives. First thing he does? Starts morning team huddles. Fifteen minutes. Standing. Eight o’clock sharp. Everyone required. And within those huddles, they implement visual Scrum board for roadblock removal. Product backlog. Sprint backlog. In progress. Complete. Moving roadblocks from left to right daily. Team aligned. Heading same direction. Clearing path for field systematically instead of fighting fires individually. And the project recovers. Finishes with flow schedule. Not because people worked harder. But because they finally worked as coordinated team instead of collection of individuals.

Here is what happens when project management teams do not huddle daily. A hospital project has eight people on office team. All experienced. All capable. But they operate like independent contractors instead of integrated unit. Superintendent focuses on trade coordination. Never tells engineer about upcoming RFI needs. So engineer gets blindsided by urgent requests disrupting planned work. Project engineer focuses on submittals. Never tells assistant superintendent about long-lead equipment requiring early coordination. So assistant plans work assuming materials will arrive on time then gets surprised by delays. Assistant superintendent focuses on inspections and permits. Never tells project manager about building department issues creating schedule impacts. So project manager commits to owner milestones without knowing field constraints. Project manager focuses on owner communication. Never tells quality manager about design changes affecting mock-up requirements. So quality builds wrong mock-ups wasting time and money. Quality manager focuses on punch list. Never tells safety manager about confined space work creating safety requirements. So safety scrambles to provide training and equipment reactively instead of proactively. Safety manager focuses on incident prevention. Never tells superintendent about near-miss trends indicating systemic crew coordination problems. So superintendent misses early warning signs of future accidents. All working hard. All doing their jobs. But zero coordination. Zero alignment. Zero systematic roadblock removal. Just eight people fighting independent battles instead of winning war together. And the project suffers. Delays compound. Costs escalate. Trust erodes. Not because individuals failed. But because team never functioned as team. Never huddled. Never aligned. Never coordinated systematically to clear path for field.

The real pain is project teams not understanding that inventory and work in progress destroy cash flow and profitability. Here is throughput reality. Factory has six machines. Five machines produce four parts per hour. One machine produces two parts per hour. People say throughput is two parts per hour because that is the constraint. Wrong. Real throughput is 1.2 to 1.8 parts per hour. Why? Because material inventory builds up at the slow machine. Other machines slow down waiting for bottleneck to clear. Resources get overburdened managing inventory. Entire system grinds slower than constraint alone would predict. So you have three options. First option: add another two-parts-per-hour machine next to bottleneck. Now throughput is four parts per hour. Fastest solution. Second option: slow all machines to two parts per hour matching constraint. Now throughput is two parts per hour. No inventory buildup. No resource overburden. Second fastest solution. Third option: run all machines at maximum efficiency with mismatched speeds. Creates massive inventory. Overburdens resources. Throughput drops to 1.2-1.8 parts per hour. Slowest solution. Yet most teams choose third option. Push everyone to maximum individual efficiency. Create chaos. Destroy flow. Lose money. Same principle in construction. CPM scheduling pushes all trades to maximum efficiency without coordinating flow. Creates massive work in progress. Crews everywhere. Materials piling up. Communication channels exploding. Complexity overwhelming teams. And throughput collapses. Not because individuals are slow. But because uncoordinated maximum effort creates system-destroying inventory and chaos. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Why Inventory and Work in Progress Destroy Cash Flow

Business theory teaches critical lesson most construction professionals miss. Biggest difference between profits and operating cash is inventory. Profits are theoretical. Cash is fact. Company can claim profitability while having zero operating cash. How? Inventory. When inventory goes up, cash goes down. When accounts receivable goes up, cash goes down. When work in progress increases, operating cash decreases. Construction projects with CPM scheduling run massive work in progress. Crews everywhere simultaneously. Materials staged throughout site. Equipment scattered across zones. All representing cash tied up in unfinished work instead of flowing to bottom line. And businesses need operating cash. Not just investing cash. Not just financing cash. Operating cash. To pay bills. To service debt. To maintain operations. So projects running high work in progress are not just inefficient from flow perspective. Not just expensive from cost perspective. But devastating from cash flow perspective. Destroying companies’ ability to operate. To pay trades promptly. To invest in next project. To survive economic downturns. Meanwhile Takt planning creates flow. Limits work in progress to only what is needed for current production. Materials arrive just-in-time. Crews flow rhythmically zone to zone. Work gets completed and billed promptly. Cash flows. Operating cash stays healthy. Companies thrive. Not because Takt makes people work harder. But because Takt eliminates inventory waste destroying cash flow.

The Meeting System That Removes Roadblocks Systematically

Best practice meeting system creates perpetual cycle gathering and removing roadblocks. Starts with afternoon foreman huddle. Every trade partner turns in daily reports. Communicates permit needs for next day. Plans next day work. Creates visual day plan emailed to all workers or posted for QR code scanning. Best in class. Workers see tomorrow’s plan before leaving today. Know exactly what is happening. Where they are working. What they need. Foremen document roadblocks during huddle. Next morning starts with worker huddle. Five to fifteen minutes with all workers on site. Talk. Love them. Form social group. Connect. Teach. Most importantly: ask how they feel about things. What they need. What is in their way? What roadblocks they face. Write those down. Then crews go to crew preparation huddle with foremen. Fill out pretask plans for quality and safety. 5S their areas eliminating eight wastes. Prepare day. Stretch and flex. Lean training. Leave aligned. Now you have roadblocks gathered from two critical meetings: afternoon foreman huddle and morning worker huddle. Document on roadblock logs (good), visual maps with plexiglass (better), or visual maps in common area with Scrum board for major roadblock removal efforts (best). Then at 8 or 9 AM when office team arrives, team huddle happens. Fifteen minutes standing. Review roadblocks gathered from field. Assign ownership for removal. Act throughout day clearing path for field. Report progress at afternoon foreman huddle. Communicate in morning worker huddle. Roadblocks flow to team huddle. Perpetual cycle. Team aligned. Rowing same direction. Clearing path systematically instead of reactively.

How Scrum Boards Transform Team Huddles

Scrum works for any development work. Design. Coordination. Software. Training. Hiring programs. BIM coordination. Anything requiring creation instead of pure execution. And project management team work is development. RFI coordination. Change order processing. Buyout completion. Mock-up scheduling. Permit acquisition. Submittal tracking. All development work. So why not Scrum it? Create visual board with four columns: product backlog (all roadblocks and office tasks needing completion), sprint backlog (items committed for this week with priority scores), in progress (work currently happening), complete (finished items). During morning team huddle, team acts as Scrum development team. Product owner (superintendent or PM) sets priorities based on field needs. Scrum master (someone trained in Scrum, maybe senior engineer or coordinator) facilitates process. Development team (entire office team) moves items from left to right. Sprint planning at week start: pull highest priority items into sprint backlog. Daily standup during team huddle: move items from sprint backlog to in progress to complete. Sprint review at week end: assess progress with stakeholders. Sprint retrospective: team asks how to work faster and have more fun next week.

This gives visibility and collaboration morning huddles often lack. Instead of vague “working on RFIs today” updates, team sees specific RFI moving from sprint backlog to in progress with assigned owner. Instead of wondering whether change order got processed, team sees it move to complete column. Instead of roadblocks living on someone’s individual to-do list getting forgotten, roadblocks are visible to entire team with clear ownership and progress tracking. Trade schedules work in timescale (Takt plans, weekly work plans, day plans showing time left to right and zones top to bottom). But office coordination work does not fit timescales well. Fits Scrum perfectly. So use Takt for trade flow. Use Scrum for office development work. Both visual. Both systematic. Both creating alignment and removing chaos.

Signs Your Team Needs Daily Huddles with Scrum Boards

Watch for these patterns that signal your project management team is not coordinated or aligned:

• Team members arrive to work, go straight to desks, start working individually without ever coordinating as group creating independent fire-fighting instead of systematic roadblock removal
• Roadblocks live on individual to-do lists instead of visual team boards so nobody knows what others are working on or whether critical items are getting addressed
• Office team gets surprised by field issues because foremen and workers have no systematic way to communicate roadblocks up to team that can remove them
• RFIs change orders submittals permits and buyouts progress unpredictably because there is no visual system tracking them from backlog to completion with clear ownership
• Team members commit to conflicting priorities or duplicate efforts because they never coordinate daily about who is doing what and why
• Project stays chronically behind schedule despite everyone working hard because individuals are productive but team is not aligned rowing same direction

These are coordination failures not effort failures. People are working. Just not together. Daily team huddles with Scrum boards fix this by creating systematic alignment and visibility.

Why Olympic Teams Military Units and Sports Teams Always Huddle

Would Olympic team show up to training, scatter to different areas, never huddle as group? No. Would professional sports team arrive to stadium, go straight to individual drills, skip team meeting? No. Would military unit start mission without briefing together? No. Why? Because high-performance teams coordinate systematically. Align on objectives. Assign roles. Remove obstacles. Track progress. Adjust tactics. Together. Daily. Systematically. Not occasionally when crises force coordination. But daily because daily coordination prevents crises. Construction project management teams are high-performance teams. Or should be. But most skip daily coordination. Arrive. Scatter. Work individually. Fight fires alone. Never huddle. Never align. Never coordinate systematically. Then wonder why projects struggle despite talented individuals. Patrick Lencioni teaches: if you can get a group of people rowing in same direction, you can dominate in any industry, in any market, against any competitor at any time. Rowing in same direction requires daily coordination. Fifteen minutes. Standing. Team huddle. Scrum board. Moving roadblocks from left to right. Clearing path for field systematically. Not heroically. Not reactively. Systematically. Through coordination that high-performance teams use everywhere except construction. Until now.

The Challenge

Stop allowing your project management team to work as independent contractors. Start daily team huddles. Fifteen minutes. Standing. Eight or nine AM. Everyone required. No exceptions. Implement visual Scrum board with four columns: product backlog, sprint backlog, in progress, complete. Load it with roadblocks gathered from afternoon foreman huddles and morning worker huddles. Add office development work: RFIs, change orders, submittals, permits, buyouts, mock-ups, coordination issues. Use sprint planning at week start to pull priority items into sprint backlog. Use daily team huddle to move items from left to right with clear ownership. Use sprint review at week end to assess progress. Use sprint retrospective to improve process. Get Felipe Engineer’s Scrum training. Learn system properly. Implement it systematically. And watch your team transform from collection of busy individuals into coordinated unit clearing path for field and dominating your market.

As Patrick Lencioni teaches: if you can get a group of people rowing in same direction, you can dominate in any industry, in any market, against any competitor at any time. Daily team huddles with Scrum boards get people rowing same direction. Not through speeches or motivation. But through systematic coordination making alignment easy and chaos impossible. Fifteen minutes daily. Visual boards. Clear ownership. Progress tracking. That is how Olympic teams win. How military units succeed. How sports teams dominate. And how construction project management teams will finally start operating like high-performance units instead of disconnected individuals. Flow over busyness. Coordination over chaos. Systematic roadblock removal over heroic fire-fighting. On we go.

Frequently Asked Questions

What is the meeting system cycle for gathering and removing roadblocks?

Afternoon foreman huddle gathers roadblocks and creates next-day plan. Morning worker huddle gathers additional roadblocks from field. Team huddle at 8-9 AM assigns ownership for roadblock removal. Team acts throughout day. Progress reports back to afternoon foreman huddle. Cycle repeats daily.

How do you implement Scrum boards in morning team huddles?

Create visual board with four columns: product backlog, sprint backlog, in progress, complete. Load with roadblocks and office development work (RFIs, change orders, submittals, permits, buyouts). During daily team huddle, move items left to right with clear ownership using Scrum methodology.

Why does inventory and work in progress destroy cash flow?

Inventory reduces operating cash because cash is tied up in unfinished work instead of flowing to bottom line. When work in progress increases, operating cash decreases. Businesses need operating cash to pay bills, service debt, and maintain operations, high inventory destroys this regardless of theoretical profitability.

What is the throughput lesson from the factory machine example?

Six machines (five at 4 parts/hour, one at 2 parts/hour) running at maximum efficiency creates 1.2-1.8 parts/hour throughput, not 2, because inventory buildup and resource overburden slow entire system. Flow at constraint pace (2 parts/hour) is faster than uncoordinated maximum effort.

Why do high-performance teams always huddle daily?

Olympic teams, military units, and sports teams huddle daily to coordinate systematically, align on objectives, assign roles, remove obstacles, track progress, and adjust tactics together, preventing crises through daily coordination instead of reacting to crises caused by lack of coordination.