Glenn Ballard said people need to “speak truth to power” and “expect help, not harm” when they question a decision or admit a mistake.
That was his opening idea at the 2018 Lean In Design forum. The Constructrr recap then moved among Glenn Ballard, Felipe Engineer-Manriquez, Kevin Labrecque, Nick Laughrin, Rachael David, Larry Kavanagh, and other forum voices. They discussed psychological safety, program learning, design decisions, planning, and collaboration.
Together, those perspectives show why Lean design cannot be reduced to a meeting format. The method depends on what the team is willing to make visible and what it does with that information next.
Information must be safe enough to surface
Glenn Ballard described psychological safety as the ability to raise questions and ask for help without expecting punishment or dismissal. His example centered on a person who recognized a possible mistake but hesitated to speak because of what had happened the last time.
In design and construction, a concern can be less dramatic and still matter. A person may see an assumption that needs testing, a constraint that has not been cleared, or an idea that does not fit the current plan. The team cannot work with information that stays hidden.
Later voices in the recap returned to the same condition through pull planning. Participants described trades seeing their dependencies face to face, leaving ego at the door, and discussing constraints before the work occurred. Those comments were event reflections, not measured proof for every project. They show the behavior the participants associated with the method.
Learning can move from one project to the next
Nick Laughrin described healthcare projects that used similar teams over several years. The repeated work gave participants a baseline and a chance to carry lessons into later projects, including lessons about prefabrication and modularization.
Glenn Ballard approached the same issue from the owner's side. He argued that savings and benefits should be viewed across a program, because value created on one project may be useful somewhere else even when it cannot be reinvested in the same job.
The reported percentages and project outcomes in the forum recap belong to those speakers and that 2018 setting. The transferable operating idea is the learning path: decide what the team learned, preserve it, and give the next project a way to start from that knowledge.
Design needs room for a better idea
When the recap returned to design, Glenn Ballard warned against treating it like construction production. If every decision is forced to the beginning, emergent ideas can be suppressed before the team understands their value.
That does not remove the need for decisions; it changes how the team reaches them. The project needs enough structure to compare choices and enough flexibility to incorporate information that appears during design.
Larry Kavanagh described a Choosing by Advantages session in which people used the same information and still selected different options. His example is a useful reminder that visible criteria do not make judgment disappear. They let the group see how a choice was made and discuss the tradeoffs together.
A Lean review can begin with one withheld fact
Choose a design decision the team has revisited more than once. Before asking for another vote, ask each person what information would make them question the current direction. Record the constraint, assumption, or advantage beside the option it affects. The decision owner can then decide whether the new information changes the choice or whether the existing direction still holds.
The value of that review is not forced agreement; it is a decision made after the team had a real chance to speak. The condition remains the one Glenn Ballard named at the forum: when people bring forward a concern, they need reason to expect help rather than harm.
