This case has been created solely to demonstrate the Operational Clarity analytical methodology. It does not represent a client engagement or an actual organisation.
An organisation had experienced a gradual increase in project delivery times over approximately nine months.
Individual departments reported that they were continuing to meet their own responsibilities and internal performance expectations. Despite this, a growing number of projects were completing later than originally planned.
Management wanted to understand what had changed.
This illustrative case demonstrates how Operational Clarity might approach that question through a Clarification Report.
The following information was available at the outset. It is recorded here as stated, without interpretation.
Average project completion times had increased during the previous nine months.
Individual departments continued to report that their own responsibilities were being completed within expected internal timeframes.
A revised approval process had been introduced during the same general period.
Two new internal workflow systems had also been introduced.
Management considered the revised approval process to have strengthened oversight.
Some project teams reported spending more time waiting for decisions.
No organisation-wide analysis had been undertaken comparing approval waiting times with overall project delivery times.
Operational Clarity separates what can be established from what people believe may be happening. Both matter, but they are not the same kind of information.
Project completion times had increased.
Department-level performance measures remained within their respective expected ranges.
The approval process had changed.
Two workflow systems had been introduced.
Project teams had reported longer waits for some decisions.
No analysis had yet established whether any of these changes caused the increase in project delivery times.
Several things had changed. That did not mean any one of them had caused the delay.
Different parts of an organisation can reasonably interpret the same situation differently. None of the views below is presented as a proven explanation.
The additional approval requirements were considered necessary and were believed to have improved oversight.
Individual departments generally considered their own processes to be operating within expected performance levels.
Some project teams reported that decisions involving more than one department were taking longer.
Interviews and stakeholder statements provide useful evidence of how an organisation understands itself. A statement being made, however, does not by itself establish that the explanation it offers is correct.
These questions remained open. They are recorded as questions because the available information did not yet answer them.
Where within the project lifecycle were delays actually accumulating?
Had approval waiting times increased?
Did delays affect all projects or particular types of project?
Were delays concentrated around particular departments or cross-department decisions?
Did the two new workflow systems alter how work moved between teams?
Had project complexity changed during the same period?
Were departmental performance measures capturing waiting time between departments?
Was there evidence connecting the revised approval process with overall project delivery times?
The following information would be requested before attempting any conclusion.
The purpose of requesting this information is not to prove an existing theory. It is to determine which explanations are supported by the evidence and which are not.
The picture that emerged was partial rather than tidy. Some expectations were supported; others were not.
Work completed inside individual departments had not materially slowed.
Approval processing itself had increased somewhat, but not by enough to explain the full increase in project duration.
The largest increase in elapsed time appeared between departmental hand-offs and cross-department decisions.
Some waiting periods were not included within individual departmental performance measures.
The two new workflow systems were initially suspected as a possible factor. The available evidence did not show a consistent relationship between system use and delayed projects.
Projects involving several departments experienced greater increases in elapsed time than projects largely contained within one department.
The workflow systems are a useful example. They were a plausible explanation, and they were examined for that reason. The evidence available did not support treating them as a contributing factor, and they are recorded here as an explanation that was considered and not sustained.
Bounded conclusions
Individual departments could genuinely be meeting their own internal performance measures while overall project delivery was becoming slower. The two observations describe different things.
The available evidence indicated that project delays were concentrated primarily around cross-department hand-offs and decision points. Existing departmental performance measures largely captured activity within individual teams and therefore provided limited visibility of waiting time occurring between them.
The revised approval process contributed additional elapsed time at some decision points, but the available evidence did not support treating it as the sole explanation for the overall increase in project duration.
The evidence suggested that the principal increase in elapsed time occurred between organisational processes rather than necessarily within them. It did not indicate that any particular department was performing poorly, and it did not establish a single cause.
The central distinction
On the evidence available, the organisation did not necessarily have a departmental productivity problem. It had limited visibility of the time work spent between departments and decision points.
Departments were meeting their measured responsibilities.
Projects were taking longer overall.
Both statements could hold at the same time. Recognising that is the clarification; deciding what to do about it remains a matter for the organisation.
A short extract showing how this might appear in the final Clarification Report.
Project delivery times increased during the review period despite individual departments continuing to operate within their respective internal performance measures.
Analysis of project timelines identified increased elapsed time around cross-department hand-offs and decision points. These waiting periods were not consistently represented within department-level performance measures.
The revised approval process contributed additional elapsed time in some cases; however, the available evidence did not indicate that approval activity alone accounted for the overall increase in project duration.
The evidence therefore indicates a difference between department-level performance visibility and end-to-end project delivery visibility.
Method, not outcome
The value of the examination was not identifying someone to hold responsible, nor proposing a solution. It was establishing a clearer picture of what was actually happening.
“Why are projects late when every department says it is meeting its responsibilities?”
The Clarification Report established that these two observations were not necessarily contradictory. Departmental measures described performance within teams. They provided less visibility of elapsed time between teams.
That distinction gave the organisation a clearer basis for deciding what, if anything, it wished to examine next.
Operational Clarity produces independent Clarification Reports for organisations seeking a clearer understanding of a specific operational, governance, dependency, resilience, or organisational question.
The purpose is clarification rather than prescription: establishing what the available evidence supports before decisions are made.