Every leader knows the feeling. A problem gets escalated, everyone agrees it is serious, a fix is put in place, and for a few weeks things improve. Then the same problem is back, sometimes with a different name.
In most cases the team is not careless and the people are not the problem. The problem keeps coming back because no one clearly owns it.
The symptom is rarely the cause
When something fails repeatedly, organizations tend to treat the visible symptom: a late shipment, a missed deadline, an unhappy customer, a penalty on an invoice. Someone works late, the symptom goes away, and everyone moves on.
The source usually sits one level down. Maybe the work crosses two teams and each assumes the other is responsible. Maybe the person who notices the problem has no authority to fix it, and the person with authority does not hear about it until it is expensive. Maybe the fix depends on one person remembering to do something every week, with nothing in place to catch it when they do not.
Those are ownership and structure problems. Effort cannot fix them, because effort is not what is missing.
Three questions that find the real gap
When a problem keeps returning, I start with three questions.
1. Who owns the outcome? Not who works on it, but who is accountable when it goes wrong. If the honest answer is “it depends” or a list of four names, you have found the first gap.
2. Who can make the decision to fix it? Ownership without authority does not work. If the owner has to wait for approval from someone who is not close to the problem, fixes will always arrive late.
3. How would we know it is happening again? If the only early warning is a customer complaint or an invoice, the organization is finding out too late. There should be a simple measure that someone reviews on a regular schedule.
What fixing it looks like
The answers point to a short list of changes. None of them are glamorous, and all of them work.
- Name one owner for each recurring outcome. One person, by name, accountable for the result, even when the work spans several teams.
- Write down decision rights. Who decides, who must be consulted, and who just needs to be informed. A one-page table settles arguments that would otherwise repeat for months.
- Build a regular review. A short, consistent meeting where owners report on the few measures that matter. Its job is to catch drift early, not to assign blame.
- Set an escalation path. Agree in advance when an issue moves up, to whom, and how fast. Escalation should be a routine step, not a sign of failure.
- Put the fix into the process. If a fix depends on someone remembering, it will fail eventually. Build it into templates, checklists, approvals, or systems.
An example from my own work
At Accenture, I was asked to stabilize a life sciences engagement that was paying $100K every month in service penalties. The failures had been “fixed” more than once.
The work that finally ended them was not dramatic. We clarified who owned each corrective action, redesigned how delivery was reviewed and how problems were escalated, and coordinated Finance, Legal, IT, and the delivery teams around the same picture. The recurring penalties were eliminated, and the engagement regained Preferred Service Provider status within six months.
The same pattern shows up in businesses of every size. A smaller company does not need a global governance model, but it does need the same clarity: one owner, clear decision rights, an early warning, and a fix built into how the work is done.
Where to start this week
Pick the one problem that has come back most often in the last six months. Ask the three questions above, and write the answers down. If you cannot name a single owner, or the only early warning is a complaint, you have found your starting point.
This is the first pillar of The Maverick S⁴ Method™: Stabilize. Before a business can simplify, sustain, or scale, it has to stop the problems that keep pulling leaders back into firefighting.
If you would like a second set of eyes on a problem that will not stay fixed, book a 30-minute introductory call.