Why Organizations Fail to Build Sustainable Practices

Why Organizations Fail to Build Sustainable Practices

Most initiatives end when the project ends. An organization launches an initiative to build a new practice — risk management, customer experience, operational excellence, data governance — allocates a budget, assembles a project team, brings in consultants, and sets a timeline with clear phases and a known closing date. On that date the final deliverable is handed over: a procedures manual, templates, training workshops, a dashboard, and a closing ceremony that declares success. Then, within months, everything erodes quietly: the templates are abandoned, the procedures forgotten, and the teams revert to what they were, until nothing remains of the practice but a folder on a server that no one opens.

This article takes a clear position that may sound obvious yet is rarely translated into action: a practice is not a project, but a sustainable system. A project has a beginning, an end, and a deliverable to hand over; a practice is a living organizational capability that recurs, learns, and renews itself, and does not end as long as the organization stands. The tragedy of most organizations is that they run practice-building with a project mindset — treating it as a temporary event with a closing date, when by nature it is a permanent commitment. So when the project closes, the practice dies, because it had not yet taken root in the organization's roles, systems, and daily rhythm. This is precisely what RAISO addresses with the Practice+™ concept and the Practice Builder™ model: an approach that builds a practice to last rather than handing it over and walking away. What follows unpacks why project logic kills practices, and what building them sustainably requires.

The Fundamental Difference: A Project Ends, a Practice Lives

At the heart of this argument is a simple distinction that changes everything. A project is a temporary effort undertaken to produce a defined deliverable and then end — constructing a building, launching a system, organizing an event — and its success is measured by delivering the output on time, on budget, and to specification. A practice, by contrast, is a recurring capability the organization performs continuously: how it manages its risks every day, how it listens to its customers, how it improves its processes without pause. Its success is measured not by a moment of delivery, but by its endurance and improvement over time.

Conflating the two is the original error. When we entrust the building of a practice to project logic, we ask the wrong question — when do we finish? — when the right question is how do we make this go on indefinitely? A project seeks closure; a practice seeks continuation. And whoever designs for closure gets closure.

And because the final product of a practice is not a document but a recurring behavior, the criteria for success differ radically. A project ends when the manual is delivered; a practice does not truly begin until the manual is practiced without anyone needing to be reminded of it. Many organizations celebrate at the very moment they should treat as the starting point — the file is closed while the practice has not yet been tested in the absence of the team that built it.

“A project asks: when do we finish? A practice asks: how do we make sure we never finish? Whoever builds a practice with a finishing mindset gets a practice that finishes.”

Pattern One: No One Owns the Practice After Go-Live

Every practice-building project has a clear team: a project lead, members, consultants, and an executive sponsor. Everyone knows who is responsible for what until the closing date. But the question rarely asked in earnest is: who owns the practice after the project closes and its team disperses? In most cases, the silent answer is: no one.

This post-go-live ownership vacuum is the first killer of practices. The project team is temporary by definition; its mandate ends at handover, and the consultant departs when the contract ends. So if, before that departure, a permanent owner has not been formed — a function or fixed role responsible for running, developing, and measuring the practice — it is left without a steward at the most delicate moment of all: the transition from a project being built to a daily job that must be practiced.

Genuine post-go-live ownership is not a name in a column. It is three things together: authority to make decisions and adjust the practice when reality changes, time actually allocated to running it rather than scraped from the gaps in a calendar, and explicit accountability for its continuation that shows up in performance reviews. When any one of these is missing, ownership becomes a title with no substance, and the practice is left to its fate.

The price of this pattern is a silent decline that begins the moment of handover. No one updates the procedures when the system changes, no one checks whether they are applied, and no one holds the authority to fix them when they break. It is not that anyone decided to stop the practice, but that no one remained responsible for keeping it alive. A practice without an owner is like a plant without anyone to water it: it does not die in a day, but it wilts steadily.

Pattern Two: A Practice Not Embedded in Roles and Systems

When a project hands over a new practice, it usually hands over a set of separate outputs: a manual, templates, a training deck, perhaps a dashboard. And these are treated as though they were the practice itself. But they are not; they are merely its tools. The real practice does not live in documents, but in the roles people perform daily and the systems they work through. When it is left hovering above the daily work rather than embedded into its core, it remains a stranger — practiced with effort while someone is watching, and abandoned the moment the gaze relaxes.

Embedding into roles means the practice becomes part of the job description rather than an addition to it. When risk management is a parallel activity performed in addition to the real work, it is the first thing sacrificed under pressure. But when it is woven into the core of the role — so that a manager's work is not complete without managing their risks, and their performance is not assessed in isolation from it — it becomes part of the definition of the work itself, not an extra burden to be dropped first.

Embedding into systems matters no less. A practice that relies on the discipline and memory of individuals is fragile by nature; people forget, get busy, and leave. A practice embedded in systems becomes a path hard to circumvent: a mandatory field without which the request cannot be completed, an approval step built into the workflow, an automatic alert when a threshold is crossed. When performing the practice becomes the easiest path — indeed the only possible one — adherence becomes a default rather than a daily decision that takes willpower.

The price of neglecting embedding is that the practice remains a surface layer that never touches the actual work. Procedures are written and filed, training is run and forgotten, while people continue working the old way because the system does not compel them otherwise and the role does not hold them accountable. So two practices coexist: one documented on paper for show, and the real one running on the ground. The gap between them is exactly the distance by which we neglected to embed the practice into roles and systems.

Pattern Three: Dependence on a Single Champion

Behind every emerging practice there is usually a champion: a passionate employee or a believing leader who carried the idea on their shoulders and pushed it through by sheer personal insistence until it became reality. This champion is a blessing at launch and a curse over the long run, because the practice forms around their person rather than around a system. Risk management becomes so-and-so's practice, and customer experience becomes her project. And when the champion leaves — through promotion, transfer, or resignation — the practice leaves with them, because it was never the organization's practice, but the practice of a person within it.

Champion dependency is a hidden danger because it disguises itself as success. As long as the champion is present, the practice looks alive and thriving, and everyone is reassured. But this thriving is conditional on the presence of a single person — a fragile condition by nature. An organization whose practices depend on specific individuals builds its capabilities on shifting sand: a capability that looks solid until the one who carries it moves on, then collapses in silence.

The difference between a champion and a system is the difference between a capability tied to a person and an institutionalized one. The champion knows how the practice works because they built it, but their knowledge is in their head, not in the system. An institutionalized system makes the practice performable by any qualified person who fills the role, because it is documented, embedded, taught, and measured independently of who performs it. A sustainable practice does not ask who will carry it; it ensures that no one needs to carry it on their back.

This does not mean dispensing with champions, but transforming their role. The champion's real task is not to be a pillar the practice leans on forever, but to build — while carrying it in its early days — the very system that makes them dispensable. A successful champion works to ensure the practice will not need them in two years. The champion on whom the practice remains forever suspended is, in good faith, the greatest threat to its sustainability.

Pattern Four: The Absence of a Renewal Loop

Even a practice that is well embedded and has a clear owner faces a slow, merciless enemy: time. The reality it was designed for changes constantly — systems shift, new technologies appear, regulations change, customer expectations evolve, and organizational priorities move. A practice designed to be delivered once and stay fixed turns, over time, from a fitting solution into an obsolete burden. This is the fourth pattern: the absence of a renewal loop.

The renewal loop is the mechanism that makes a practice review itself, learn, and update continuously — what distinguishes a living system from a dead one. A dead system is delivered in a final state and left to age; a living system carries within it the ability to monitor its own performance, detect its own dysfunction, and adjust in response to change. Without this loop, every practice begins losing its validity from the moment it is delivered, however well it was built.

The absence of a renewal loop produces an insidious failure: the practice that succeeded and then became an obstacle. The procedure that made sense three years ago now hampers the work because reality has overtaken it, yet it is followed out of inertia because this is how we have always done it. So the practice turns from a tool that serves the organization into a ritual the organization serves. The irony is that the most entrenched practices are the most exposed to this fate, because their very entrenchment makes reviewing them seem unnecessary.

A sustainable practice is measured not by its stability, but by its ability to evolve without losing its identity. The renewal loop is not a luxury added after stabilization, but an integral part of the design from the start: who reviews the practice, when, against what criteria, how it is updated, and who approves the change. A practice that does not answer these questions from its first day is designed — without knowing it — for obsolescence.

Pattern Five: Measurement That Ends When the Project Ends

During the project phase, everything is measured carefully: progress against plan, completion of deliverables, the percentage who attended training, stakeholder satisfaction. But this measurement is designed to serve the project — to answer the question did we deliver? — not the practice. So when the project closes, measurement closes with it, and the practice is left to operate in the dark, with no indicators to reveal whether it is still being practiced, practiced well, or making any impact.

This temporary measurement creates a dangerous illusion at closing. The project's indicators show resounding success: all deliverables handed over, everyone trained, stakeholders signed off. So success is declared and the budget is closed. But these indicators measure the completion of the project, not the vitality of the practice. Between the practice was delivered and the practice is being practiced lies a gap that project measurement cannot reveal, because it was not designed to endure beyond handover.

A sustainable practice needs a different kind of measurement: a permanent operational one that accompanies it throughout its life, not a momentary one that ends at closing. It does not measure whether the manual was delivered, but whether it is followed; not how many were trained, but whether behavior actually changed; not stakeholder satisfaction at launch, but the impact the practice produces month after month. This permanent measurement feeds the renewal loop and enables the owner to manage the practice by the numbers rather than by impression.

And when permanent measurement is absent, the early warning is absent with it. The practice deteriorates without anyone noticing, because no one measures its deterioration. Years may pass before the organization discovers that a practice it spent heavily to build has in fact been dead for some time, and that what remains is an empty ritual. A practice that is not measured continuously does not die suddenly; it dies without its death being recorded.

The Common Thread: We Ran the Practice as an Event, Not a Capability

The five failure patterns may seem separate: the post-go-live ownership vacuum, the absence of embedding in roles and systems, dependence on a single champion, the absence of a renewal loop, and measurement that ends with the project. But they are not five diseases; they are one symptom appearing in five guises. The common disease is a misclassification from the start: that we treat practice-building as a temporary project, when in truth it is the building of a permanent capability.

Consider how each pattern branches from this root. The ownership vacuum arises because the project hands over and departs, never designed to bequeath the practice to a permanent owner. The absence of embedding arises because the project produces outputs, not enduring transformations in roles and systems. Dependence on a champion arises because the project relies on whoever pushes it, not a system that makes the push unnecessary. The absence of renewal arises because the project seeks a final state to close, not a system that evolves without end. And measurement ends because project measurement serves closing, not continuation. The root is one: a project mindset applied to what is, by nature, a capability.

This radically changes the treatment. Instead of treating each symptom separately — appointing an owner, improving embedding, reducing dependence on the champion — we realize that genuine treatment begins with reclassification: we stop running practice-building as a project with a closing date, and start running it as the building of a capability designed to endure. Treat the root, and the five symptoms recede together.

This does not mean the project has no role. Building a practice may well begin with a project that has a beginning and an end — but a project whose mission is not to hand over documents, but to establish a system that continues after its own closing. The distinction is subtle but decisive: the wrong project asks what do we deliver before we close?, and the right one asks what must we leave behind so that it stays alive without us? The first measures success by the handover; the second by what endures after the departure.

What Building a Sustainable Practice Requires

If the original error is running a practice as a temporary event, the cure is to build it from the start as a system designed to endure. This is the purpose for which RAISO developed the Practice+™ concept and the Practice Builder™ model: an approach that does not stop at launching the practice, but builds it to take root as an organizational capability that outlives any project or person. The core idea is that a practice is not complete when its outputs are handed over, but when it becomes capable of continuing and renewing itself without the people who built it.

The purpose of this model is not to produce a larger bundle of outputs, but to convert the practice from something handed over into a capability that is established. It addresses, by design rather than by chance, every failure point that kills practices: establishing permanent ownership before the project team departs, embedding the practice in roles and systems instead of leaving it hovering above them, converting champion dependency into an institutionalized system, building a renewal loop that makes the practice learn and evolve, and laying down permanent measurement that accompanies it after handover. The single unifying goal: that the practice stay alive after the project closes, the consultant leaves, and the champion moves on.

This approach rests on principles that any serious organization can adopt regardless of the named model:

When a practice is built on this foundation, the five failure patterns turn on their heads. There is no longer an ownership vacuum, because the permanent owner took over before the team left. No practice hovering above the work, because it was embedded in roles and systems. No fragile dependence on a champion, because the system has made them unnecessary. No silent obsolescence, because the renewal loop keeps the practice current. And no unrecorded death, because permanent measurement reveals any deterioration early. The practice is no longer an event that ended, but a capability that lives.

“A successful practice is not the one whose handover was celebrated, but the one still being practiced and improved after everyone has forgotten it was ever a project.”

Sustainability Is a Condition for Vision 2030 Capabilities

Within the broad institutional capability-building 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 practice-building: in operational excellence, customer experience, risk management, governance, sustainability, and digital transformation. This momentum is a blessing if matched by an ability to entrench what is built, and a source of enormous waste if the practices are built with a project mindset and die when it ends. The scale of investment makes the price of dead practices higher than at any time before.

The real difference between organizations will not lie in the number of initiatives they launch, but in the number of practices they manage to keep alive. An organization that launches ten initiatives, nine of which die when their projects end, is poorer in capability than one that launched three and entrenched them all. Capability-building is measured not by what is launched, but by what endures. The mature organization understands that closing the project is not the end of the work, but the beginning of the real test.

Perhaps the hardest thing about this argument is that it asks leadership to defer the moment of celebration. The natural inclination is to celebrate closing the project and handing over its outputs, because that is a tangible, presentable moment. But a sustainable practice demands a different patience: to celebrate not the handover but the endurance; to measure success not by what we accomplished at closing, but by what stayed alive years after the departure of those who built it. This shift in the definition of success — from delivery to continuation — is the essence of maturity in capability-building.

Organizations fail to build practices when they run them as projects that end on schedule. They succeed when they grasp them for what they are: sustainable systems built to live and renew themselves. A practice is not what we hand over and then leave, but what we leave behind capable of continuing without us. From here, the most important question in any practice-building initiative is not when do we finish?, but what will stay alive after we finish?; whoever dares to ask it from the start builds practices that last, while whoever defers it until after the closing discovers that they never built a practice at all, but only a project that ended.