THE OPERATING CODE | 013
PROTECT WHAT HAPPENS NEXT
Not every unfinished task carries the same consequence.
Some days we don't accomplish everything we planned. We adjust the schedule, carry the remaining work forward, and keep moving.
Other days, what we finish today determines whether something else can happen tomorrow.
Commissioning. An inspection. An outage. Another trade. Another crew. A customer commitment.
When someone else's plan depends on our work being ready, the priority changes.
We need to protect what happens next.
KNOW WHAT CANNOT SLIP
When a downstream commitment is approaching, we need to identify the work that absolutely has to be complete for that commitment to happen.
The full scope may contain twenty things.
Maybe only eight of them have to be finished before tomorrow's commissioning can begin.
Those eight become the priority.
That doesn't mean the other twelve don't matter. It means we understand the sequence.
If we finish the critical work at four o'clock, we keep going. Everything else we complete makes tomorrow easier.
If we reach the critical minimum at eight or nine at night, continuing may no longer be the right decision. The crew still needs to get back to the hotel, eat, sleep, and be capable of performing tomorrow.
We don't sacrifice tomorrow just to make today's numbers look better.
SUPERINTENDENT VIEW
PROTECT THE EXECUTION
At the superintendent level, we need visibility.
An experienced foreman should understand the scope, the milestones, and what his crew needs to accomplish. We don't need to run his crew for him.
But we do need accurate information.
If tomorrow's commitment is at risk, we need to know while there are still options.
A two o'clock phone call saying, “We're behind,” gives us time to respond.
Why are we behind?
What is actually complete?
What's left?
What does the foreman think the recovery plan should be?
Do we need another person?
Can we change the sequence?
Is something consuming resources that can wait?
At seven o'clock, many of those options may already be gone.
Checking progress isn't micromanagement. If we're responsible for tomorrow's execution, we need enough visibility today to know whether the plan is still achievable.
And we cannot rely entirely on verbal progress reports.
If someone says a task is almost finished, sometimes we need to go look.
If the information repeatedly turns out to be wrong, we need the root cause before deciding who failed.
Maybe the foreman estimated poorly.
Maybe somebody on his crew gave him bad information.
Maybe material failed.
Maybe something was damaged.
Maybe the original commitment was unrealistic.
Two failures can produce the same outcome for completely different reasons.
We need to understand the cause before we decide what needs to change.
PUT ATTENTION WHERE FAILURE COSTS THE MOST
We cannot stand beside everyone and prevent every mistake.
Some mistakes are going to happen.
What we can do is recognize where a mistake carries a larger consequence.
A blurry picture can be taken again.
A missed scan can usually be corrected.
But if we're about to cut something that cannot be put back, change something that cannot easily be reversed, or perform a task that can threaten tomorrow's milestone, that work deserves additional attention.
We need to communicate that before the mistake happens.
Slow down here.
Double-check this.
Pay attention to this measurement.
Once we do this, we may not be able to go back.
Eventually, experienced foremen learn to recognize those critical points themselves.
That's part of development.
What once required instruction and additional supervision eventually becomes experience and judgment.
Eventually, it's just another Tuesday
PROJECT / OPERATIONS VIEW
PROTECT THE COMMITMENT
At the project or operations level, our responsibility changes.
We cannot go to the field every time a crew falls behind and personally recover the work.
That's the superintendent's responsibility.
We have to trust the superintendent to understand field execution, recognize inefficiencies, work with the foreman, adjust resources within his authority, and develop a recovery plan.
Our job is to understand what that recovery means to the larger operation.
Suppose we have a customer meeting in ten minutes about tomorrow's commissioning and the superintendent sends a message:
“I don't think we're going to make tomorrow's commissioning. I wanted to let you know as soon as I found out.”
We don't need to take over the site.
We need information.
What happened?
What is still incomplete?
What is the recovery plan?
What support does the superintendent need that he cannot provide himself?
And when will we know whether tomorrow's commitment can still be met?
Then we need to look beyond the site.
Is commissioning personnel already traveling?
Does the customer have other resources committed?
Will another contractor be affected?
Can we move resources without creating another problem somewhere else?
Is there additional cost?
Do we need customer or engineering approval?
What does the customer need to know now, and what still needs to be verified before we give them a final answer?
The superintendent protects the field recovery.
Management protects the commitment around it.
That means communicating risk without creating unnecessary alarm. It means being truthful about what we know, clear about what we don't know yet, and responsible for getting the answer.
It also means taking the heat.
We don't sit in front of the customer and blame the foreman or superintendent.
Internally, we need accountability and root-cause analysis.
Externally, we represent the organization.
If we made the commitment, we own the conversation.
DON'T SOLVE EVERY PROBLEM AT THE LEVEL BELOW YOU
Moving into management changes how we control the work.
As a foreman, we can physically control much of what happens on one site.
As a superintendent, we can still go to the site, watch the work, move resources, find material, coach the foreman, and directly influence execution.
At the project or operations level, we cannot operate that way across every project.
We need capable people below us.
We need reliable information.
We need clear authority.
We need escalation before options disappear.
And we need enough trust to allow the superintendent to do the job we put them there to do.
Our field experience still matters.
It helps us ask better questions, recognize weak recovery plans, understand what is realistic, and know when something doesn't sound right.
But experience at the level below us should help us manage that level.
It shouldn't require us to keep doing the job for them.
PROTECT WHAT HAPPENS NEXT
Plans will change.
People will make mistakes.
Equipment will fail.
Production will fall behind.
Protecting what happens next doesn't mean preventing every problem.
It means recognizing which commitments are exposed, getting accurate information while options still exist, putting attention where failure carries the greatest consequence, and responding at the level we're responsible for.
At the field level, we protect the execution.
At the management level, we protect the commitment.
And as responsibility grows, we have to learn the difference.