Finding Your Team's Unwritten Rules: A Chat Audit for Lean Groups
Most teams that struggle with chat do not struggle because of a missing feature. They struggle because nobody ever wrote down how the conversation is supposed to work. Who answers a question posted at 9 p.m.? Is a message in the general room a request or an announcement? Does a thumbs-up count as agreement? These rules exist in every active workspace, but they live in people's heads and get enforced socially, which makes them hard to evaluate. This article offers a method for pulling them into the open, so a founder group or small operating team can decide deliberately which norms to keep. The aim is not to recommend a particular product. It is to give you a way to judge any team chat setup, including the one you already use, by how well it fits the way your people actually work.
Start by Collecting Evidence, Not Opinions
Ask a team what its chat norms are and you will get idealized answers. People describe the process they wish they followed. A more reliable starting point is the recent history of the channels themselves. Pick a window of two to four weeks and read through the busiest rooms with a notebook open. You are not judging the content yet. You are noting patterns: which messages got replies within an hour, which got replies after a day, which got no replies at all, and which were answered in a different place entirely, such as a call or a direct message.
Pay special attention to repeated questions. If the same question about deployment access, budget approval, or meeting notes appears three times in a month, that is a signal that a norm is missing or that the existing norm is not discoverable. Count these. A rough tally of ten to twenty repeated questions is usually enough to show where the friction concentrates.
Separate Norms Into Four Kinds
Once you have evidence, sort the implicit rules you found into four rough kinds. Response expectations cover how quickly people are expected to reply and in which rooms. Message purpose covers what a post is meant to do: ask, inform, decide, or celebrate. Placement covers where particular kinds of conversation belong, such as decisions in one room and social talk in another. Closure covers how a thread ends, including who summarizes it and where the outcome is recorded.
Sorting matters because each kind fails differently. Response expectations usually fail through silence or resentment, when someone assumes a fast reply is required and feels ignored when it is not. Placement fails through scatter, when a decision made in a thread is never seen by the people it affects. Closure failures are the quietest and most costly, because nothing visibly breaks until a month later, when someone asks what was agreed and nobody can find out.
Ask Five Questions of Each Norm
For each norm you surfaced, put it through a short set of questions. Is it written anywhere a new member could find it? Do the people who rely on it agree on what it means? Does it match how urgent the work actually is, or does it reflect habit? What happens when it is broken, and does that consequence fall on the right person? Would the team still need this norm if the tool changed?
The last question is useful when evaluating software. A norm such as 'decisions get summarized in the decision log' is a human practice that any tool can support or hinder. If a norm only works because of one particular feature, that is worth noticing, because it means the norm is fragile to change. Good norms describe human behavior and can be carried across tools.
A Comparison Method for Evaluating Any Chat Setup
When you are weighing a new chat tool against your current setup, avoid comparing feature lists. Instead, run the same realistic scenario through each option and see where the norms survive. Take one real week of work and replay it: post a request, make a decision, hand off a task to someone in another time zone, and try to find something agreed three weeks ago. Note how many steps each action takes, how many places a person must check, and where information gets lost.
Keep the comparison in plain terms. For each setup, write a short paragraph answering three things: where do decisions end up, how does a newcomer find the rules, and what does a missed message cost? A setup that scores well on these questions for your team is a better fit than one with more capabilities you will never use. Be cautious with any claim about a product's behavior that you have not verified yourself in your own workspace, and confirm details such as retention, access controls, or export options directly with the vendor before relying on them.
A Short Checklist for Your Next Chat Review
Collect two to four weeks of real messages from your busiest rooms. Tally repeated questions and note where decisions were actually recorded. Sort each unwritten norm into response expectations, message purpose, placement, or closure. Ask each norm whether it is written down, whether people agree on its meaning, and whether it matches the real urgency of the work. Replay one realistic week of work in your current setup and in any candidate tool, noting steps, places checked, and information lost. Write one page that names the three norms you will keep, the two you will rewrite, and the one you will retire.
Finish by assigning a single owner for the written norms and a date to revisit them. Chat norms decay quietly as people join and leave, so a review that happens once and is never repeated will drift back toward the same confusion. A small, regular audit keeps the conversation useful as the team grows, whatever tool carries it.