Audit the assumption behind the work

A team can improve its execution while continuing to serve an assumption that no longer holds. The schedule looks healthy because nobody has asked whether the work still solves the problem it was created for.

An assumption audit begins with one consequential belief, not a general invitation to doubt everything.

Make the belief inspectable

Write the belief in a form that could be contradicted. “Users need this report before making the weekly decision” is more useful than “Reporting is important.” Name the evidence currently supporting it and what would cause you to change it.

Then inspect actual use. A report may be opened without influencing a decision. A missing response may reflect poor access rather than lack of need. Keep competing explanations visible.

One bounded review

Select a recurring deliverable. Ask its intended recipient to describe the last decision it informed. Compare that account with the purpose you had assumed.

If the evidence is weak, do not immediately remove the deliverable. Test a smaller or different version where consequences allow, and check who else depends on it.

What makes the audit useful

Record the decision changed by the review, including a reasoned decision to continue. If every audit ends with the same answer regardless of evidence, the exercise is ceremonial.

The aim is a model that can be corrected while correction is still manageable. Constant novelty is no better evidence of judgment than unquestioned routine.

Source note

This work develops the concern in “The Assumption Audit,” published on 2026-02-07.