Goalpost Drift

A hypothesis that pressure is being relieved by quietly lowering the standard, which weakens future correction.

On your product team, shipped used to mean tested, documented, and announced. Under this year's deadline pressure, releases kept counting as shipped with docs to follow, then with known bugs logged, then with testing planned. The dashboard shows a record shipping quarter. Support tickets show something else.

Used as a diagnostic, Goalpost Drift is the hypothesis that pressure is being relieved by quietly lowering the standard, which weakens future correction, because each lowered bar makes the next lowering smaller and less visible. Make it predict. If drift is the structure, the gap between the original written definition of done and current practice should widen in steps that each coincided with a crunch, no meeting should exist where the change was decided, and downstream costs (tickets, rework) should rise while the headline metric improves. The strongest rival: the team consciously and sensibly retraded quality for speed, in which case you will find the decision discussed and owned somewhere. The distinguishing observation: audit five recent shipped items against the original checklist and search the decision record. If drift is confirmed, the intervention is re-anchoring the standard to something that cannot slide silently, an external checklist with named sign-off. Do not treat every standard change as drift; chosen, documented adaptation is management, not decay.