Collaboration tools fail the same way spreadsheets fail: a second copy appears, and suddenly nobody knows which one is true. Comments, mentions, and shared docs are useful only if the work has one home. Your job is to name that home and be politely tedious until people use it.
One home for the work
Pick a system of record for tasks, decisions, and files — or a tight pair, such as the tracker for work and the wiki for decisions. Write it down in one paragraph. 'We track work in X. We do not accept new scope that exists only in email. Decisions that change the plan are logged in Y.' If you cannot say that in a paragraph, you do not have a toolset. You have an archipelago.
Redirect, do not shame. When someone briefs a change in a thread, thank them and move the action onto the card with a link back. The third time, they will start there. The tenth time, a senior person will still email you a screenshot. Move that too. Single source of truth is a habit enforced by the PM, not a setting in the admin panel.
Kill the shadow tracker. The spreadsheet 'just for me' becomes the real plan within a fortnight because it is easier to edit than the official board. If the official board is unusable, fix the board. If the spreadsheet exists because someone does not trust the team to update the tool, you have a behaviour problem. A second system will not repair trust. It will hide the distrust until the two plans disagree in a steerco.
Meetings feed the record. They are not the record.
A standup or weekly that does not update the board is a radio play. Open the tool in the meeting. Move the cards. Capture the decision while the people who made it are still in the room. 'We'll update Jira later' is how later becomes never and the board becomes a museum of last Tuesday.
Store files where the work lives, with names a stranger can search. Final_v3_USE_THIS is a cry for help. One current document, one owner, old versions in history. If legal needs a frozen copy, export it and say so. Do not fork the working file into a parallel universe called 'steering version' that quietly diverges.
Access is part of collaboration. A 'shared' folder that half the vendors cannot see will recreate email attachments by Thursday. Check permissions when you onboard someone, not when they miss a review. And do not put secrets in a comment thread that will be exported to a contractor next quarter. The tool is a room. Know who is in it.
Summary & next steps
Name one system of record and retire the shadow copies. Comment on the work with a single owner and a date. Use meetings to update the record, not to replace it.
Next: choosing a tool — team size, method, and admin cost, without a vendor bake-off dressed up as strategy.
Comments that close, mentions that ask
Comment on the work item, not in a side-channel that the next person will never see. Write the decision, the ask, or the blocker. 'FYI' comments that tag eight people are how mention fatigue is born. If nobody needs to act, do not mention them. If someone needs to act, mention one owner and a date. 'Can you confirm the API freeze by Thursday?' is a comment. '@team thoughts?' is a shrug with notifications.
Close the loop on the same thread. When the answer arrives in a meeting, go back and write it on the card. Future you — and the person who joins in week six — should not have to reconstruct a decision from three tools and a hallway. A card that says 'agreed in standup' with no substance is a breadcrumb that leads to a cliff.
Use mentions as a queue, not a siren. If everything is urgent, nothing is. Batch non-urgent questions. Escalate genuinely blocked work with a status change plus a mention, not a louder ping. People learn to ignore a tool the same way they learn to ignore a PM: too many false alarms, then silence when it matters.