Teiwaz Management

Happy Engineers Week! 🛠️

Your kitchen was engineered for efficiency decades before you were born.

If you’ve ever prepared a meal without feeling like you ran a marathon, you owe a debt to Lillian Gilbreth—the "Mother of Modern Management" and a pioneer of Industrial Engineering.

In the 1940s, Gilbreth didn't just see a kitchen; she saw a high-output factory floor that was failing its workers. Her solution? The Work Triangle.

📐 The Engineering Behind the Prep
By applying Motion Study (Gilbreth's signature IE methodology), she identified the three vertices of domestic productivity:

The Sink (The Cleaning Zone)
The Refrigerator (The Storage Zone)
The Stove (The Cooking Zone)

The "Magic Formula" she helped perfect:

Each leg of the triangle: 4 to 9 feet.
The total perimeter: 13 to 26 feet.
The result: Eliminating "step fatigue" and redundant movement.

🚀 Why It Was Revolutionary

Before this, kitchens were collections of disconnected furniture. Gilbreth used Chronocyclegraphs (tracking movement with light) to prove that a poorly designed kitchen forced a person to walk miles extra every single day.

She didn't just design a layout; she engineered time.

🏗️ Engineers Week: Celebrating the "Invisible" Infrastructure

Engineering isn't always about skyscrapers and bridges. Sometimes, it’s about the ergonomics of a countertop or the flow of a 100-square-foot room. Gilbreth proved that the home is a system worthy of the same precision as any manufacturing plant.

This week, let’s celebrate the engineers—past and present—who look at the "ordinary" parts of our lives and ask: "How can we make this better?"

Is your kitchen a "Triangle" or a "Zone" layout? 🍳 Let’s discuss the ergonomics of your favorite space below!

A Question for the Last Planner® Community: How "Liquid" are Your Milestones?

I’ve been thinking lately about the tension between a rigid Master Schedule and the reality of flow on a jobsite.

For those of you coaching or using the Last Planner System, I’m curious how you handle milestone adjustments during the "Do" and "Check" phases.

The 5-Day Logic Test
Imagine you’ve planned your project, but reality hits and you’re 5 days late entering the next phase.

- Do you shift the next milestone immediately to reflect the actual hand-off date?
- Or do you hold the line, essentially asking the next phase to absorb that 5-day variance?

Conversely, if a team finishes early, do you pull the next milestone back to capitalize on that momentum, or leave the buffer as is?

When the Logic Doesn’t Align

We often encounter two scenarios that test our commitment to the system:

Owner Changes: When scope is added, is the milestone shift automatic, or is it negotiated through a new pull plan?

The Validation Gap: When a pull plan is completed and the team’s collective commitment doesn't fit the allotted time in the master schedule, which one gives way?

The Health of the Project

I’ve found that Milestone Variance is often a more reliable leading indicator than a simple "Yes" when asking if a project is on schedule. It provides a level of transparency that's hard to find in a standard Gantt chart.

How are you handling these shifts?

Are you a "protect the dates" coach, or do you believe the schedule should be a living, breathing reflection of the site's reality?