The rule should not live in a side message

Teams often say they have a process when what they really have is a public process plus a hidden one.

The public version lives on the board, in the checklist, or inside the tool. The hidden version lives in a side message, an old chat thread, or in one person's memory. The work looks straightforward until it reaches the point where the undocumented rule suddenly matters. Then somebody says, "We actually do it this other way," and the task has to get reworked.

That kind of rule is expensive, even if it sounds small. It slows down handoffs, makes onboarding harder, and creates avoidable mistakes because people can only follow what they can see. If the real process depends on private context, then the workflow is asking people to guess.

Good systems do not rely on folklore. If a rule affects approval, routing, timing, or formatting, it should appear where the decision happens. Attach it to the task. Put it in the checklist. Build it into the form. Make it visible before the work starts drifting.

This matters even more in fast teams. The busier the workflow gets, the less room there is for hidden process and unofficial exceptions. People should not need a perfect memory or a backchannel explanation to do routine work the right way.

If the team keeps fixing the same mistake with the same private reminder, the reminder is not the solution. The workflow needs to carry the rule.