When the same problem keeps returning, organisations often respond as though they are encountering it for the first time.

A deadline is missed, so someone receives a reminder. A client becomes confused, so another email is sent. An important task is overlooked, so the team is told to be more careful. A project exceeds its budget, so the people involved are asked to manage costs more responsibly.

These responses may address the immediate situation, but they rarely explain why it happened.

When a problem occurs once, it may be an isolated mistake. When it occurs repeatedly, it is more likely to be the predictable result of the way the work has been organised.

The process is producing the result.

That statement can feel uncomfortable because it moves attention away from the person closest to the failure. It asks leaders to examine the system they designed, approved or allowed to develop.

It does not mean individuals have no responsibility. It means personal responsibility is only part of the picture.

People make decisions inside structures. They respond to incentives, deadlines, information, authority and expectations. If the surrounding process repeatedly makes the wrong action easier than the right one, even capable and conscientious people will struggle to produce dependable outcomes.

The visible error may belong to an individual. The conditions that made it likely often belong to the organisation.

Repetition Is Information

Repeated problems are frustrating, but they are also informative. They reveal where the formal process does not match the reality of the work.

If invoices are regularly sent late, the answer may not be that several people lack discipline. The invoicing process may depend on information that arrives inconsistently. Responsibility may be unclear. The task may sit with someone whose workload leaves no reliable time for it.

If clients repeatedly misunderstand what a service includes, the problem may not be their failure to read carefully. The offer may be unclear. Different parts of the website may describe it differently. The sales conversation may create expectations that the delivery process cannot meet.

If projects regularly exceed their original scope, the team may not simply need to “manage boundaries better.” The organisation may have no clear method for recognising, discussing and pricing new requests.

Each recurring problem contains evidence about the system surrounding it.

The useful question is not:

“Who failed to do what they were told?”

It is:

“What makes this outcome keep happening?”

That change in question does not excuse poor performance. It makes accountability more intelligent. Instead of treating each incident as an isolated moral failure, the organisation begins to examine patterns, pressures and design choices.

The Official Process May Not Be the Real Process

Most organisations have an official account of how work happens. A request is received. It is reviewed by the appropriate person. A decision is made. The work is assigned, completed, checked and delivered. The sequence appears logical.

Reality is usually more complicated.

Information arrives through several channels. People begin tasks before the brief is complete. Approvals are delayed because the authorised person is unavailable. A deadline moves, but the supporting schedule does not. Clients make reasonable requests that the original process did not anticipate.

People then create informal ways to keep the work moving. They send private messages, maintain separate documents, rely on memory or ask the most experienced colleague what normally happens. These workarounds may be effective, but they also create inconsistency. Two people following the supposedly same process can produce very different results.

The gap between the official process and the real process is where many recurring failures begin. A procedure cannot protect the organisation if it describes work that no longer exists.

Before changing a process, leaders need to understand how people actually use it. That requires observation, conversation and a willingness to hear that the official version may be incomplete.

The people closest to the work often know where the process breaks. They know which form asks the wrong question, which approval creates delay and which task depends on knowledge that has never been written down.

If leaders only consult the policy, they will miss the practical intelligence held by the people navigating the process every day.

People Respond to the System Around Them

Organisations sometimes expect people to behave in ways the system actively discourages.

They ask employees to prioritise quality while rewarding speed. They encourage people to raise concerns while punishing delay. They say collaboration matters while measuring only individual output. They ask teams to experiment while treating every unsuccessful attempt as evidence of poor judgement. They promote thoughtful decision-making while creating workloads that leave no time to think.

In each case, the official message and the operational message are different. People usually respond to the operational message.

If meeting the deadline is treated as more important than completing the review, people will shorten the review. If admitting uncertainty causes a person to lose influence, they will appear more confident than the evidence justifies. If every problem is followed by a search for someone to blame, people will conceal difficulties until they can no longer be hidden.

This is not necessarily dishonesty or resistance. It is adaptation.

People learn what the organisation truly values by watching what receives attention, reward and protection.

A process is therefore more than a sequence of steps. It includes the pressures, permissions and consequences attached to those steps. Changing the written instructions without changing those conditions will rarely change the outcome.

Blame Is Fast but Incomplete

Blaming an individual offers a quick explanation. It gives the organisation a clear cause, a person to correct and the reassuring belief that the wider system can remain unchanged.

Sometimes individual action genuinely is the main issue. A person may ignore a clear procedure, act carelessly or make a decision outside their authority. Accountability matters, particularly when another person has been harmed or placed at risk.

But blame becomes dangerous when it ends the investigation too early.

Imagine that an employee sends a client the wrong version of an important document. The immediate explanation is simple: they selected the wrong file.

A closer examination might reveal that the organisation stores several similarly named versions in different folders. The final version is not clearly marked. More than one person can edit the document, and no release check is required before it is sent.

The individual made the final mistake. The system supplied multiple opportunities for that mistake to happen.

Replacing or reprimanding the employee may create the impression of action, but another person working within the same arrangement could easily repeat it.

A stronger response addresses both levels. The organisation discusses the individual decision where appropriate. It also redesigns the storage, naming, access and approval process so that the same error becomes less likely.

Accountability should help prevent recurrence. If it only identifies someone to absorb the blame, it has not completed its job.

Workarounds Can Hide Weak Design

Some processes continue functioning because experienced people have learned how to work around them. They know which official steps can be skipped, which colleague can unlock a delayed approval and which piece of missing information must be found before the work can begin.

These informal adaptations are often described as initiative. Sometimes they are. Human judgement is essential in any complex organisation. But workarounds can also conceal structural weaknesses.

A process may appear efficient because one person regularly intervenes before it fails. A client relationship may appear well managed because an experienced employee remembers every detail. A project may appear financially successful because someone contributes additional unpaid hours.

The result looks acceptable. The method producing it is not sustainable.

When that experienced person takes leave, changes role or leaves the organisation, the hidden weakness becomes visible. Tasks slow down. Important context disappears. Mistakes increase.

The organisation may conclude that the replacement is less capable. In reality, the previous employee may have been carrying responsibilities that the formal process never recognised.

Leaders should pay close attention to repeated workarounds. They are evidence that people have found a need the official system does not meet.

The right response is not always to eliminate them. It is to understand them. Some should become part of the formal process. Others reveal unnecessary complexity that can be removed. A few may introduce risks that need to be addressed.

What matters is that the organisation stops depending on invisible labour without acknowledging it.

Process Design Is Also About Power

Processes are often presented as neutral. They are not.

Every process determines who must wait, who receives information, who can make a decision and whose account is treated as credible.

A complicated funding application may appear equally available to everyone, but it will advantage organisations with experienced staff, specialist knowledge and time to complete it.

A complaints procedure may exist, but it offers little protection if the person receiving the complaint also controls the complainant’s future opportunities. A consultation process may invite participation while making decisions before the consultation begins. A client onboarding system may be efficient for the provider but inaccessible to someone who requires a different communication method.

These are not simply administrative details. They shape who can participate and on what terms.

Cultural intelligence adds an important dimension to process design because people do not encounter systems from identical positions. Language, disability, income, professional status, digital access and previous experiences of institutions can all affect how a process is understood and navigated.

Treating everyone identically does not automatically create fairness.

A well-designed process considers where different people may encounter different barriers. It distinguishes consistency from rigidity and asks whether the system protects only the organisation’s convenience or also the dignity and agency of the people using it.

The process is producing a result—but it may not be producing the same result for everyone.

Fix the Conditions, Not Only the Symptoms

When a recurring problem appears, organisations often add another step. A new form is introduced. Another approval is required. A longer checklist is created.

This can make the process feel more controlled, but additional control does not always produce greater reliability. Every new stage introduces time, effort and another point at which the work can stall. If the real issue is unclear ownership, poor information or conflicting incentives, an extra form may simply add frustration.

Improvement begins with diagnosis.

A useful review might ask:

What result is this process intended to produce?

What result is it producing in practice?

Where does the real process differ from the official one?

What information do people need, and when do they receive it?

Who has authority to act when the usual route fails?

Where do people rely on memory, goodwill or unofficial workarounds?

Which measures or incentives are shaping behaviour?

Who benefits from the present design?

Who experiences delay, confusion or exclusion?

What would make the desired action easier to complete correctly?

These questions move the organisation beyond the visible incident.

They help identify whether the problem involves knowledge, capacity, authority, communication, technology, incentives or the design of the service itself.

The best intervention may be smaller than expected. Clarifying one decision, removing one unnecessary handover or creating one dependable source of information can be more effective than rewriting an entire manual.

Change the System and Watch What Happens

A process change should be treated as a test, not as proof that the problem has been solved.

After making a change, the organisation needs to observe what happens. Did the delay reduce? Did the error move somewhere else? Did the process become easier for one group but more difficult for another? Did people adopt the new method, or did they immediately create another workaround? What unintended effects appeared?

This matters because systems respond to intervention. Improving one measure can weaken another. Reducing approval time may increase risk. Adding checks may improve accuracy while creating delays. Automating a task may save time but make unusual cases harder to resolve.

The aim is not to design a perfect process and declare the work complete. The aim is to build a process capable of being examined and improved.

That requires evidence, feedback and enough psychological safety for people to say when the new arrangement is not working.

A process becomes more resilient when the organisation can learn from its consequences without defending it simply because senior leaders approved it.

Design for the Result You Actually Want

Every repeated outcome is telling the organisation something.

Chronic overwork may indicate that demand exceeds capacity. Repeated confusion may indicate that communication is unclear. Persistent delays may reveal too many dependencies or uncertain authority.

Silence may not mean agreement. It may mean people do not feel safe enough to disagree. A lack of participation may not mean people are uninterested. The route into the organisation may be difficult, unfamiliar or unwelcoming.

Leaders cannot control every result. People and circumstances remain unpredictable. But organisations can examine whether their systems make the desired outcome more or less likely.

If you want people to share knowledge, give them time and a dependable place to record it. If you want thoughtful decisions, do not reward speed alone. If you want concerns raised early, protect the people who raise them. If you want greater participation, examine who the current process quietly excludes. If you want people to take responsibility, give them the information and authority required to act.

A process is not successful because it looks orderly. It is successful when it helps people produce the right result reliably, ethically and without unnecessary harm.

When the same problem returns, resist the temptation to ask only who made the mistake. Look at the conditions around them. Look at what is rewarded, what is difficult, what is missing and what people have learned they must do to keep the work moving.

Then ask the more demanding question:

“What result has this process been designed to produce—even if nobody intended it?”

The answer may be uncomfortable. It is also where meaningful improvement begins.