Dr. Dean Kashiwagi's 2017 framework challenged a familiar risk response: add direction, supervision, and checkpoints until the buyer feels in control. A narrower question is more useful here. Does the owner's control make expert planning easier to see, or does it crowd the expertise out?
Dean's answer was that complexity rises as the project adds more layers of direction.
Control can multiply decisions instead of reducing them
Dr. Dean Kashiwagi described a buyer who seeks certainty by specifying more, supervising more closely, and adding more checkpoints. In his framework, layered direction increased the number of people telling other people what to do and made the system more complex.
His critique was not that owners should stop caring. It was that control can create a chain of people directing other people, followed by blame when the work goes wrong.
That is a harder idea than a simple procurement tweak because it asks leaders to examine whether their version of risk management is actually making expertise harder to use.
Expert planning has to be visible to nonexperts
Dean also emphasized transparent preplanning. He wanted the expert vendor to show expected time, cost, and deliverables in a way stakeholders could follow without mastering every technical detail.
That is where many teams miss the opportunity. They choose a capable specialist and still fail to create a simple shared view of what success looks like, what can disrupt it, and how the next milestone will be judged. Once that view is missing, more people step in with more opinions, and the project starts treating intervention as control.
Visible planning does not remove uncertainty. It gives the team a way to see whether uncertainty is being anticipated responsibly.
A contract label does not fix control behavior
Dean also pushed back on the idea that a delivery method solves the problem by itself. He argued that design-build can still behave like the old system if the owner continues directing the vendor instead of letting expertise own the plan and the mitigation path. Dr. Dean Kashiwagi replied, “It's the ability to identify and utilize expertise.”
That distinction matters because teams often look for one structural answer. A new contract, a new procurement step, a new set of standards. Those choices matter. They do not replace the deeper question of who is being trusted to plan, who is being measured, and who is being asked to respond when something starts to move off course.
The label can change while the behavior stays the same.
The owner's role can shift from control to assurance
Dean also described an owner role built more around assurance than duplicate direction. In that model, the vendor owns planning, performance, and risk mitigation. The owner verifies that the system is visible, credible, and being followed.
That is a meaningful shift. It does not remove owner responsibility. It changes the owner's job from trying to outperform the expert on method to checking whether the expert is making the plan understandable, measurable, and accountable.
For one outside expert on the next project, ask that vendor to show the next milestone, the main risk path, and how a deviation will be reported. A nonexpert stakeholder should be able to follow the explanation without directing the technical method. The owner can then decide whether the assurance view is clear enough or needs revision.
Dean's 2017 framework leaves owners with a role choice: duplicate the expert's direction, or require a plan that makes expertise, progress, and accountability visible.
