“No problem. I’ll get it done.”

☕ SATURDAY MORNING COFFEE PERSPECTIVE #006

What happens when an organization updates the SOP for the audit but not the operating system behind it?

I was once tasked with rewriting a standard operating procedure ahead of a major external audit.

The assignment was reasonable.

The audit mattered.
The document needed attention.
Someone needed to own the work.

But as we moved forward, I realized we were placing most of our emphasis on carrying the water for the audit, not correcting the known ambiguities inside the operation.

We were adding language without fully reviewing what was already there.

Some processes needed refinement.
Some needed replacement.
Some needed redaction.
Some simply needed to be removed because they were outdated or had a proven record of not working.

Instead, the new requirement was being layered onto the old system.

That is how organizations often weaken.

Rarely through one catastrophic decision.

More often through accumulated decisions that never displaced anything.

Every addition may be reasonable by itself. But when nothing is reviewed, sequenced, simplified, or stopped, the combined operating picture eventually becomes unreasonable.

The dashboard may not show it immediately.

In fact, the dashboard may stay green.

The people closest to the work will close the gaps. They will build workarounds, repeat unclear instructions, check one another’s work, answer messages after hours, and quietly absorb the difference between what the process says and what the operation actually requires.

They are often the people who smile and say:

“No problem. I’ll get it done.”

They believe in the work.
They trust the leadership.
They do not want the mission to fail.

So they compensate.

For a while, the organization may look as though it absorbed the new priority without consequence.

But the system did not absorb it.

The people did.

If the old process remains in place while the new requirement is added, the consequences may appear during the next operating cycle: uneven burnout, delayed decisions, turnover, inconsistent quality, or the sudden loss of an indispensable person who had been holding several disconnected parts together.

The system can keep reporting green long after the people carrying it have begun to burn out.

That creates an uncomfortable responsibility for leadership.

We must evolve the operation not merely update the document.

When a new priority enters an already full organization, leadership should first assign someone to understand it completely. That owner should clarify the intent, reconcile assumptions with facts, and identify what the new work changes.

Then leadership must decide what balanced exchange is acceptable.

What should stop?
What should move later?
What should be delegated?
What can be simplified?
Where is additional capacity genuinely required?
What temporary overload is acceptable and what is the recovery plan?

Leaders often resist stopping anything because every function has an advocate. Each owner can explain why their portion still matters.

But if everything remains a priority, leadership has not prioritized.

It has transferred the burden of choosing to the people doing the work.

Words and actions must eventually match.

If leadership says people are the mission, then the operating system must demonstrate it. Because without their judgment, effort, adaptation, and trust, every strategy is merely language in a PowerPoint presentation, an email, or an SOP.

Here is the practical challenge for Monday:

Take one new priority your organization has accepted.

Name its owner.

Then write down what it will replace, defer, reduce, simplify, or stop.

If the answer is “nothing,” you may not have added a priority.

You may have added another burden for committed people to carry.