Why Excellence Initiatives Fail Before They Start
Most excellence initiatives begin without any genuine understanding of reality. This is not rhetorical exaggeration but a recurring observation that surfaces every time we open the file on a stalled initiative: a prestigious global model, an approved budget, an enthusiastic team, and an executive sponsor who believes in the idea — and then, months later, pale results, silent resistance, and elegant documents that reflect nothing of what is actually happening on the ground. The question usually asked at this moment is wrong from the outset: why did we not execute hard enough? When the right question is: did we even start from an accurate understanding of what we were trying to change?
This article takes a clear position that may seem jarring to anyone who has spent heavily on methodologies and certifications: excellence initiatives rarely fail because of insufficient effort, nor because of a poor choice of model, nor because of weak tools. They fail because they set off from a wrong diagnosis of reality. The organization builds its solutions on an imagined reality — reality as it ought to be, or as it appears in slide decks — rather than on reality as it actually is, in all its tangled detail. And when the diagnosis is wrong, everything built upon it, however well crafted, is built on soft ground. What follows unpacks the roots of this wrong diagnosis, walks through the six most common failure patterns, and then sets out how genuine excellence begins from an honest understanding of the operational baseline.
The Initiative Does Not Fail in Execution, but in Assumption
When we dissect a stalled excellence initiative, the instinctive tendency is to look for the moment of collapse somewhere in the execution phase: here the team fell behind, there commitment weakened, at that stage leadership support faded. But this dissection starts in the wrong place. The moment that decided the initiative's fate was not the faltering execution; it was the silent assumption that preceded execution by months: the assumption that we know our own reality.
Every excellence initiative carries within it a mental model of the organization — a picture of how processes work, where the problems lie, who does what, and why things take so long. That mental model is the diagnosis. And in most cases the diagnosis is never written, never tested, and never reviewed; it is simply assumed. Leaders gather in a room, processes are sketched on a whiteboard as those present remember them, everyone agrees on the problem, and off they go toward the solution. The trouble is that what was drawn on the board is the process as imagined by people who do not run it daily, not as it is lived by those standing on the production line or behind the service window.
Here lies the fundamental fallacy: we treat diagnosis as a quick, self-evident step, when in truth it is the hardest and most consequential phase of the entire initiative. Diagnosing the body of an organization is no less complex than diagnosing the human body; and a physician who prescribes before examining is not described as fast, but as reckless. Yet in the corporate world we accept that initiatives worth millions begin on the basis of a diagnosis that took no longer than a single meeting.
The logical result of this flaw is that the initiative has effectively failed before it began. Not because the team will not work hard, but because all that hard work will be aimed at solving a problem that is not the real problem. And the more refined the execution, the more deeply we entrench the wrong solution, and the harder and costlier it becomes to walk it back.
Pattern One: Setting Off Without a Diagnosis
The most common failure pattern is also the simplest and most dangerous: the initiative begins with no diagnosis at all. No examination of reality, no measurement of the operational baseline, no serious attempt to understand how things work before trying to change them. The entire phase of understanding is compressed into leadership's impressions and memory, and then the work jumps straight to designing the solution.
This happens for understandable, if unjustifiable, reasons. Leadership feels the urgency of results, and diagnosis looks like a delay with no visible payoff. There is also overconfidence in experience: we know our organization, we have worked here for years. And there is a prevailing culture that rewards rapid motion and punishes deliberation, so anyone who asks for time to examine is seen as hesitant rather than wise. The initiative is thus born of urgency rather than understanding.
But leadership experience, however great, remains a view from the top. The executive sees the process as it appears in reports and dashboards, not as it runs in its daily detail. Between what is escalated upward and what happens below there is a systematic gap: reports are filtered and polished on their way up, so leadership receives a cleaner, simpler picture than reality. A decision built on that filtered picture is a decision built on structurally incomplete information.
The price of this pattern is that the initiative solves problems that do not exist, or ignores the real problem entirely. The organization invests in automating a process that is broken at its core, and gets a faster version of the chaos. Or it launches a massive training program when the real problem is in the design of the process rather than the skill of those executing it. The effort is real and the spending is real, but the impact is nil because the arrow was aimed at the wrong target from the start.
Pattern Two: Copying Models Instead of Building Understanding
When an organization decides to pursue excellence, the first thing it usually does is search for a model that succeeded somewhere else. A global company applied a particular methodology and made a leap, or a government entity adopted a famous excellence framework and won an award. So the whole experience is imported — with its tools, its terminology, and its steps — in the hope that the result will repeat. This is the second failure pattern: replacing understanding with copying.
The heart of the fallacy here is that a successful model is a solution designed for a specific problem in a specific context. The model did not succeed because it is a good model in itself, but because it fit the reality of the organization that applied it: its culture, its operational maturity, the nature of its sector, and the kind of challenges it was facing. When you transfer the solution without transferring an understanding of the problem it was designed for, you transfer the shell and leave the substance behind.
“A global model is not a ready-made recipe; it is the answer to a question another organization asked. Whoever imports the answer without first asking their own question gets a correct answer to a problem they do not have.”
This problem worsens in our context when the relationship between model and reality is misunderstood. Global excellence frameworks — for all their great value — were designed to be mirrors against which an organization measures itself, not molds into which it is poured. When an organization treats the framework as a checklist of items to satisfy in order to please an external assessor, excellence turns from a genuine practice into a documentation ritual. Evidence is gathered, policies are written, and files are prepared for assessment — while the operational reality remains untouched by change.
More dangerous still, copying disables thinking. When we hold a ready-made model to apply, we feel exempted from the trouble of understanding our own reality. The model becomes a substitute for diagnosis rather than a tool for it. So we spend months aligning our organization to the model, instead of spending days understanding our organization first and then choosing what suits it from the model. The difference between the two paths is the difference between an initiative that serves the organization and one that serves the model.
Pattern Three: The Absence of an Operational Baseline
Imagine a physician who begins treatment without measuring the patient's blood pressure, temperature, or lab results. How will they know whether the treatment is working? How will they tell improvement from deterioration? This is exactly what many initiatives do when they set off without a measured Operational Baseline — an accurate, documented picture of reality as it is now, before any intervention.
The operational baseline is not just numbers gathered for decoration. It is the reference against which everything to come is measured. How long does the process actually take from start to finish? How often is a task redone because of an error? Where does work pile up and wait? How much of an employee's time goes to value-adding work, and how much to correction, rework, review, and waiting? Without measured answers to these questions, every later claim of improvement becomes an opinion that can be neither proven nor disproven.
The absence of a baseline produces two coupled problems. The first is that we do not know where we are starting from, so we diagnose by hunch: the process is slow — how slow? Compared to what? No one knows. The second, and more dangerous, is that we will never know whether we improved. After months of the initiative, when the team is asked about impact, all it has are general impressions: things are better, people are more satisfied. And these impressions do not survive a single executive question: by how much did we improve, and on what evidence?
This measurement vacuum carries a political price too. An initiative with no reference baseline cannot prove its value, and so becomes the first casualty of any budget pressure. When its budget is cut, the initiative's leader has no numerical argument to defend it, because they never established the starting point in the first place. Work that may well have been useful is condemned to death because it could not prove it had been useful.
Pattern Four: Leadership Theater Instead of Commitment
Every major initiative launch features a recurring scene: the executive opens the event with an inspiring speech, declares that excellence is a strategic priority, unveils the slogan, and then photographs are taken and distributed across the internal channels. This scene, if it stops there, is not leadership commitment — it is leadership theater. And leadership theater is among the most dangerous failure patterns, because it mimics genuine support with a precision that deceives everyone, including leadership itself.
The difference between theater and commitment shows after the ceremony ends. Genuine commitment means the leader gives their time, not just their words; that they attend progress reviews regularly, ask hard questions, make costly decisions that clear obstacles, and actually reallocate resources when the situation demands it. Theater, by contrast, settles for the symbolic: a speech at the start, absence thereafter, and preoccupation with what is more important the moment the initiative hits its first wall.
Employees read these signals with astonishing accuracy. They listen less to what the leader says than they watch what the leader does. And when they see that the leader who launched the initiative with such enthusiasm attended none of its reviews and made not a single hard decision in its favor, they instantly draw the real conclusion: this is not a genuine priority. So they grant it, in turn, the same measure of attention the leader granted it — which is to say, a token one.
Leadership theater has a hidden link to the wrong diagnosis. When the diagnosis is built in a closed room, far from reality, it is hard for the leader to commit deeply, because deep down they are not certain that the stated problem is the real problem. Deep commitment is born of conviction, conviction is born of understanding, and understanding is born of honest diagnosis. A leader who took part in examining reality and saw the numbers with their own eyes commits because they know; a leader who was simply shown a slide deck merely humors it, because they do not.
Pattern Five: An Initiative Without an Owner
Many excellence initiatives are born orphans. They are launched with momentum and handed to a committee, a task force, or a department already buried under its own workload, without a single, named person who truly owns the initiative and is held accountable for its outcome. And when responsibility is spread across everyone, it in fact rests on no one. This is the fifth pattern: the absence of clear ownership.
Ownership is not merely a name in the owner column of a project plan. Genuine ownership means three things together: the authority to make decisions and move resources, time that is actually allocated rather than scraped from the gaps in a calendar, and explicit accountability for the outcome, in success or failure. When any one of these three is missing, ownership becomes a title with no substance.
In the absence of an owner, the initiative stalls in ways that are hard to trace. Pending decisions pile up because no one holds the authority to settle them. Disputes arise between departments over priorities and resources with no arbiter to rule. And the initiative's momentum dies slowly in the administrative void — not by an explicit decision to stop it, but by gradual neglect until it is forgotten. This slow death is more dangerous than an outright cancellation, because it drains resources without freeing anyone to look for an alternative.
This pattern intersects with the wrong diagnosis from an important angle. When the diagnosis is vague and undefined, it is hard to identify the right owner, because the problem itself has no clear boundaries. But when the diagnosis is precise and specifies where the problem actually lies, in which process and under which department, the natural owner of the initiative all but designates itself. A good diagnosis does not only reveal the problem; it also reveals who ought to own its solution.
Pattern Six: Change Fatigue
When a new excellence initiative knocks on the door of an employee who has known the organization for years, it does not find an empty mind ready for enthusiasm, but a mind weighed down by the memory of earlier initiatives that launched with the same fanfare and then evaporated. This is the sixth pattern: change fatigue. It is a tax the organization pays for every earlier initiative that began and was never completed.
Change fatigue is neither laziness nor blind resistance; it is an entirely rational response from the employee's standpoint. They have seen a recurring cycle: a big announcement, initial enthusiasm, new training and templates, then a gradual cooling, then a silent return to what was. And after living through this cycle twice or three times, they learn a clear lesson: the best survival strategy is to wait. They do not resist the initiative openly; they go along with it on the surface and continue their real work as before, confident that it will pass as its predecessors passed.
The painful irony is that change fatigue is a direct product of accumulated wrong diagnoses. Every earlier initiative that failed because it set off from an incomplete understanding of reality left behind a residue of doubt. The employee who watched the organization launch three initiatives in five years — all of them solving problems they never saw as real problems while ignoring what they struggle with daily — has every reason to assume the fourth will be just like them. A wrong diagnosis does not only waste the current initiative; it poisons the soil of every initiative to come.
Here a dangerous vicious circle becomes clear: a wrong diagnosis produces a failed initiative, the failed initiative produces change fatigue, change fatigue makes the next initiative harder, so it needs greater effort, and when it too fails the fatigue deepens further. Breaking this circle does not come from a louder initiative, but from an initiative that begins — for the first time — from an accurate diagnosis that proves to the employee that someone has finally understood their reality.
The Common Thread: All of Them Are Symptoms of One Disease
The six failure patterns may seem independent of one another: setting off without a diagnosis, copying models, the absence of a baseline, leadership theater, the absence of ownership, and change fatigue. But a careful look reveals that they are not six diseases, but one symptom appearing in six guises. The common disease is disconnection from reality — beginning from a conception of the organization instead of beginning from the organization itself.
Consider how each pattern branches from this root. Setting off without a diagnosis is an outright refusal to examine reality. Copying models is replacing an understanding of reality with an imported one. The absence of a baseline is a neglect of measuring reality. Leadership theater is weak commitment because it is not built on a conviction drawn from reality. The absence of ownership is the fruit of a vague diagnosis that does not specify who owns the problem. And change fatigue is the accumulated inheritance of earlier initiatives that disconnected from reality. The root is one, and the fruit is bitter.
This diagnosis of the diagnosis, so to speak, changes how we deal with the failure of initiatives at its core. Instead of treating each symptom separately — appointing an owner, improving the leadership's rhetoric, fighting change fatigue with a communications campaign — we realize that genuine treatment begins at the source: building an honest, accurate understanding of the operational reality before any intervention. Treat the root, and the six symptoms recede together.
This is precisely what makes the diagnosis phase not one step among the initiative's steps, but the condition that governs the success of everything after it. An initiative that begins from an accurate diagnosis may stumble in execution and correct its course; but an initiative that begins from a wrong diagnosis is not saved by excellent execution, because it is excellently marching in the wrong direction.
How Genuine Excellence Begins: From Understanding the Operational Baseline
If the wrong diagnosis is the root of the ailment, the cure is a commitment to honest diagnosis before choosing any solution. This is the purpose for which RAISO developed its diagnostic approach, CorexSight™: a structured way to understand an organization's operational baseline as it actually is, not as it appears in reports or as it is assumed in meeting rooms. The core idea is simple yet rarely applied: before we prescribe the medicine, we examine the patient properly.
The purpose of this diagnostic approach is not to produce a vast report that is filed away in drawers, but to build a realistic, measurable picture of how processes actually work, where value is wasted, and where the gap lies between what is documented and what is practiced. It turns diagnosis from an impression gathered in a meeting into a disciplined practice that listens to reality at its source: from those who stand on the line of work, from numbers measured at the source rather than after filtering, and from observing the process as it runs rather than as it is recounted.
This approach rests on principles that any serious organization can adopt regardless of the named method:
- Go to the source: understand the process where it actually runs, by listening to those who execute it daily, rather than settling for what is escalated upward.
- Measure before you change: establish a measured reference baseline for time, quality, and waste, so you know where you are starting from and how to prove your impact later.
- Distinguish the documented from the practiced: look for the gap between the process as written and the process as actually practiced; in that gap most of the dysfunction lives.
- Define the problem before the solution: resist the temptation to leap to solutions and models before you have an accurate, proven description of the real problem.
- Involve those who will live the change: make the people who do the work part of the diagnosis, and you build a truer understanding and a deeper acceptance at once.
When an initiative begins from this foundation, the six failure patterns turn on their heads. There is no longer setting off without a diagnosis, because diagnosis is the starting point. No blind copying of models, because choosing the solution comes after understanding the problem rather than before it. There is a measured baseline that proves impact. A deeper leadership commitment, because it springs from conviction in the results of the diagnosis. A clear owner, because the diagnosis specified where the problem lies. And a renewed trust that breaks change fatigue, because the employee sees — for the first time — that someone understood their reality before asking them to change.
“Excellence does not begin with the ambition to be better, but with the courage to see ourselves as we actually are; whoever dares not diagnose their reality has no right to prescribe its cure.”
Honest Diagnosis Is a Condition for Vision 2030
Within the broad institutional transformation that Saudi organizations are living through under Vision 2030, the importance of this argument multiplies. The Vision is pushing organizations — public and private — toward an unprecedented wave of development, excellence, and efficiency initiatives. This momentum is a blessing if it is matched by maturity in how we begin, and a source of enormous waste if all the initiatives set off from the same wrong diagnosis. The scale of investment in transformation makes the price of a wrong diagnosis higher than at any time before.
The organization that absorbs this lesson gains a quiet but decisive competitive advantage. While others drain their budgets on initiatives built on an imagined reality, the mature organization directs every riyal toward the real problem because it knows what it is. Not necessarily spending more, but aiming more precisely. And in a world where transformations accelerate and windows of opportunity narrow, precision in diagnosis becomes the difference between an organization that advances with confidence and one that spins in circles of stalled initiatives.
Perhaps the hardest thing about this argument is that it demands of leadership a rare virtue: intellectual humility. That the leader acknowledge that — despite years of experience — they may not know their organization's reality as well as they think, and that the picture reaching them from above is not the complete picture. This acknowledgment is not weakness; it is the highest degree of leadership maturity. The leader who dares to say let us examine before we decide protects the organization from the costliest error of all: the well-executed mistake in the wrong direction.
Excellence initiatives fail before they begin when they set off from a conception instead of from reality. And they succeed when they begin where every serious change ought to begin: from an honest, courageous, and accurate understanding of what we are now. A correct diagnosis does not guarantee success on its own, but it makes it possible; and a wrong diagnosis does not guarantee failure on its own, but it makes it all but certain. From here, the most important decision in any excellence initiative is not which model we choose, but whether we dared to see ourselves as we are before deciding who we want to become.
