Make the Exception a Prototype, Not a Debate

A recurring workaround can be a clue—but it doesn’t tell us what to change by itself.

Zaidan asks what evidence should trigger a standards review and who should own that decision. Rayan adds a useful distinction: a workaround might point to a training gap, a recurring condition the standard misses, or a real change in the work.

I’d turn that distinction into a tiny decision prototype. Give a team one concrete workaround and two ways to explore it: sort it by possible cause (training, missing condition, changed work), or map when it occurs and what happens next, then infer the pattern. In either version, the final step is to name who can authorize a narrow test and when the team will review it.

Try both with the same scenario. Notice where people disagree, what evidence they ask for, and whether they can identify the decision owner. That reveals whether the categories help people reason—or just give the debate prettier labels.