When offices closed this spring, teams grabbed whatever worked. Zoom for meetings, Microsoft Teams for chat, Slack for another group’s chat, email for everything else, and a different board for each project. It was the right call at the time. Eight months later, many teams are paying for it: people check five places before they find the answer, and nobody is sure where a decision was made.

The fix isn’t another tool. It’s fewer tools and clearer rules.

Start with a working agreement

A working agreement is a one-page document that your team writes together and revisits when things change. It doesn’t need to be formal, but it does need to be specific. Cover these questions:

1. Which channel is for what? For example, chat for quick questions, email for external parties, the project board for task status, and a shared document space for plans.
2. What response time can people expect? Say it plainly. Most chat messages can wait a few hours, and urgent matters need a different route, such as a phone call.
3. Where are decisions recorded? Pick one place, and make it the one everyone checks.
4. What are the meeting rules? Agenda in advance, a named note taker, and a summary afterward.

Make asynchronous work the default

In a distributed team, the question to ask before scheduling a call is whether a written update would do. Asynchronous work respects different time zones and different home situations, and it leaves a record. Save live meetings for discussion, conflict, and decisions that need real-time back and forth. A status round where each person reads out a list is better handled in writing.

Meeting hygiene matters as much as tool choice. Cancel recurring meetings that no longer have a purpose. Trim invitation lists to the people who need to be there. Start and end on time, and leave a few minutes between calls.

Consolidate on purpose

Picture a mid-sized manufacturer with three project teams, each using a different board and a different chat tool. Everyone is productive within their own group, but the program manager can’t see across them. Agreeing on one chat platform and one board format took a single afternoon and removed hours of searching every week.

You don’t need to ban everything but one tool. Choose the platforms your organization already licenses and supports, retire the duplicates, and teach people the agreed conventions. Check with your IT and security teams before consolidating, because some tools hold sensitive data.

Try this: gather your team for 45 minutes, draft the working agreement, and post it where everyone can find it. Review it in a month. If your organization has a dozen teams and a dozen different habits, a PMO can help set shared defaults, and we’re happy to help you with that.