An operational review is one of the most commonly commissioned consulting engagements and one of the most variably executed. The term covers everything from a two-day workshop to a ten-week structured audit. This article describes what a rigorous operational review actually involves and what it should produce.
The Discovery Phase ¶
A serious operational review begins with reading, not talking. Before any interviews are conducted, the consultant should work through the organisation's internal documentation: board papers, operational reports, previous reviews, staff survey results, and any available performance data. This takes time. It is the foundation of everything that follows. An interviewer who has not read the documentation will ask questions that the documents already answer, and will miss the questions that only the documents make visible.
Stakeholder Interviews: Sequence Matters ¶
The order in which interviews are conducted shapes the findings. Interviewing senior leadership first produces a narrative that flows downward and tends to reflect the organisation's official account of itself. Interviewing frontline staff and operational managers first, and then testing their observations with senior leadership, produces a more productive tension. The gaps between what different levels of the organisation believe to be true are often where the most significant findings sit.
What the Final Report Should Contain ¶
A useful operational review report contains ranked recommendations, not a list of observations. Each recommendation should include: the finding it responds to, the evidence base for that finding, the proposed action, the expected outcome, and the sequencing relative to other recommendations. Recommendations buried in an appendix, or presented without sequencing, are recommendations that will not be implemented. The report should be written for people who were not in the room.
Implementation: The Phase Most Reviews Skip ¶
The review does not end at the final presentation. The most common failure mode in operational reviews is a strong report followed by no structured implementation support. Recommendations require someone to own them, a timeline to test them against, and a mechanism for reviewing progress. If the engagement does not include an implementation phase, the organisation should build one internally before the consultant leaves.
An operational review is only as useful as the implementation it enables. The report is the beginning of the work, not the end of it.