When You Are the Process: How to Tell the Difference Between a Capable Process and a Capable Person
One of the easiest ways to overestimate a process is to look only at the outcome. - 10 mins read

By Stefani Markov
Authors

Stefani Markov
Lean Six Sigma Black Belt, PMP, and MOS: Expert(Microsoft)
Founder & CEO

Orlin Markov
Lean Six Sigma Black Belt, PMP
8/11/26, 7:30 AM
I've noticed that one of the easiest ways to overestimate a process is to look only at the outcome.
If the customer is happy, deadlines are being met and the monthly KPIs are comfortably green, it's tempting to conclude that the process must be working well. In practice, those results can be achieved in very different ways.
One process reaches them because the design is robust, the controls make sense and people can follow the work without constantly improvising.
Another reaches exactly the same outcome because somebody quietly corrects the report before it goes out, remembers the exception the procedure forgot to mention, maintains the spreadsheet that was meant to be temporary and knows which system warning can safely be ignored because "it always does that."
From the dashboard, both processes look equally successful, which is exactly why the more interesting question - where the capability actually resides - never gets asked.
That's the distinction the Process Dependency Matrix in the full article is trying to pin down - process performance plotted against dependency on individuals, because the two don't always move together.
The matrix has nothing to do with statistical process capability in the Lean Six Sigma sense - it's a more modest tool for asking whether operational capability actually lives in the process, or in the people quietly propping it up.
The quadrant I find most interesting is the one where performance is high and dependency on people is equally high. It rarely attracts much attention because everything appears to be working, yet it often represents one of the biggest operational risks. What's improved isn't the process but the people's ability to compensate for it, which is a harder thing to notice and a much harder thing to lose.
Temporary workarounds have a habit of settling in. Given enough time, they acquire documentation, an owner and, in some cases, several versions of the same spreadsheet. Eventually they stop feeling temporary altogether. That's usually the point where it's worth asking whether you're looking at a capable process or a capable person.
The full article explores this idea through examples from the Toyota Production System, the Challenger investigation and lessons from ERP implementations, together with a practical framework that process managers can use to identify hidden dependencies before they become visible the hard way.
#ProcessManagement #BusinessProcessManagement #OperationalExcellence #ContinuousImprovement #ProcessImprovement
One of the more challenging aspects of process management is deciding whether a process is genuinely capable or simply appears that way because of the people performing it.
At first glance, the distinction doesn't seem particularly important. If customers receive what they need, deadlines are met and operational metrics remain healthy, it is tempting to conclude that the process is working as intended. After all, process performance is usually judged by outcomes, and outcomes are often what organisations pay the most attention to.
The difficulty is that outcomes tell us very little about the effort required to achieve them. Two organisations may report almost identical levels of performance while relying on entirely different operating models. In one, the process consistently delivers the expected result because it has been designed, understood and improved over time. In the other, the same result is achieved because experienced employees recognise process weaknesses and quietly compensate for them before they become visible to anyone else.
From a dashboard, these organisations can look remarkably similar. From a process management perspective, however, they represent very different levels of maturity.
Capable people can make almost any process appear healthier than it really is. Experience allows them to recognise situations that documentation never anticipated, identify errors before they reach customers and navigate system limitations that less experienced colleagues would struggle with. None of this is inherently problematic. Judgement and expertise are valuable parts of any organisation, and no well-designed process should attempt to eliminate them.
The challenge begins when these individual interventions become a permanent part of how the process operates. A manual correction becomes a monthly activity. An exception remains undocumented because one person remembers how it should be handled. A spreadsheet originally created as a temporary workaround quietly celebrates its fifth birthday. Over time, capability begins to shift away from the process itself and into the experience of the people performing it.
The organisation continues to achieve the expected outcomes, which makes this dependency surprisingly difficult to detect.
The difficulty is that performance and resilience are not the same thing. A process may perform exceptionally well while remaining surprisingly fragile because too much of its capability resides with a handful of experienced individuals.
Looking beyond performance
Traditional process measures remain important. Cycle times, error rates, customer satisfaction and compliance all tell us whether a process is delivering the expected outcome. What they rarely tell us is where the capability responsible for those outcomes actually resides.
One way of thinking about this is to consider two dimensions simultaneously: process performance and dependency on individuals.
Process Dependency Matrix

Most organisations naturally aspire to the Robust Process quadrant, where high performance is achieved because the process itself is reliable, repeatable and well understood. Experienced employees remain essential, but they spend their time improving the process rather than compensating for weaknesses in it.
The Design Issue quadrant represents a different challenge. Here, poor performance is largely explained by shortcomings in the process itself. Although frustrating, these situations are often easier to improve because the underlying problems are visible and can be analysed systematically.
An Operational Crisis is easier still to recognise. Performance is poor, and the organisation relies heavily on a small number of experienced individuals simply to keep work moving. Most effort is directed towards firefighting, leaving little capacity to improve the process.
The quadrant that deserves the most attention, however, is Hidden Dependency.
Processes in this quadrant often appear healthy. Targets are achieved, customers remain satisfied and operational reports provide little reason for concern. The difference is that much of this performance is created by experienced employees who continually compensate for weaknesses that the process has never addressed. Their interventions rarely appear in documentation because they have gradually become part of everyday work.
This is often where a process manager can add the greatest value. The objective is not simply to improve performance, but to determine whether the capability belongs to the process or to the people holding it together.
Testing where the capability really lives
Hidden dependency is rarely discovered by reviewing process documentation or operational dashboards. In fact, some organisations often have excellent documentation describing how work is supposed to happen while the real process has gradually evolved somewhere else.
Instead, identifying dependency usually requires asking a different set of questions. Not questions about performance, but about resilience.
Consider the following:
Could somebody with normal training perform this activity successfully, or does it rely on years of accumulated experience?
What happens when the most experienced person takes two weeks of annual leave? Does work continue largely as expected, or does the team begin collecting questions for their return?
Which manual checks exist because the process requires them, and which exist because somebody no longer trusts the process to produce the correct outcome?
How many spreadsheets, personal trackers or unofficial documents would disappear if the process worked exactly as designed?
When something unusual happens, do people reach for the documented process or for a particular colleague?
None of these questions suggest that experienced employees are a problem. Quite the opposite. The answers often reveal where the organisation has quietly accumulated valuable operational knowledge without ever converting it into organisational capability.
That distinction matters because a process that depends on expertise is not necessarily an immature process. A process that depends on expertise remaining with the same individuals indefinitely is.
How capability quietly migrates
These dependencies rarely emerge because somebody consciously decides to build them.
They usually develop through a series of entirely sensible operational decisions, made independently by different people at different times, none of whom are in a position to see the pattern forming. Viewed individually, none of these decisions are particularly concerning. Each solves a genuine operational problem and allows work to continue. Taken together, however, they gradually move capability away from the process and into the people who have learned how to compensate for its shortcomings.
By the time the organisation notices, the process still appears successful, which is precisely the problem - the capability hasn't disappeared, it has simply migrated somewhere else, usually into someone's head or someone's spreadsheet. The organisation often celebrates the outcome without noticing that its operational resilience has quietly declined.
Learning from organisations that faced the same challenge
The distinction between process capability and individual capability is not unique to process management. It appears repeatedly in organisations that have either succeeded or struggled to turn expertise into organisational capability.
Toyota: making improvements part of the process
One of the reasons the Toyota Production System continues to influence operational excellence decades after its introduction is that it deliberately prevents improvements from remaining with individuals.
When employees identify a better way of performing a task, the expectation is not simply that they continue using it themselves. The improvement is analysed, standardised where appropriate and incorporated into the standard way of working so that everyone benefits from it. Capability moves from the individual into the process.
This does not diminish the importance of expertise. On the contrary, Toyota relies heavily on experienced employees to identify waste, solve problems and improve operations. The difference is that expertise is expected to strengthen the process rather than become a permanent substitute for it.
For process managers, the lesson is straightforward. The objective is not simply to document what experienced employees know. It is to create mechanisms that continually transform individual learning into organisational capability.
Challenger: when expertise never reaches the process
The Space Shuttle Challenger disaster is frequently described as an engineering failure, yet the Rogers Commission reached a more nuanced conclusion.
Engineers had raised concerns about the performance of the shuttle's O-rings in low temperatures before launch. The technical expertise already existed within the organisation. The problem was that this knowledge was not consistently translated into operational decision-making. Weaknesses in communication, governance and decision processes prevented known risks from influencing the final outcome.
Few organisations will ever experience consequences on that scale, but the underlying pattern is surprisingly familiar. Valuable knowledge exists, experienced people understand the risks and informal conversations take place, yet the organisation lacks reliable mechanisms for embedding that knowledge into how work is performed or decisions are made.
The lesson extends well beyond engineering. Organisational capability increases not because knowledgeable people exist, but because their knowledge becomes part of the organisation rather than remaining dependent on the individuals who possess it.
ERP implementations: when the system changes but the process doesn't
Many ERP programmes promise standardisation, automation and consistent ways of working. Yet post-implementation reviews often uncover a different reality. The system may have been implemented successfully, while the process continues to rely on spreadsheets, manual reconciliations and experienced employees who know how to navigate the gaps between the designed process and operational reality.
The result is an organisation that appears standardised because everyone uses the same system, while much of the real capability still resides in personal workarounds and undocumented knowledge. Reports continue to require manual adjustments, exceptions remain dependent on individual judgement and shadow processes ensure that operations continue running, largely off the books.
The organisation may appear highly standardised until a key individual leaves, at which point it discovers that much of its operational resilience was being provided by people rather than by the process itself.
For process managers, this is an important reminder that system capability and process capability are not the same thing. A successful implementation should reduce dependency on individual intervention, not simply teach experienced employees new ways to compensate for it.
The real objective of process management
This is perhaps where process management is most often misunderstood.
The objective was never to eliminate expertise or make experienced employees interchangeable, valuable as that fantasy might be to certain finance directors—organisations benefit enormously from people who understand complexity, exercise sound judgement and recognise opportunities for improvement, capabilities that are impossible to capture entirely in documentation. It was, instead, to ensure that expertise continuously improves the process instead of quietly replacing it.
Addressing hidden dependencies is rarely just a technical challenge; it is equally a psychological one. In many organisations, being the indispensable problem-solver, the operational hero who steps in to save the day, comes with immediate visibility and social rewards. Firefighting feels valuable. Standardisation, by contrast, can feel to an expert like a step toward commoditisation, as if capturing their tacit knowledge makes them redundant.
This is why the transition requires a shift in framing: moving capability into the process is not about replacing the expert, but elevating them.
When an organisation creates mechanisms to absorb individual learning into standard ways of working, experts are freed from the exhausting cycle of operational maintenance. They move from being Firefighters, endlessly rescuing a fragile workflow, to Architects, designing resilient systems that enable everyone else to perform at a higher standard.

When experienced employees spend their time repeatedly correcting the same reports, handling the same undocumented exceptions or maintaining the same temporary workarounds year after year, the organisation has an opportunity to learn. Those activities are evidence of capability, but they are also evidence that the capability has not yet become part of the process.
Perhaps that is the simplest test of process maturity: the ratio of time experts spend rescuing the process against the time they spend improving it, and whether the organisation rewards them for keeping a broken machinery running, or for building a system that no longer needs saving.
Ready? Let's talk.
Related Consulting Serivces
How We Can Help