The short answer
A business process assessment establishes how well a specific process performs, why it performs that way, and what should change.
That is three questions and most assessments answer only the first. Performance data is available: cycle time, volume, error rate, cost. Cause and disposition require evidence about how the work actually runs, which is not in any system.
The assessment below covers seven dimensions. Each one is scored, each requires a specific kind of evidence, and each weak result names a disposition rather than a maturity label.
Two rules make it useful. Assess one process, with defined boundaries, rather than a function. And require evidence for each score, since an assessment built from assumptions produces confident numbers with no basis.
Key takeaways
- Performance, cause and disposition are three separate questions, and most assessments answer one.
- The seven dimensions are: outcome, flow, ownership, systems, exceptions, controls and knowledge.
- Every score needs named evidence, otherwise the assessment records opinions.
- The exceptions dimension is the most predictive and the least often measured.
- Weak dimensions name a disposition: remove, integrate, standardize, automate, clarify or document.
- A process assessment that produces no disposition was a documentation exercise.
Before you start: define the boundary
Set explicit start and end points, and name the decision the assessment supports.
"Vendor onboarding" can mean supplier request through first payment, or only the compliance review. A boundary drawn too wide produces vague findings. Drawn too narrow, the upstream cause sits outside the frame and the assessment finds symptoms.
The decision matters because it determines the required depth. An assessment supporting a system replacement needs exception distributions and variant catalogues. One supporting a quarterly improvement cycle can work at a coarser level.
The seven dimensions
1. Outcome
Whether the process delivers what it exists to deliver.
| Score | Condition |
|---|---|
| 1 | No agreed outcome measure exists |
| 3 | Outcome measured, performance inconsistent or unexplained |
| 5 | Outcome measured, performance stable and understood |
Evidence required: the outcome metric with its current value and its variance over the last several cycles.
If weak: the disposition is measurement before anything else. Every subsequent dimension is harder to act on without a baseline.
2. Flow
Whether the sequence is known, including where work waits.
| Score | Condition |
|---|---|
| 1 | The documented flow does not match practice, or no documentation exists |
| 3 | Main flow known, variants and wait states unclear |
| 5 | Flow known including variants, with touch time and wait time separated |
Evidence required: the end-to-end sequence as described by people who run it, and the split between time spent working and time spent waiting.
If weak: the disposition is discovery with the people performing the work. The touch and wait split is the single most useful number this dimension produces, since it determines whether the constraint is capacity or queue structure.
3. Ownership
Whether responsibility is clear at each step and at each decision.
| Score | Condition |
|---|---|
| 1 | Ownership unclear, cases wait for someone to claim them |
| 3 | Steps owned, cross-functional decisions ambiguous |
| 5 | Every step and decision has a named owner who acts on it |
Evidence required: for each decision point, who actually decides, as distinct from who is named.
If weak: the disposition is assigning decision rights. This frequently reduces cycle time without changing anything else, since a substantial share of wait time is cases waiting for an unclear owner.
4. Systems
Whether the systems support the process or the people compensate for them.
| Score | Condition |
|---|---|
| 1 | Critical state held outside systems, in spreadsheets or personal trackers |
| 3 | Systems hold state, manual bridging between them |
| 5 | Systems hold state and exchange it without manual intervention |
Evidence required: a list of every artifact maintained outside the systems of record, and the hours each consumes.
If weak: the disposition is integration or consolidation. This dimension produces the clearest recoverable hours in most assessments.
5. Exceptions
Whether the variation in the process is known and quantified.
| Score | Condition |
|---|---|
| 1 | Exception rate unknown |
| 3 | Exception types known, frequencies estimated |
| 5 | Exception types and frequencies known, with handling defined for each |
Evidence required: what proportion of volume follows the standard path, and the distribution of what does not.
If weak: the disposition is discovery targeted at exception handlers. This is the most predictive dimension in the assessment and the one most often skipped, because the number is uncomfortable and nobody is asked for it.
6. Controls
Whether each control still reduces a real risk.
| Score | Condition |
|---|---|
| 1 | Controls exist with no recorded rationale |
| 3 | Rationale known, currency not verified |
| 5 | Each control traced to a current requirement with a named owner |
Evidence required: for each check, approval or validation, why it exists and whether the reason still holds.
If weak: the disposition is a control review. Assessments routinely find controls added after incidents that were resolved years earlier, retained because nobody had authority to remove them.
7. Knowledge
Whether the process can run without specific individuals.
| Score | Condition |
|---|---|
| 1 | Critical knowledge exists only with a few people |
| 3 | Documentation exists and is partly out of date |
| 5 | A capable new person could run the process from documentation |
Evidence required: identify whose absence would materially slow the process, and test whether the documentation covers what they know.
If weak: the disposition is documentation generated from practice rather than from intent, since documentation written from the intended process reproduces the gap.
Assessment reading
Each weak dimension names one disposition
| Dimension | If weak | Disposition |
|---|---|---|
| Outcome | No baseline exists | Measure before changing anything |
| Flow | Practice diverges from documentation | Discovery with the people performing the work |
| Ownership | Cases wait for an unclear owner | Assign decision rights |
| Systems | State held outside systems | Integrate or consolidate |
| Exceptions | Rate unknown | Targeted discovery with exception handlers |
| Controls | Rationale unverified | Control review, remove what no longer applies |
| Knowledge | Held by individuals | Generate documentation from practice |
The lowest score governs the next action. Averaging the seven produces a number that hides the constraint.
Turning the result into a plan
The output of the assessment is a disposition per weak dimension, sequenced.
Measurement comes first when the outcome dimension is weak, since nothing downstream can be verified without it. Discovery comes next when flow or exceptions are weak, because the remaining dispositions depend on knowing what the process actually does. Integration, control review, decision rights and documentation follow, and can frequently run in parallel.
Each disposition needs an owner, an expected effect and a review date. An assessment that ends with a scored table and no owners has produced a document.
The evidence requirement
Worth stating plainly because it is the difference between an assessment and an opinion survey.
Every score needs named evidence. Not "we think the exception rate is about 20%" but a number with a source: a sample of cases, a count from the queue, or a consistent account from the people handling them.
Where evidence does not exist, record the score as unknown rather than estimating. An unknown is an actionable finding. An estimate presented as a score is a number that will be cited later by someone who does not know it was a guess.
Where Horizon fits
Horizon is an AI-powered continuous discovery platform. It produces the evidence that dimensions 2 through 7 require, which is the part of a process assessment that cannot be derived from system data.
Discovery Cycles run AI-led interviews across the roles that operate the process, adapting to each role and following up on why a step exists rather than only recording that it does. The Insights Dashboard ranks findings by impact and effort with traceability to the input behind each one, which is what makes the evidence requirement satisfiable. The Process Library structures the result into documentation generated from practice, which addresses dimension 7 directly, and the Initiatives Dashboard converts dispositions into business cases with owners.
AFAP SURA, a pension fund administrator in Uruguay with 600 employees and part of the regional SURA group, ran exactly this kind of assessment on two processes.
The ANR process, covering international transfers for members living abroad, and the BPC workflows had required weeks of manual interviews reaching only a small portion of the team. Information was scattered across five systems. The team had to request status updates continuously to understand where each case stood, which is a dimension 4 failure. An error in an international transfer could produce a financial loss that is difficult to recover, which is a dimension 6 condition.
In under seven days Horizon delivered 63 prioritized insights covering bottlenecks, repetitive tasks and operational risk points, with a complete view integrating all five systems and evidence-based recommendations to improve traceability, reduce risk and accelerate processing times. The comparison against the manual approach was three weeks against seven days, and the pilot returned 186% ROI.
The composition of those findings maps onto the dimensions above. Bottlenecks are a flow finding. Repetitive tasks are a systems finding. Operational risk points are a controls finding. Separating them is what turned the assessment into a set of dispositions rather than a list of complaints.
That is one engagement under specific conditions rather than a projection for any organization.
Assessment template
Copy this table and complete it for one process.
| Field | Entry |
|---|---|
| Process name | |
| Boundary: starts at | |
| Boundary: ends at | |
| Decision this assessment supports | |
| Outcome metric and current value | |
| Score: Outcome | |
| Touch time / wait time split | |
| Score: Flow | |
| Decisions without a clear owner | |
| Score: Ownership | |
| Artifacts maintained outside systems | |
| Score: Systems | |
| Proportion of volume on standard path | |
| Score: Exceptions | |
| Controls without verified rationale | |
| Score: Controls | |
| Knowledge held by individuals | |
| Score: Knowledge | |
| Lowest dimension | |
| First disposition and owner | |
| Review date |
FAQ
What is a business process assessment?
A structured evaluation of how well a specific process performs, why it performs that way, and what should change. It covers outcome, flow, ownership, systems, exceptions, controls and knowledge, and produces a disposition per weak dimension rather than a maturity score.
How do you assess a business process?
Define the boundary and the decision the assessment supports, then score seven dimensions with named evidence for each. Where evidence does not exist, record the score as unknown rather than estimating. The lowest dimension governs the next action.
What is the difference between a process assessment and a process audit?
An audit checks compliance against a defined standard and produces findings of conformance or deviation. An assessment evaluates performance and cause to decide what should change. An audit asks whether the process was followed. An assessment asks whether the process is the right one.
Which dimension matters most in a process assessment?
Exceptions, in practice. The proportion of volume that does not follow the standard path determines how much of every other finding applies to the real operation, and it is the dimension most often unmeasured. An assessment that scores six dimensions confidently and leaves this one unknown has assessed the documented process.
Should you average the dimension scores?
No. Averaging hides the constraint. A process scoring well on six dimensions and poorly on systems will not improve until the systems dimension is addressed, and the average suggests moderate health. Use the lowest score to determine the next action.
How often should a process be reassessed?
After any disposition is implemented, to verify the expected effect, and whenever the process, its systems or its regulatory context changes materially. Fixed-calendar reassessment without a trigger tends to reproduce the previous result.
An assessment that names no action was a description
Most process assessments produce a scored table, a set of observations and a slide. The scoring is usually reasonable and the observations are usually correct.
What determines whether it was worth running is whether each weak dimension left the room with a disposition, an owner and a date.
See it. Fix it. Own it.