At the 2017 Lean Construction Institute Congress, I went looking for specific tools, techniques, metrics, and hard data. Later in the recap, I admitted that I was surprised by the answer. No single A3, Last Planner practice, or decision method emerged as the one thing that made a team successful.
The interviews with Greg Zinberg, Bernita Bikeman, Andrea Sponsal, Dan Fouchet, and Derek Brown pointed to two different kinds of readiness. People needed enough trust to share the work honestly, and the project needed enough visibility to see where material and information were getting stuck.
The tool I expected was not the answer
Andrea Sponsal said inclusion in decision making mattered more than passive acceptance. Bernita Bikeman separated talking about trust from building real trust and being comfortable with conflict. Greg Zinberg described Lean basics as a way to empower project teams to change processes and understand the viewpoints of owners, designers, and trade partners.
When the discussion returned to tools, the guests emphasized the team foundation underneath them. Trust, commitment, and a common objective were not presented as rewards after implementation. They were conditions for using collaborative tools with enough honesty to learn from the work.
Practice where a mistake costs less
Andrea Sponsal described applying Lean ideas to familiar office work before moving them into a client project. Teams used office moves, waste walks, and workspace changes to learn the process in a setting she called “a safe place.”
That sequence gives practice a purpose. The internal exercise is not the final goal. It gives people a chance to understand the change before the social and project cost of getting it wrong becomes higher.
Material flow widened the view
Derek Brown shifted the conversation from meetings to the inbound path of materials. He described teams managing a detailed project schedule while learning too late that a supplier or fabrication shop was behind. He also described sites crowded with deliveries that interfered with other trades.
The issue was not that people did not care. In Derek's account, many had learned to accept those logistics constraints as the normal way of working. Looking at vendor flow, fabrication, delivery, staging, and installation as one connected path made a different kind of waste visible.
Technology could not repair weak information
The recap also carried a clear limit on technology. A model could help communication, but it was only as useful as the information entered, managed, and discussed. A whiteboard or printed measure could serve the team better when it made the work easier to see and talk about.
That is a useful decision rule for any Lean tool. Choose the form that helps the people doing the work see the problem and coordinate the next handoff. More software is not evidence that the team has more clarity.
Stop and watch the material move
Derek Brown offered a concrete place to begin: the next time you are in the field, pause and watch through the eyes of material flow. Notice people searching through containers, stepping over stored material, or waiting for a delivery that the schedule assumed would be ready.
Then choose one handoff to trace from vendor to installation. The point is not to redesign the entire supply chain in one review. It is to see one constraint the current planning conversation has been treating as normal.
A tool can organize work. It cannot substitute for people willing to surface a problem or for a team able to see the handoff causing it.
