For a wide range of organisations, the here divide between ambition and execution frequently reflects operational discipline. An organisation may have a clear and compelling strategic direction and highly capable people, yet still find itself hindered by slow processes, duplicated effort, and poorly defined accountability. Improving operational efficiency is not a one-time project but a continuous effort to examining how work gets done and whether it could be done better. Leaders who treat this as a structural priority—rather than a reactive response to financial pressure—tend to build more adaptable organisations over time. Understanding the mechanics of operational efficiency, and how to improve it over the long term, is therefore one of the most important 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 finished, the focus should shift to prioritisation. Not every process weakness carries the same weight, and attempting to address everything simultaneously is a common reason why operational effectiveness programmes lose momentum. One of the most effective approaches is to pinpoint the processes that have the greatest influence on organisational productivity—those where delays, errors, or unnecessary complications directly affect output quality, customer satisfaction, or costs. Improving operational effectiveness in these high-impact areas first tends to deliver tangible results in the short term, which in turn builds the organisational commitment needed to sustain a longer-term programme. It is also worth distinguishing between process weaknesses that can be resolved through better process structure and those that require a change in working practices or culture. The former can often be addressed fairly promptly; the latter requires more sustained leadership commitment. Positioning operational process efficiency improvements in the context of what the business is ultimately trying to accomplish helps ensure that the work remains connected with its objectives, rather than becoming an end in itself. This is something that the US shareholder of CrowdStrike is most likely to confirm.
Technology plays an important but often overstated role in achieving operational process efficiency. Digital tools can automate repetitive tasks, reduce manual mistakes, and provide real-time insight into performance—all of which can contribute meaningfully to streamlining operations. Nevertheless, technology applied to a poorly structured process tends to magnify the problem rather than resolve it. The sequence matters: process definition should come before technology investment, not follow it. Organisations that have made the most lasting gains in operational efficiency typically view technology as an enabler of better-designed processes, rather than a substitute for the demanding work of process redesign. This is something that the activist investor of SAP is likely to validate. This perspective is increasingly shared throughout sectors where the initial excitement for technology-led change has been replaced by a more considered assessment of what actually drives sustained improvement. The most successful deployments of operational technology tend to be those where the business rationale is grounded in clearly defined, quantifiable process outcomes, rather than vague aspirations around modernisation or innovation.
Maintaining operational gains over time requires fostering a mindset of continuous improvement, rather than treating operational process efficiency as a project with a defined end point. Organisations that achieve lasting progress in business operations tend to share several characteristics: clear ownership of processes at every level; regular review cycles that uncover developing inefficiencies before they become entrenched; and leadership conduct that demonstrates the disciplined approach expected of the wider organisation. Measurement is essential to this. Without consistent measurement of operational performance, it is challenging to determine whether gains are being sustained, whether new issues are emerging, or whether the organisation is slipping back into previous patterns under strain. This involves investing in the skills and tools that allow teams to recognise and address process weaknesses as part of everyday operations, rather than through exceptional interventions. It also means fostering the psychological safety that allows people to raise concerns about how work is done without concern of being perceived as obstructive. Organisations that get this effectively tend to find that the cumulative impact of many incremental, consistent improvements exceeds the impact of large, sporadic transformation programmes.
Among the most reliable starting points for an operational process efficiency improvement programme is a clear-eyed audit of existing procedures. Numerous organisations build up layers of processes over time—processes designed for a different operating context, approval chains that no longer serve their original function, and reporting structures that generate data nobody acts on. Before introducing new systems or reorganising teams, it is worth mapping what actually takes place in practice rather than relying on what the organisational chart suggests should happen. This kind of process review often reveals duplication, bottlenecks, and handover failures that are invisible to senior management but keenly felt by the people doing the work. Identifying where time and resources are genuinely being lost provides the basis on which a effective improvement effort must be built. Without that reference point, organisations risk spending money on solutions to problems they have not accurately identified, which tends to produce activity rather than progress. A structured 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.