The 2017 owner research John Pemberton shared compared 81 owners' self-identified best and typical projects. The stronger-project group reported more deliberate team formation, earlier participation, more value-based selection, and more collaborative delivery practices. Those are associations from the study, not proof that any one practice caused the outcome.
That boundary makes the research useful as a review lens rather than a promise. A team can examine how it forms, selects, and works together while staying honest about what the study did and did not establish.
Team formation appeared more often in the stronger-project group
John Pemberton used a sports analogy to interpret the association. A championship team would not enter its final game without practicing together, yet an average project can assemble people and expect immediate coordination. He called that time “very, very productive time.”
In the study, the stronger-project group reported more attention to team chemistry, integration of new members, commitment to project goals, and decision-making. The episode presented these as differences between the two groups.
That finding supports a project-start question: what practice will help this particular group establish expectations and integrate a new member? It does not establish that one onboarding routine will produce a particular budget or schedule result.
The owner survey prioritized budget and operational date
John said the surveyed owners placed approved budget and committed operational date at the top of their project-success measures. Those priorities shaped how the research compared the self-identified best and typical projects.
Activity at project start is therefore not the measure the study used. Budget and operational date were. Team formation belonged in the analysis because it appeared more strongly in the group owners identified as their best projects.
The practical review is whether the project has defined how people will join, communicate, and make decisions before relying on speed as evidence of progress.
Earlier onboarding was another reported association
John also pointed to the timing of stakeholder involvement. In the reported data, the stronger-project group more often had key designers, contractors, and trades on board by the start of design than the typical-project group.
Earlier participation makes production, cost, and construction knowledge available while design choices are still being discussed. Whether that availability changes an outcome depends on how the team uses it, which the comparison alone cannot prove.
John challenged the claim that early involvement necessarily costs too much by pointing back to the study's under-budget association. The comparison leaves the cause unresolved.
Selection and collaborative practices appeared in the same comparison
The stronger-project group also showed more value-based selection, more collaborative delivery structures, and greater use of practices such as Big Room and target value design. John presented those as additional differences in the comparison, not as a single required bundle.
Big Room and target value design were useful to his interpretation because they brought information and trade knowledge into shared problem solving. The comparison does not isolate either practice as the reason for a result.
For one upcoming project start, record when key builders and trades will join, how new members will be integrated, and where the group will solve problems together. Review those team-formation choices as design starts. Treat the result as learning from this project, not proof of a universal formula.
John's 2017 research gives teams a set of associations worth examining. The responsible decision is to test those practices in context and keep the claim no stronger than the evidence.
