The reflex
A problem has just happened. The team adds a rule so it does not come back.
The builder’s reflex
Before adding a rule, ask which risk it handles, what it will cost every time, and whether a lighter answer exists.
Why
Every rule costs a little each time it is applied. Added one by one after each incident, rules end up slowing everyone down for risks nobody remembers.
A quote goes out with the wrong price. You could add a manager’s sign-off on every quote. You could also fix the price list, calculate the price automatically, or review only the quotes above a certain amount. Systematic sign-off is rarely the best answer.
If the consequence is serious, one occurrence is enough: protect right away. For a limited nuisance, watch a few cases before imposing a procedure on everyone.
A rule has to state its reason. Without it, nobody will know when to remove it.
Try this
On a proposed or existing rule, ask three questions: which risk does it handle, what other answers exist, and what does it cost the people applying it?
Pick the lightest answer that genuinely protects. Set a date to check whether it is still useful.
To discuss
Which rule do we apply without anyone remembering why?