When a team rule belongs in onboarding instead of another chat reminder

A team rule belongs in onboarding when people keep breaking it because they never learned the reason, not because they forgot a reminder.

Chat reminders are useful for temporary coordination: today’s deadline, this week’s release freeze, a one-time channel move, or a short incident rule. They are weak for permanent expectations. If a rule appears every few weeks in chat, new people will miss the history and experienced people will treat it as background noise.

Move a rule into onboarding when it affects quality, safety, customer promises, review time, or repeated team friction. Examples include how to label support severity, when to create a ticket instead of a chat thread, which decisions need written owners, how to request design review, and where to put customer-facing wording. These rules shape behavior beyond one day.

The onboarding version should not be a scolding paragraph. Write the rule, the reason, a good example, a bad example, and the first place to ask when unsure. The reason matters because people follow rules better when they understand the cost of skipping them. A rule without a reason becomes a preference fight.

Keep chat reminders for exceptions and deadlines. Keep onboarding for repeated rules that a new teammate must know before they can work safely. That split makes chat lighter and documentation more useful.

When a team rule belongs in onboarding instead of another chat reminder

// COMMENTS

ON THIS PAGE