Most Project Problems Are Not Design Problems
They're Communication, Ownership and Decision Problems
Field Note — July 2026
Framework Layer: Design Intelligence
Project Insight: Projects rarely fail because ideas are weak. They fail because intent slowly degrades as it moves through people, decisions and time.
One of the biggest surprises of my career is that very few difficult projects were actually difficult because of design.
The design usually wasn't the problem. The concept made sense. The proportions worked. The material palette was appropriate.
The strategy was clear.
Yet somewhere between approval and delivery, the project began to drift.
Execution was first to be blamed.
Poor coordination. Late procurement. Weak supervision.
Eventually symptoms appear.
The actual problems had appeared much earlier. Not in the drawings.
But in the conversations surrounding them.
I've come to believe that projects don't usually fail where they're built. They fail where thinking quietly stops.
Key Insight
Every project begins with a shared understanding. A group of people agree, however briefly, on what they are trying to achieve.
From that point onwards, the project has one job: Preserve that understanding.
Not the drawing. Not the specification.
Not even the programme.
Understanding.
Because the moment different people begin carrying different versions of the same project, entropy begins.
One person is solving for cost.
Another is protecting programme.
Another is focused on fabrication.
Another is protecting aesthetics.
Individually, none of these are wrong.
Collectively, they slowly pull the project apart.
Most project problems are simply evidence that shared understanding has started to fragment.
Project Insight
I've stopped seeing communication as the exchange of information.
Information is easy. Communication is the preservation of intent.
A drawing communicates.
A meeting communicates.
A material sample communicates.
Even silence communicates. Every interaction either strengthens a shared understanding or slowly replaces it with assumptions.
That's why I've become suspicious of projects with excessive meetings but very few decisions.
Everyone is talking.
Yet the project becomes less aligned.
Communication isn't measured by how much is said. It's measured by whether everyone leaves thinking the same thing.
Ownership
Ownership is often misunderstood as responsibility. They're not the same.
Responsibility is assigned. Ownership is assumed.
You can assign someone a task.
You cannot assign someone to care.
Ownership begins when someone continues thinking about the project after everyone else has left the room.
They notice what hasn't been discussed.
They ask the uncomfortable question.
They make the follow-up call nobody requested.
They close the loop before someone else even notices it was open.
Good projects aren't held together by process alone. They're held together by people who quietly preserve intent when nobody is watching.
Decision
One pattern appears repeatedly.
Projects rarely stop because nobody knows the answer. They stop because nobody wants to own the decision.
Waiting often disguises itself as caution.
"We need more information."
"We'll review it next week."
"Let's wait for confirmation."
Sometimes that's true.
More often, the project already knows enough to move. The cost isn't making the wrong decision.
It's allowing uncertainty to compound while waiting for certainty that may never arrive.
Design is fundamentally an act of decision-making. Project delivery is simply the continuation of that discipline.
Quality
Quality control is another phrase I've gradually stopped using. Not because quality matters less.
Because I think the phrase describes the wrong activity.
Quality isn't controlled. It's protected.
Every review asks the same question: Has the original intention survived another layer of interpretation?
The drawing interpreted the concept. Fabrication interprets the drawing.
Installation interprets fabrication.
Operations interpret installation.
Every transition creates opportunities for intent to drift.
Quality isn't catching mistakes. Quality is preserving meaning.
Pressure
Pressure has an interesting effect on projects.
It doesn't usually create new problems.
It accelerates existing ones.
Weak communication becomes silence.
Unclear ownership becomes inaction.
Delayed decisions become programme failures.
Minor quality issues become expensive rework.
Pressure simply removes the time available to hide them.
That's why difficult projects often teach us more than successful ones.
They reveal where the system was always fragile.
Reflection
Looking back, I've realised that the visible project and the actual project are rarely the same thing.
The visible project is the sculpture. The building.
The museum. The public space. The actual project is invisible.
It's the thinking required to preserve alignment across months—or sometimes years—of changing conditions.
Perhaps that's why some projects feel remarkably effortless. Not because they encountered fewer problems. Because they lost less understanding along the way.
Closing
These days, our project reviews sound different.
We rarely begin with: "Does this look right?"
Instead we ask:
Has everyone understood the same objective?
What assumption is being made that nobody has tested?
Where has ownership quietly become shared?
Which decision is waiting because nobody wants to make it?
What part of the original intention is now at risk of being diluted?
Those questions rarely change the design. They change the likelihood that the design survives.
I've stopped believing that good projects are protected by better drawings alone.
They're protected by better thinking.
Thinking that continues after meetings finish.
Thinking that survives pressure.
Thinking that keeps asking whether the project is still trying to achieve what it originally set out to do.
Most project problems aren't design problems.
They're signs that somewhere along the way, the project stopped thinking together.
Perhaps that's the real discipline.
Not creating remarkable ideas.
But preserving remarkable clarity from the first sketch until the day people finally experience the work.
Design is the creation of intent.
Project delivery is the preservation of that intent.
The quality of a project is often determined not by how well it was designed—but by how little of its original thinking was lost along the way.
This field note forms part of Sculptura’s ongoing observations on placemaking, design execution and the built environment.