A project story can be inspiring and still be difficult to use. That was the research problem architect Renee Cheng described in the 2017 conversation. Owners and project teams needed more than memorable success stories. They needed a way to compare cases and find a relevant lesson when a real decision became active.
Renee's work was trying to close that gap. She was not only collecting examples. She was working toward a way for owners and teams to compare situations, retrieve relevant lessons, and make better use of research while the work was still underway.
A good case story is not the same as a useful decision tool
Renee Cheng described how early IPD success stories began to blend together. A reader could remember that a result was impressive and still be unable to answer the practical questions that showed up later.
Which team brought in key partners earlier? Which one used a different contract structure? Where did trust become visible in the process? What did the owner actually do when a difficult decision arrived?
That is where research has to do more than celebrate outcomes. It has to make comparison possible. Renee's approach moved in that direction by organizing cases so readers could move across projects by issue instead of reading everything as one long narrative.
Architects need to see how Lean changes design value
Renee also spoke directly about designers. She said architects were often less satisfied with Lean projects than other participants and that part of the challenge was translation. Construction teams can see the production logic more quickly. Designers need a clearer explanation of how Lean improves the value of design work itself.
That is an important distinction. If Lean is explained only through construction efficiency, a design team may not see how it can support the design process or its outcomes. Renee's research question was how to explain where Lean could benefit the design process and its outcomes.
Renee was not arguing for design to sit outside the Lean conversation. She was arguing that the value proposition has to be real for the people being asked to change the way they work.
Human outcomes belong in the value conversation
Renee also widened the definition of project value. She did not stop at first cost or even lifecycle cost. She talked about comfort, behavior, productivity, capacity, and the human experience of the building.
That makes the research harder. It also makes it more useful. A team can hit technical targets and still miss the lived experience the building was supposed to support. Once that is true, value is no longer only a construction question. It becomes a question about whether the project helped the people who were meant to use the space.
Renee did not pretend those outcomes were easy to measure. She was clear that many variables influence them. The important move was refusing to leave them out simply because they were harder to study.
Research gets stronger when teams can return to it by issue
Renee described a more structured research approach for exactly that reason. Instead of asking readers to remember one project at a time, she was organizing case work so teams could move by category and compare similar problems across more than one source.
Renee Cheng described the intended use directly as “a tool more than just something that you would read and remember.” A project rarely needs every lesson from another building. It needs the few comparable lessons that help the team examine the issue in front of it.
Pick one recurring decision that currently depends on memory or a favorite example. Before the next review, name the comparison that would help: team selection, contract approach, BIM execution, trust, or another source-backed category. Organize the next research pull around that category and record which parts of the comparison actually match the project.
The decision is not whether a case study tells a good story. It is whether the team can retrieve and compare the part of that story it needs before choosing a path.
