The Work Between The Work :
Nothing Happens One Thing At A Time
Projects Are Defined By Milestones And Delivered By Everything That Happens Between Them
Field Note — October 2026
We draw project programmes as though reality has agreed to behave.
Design.
Approval.
Documentation.
Fabrication.
Installation.
Handover.
Clean lines. Clear dates. One thing followed by another.
Then the project actually starts.
A client changes direction after something was already approved.
A supplier clarifies that something everyone assumed was included actually isn’t.
A claim needs to go out before another payment can move.
A defect appears after everybody thought the job was finished.
A drawing needs one more revision.
Someone on site needs an answer now.
Another project is calling.
And somewhere between all of that, life continues behaving as though the project is not the only thing happening.
There is a school window we have to make. A daughter waiting outside a meeting with colouring pencils.
Birthday food being organised while another design conversation continues.
A call taken in the car. Another conversation on the drive home.
None of those moments looks particularly important on its own.
Together, they are where most projects are actually lived.
We remember projects through their milestones. The presentation. The approval. The prototype. The fabrication. The installation.
The finished photograph.
But the outcome is usually being decided somewhere else.
In the spaces between them.
The follow-up nobody sees. The detail checked one more time. The conversation that prevents a misunderstanding. Responsibility that almost fell between two people.
The decision made before a small problem becomes an expensive one. And thing everyone thought was finished that somebody still had to go back and finish.
That is the work between the work.
The Programme Is Not the Project
Programmes are useful because they turn complexity into sequence. Real life immediately puts the complexity back in.
We may allocate two weeks for design development. But during those two weeks, fabrication from another project is continuing.
A commercial claim needs resolving. A client needs a revised option. A supplier is waiting for confirmation. A site visit exposes something we did not know when we drew the programme.
Someone changes their mind. Someone else is waiting for that decision before they can move.
Then one delay reaches another package.
The clean horizontal bars begin crossing over each other.
This does not mean the programme has failed. It means the programme was always only a representation of the project.
The project itself is something much more alive.
People. Money. Materials. Weather. Traffic. Energy. Information. Timing. Relationships.
Different people carrying different understandings of the same thing. And all of them moving simultaneously.
We tend to describe project complexity through the size of the job.
Large development. Major installation. Complicated structure.
Multiple consultants.
Complexity has less to do with scale than with interdependence.
A relatively small project can become extraordinarily difficult when ten decisions depend upon one another.
A large project can move surprisingly well when responsibility is clear and decisions happen when they need to.
The difficulty is rarely the number of things happening. It is keeping them connected.
The Long Middle
There is usually excitement at the beginning of a project.
A new idea. A new opportunity. Possibility.
Then eventually there is the satisfaction of seeing something completed. Those are the easy moments to tell stories about. What receives much less attention is the long middle. The part where the idea already exists but reality has not finished negotiating with it.
This is where projects spend most of their lives.
Approvals. Revisions. Technical coordination. Supplier questions. Mock-ups. Pricing. Variations.
Material samples. Site conditions. Installation sequences.
Defects. Payments. More approvals. Another drawing. Another call.
Another decision.
Nothing particularly dramatic may happen for days. And yet this is usually where the quality of the final work is being decided.
We have been thinking a lot recently about design custodianship — the responsibility of protecting design intent as projects change.
But custodianship is not only about the obvious design decisions. It also exists in the ordinary operational work.
Did someone follow up?
Was the decision documented?
Did the revised drawing reach the fabricator?
Does the person installing it understand why that dimension matters?
Did anybody check the finish before twenty more pieces were made?
Has the supplier actually confirmed the date?
When somebody says something is finished, is it?
Good execution often looks disappointingly mundane.
Check. Call. Confirm. Photograph. Measure. Write it down.
Ask again. Return.
Correct.
Close the loop.
There is very little theatre in it.
But the absence of that work becomes extremely visible later.
Small Things Quietly Change Outcomes
Projects are rarely difficult because of one spectacular failure.
More often, they become difficult through accumulation.
A response comes one day late.
A dimension is assumed.
A material substitution is not properly reviewed.
A conversation happens but is never documented.
Something is supposed to be included. Someone else believes it is excluded.
The programme loses two days here. Three days there.
A defect is accepted temporarily. Temporary becomes permanent. Nobody notices any single moment when the project went off course. There may not have been one.
It drifted.
This is the strange thing about execution.
Most problems begin while they are still small enough to look unimportant. And most good project management is simply recognising them before they become interesting.
There is a temptation, particularly in creative work, to think that our real value sits in the big decisions.
The concept. The design language. The hero gesture. Of course those things matter.
But the hero gesture eventually depends upon somebody resolving a bracket.
A beautiful surface depends upon someone rejecting the wrong finish.
A public space depends upon drainage working.
A sculpture depends upon a delivery route.
The idea and the ordinary task are not opposites.
The ordinary task is often what allows the idea to exist.
That is why planning, execution and finishing cannot really be separated.
Planning tells us where we are trying to go. Execution moves the work toward it. Finishing makes sure we actually arrived.
And finishing is perhaps the one we underestimate most.
A project can be ninety-five per cent complete for a remarkably long time. The last five per cent contains all the things nobody wants to return to. Touch-ups. Defects. Loose ends. Documentation. Corrections. Handover items. Things too small to feel urgent and too visible to ignore once somebody notices them.
Starting creates momentum. Finishing requires discipline.
Life Does Not Wait Outside the Project
Then there is everything that does not belong on the programme at all.
Recently, I found myself in a project meeting while my daughter waited nearby with colouring pencils.
The room was discussing design decisions, dimensions, cost and execution.
Outside it, she was simply waiting for us to finish.
Later she came in and, within minutes, was happily talking to some of the same people whose opinions and decisions we had spent hours trying to navigate professionally.
Another day, project conversations were continuing while I was also trying to organise something for her at school.
Nothing extraordinary happened. That is precisely why it stayed with me. We often speak about work as though it occupies a protected portion of life.
Work happens here. Family happens there. Personal responsibilities happen somewhere else.
Real life has never respected those boundaries particularly well.
A parent is still a parent during a client meeting.
Someone may be dealing with something difficult at home while reviewing our drawing.
A contractor may have been awake all night before arriving on site.
A client may be carrying pressures we know nothing about.
People do not enter projects as clean professional functions.
They enter them as people.
Tired sometimes. Distracted sometimes. Brilliant sometimes. Worried. Excited. Impatient. Generous.
Unequivocally human.
This is not an argument for lowering professional standards. If anything, it explains why systems and discipline matter.
We need clear drawings because people cannot remember everything. We need documentation because conversations disappear. We need programmes because time becomes crowded. We need responsibility because attention is finite.
Good process does not remove the messiness of human life. It gives the work a better chance of surviving it.
Then Someone Just Looks at the Thing
There is another useful consequence of having a child around the work occasionally.
She has no interest in the machinery behind a project. She does not know how many meetings happened. How many drawings were revised. Which material was difficult to source. Which supplier caused a problem. How much something cost.
How long an approval took.
She looks at the thing.
And the judgement is usually much simpler.
Is it cool? Does she like it? Can she touch it? What does it do? Why is it like that?
There is something refreshing about that.
Design professionals can spend months discussing intention.
Proportion. Materiality. Context. Narrative. Fabrication. Commercial viability. Technical resolution. And all of that matters.
Then eventually somebody who knows none of the history encounters what we made. They do not experience the process.
They experience the result.
That does not make simple reactions more important than professional judgement. But it does remind us what all the professional machinery is ultimately for.
A place has to feel like something.
An object has to communicate something.
A public intervention has to make somebody notice, pause, gather, remember, use it, question it or simply enjoy being around it.
The process exists to make the experience possible. Not the other way around.
Perhaps one of the dangers of spending too long inside a project is that we begin experiencing it through everything required to deliver it.
The client sees the approval history.
The designer sees all the compromises.
The contractor sees the installation problems.
The commercial team sees the numbers.
The public sees none of that.
They just see what is there.
Sometimes we need that reminder.
The Work Has Two Lives
Every project has a visible life.
The sketch. The model. The render. The prototype. The fabrication. The installation. The finished work.
These are the things we photograph.
They become the portfolio. They become the case study. They become the image people associate with the project.
Then there is another life almost nobody sees.
The call at 7.30 in the morning.
The message sent again because nobody replied yesterday.
The invoice followed up.
The material checked.
The awkward conversation.
The site measurement.
The correction.
The supplier chased.
The photograph sent for confirmation.
The drawing revised after dinner.
The decision made while travelling somewhere else.
The thing remembered five minutes before it would have become a problem.
The return visit after everyone else had moved on.
Individually, almost none of these moments deserves a photograph.
But remove enough of them and the photograph at the end changes.
That is the relationship we sometimes miss.
The invisible work is not separate from the finished work.
It accumulates inside it.
Every resolved detail is there.
Every useful conversation is there.
Every prevented mistake is there.
Every person who cared enough to check again is there.
Every small decision that kept the work moving in the right direction eventually disappears into the final result.
Which is probably why good execution can look effortless from the outside.
The effort has been absorbed by the work.
Nothing Happens One Thing at a Time
Maybe this is simply what we are learning about running a design practice.
There will probably never be a period where everything becomes beautifully sequential.
One project will be beginning while another is finishing.
A design presentation will happen while something else is being installed.
A claim will need attention during a creative discussion.
A supplier problem will arrive during a family obligation.
There will always be another call. Another decision. Another thing that was apparently urgent yesterday.
The goal cannot be to make all of that disappear. The goal is to maintain direction through it.
To know what matters now. What can wait. What needs somebody else’s attention. What needs ours. What is genuinely finished. What everybody has simply become tired of looking at.
And above all, what the work was trying to become before all of this started happening around it.
Projects are defined by milestones because milestones are easy to see.
But perhaps execution lives somewhere else.
In continuity.
The ability to carry an idea from one visible moment to the next without losing it in everything happening between them.
The work is the drawing. The prototype. The fabrication. The installation.
But it is also every conversation, correction, decision, interruption and return required to keep those moments connected.
Projects are rarely difficult because of the milestones. They become difficult in the distance between them.
And perhaps this is the simplest way we can describe the work we are increasingly learning to respect:
The work between the work.
Sculptura Principle
The visible work is only part of the work.
What happens between milestones determines whether the idea survives them.
Maintain the direction. Close the loops. Finish properly.
This field note forms part of Sculptura’s ongoing observations on placemaking, design execution and the built environment.