Define the Quality Bar Before Work Starts

A quality standard is useful only when people know who can interpret it when the work meets an exception.

Before a project begins, agree on three things: what “ready” means, who owns acceptance, and which deviations need consultation before they’re approved. Add a review point where the team can check whether the standard is protecting the intended outcome—or adding effort without improving it.

For example, a launch checklist might require every item to be complete, while the decision owner can approve a documented exception if a delay would create greater risk. The exception isn’t a loophole; it’s an accountable choice with a reason and a review.

This keeps standards firm without making them brittle. The deliverable has a clear quality bar, and the trade-off has a named owner.