How To Start A Lean Project: Team Formation And Kickoff

How to Start a Lean Construction Project: Team Formation and Kickoff

There is a line I heard years ago that changed the way I think about everything: projects don’t go wrong, they start wrong. Bent Flyvbjerg and Dan Gardner wrote that in their book How Big Things Get Done, and I have not been able to shake it since. I’d add one more layer to it. When projects do go wrong, it is almost always rooted in the team. And if you don’t build that team correctly in pre-construction, no system, no schedule, and no amount of field heroics will save you downstream.

The Pain That Starts Before the First Shovel

You know the feeling. The project mobilizes with energy. The contract is signed. The schedule looks manageable. People are confident. And then slowly, almost invisibly, the cracks appear. Trade partners who were selected on price alone show up unprepared to collaborate. Nobody is quite sure who owns which decision. The owner’s expectations exist somewhere in someone’s head rather than on the wall where the whole team can see them. And the foreman closest to the actual work does not feel safe raising his hand and saying there is a problem. The result is a project that runs entirely on reaction instead of intention. People are working, but not necessarily the right work at the right time in the right sequence.

The Failure Pattern Is in the System, Not the People

The failure pattern on these projects is predictable. Trade partners were invited to bid, not to partner. Purpose was never made specific or shared with the whole team. Roles and communication channels were assumed rather than defined. Nobody created an environment where speaking hard truths was welcome, so problems went underground until they became expensive. These are not people failures. These are system failures. The moment you can see that, you can stop repeating them.

The System Failed Them

I want to be honest about something. When a project team underperforms, the instinct in our industry is to look at who was responsible. But that framing misses the point almost every time. The trades showed up to a system that did not give them what they needed to succeed. The foremen worked inside a communication structure that was never clearly defined. The owner’s expectations never made it to the people doing the daily work. The system failed them. They did not fail the system.

A Story From the Bioscience Lab

I was the project superintendent for a bioscience research laboratory with DPR Construction in Tucson. From day one, that project was built differently. DPR did not select the lowest bidder. They selected partners. Wilson Electric and Sun Mechanical came on board as collaborators. We built the plan together in pre-construction. We enforced Lean together. We were one team before we ever broke ground.

Nick Carrasco was the HVAC foreman for Wilson Electric and later became a senior project manager. He came to one of our Super PM Boot Camps years later, and when I referenced that project, he lit up. He said, “Yep, we did that. I was there.” That kind of validation does not come from a low-bid contract. It comes from starting right.

John Boore, the foreman on that job, is probably the best field leader I have ever worked with. He was blunt. He would tell me the hard truth, and he did it directly. We wanted that. We asked for it. We cleared every roadblock he surfaced. And because of that culture, even when 30 percent of the building was being reconfigured mid-construction by the researchers who were moving in, we still finished on time. That does not happen by accident. It happens because the team was built before the work started.

Why the Kickoff Is a Production Decision

Most project teams treat the kickoff as a formality. A room full of introductions, a slide deck, and a handshake. But the kickoff is one of the highest-leverage moments in the entire project. Every hour invested in getting it right saves days in the field. When a team leaves a kickoff without shared purpose, clear conditions of satisfaction, defined roles, and safe channels for honest communication, they mobilize into the fog. And fog in construction is expensive.

There is a concept worth understanding here. The ninth waste in Lean is not overproduction or defects or waiting. It is lack of alignment. Unhealthy conflict, miscommunication, and sub-optimization all flow from teams that are pulling in different directions. The kickoff is where you eliminate that ninth waste before it ever starts.

How to Start a Lean Project Right

The first move is to choose partners, not bidders. A true partner comes to pre-construction ready to plan together, commits to the production system before mobilizing, and stays invested in the success of the whole project. Price matters. But a right-fit trade partner at a fair price is almost always less expensive than a low bidder who was never aligned with how you build. Here are the signals that separate a genuine partner from a bidder in disguise:

• They ask questions about the production system, not just the scope
• They bring their foremen to planning sessions
• They surface problems early rather than banking them into change orders
• They stay engaged when the plan changes instead of retreating to the contract

The second move is to align on purpose before anything else gets designed. On the bioscience project, the team’s shared purpose was explicit: finish on time, on budget, with great quality and safety, and implement Lean to its fullest extent including Takt, Last Planner, the Kanban method. Everyone knew it. Everyone bought in. Purpose alignment is not a soft concept. It is a production strategy. Without it, teams optimize for their own scope and sub-optimize the whole.

The third move is to establish conditions of satisfaction in the kickoff and put them somewhere the entire team can see. The owner on the bioscience project said it plainly and repeatedly: keep it safe, don’t be on the news, keep it clean, and don’t mess with the waterproofing. I repeated those conditions in morning worker huddles two to three times a week. Every person on that site knew them. That level of clarity eliminates the guesswork that generates waste. Conditions of satisfaction are specific, measurable, and visible. They are the north star every decision gets measured against.

The fourth move is to create safety for speaking out. This is one of the most underrated disciplines in construction leadership. When people closest to the work do not feel safe raising problems, the problems do not disappear. They go underground and become schedule surprises, quality failures, and budget overruns. You build psychological safety by asking for honest input and then visibly responding to what you hear. When a foreman raises a roadblock in a huddle and the response is problem-solving and follow-through, the culture shifts. Over time, the team learns that honesty is welcome. That is when you start getting the real information you need to run the project well.

The fifth move is to define roles and communication channels before the project mobilizes. Who owns each decision? Who gets called when a trade hits a roadblock? How does the owner’s input reach the field? Without defined channels, information gets filtered, delayed, or lost entirely. Teams that define this in kickoff are teams that maintain alignment when the project gets complex.

The Human Side of Starting Right

Every Lean project that begins with the right team, the right purpose, and the right conditions is a statement about what construction can be. It is a statement that trade partners deserve to be selected as partners, not just bidders. That foremen deserve clear expectations. That the workers doing the daily work deserve flow, not chaos. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. When you start right, you protect the schedule. You also protect the people inside it. Flow is never an accident, and neither is a team that trusts each other.

A Challenge Before Your Next Kickoff

Before your next project mobilizes, ask yourself these questions honestly: Do we have the right partners? Have we aligned on shared purpose? Do our conditions of satisfaction live somewhere the whole team can see and repeat? Is there safety on this team to surface hard truths early? Are roles and communication channels defined clearly enough that no one has to guess?

W. Edwards Deming said it plainly: “A bad system will beat a good person every time.” The answer is not to find better people. The answer is to build a better system, starting at the very beginning. Projects don’t go wrong. They start wrong. That means they can also start right.

On we go.

Frequently Asked Questions

What does “choose partners, not bidders” actually mean in practice?

It means your trade selection criteria must include cultural fit, willingness to collaborate in pre-construction, and commitment to the production system, not just price. The right partner saves far more in field efficiency than a low bidder ever saves on paper.

Why do conditions of satisfaction matter so much in pre-construction?

Without them, the owner’s expectations live in someone’s head instead of on the wall where the whole team can see them. When conditions are specific, visible, and reinforced in huddles, every decision on the project gets measured against the same standard.

How do you build psychological safety on a construction project?

Ask for hard truths, then respond to them visibly with problem-solving. When a foreman raises a roadblock and sees action, not blame, the culture shifts. That loop repeated consistently is how trust gets built on a jobsite.

What should a Lean kickoff meeting actually accomplish?

It should produce shared purpose, documented conditions of satisfaction, defined roles, clear communication channels, and a team that leaves aligned rather than assuming. The kickoff is not a formality. It is the foundation.

Can these principles apply outside of IPD or Lean contracts?

Absolutely. Partner selection, purpose alignment, conditions of satisfaction, and psychological safety work on any project under any contract delivery method. They are people and systems principles, not contract provisions.