Why most debriefs fail to change the next audit—and how to turn them into real design inputs
By William Englehaupt
As one audit cycle closes and the next begins, most teams go through some form of debrief. In theory, this is where learning happens, where teams step back, reflect on what worked, what didn’t, and carry those insights forward.
In practice, it rarely works that way.
MORE Audit & Assurance
Debriefs are often rushed or treated as closure rather than input. The questions are familiar—what went well, what didn’t—but the discussion stays at the surface. Late nights, difficult clients, tight deadlines. The symptoms are easy to identify. The underlying causes are not.
Then planning begins, and the same patterns quietly return.
As W. Edwards Deming observed, “Every system is perfectly designed to get the results it gets.” Audit outcomes are not accidental. They reflect how the work is designed.
The issue is not that firms fail to reflect. It is that they reflect on the wrong level.
Most debriefs focus on experience rather than system behavior. Teams describe what happened, but not how the work actually flowed. The conclusions are often directionally true—staffing was tight, the client was slow, review took longer than expected—but they stop short of explaining why those conditions led to rework, delays, and late pressure.
Without that clarity, there is nothing to redesign.
Timing compounds the problem. Debriefs often occur after the engagement is effectively complete and teams have already shifted to other work. By the time insights are discussed, they are disconnected from the planning decisions that would make them actionable.
A more effective debrief shifts the focus from narrative to system behavior. Instead of asking what went wrong, it asks where the flow of work broke down.
Where did work cycle back for rework? Where did “done” turn out not to be done? When were issues first visible—and when were they raised? Where did review clarify expectations that should have been clear upfront?
These questions move the conversation from symptoms to mechanisms. And when teams answer them honestly, the patterns are consistent. Clarity arrives late. Coaching happens during review instead of before work begins. Uncertainty is held until deadlines make it expensive to resolve.
Internal debriefs, however, only tell part of the story.
Many of the same dynamics that drive rework and delay sit at the boundary between the firm and the client—timing of requests, clarity of expectations, and availability of data. Yet client debriefs are often informal, softened, or skipped altogether. That is a structural blind spot.
If audit performance is a system outcome, then the client is part of that system. Debriefing only one side guarantees an incomplete diagnosis. A rigorous client debrief should mirror the internal one, not as a satisfaction check, but as a shared examination of how the process performed.
Where did requests create rework or delay? Where were expectations unclear on either side? When did information become available relative to when it was needed? Where did timelines break and why?
This is not about assigning blame. It is about aligning on how the system behaved. Clients often experience the same friction as auditors and are often willing to improve the process when it leads to greater predictability.
A one-sided debrief improves awareness. A two-sided debrief improves the system.
The purpose of a debrief is not to document the past. It is to design the next audit. That only works if the output feeds directly into planning.
If rework was driven by unclear expectations, “done” must be defined more precisely. If review became a bottleneck, its timing and structure must change. If issues surfaced late, escalation expectations must be made explicit before work begins.
This is where many firms fall short. They debrief. They plan. But they do not connect the two in a way that changes how the work is designed.
The result is predictable: the same system produces the same outcomes.
As teams enter the new audit year, the opportunity is not to work harder or respond faster. It is to use the debrief as a true design input—focusing on where rework was created, where expectations were unclear, and when issues surfaced relative to when they were first visible.
Because the next audit will not be defined by effort. It will be defined by whether the system that produced last year’s problems is allowed to run again.