One of the assumptions I have gradually become less convinced of is that organizations should be assessed primarily through their processes. This assumption is deeply embedded in many maturity models. Whether we look at software testing, quality assurance, data management, or other organizational disciplines, the assessment often revolves around questions such as:
- Are processes documented?
- Are they followed consistently?
- Are they measured?
- Are they continuously improved?
The underlying logic is straightforward: Better processes lead to better outcomes.
For a long time, I accepted this logic without much reflection. After all, processes are visible, assessable, and relatively easy to compare across organizations.
Yet experience has repeatedly shown something different. Some organizations score highly against process-oriented models while struggling to deliver meaningful results. At the same time, other organizations operate with surprisingly lightweight processes and consistently outperform their peers.
This raises an uncomfortable question:
What exactly are we assessing?
From Processes to Capabilities
Over time, I have found it more useful to think in terms of capabilities rather than processes. A capability describes what an organization is able to do.
Examples include:
- Managing quality risks
- Designing effective test strategies
- Detecting data quality issues
- Learning from production incidents
- Making informed release decisions
These capabilities exist independently of any particular process.
Organizations can realize the same capability in very different ways. One organization may rely on formal governance structures, documented procedures, and predefined workflows. Another may achieve similar outcomes through strong collaboration, experienced practitioners, and adaptive working methods.
The capability is the same. The implementation differs.
Capabilities and Practices
This distinction becomes clearer when separating capabilities from practices.
A capability describes an outcome-oriented ability.
A practice describes one way of realizing that ability.
For example, an organization may have the capability to manage quality risks effectively. The practices used to support that capability could include:
- Risk workshops
- Risk matrices
- Exploratory testing charters
- Failure mode analysis
- Automated risk detection
- AI-assisted analysis
None of these practices are the capability itself. They are merely different ways of expressing it.
This distinction matters because practices evolve continuously. New techniques emerge, old techniques disappear, and fashionable methods come and go. The underlying capability, however, remains relevant.
The Limits of Process Assessments
Many traditional assessments unintentionally reward compliance rather than effectiveness.
Consider a common assessment question:
Is there a documented test strategy?
The existence of a document may provide evidence of organizational discipline. It does not demonstrate that the organization can make sound testing decisions.
Similarly:
- A retrospective does not prove learning.
- A dashboard does not prove insight.
- A governance process does not prove control.
- A strategy document does not prove strategic alignment.
These artifacts may indicate capability. They are not proof of capability.
The real question is whether the organization can consistently achieve the desired outcome.
What Should Be Assessed?
This leads to a different perspective on organizational assessments. Rather than asking whether predefined processes exist, we should ask whether the organization possesses the capabilities required to achieve its objectives.
Processes remain important. Practices remain important. Artifacts remain important. But they should be treated as evidence rather than objectives.
The purpose of an assessment is not to determine whether an organization resembles a reference process model.
The purpose is to understand what the organization is capable of achieving.
A Working Hypothesis
This leads me to a hypothesis that increasingly influences how I design assessments:
Organizations are more meaningfully assessed through their capabilities than through their compliance with predefined process models.
Processes are valuable. Practices are valuable. But they are ultimately means rather than ends. What matters is not whether an organization follows the prescribed path. What matters is whether it can reliably achieve the outcomes that the path was intended to support.
Leave a Reply