Skip to content
Articles

Why 30 to 50% of Consulting Recommendations Are Never Operationalised

Industry data shows 30–50% of consulting recommendations are never fully implemented. The root cause is not the quality of the advice but the absence of enforcement infrastructure to make governance permanent.

April 2026 · Estimated reading time: 5 minutes
Industry
Enterprise Governance
Services
Advisory & Transformation

The Recommendation Graveyard

The consulting industry generates excellent governance recommendations. Frameworks are designed with rigour. Gap assessments are thorough. Roadmaps are detailed. Presentation decks are polished.

And then the engagement ends.

Industry data consistently suggests that 30 to 50 percent of consulting recommendations are never fully operationalised. Not because the recommendations were wrong. Not because the client disagreed. But because the machinery to convert recommendations into permanent operational governance does not exist.

The recommendations become a document. Implementation depends on the client team’s capacity, competing priorities, institutional memory and, critically, the availability of infrastructure to make governance permanent.

The Decay Pattern

Consulting recommendations follow a predictable decay pattern. In the first three months after an engagement, momentum is high. The project sponsor is engaged. The team remembers the workshops. Quick wins are implemented. The framework feels alive.

By month six, attention has shifted. New priorities have emerged. The project sponsor has moved to a different initiative. The team has partially turned over. Implementation stalls on the items that require cross-functional coordination, system changes or sustained effort.

By month twelve, the recommendations document is in a shared drive, rarely opened. The framework that was designed to transform governance has become another artefact of good intentions that did not survive contact with operational reality.

This is not a criticism of consulting. It is a recognition that recommendations, however brilliant, are inherently temporary unless they are embedded in infrastructure that runs regardless of who is paying attention.

Why Recommendations Fail to Stick

Capacity constraints

Client teams have day jobs. Implementing governance recommendations is additional work layered onto existing responsibilities. When deadlines compete, the urgent displaces the important. The governance improvement that would prevent next year’s audit finding loses to the operational crisis that needs attention today.

Knowledge dependency

Recommendations are often understood deeply by a small number of people: the project team who participated in the workshops, the sponsor who commissioned the engagement, the senior leaders who attended the presentation. When any of these people move roles, the institutional knowledge required to implement and maintain the recommendations depletes.

System limitations

Many governance recommendations require enforcement inside operational systems. “Implement a five-dimensional delegation of authority” is a recommendation. Making SAP, Oracle and three other systems enforce all five dimensions on every transaction is an engineering challenge that may require infrastructure the enterprise does not have.

No enforcement mechanism

A recommendation to “strengthen vendor governance” is actionable in principle. But without infrastructure to continuously monitor vendor compliance, track obligations, hold purchase orders against non-compliant vendors and score risk from operational data, the recommendation remains a process improvement rather than an operational reality.

The Infrastructure Solution

The gap between recommendation and operational reality is an infrastructure gap. Governance recommendations become permanent when they are converted into executable controls enforced by systems rather than people.

Consider the transformation. A consulting engagement recommends strengthening delegation of authority enforcement. Without infrastructure, this means updating policy documents, training approvers, and hoping compliance improves. With enforcement infrastructure, the delegation matrix becomes a set of rules evaluated on every approval across every connected system. The recommendation is not just implemented. It is infrastructure. It runs on every transaction. It generates evidence. It cannot be forgotten, circumvented or eroded by staff turnover.

The same applies to every category of governance recommendation. Vendor governance becomes continuous monitoring infrastructure. Contract obligation tracking becomes automated extraction and SLA management. Regulatory filing compliance becomes governed workflows with evidence collection. Risk framework improvements become dynamic scoring from operational data.

The consulting engagement designs the framework. The enforcement infrastructure makes it permanent. The value of the engagement compounds over time rather than decaying with attention.

A New Model for Consulting Engagements

The most sophisticated consulting firms are recognising this dynamic. Rather than delivering recommendations and hoping for implementation, leading engagements are designed with enforcement infrastructure as the delivery vehicle.

The engagement does not end with a document. It ends with governance rules live in production, enforcing on real transactions, generating evidence continuously. The framework is not a recommendation. It is operational infrastructure.

This model changes the economics of consulting for both parties. The client gets permanent governance improvement rather than a transient recommendation. The firm gets demonstrable impact rather than a report that may or may not be implemented. The engagement’s value is measurable, provable and durable.

The Compounding Effect

When consulting recommendations are embedded in enforcement infrastructure, something remarkable happens: they compound. The governance framework that was designed in a workshop becomes a living system that improves with every transaction. It identifies patterns. It spots ineffective rules. It recommends adjustments.

The consulting framework becomes smarter over time. Rules are refined based on real operational data. Thresholds are optimised based on exception patterns. New risks are detected before they materialise. The value of the original engagement increases rather than decreases.

This is the difference between a recommendation and infrastructure. Recommendations decay. Infrastructure compounds.

Ready?

Let's build your connected enterprise

Share your priorities and we'll show you how Jalubro can unify your operations.

Book a discovery call →