How to manage project communication without losing decisions

The short version

1. Map who needs to know what.
2. Give each type of message one channel.
3. Keep discussion on the work itself.
4. Record decisions where people will look.
5. Set a rhythm for updates.
6. Include clients and outside partners deliberately.
7. Control notifications.
8. Tidy up as the project runs.

Project communication fails less from too little talking and more from talking in the wrong places. The steps below fix where information goes.

Step 1: Map who needs to know what

List the groups involved in the project and what each needs:

This keeps you from sending everything to everyone, which is how important messages get ignored.

Step 2: Give each type of message one channel

The core rule: every kind of message has a single, agreed home.

• Quick coordination: the project's group chat.
• Feedback on a specific deliverable: a comment on that task, file or document.
• Announcements, decisions and weekly updates: a longer written post in the project.
• Deadlines and meetings: the shared project calendar.
• Private matters: direct messages, but not project decisions.

Write this down in a pinned note at the top of the project so new people learn it fast.

Step 3: Keep discussion on the work

When feedback about a design is in a chat thread, the designer has to find it, connect it to the right file and hope nothing was missed. When feedback is a comment on the file itself, the context is obvious. Encourage the team to comment on the card, task, event or document the discussion is about. This is the core of connected work.

Step 4: Record decisions where people will look

Chat is good for reaching a decision and poor for storing one, because it scrolls away. Once something is decided:

• Summarise it in a short written post or in the relevant task.
• Say what was decided, why, and who agreed.
• Link or mention the people affected.

A simple habit: whoever closes a discussion in chat writes the one-line decision somewhere permanent.

Step 5: Set a rhythm for updates

Predictable updates reduce ad hoc "any news?" messages. For example:

• A weekly written update to the wider team and the client.
• A short weekly internal review focused on blockers.
• Milestone summaries when a phase ends.

See how to run weekly team meetings for a meeting format that pairs well with this.

Step 6: Include clients and partners deliberately

Clients often end up on long email chains copied to half the team. A better pattern is to give them controlled access to a shared project area where they can see progress, comment on deliverables and ask questions, while internal discussion stays internal. Decide in advance which areas they see.

Step 7: Control notifications

If every message pings everyone, people start ignoring notifications, and the important ones get missed. Use mentions for specific people, reserve "notify everyone" for real announcements, and encourage people to tune their notification levels.

Step 8: Tidy up as the project runs

Pin the messages and posts that matter, archive finished tasks and keep documents in their folders. A tidy project is easier to catch up on after a holiday or when a new person joins.

Common mistakes

• Everything in one chat, so decisions and files disappear in the scroll.
• Email chains with clients, which fragment feedback and leave people out.
• Decisions only in meetings, with no written record.
• Over-notifying, which trains people to ignore alerts.
• Private side conversations about project matters.

How to do it in Emitii

In Emitii, each project has a space, and the communication channels are part of it:

• Pulse is the space group chat, with threads, @mentions, reactions, pinned messages and file attachments. Use it for quick coordination.
• Comments work the same way on cards, to-dos, events, posts and docs, with attachments, mentions and reactions, so feedback stays on the item it is about.
• Posts carry announcements, decisions and weekly updates, with a title, a Markdown body, comments, pinning and "Notify everyone".
• Schedule holds meetings and deadlines, and card and to-do due dates appear on it.
• Direct and group messages handle conversations outside a project.
• Guests. Invite clients as guests to their space only. Everything stays internal until a member shares it, and the client talks with the team in Guest Pulse while the team keeps its own Pulse.
• Notifications. Everyone can choose "Everything", "Involved" or "Just me", set quiet hours and mute specific scopes.
• Emit and @emitii. Mention @emitii in Pulse or a comment to ask a question about the space, or use the Emit tab to draft a weekly update post; it asks before publishing anything.

The space Activity feed shows what changed across cards, comments, posts, schedule and tasks.

See team communication in Emitii and Posts, how marketing agencies keep client communication together, the marketing campaign template for a sample setup, and how Emitii compares with Basecamp in Emitii vs Basecamp.