Abstract
To identify operational inefficiencies, I start by establishing what is producing the current state. That includes the decisions leaders make, what people actually do and how work moves between teams. Interviews, observation and Value Delivery Mapping expose gaps between individual perspectives and the complete process. RASCI establishes who is accountable and responsible for addressing them. Workarounds provide evidence of what the organisation cannot currently deliver through its agreed processes. Automation requires the same scrutiny because speeding up one activity can create a backlog elsewhere. Improvement depends on understanding these connections, agreeing ownership and measuring the outcome across the whole process.
Operational excellence; process improvement; process mapping; leadership accountability; RASCI
Start with the work and the evidence
To identify operational inefficiencies, I ask to see the processes, speak with the people doing the work and establish what the organisation is trying to achieve. I look at how work moves from one team to another, where it gets held up and what people have to do to keep it moving. I also examine the part leaders have played in creating the current state.
Work piling up, repeated corrections, duplicate entry, information chasing and customer complaints indicate where to investigate, but do not establish the cause. Where available, I examine order records, queues, exception logs, rework rates and handover times alongside direct observation, or ask colleagues responsible for those areas to investigate. When teams offer conflicting explanations, I trace individual examples through the process with them and test whether the proposed causes explain the broader pattern. This helps distinguish where a problem becomes visible from the conditions producing it.
That is abdication of leadership. Assigning somebody a task does not remove a leader’s accountability for the decisions, priorities and resources needed to complete it. If those arrangements are causing the problem, a process improvement exercise needs to expose them.
In their commercial consulting articles, Borges (2024) for Codence and Arthur (n.d.) for Trinity recommend gathering employee feedback and examining how work actually happens. Borges also recommends process audits and investigating causes. Those are useful starting points. My interviews also examine whether leaders understand what they have committed the organisation to deliver.
Compare leadership and employee perspectives
I always use a ten question questionnaire with a cross section of the leadership team, or all of them. I design the questions for the particular problem and organisation. Comparing the answers reveals different perspectives, agendas and gaps between the current state and the desired end state.
For a customer ordering portal, I asked what the initiative was, what each leader was accountable for and what they were responsible for. I asked about the benefits for their team, their understanding of the changes, the risks they had identified and whether their proposed solutions would meet the programme timeline. I also asked what success looked like for their group. Different answers to those questions tell you where further discussion is needed.
I do this extensively with employees too, through interviews and workshops. My military experience taught me to prioritise speaking directly with the people doing the work. I compare their position descriptions with their actual duties. What the job description says and what the person does can be completely different. Finding those gaps matters when assessing workload and responsibility.
Map the complete process with the people involved
In a previous role, I was brought into a stalled customer ordering portal initiative. There was no executive sponsor, insufficient commitment from senior leaders and no agreed success measures showing improved efficiency against the current state. The internal stakeholders affected by the portal and the subsequent business changes had not been properly consulted.
Although there was a team responsible for process mapping, I was told it would take years to produce something useful. Meanwhile, orders passed through several internal teams, but nobody had captured that complete journey.
I identified the teams involved and got them in a room together. We mapped the ordering process from the customer placing an order through to the delivery arriving. I ran a Value Delivery Mapping workshop, or VDM, so we could work backwards from the desired end state and understand what had to happen to achieve it.
People discovered processes and activities in other teams that they had no idea existed. Individual points of view and issues that had not been discussed could finally be brought into the open. We worked through the handovers, dependencies and problems together and agreed how to proceed.
By the end, one of the strongest opponents of the initiative said we should have done this at the start. People understood the complete ordering process and began actively collaborating to move it forward. We still needed to measure what changed in day to day delivery.
The Lean Enterprise Institute (n.d.) describes value stream mapping as examining material and information flows through a complete value stream, including current and future states. VDM is the approach I use to work backwards from the required outcome with the people involved, expose gaps and agree what needs to happen. They are distinct methods with a shared concern for the complete flow.
In a study of care after surgery in nine hospitals, Gittell (2002) found that strong working relationships between service providers contributed to better coordination and customer satisfaction. That finding concerns hospital care; the VDM observations here come from my own practice.
Understand the gap a workaround is filling
A workaround can tell you a great deal. People are creatures of habit and may continue doing something because it is familiar or easier. They may also have found a way to deal with a gap in your processes, systems or architecture. You need to understand which it is before deciding what to change.
Arthur (n.d.) identifies workarounds as a sign that processes have drifted from how the business operates. I want to know exactly what gap the workaround is plugging. A spreadsheet or manual check might be the only thing keeping an order moving. Removing it without addressing that gap will make things worse.
If technology is being introduced to improve the current state, it needs to do the job that workaround is doing. Include that in the success measures. If people still need the workaround afterwards, the project has failed to resolve the gap. If the new process removes the need but people continue using it out of habit, investigate their understanding and adoption of the change.
Clarify accountability with RASCI
RASCI is the mother document for an organisation in my approach. Done properly, it makes clear who is Responsible, Accountable, Support, Consulted and Informed for each key activity.
The rows are the organisation’s key activities, often grouped by accountable executive. Technology activities, for example, sit in a section under the executive accountable for technology. The columns are the key roles, from the CEO and other executives through to functional leads and stakeholders who affect how the organisation runs.
Responsible identifies who does the work. Accountable identifies who answers for the outcome. We work through those assignments together, including who provides support and who must be consulted or informed. APQC (2025) identifies roles, accountability, sponsorship and oversight as elements of process governance.
The discussion matters as much as the document. Leaders need to understand what they retain when they delegate and what other teams need from them. I keep RASCI on the weekly leadership agenda so that disputed ownership and unresolved decisions are dealt with as part of running the organisation.
Assess automation across the complete process
Borges (2024) recommends automating repetitive tasks. Before choosing automation, I want to see the baseline for the complete process and understand where it requires human intervention.
In a previous technology services role, the processes identified for automation were, in the main, parts of larger processes that eventually required manual handling. I said that speeding up those parts could create a larger backlog for the people handling the work later.
If more work arrives than they can process, the queue grows. You may have made one activity faster while making the customer wait longer. Assess the volume arriving, the capacity available and the exceptions people must resolve. Measure how long work takes from start to finish, where it waits, how often it needs correcting and what the customer receives. Use actual records and observation to establish the baseline before making changes.
Examine decisions, priorities and outcomes
I also use OODA, Observe, Orient, Decide and Act (Wright, 2010), to examine how leaders make decisions. Are they gathering facts, understanding what those facts mean and acting on them? Do they examine the result before deciding what to do next? That helps expose decisions driven by the opinion of the most senior person in the room.
Prioritisation comes directly from the VDM. With the relevant people together, we can see the gaps, the dependencies and what is needed to reach the desired end state. We establish which actions must happen first, who owns them and when they need to be completed. The people who depend on those actions are part of the discussion, so there is nowhere to hide from ownership.
I turn that into a programme plan with names against tasks, timelines, interdependencies and success measures. I manage it weekly. In the situations I am describing, expecting people to resolve competing priorities and motivate themselves has not been enough. They need objective leadership that follows through and brings blocked decisions back to those accountable for making them.
Success measures must show whether the original problem has been resolved. Are the workarounds still necessary? Has the backlog moved to another team? Is the customer receiving the required service? Compare those results with the baseline, including quality and service requirements.
Leaders need to be prepared to examine their own contribution to the current state. Until they understand the work and accept their accountabilities, they can keep causing the very problems they are asking others to fix.
References
APQC. (2025, 6 June). What Is Process Governance?
Borges, D. (2024, 2 December). 13 Steps to Spot and Fix Operational Inefficiencies. Codence.
Lean Enterprise Institute. (n.d.). Value Stream Mapping. Accessed 3 November 2026.
Wright, K. (2010, 24 August). OODA Loop makes its mark on Maxwell. Air University.
Publication and disclosure notes
Scott Howe provides consulting services in the areas discussed. The examples describe previous professional experience and are anonymised. They are not presented as results delivered by Successium. Participant comments are paraphrased from his recollection. The workshop outcome describes observations during the session. The automation example describes a risk he identified. Neither example makes a quantified savings claim. ChatGPT by OpenAI assisted with research, drafting and editing using the experience and argument he supplied. Scott Howe retains responsibility for the final article.