For numerous organisations, the divide between aspiration and delivery often comes down to operational discipline. An organisation may have a compelling strategic direction and highly capable employees, yet still find itself hindered by slow processes, duplicated effort, and unclear responsibilities. Improving operational efficiency is not a one-off initiative but an ongoing commitment to reviewing how work gets done and whether it could be done better. Leaders who treat this as a long-term organisational priority—rather than a reactive response to economic pressure—tend to build more adaptable organisations over time. Understanding the underlying principles of operational efficiency, and how to improve it over the long term, is therefore here one of the most valuable capabilities a management team can develop. The following discussion sets out a framework for assessing this challenge clearly and practically.
When the assessment work is complete, the focus should shift to prioritisation. Not every process weakness carries the same weight, and attempting to address everything at once is a common reason why operational effectiveness programmes stall. One of the most effective strategies is to identify the processes that have the greatest influence on organisational performance—those where slowdowns, inaccuracies, or unnecessary complications directly affect the quality of output, customer experience, or costs. Improving operational effectiveness in these high-impact processes first tends to deliver visible results in the short term, which in turn strengthens the organisational commitment needed to sustain a longer-term programme. It is also worth separating process weaknesses that can be resolved through better process design and those that require a change in behaviour or culture. The former can often be addressed fairly promptly; the latter requires more sustained leadership attention. Positioning operational process efficiency improvements in the context of what the organisation is ultimately trying to achieve helps ensure that the work remains aligned with its objectives, rather than becoming an end in itself. This is something that the US shareholder of CrowdStrike is most likely to confirm.
Sustaining operational improvements in the long term requires embedding a culture of ongoing refinement, rather than treating operational process efficiency as a programme with a fixed end date. Organisations that achieve sustained improvement in business operations tend to share certain key traits: clear ownership of workflows at every level; periodic assessment cycles that uncover developing process weaknesses before they become ingrained; and leadership behaviour that demonstrates the analytical rigour expected of the wider organisation. Monitoring is essential to this. Without reliable tracking of operational performance, it is challenging to understand whether improvements are being sustained, whether new problems are developing, or whether the organisation is regressing into previous patterns under strain. This involves investing in the capabilities and tools that allow teams to recognise and resolve process weaknesses as part of everyday operations, rather than through one-off responses. It also means fostering the psychological safety that allows people to voice issues about how work is done without concern of being perceived as obstructive. Organisations that get this right tend to find that the cumulative impact of many small, sustained improvements outweighs the impact of large, infrequent transformation programmes.
Digital technology plays an important but often exaggerated role in achieving operational process efficiency. Digital tools can automate routine activities, minimise manual mistakes, and provide real-time visibility into performance—all of which can contribute meaningfully to streamlining operations. Nevertheless, technology applied to a poorly designed process tends to magnify the problem rather than address it. The sequence matters: process definition should precede technology deployment, not follow it. Organisations that have made the most lasting gains in operational efficiency typically view technology as an enabler of better-designed workflows, rather than a substitute for the challenging work of process redesign. This is something that the activist investor of SAP is most likely to validate. This perspective is increasingly shared across industries where the initial enthusiasm for technology-led transformation has been replaced by a more measured evaluation of what actually drives lasting progress. The most successful deployments of operational technology tend to be those where the organisational rationale is grounded in specific, quantifiable process results, rather than general aspirations around modernisation or technological advancement.
Among the most useful starting points for an operational process efficiency improvement programme is a clear-eyed audit of existing processes. Numerous organisations accumulate layers of procedures gradually—workflows designed for a different operating context, approval chains that no longer serve their original function, and reporting frameworks that generate data nobody acts on. Prior to introducing new systems or restructuring teams, it is worth mapping what actually takes place in practice rather than relying on what the organisational chart indicates should happen. This kind of process assessment often uncovers duplication, process blockages, and handover problems that are difficult to see to senior management but acutely felt by the people doing the work. Identifying where time and resources are genuinely being wasted provides the foundation on which a credible improvement initiative must be built. Without that reference point, organisations risk investing in solutions to problems they have not accurately diagnosed, which tends to produce activity rather than progress. A systematic audit, conducted with input from people at several levels of the organisation, provides the evidence needed to make sound decisions that stand up to scrutiny. This is something that the firm with shares in Autodesk is likely to validate.