Rules
Part of Team collaboration: methods, tools and useful context
Team collaboration alternatives explained with examples
Team collaboration alternatives, compared honestly: mail with a rule, a shared document, the work tracker, and a removal test to run before you buy.
Most teams shopping for a collaboration product have already decided that the answer is a product. That is the step worth going back to, because the four most common complaints in this category are not solved by any of them.
Nobody knows what was decided. Nobody can find last month's thread. Everything arrives at once and none of it is marked urgent. Two people are doing the same job. Those are coordination problems, and a channel is only one way to fix them.
What to take away
- Write down the coordination failure in one sentence before you look at anything. If it names a person or a decision rather than a feature, no product will fix it.
- Mail, a shared document, and the work tracker are all legitimate answers, and each has a shape of work it fits better than chat does.
- The real cost of a chat product is not the seats. It is the expectation that everyone is reachable and that everything is written somewhere ephemeral.
- Run a removal test before a purchase test. Take one habit away for two weeks and see what actually breaks.
Name the failure before you name a tool
| What people say is wrong | What is usually underneath it | What a chat product does about it |
|---|---|---|
| Too much email | Everyone is copied on everything because nobody knows who owns what | Moves the same volume somewhere with fewer filters |
| Nobody knows what was decided | Decisions are made in conversation and never written down | Makes it worse, because conversation gets faster |
| I cannot find anything | There is no agreed home for a finished thing | Adds another place things can be |
| We keep duplicating work | Two people believe the same task is theirs | Nothing, unless the work is tracked somewhere |
| Remote people are out of the loop | Decisions happen in a room and get summarized late, or not at all | Genuinely helps, if the room agrees to stop deciding in the room |
Only the last row is a tooling problem. The others are questions about ownership and about where a finished thing lives, and buying software to answer them produces a fifth place to look.
Five arrangements that are not a chat product
Mail, used with a rule. Mail is unfashionable and it has two properties nothing else has: everyone already has it, and it reaches people outside your organization without an invitation. It also creates a record by default. Records bodies treat it as one for exactly that reason, which is why the National Archives guidance on managing email reads as a filing problem rather than a messaging one. The rule that makes mail work is a convention about the subject line and about who is on the To line versus the copy line. Two sentences of agreement, no purchase.
A shared document as the working surface. For anything that has to end in a decision, a live document beats a thread, because the document holds the current state and the thread holds the history of people changing their minds. A weekly agenda document that people write into before the meeting is the cheapest coordination improvement available to most teams.
The work tracker as the conversation. If the unit of work is a task, then the task should carry the discussion. Comments attached to an item stay attached to it forever and are found by anyone who opens the item in a year. Chat comments about the same item are gone.
A written weekly update. One paragraph per person or per team, on a schedule, in one place. It is dull and it removes an enormous amount of status chasing. It also gives you an honest record of what a quarter actually contained.
A short scheduled call. Some things resolve in four minutes of talking and never resolve in writing. The mistake is not having the call; it is having it every day out of habit when the work does not change daily.
What each one costs
Nothing here is free. Mail costs you attention control, because you cannot easily mute a thread that is still relevant to somebody else. Documents cost you conflict, since two people editing the same paragraph is still awkward. Trackers cost you setup and maintenance, and they punish teams whose work does not divide into items. Written updates cost the discipline of writing them when nothing interesting happened. Calls cost the most expensive thing anybody has, which is a block of uninterrupted time.
The point of listing costs is that a chat product also has one, and it is rarely stated: it changes the default expectation of response time. That expectation, once set, is very hard to reset, and it is the part people describe two years later as the reason work got harder.
When a channel product genuinely is the right answer
Three situations, and they are recognizable.
The work is genuinely continuous and interruptible, such as support, operations, or anything with an on-call rotation. The team is distributed across time zones, so the alternative is not talking but waiting a day. Or the organization is large enough that people need a way to reach a function rather than a person, and a named channel does that better than a distribution list.
If none of those describes you, a collaboration product is still allowed. It is just not a fix for anything, and it should be bought as a convenience rather than as a remedy. The category overview sets out what these products actually differ on, and the cost model shows how quickly a convenience becomes a fixed line in the budget.
The removal test
Before you add anything, take something away for two weeks and write down what breaks.
- Pick one habit: the daily call, the copy-everyone convention, the channel nobody reads.
- Remove it, and tell people it is coming back if it is missed.
- Log every moment somebody had to ask for something they would previously have seen.
- At the end, look at the log. If it is short, the habit was overhead. If it is long, you now know exactly what the habit was doing, and that is your requirement.
This is a two week exercise that costs nothing and routinely tells you more than a trial does. Public sector guidance on technology choices makes the same point in a more formal register: the advice on choosing technology starts from the user need rather than the product category, because starting from the category means the answer is already fixed.
The decision nobody wants to make
Here is the honest version. A great deal of what gets described as a collaboration problem is a decision rights problem: nobody is clearly allowed to say no, so everything is discussed by everyone until it dissolves. Software makes that discussion faster and more visible. It does not end it.
If your meeting notes contain the same open question three months running, the next purchase will not close it. Naming the person who decides will. That is uncomfortable, unbudgeted, and free.
Where this fits
If you do buy, buy against written agreements rather than a feature list, which is the method in the selection guide. If mail is doing more of this work than you realized, the mail comparison method is the right next read, and if the answer turns out to be documents rather than messages, the document capability checklist covers what to look for there.
Common questions
Is it realistic to run a team with no chat tool at all?
Yes, and plenty do. It works best where the work is scheduled rather than reactive and where most people share working hours. It works badly for anything with an on-call rotation, because there is no good way to reach whoever is holding the pager without a shared place.
We already have chat inside another product we pay for. Is that enough?
Often, and it is worth exhausting before buying a second one. The usual reason it is judged insufficient is that it lacks one feature somebody liked elsewhere. Write down that feature and ask whether it is worth a second product, a second place to search, and a second set of accounts to close when someone leaves.
What about the argument that the tool creates a searchable record?
Test it. Search for a decision you know was made four months ago and time how long it takes to find. Most teams discover that the record exists but is not findable, because the decision is spread across nine messages and two of them are in a private conversation. A record you cannot retrieve is not a record.
Does moving conversation into the work tracker actually stick?
Only if the tracker is where work genuinely lives. If people update items to keep a manager quiet rather than to do their job, comments will not migrate there either. Fix the first problem and the second one goes away on its own.
