HireOrSell logo
All articles
Projects & operations

Keep project talk out of email: a simple team chat setup

Internal project talk buried in email threads costs hours every week. Set up a small set of team chat channels, a few naming rules and a short list of habits to move it out.

Cover graphic titled Keep project talk out of email: a simple team chat setup

Project talk in email is slow to find, easy to miss and hard to skim. When a client question lands in a thread of 23 replies, the answer is somewhere in the middle and only two people know where. This post gives you a small channel structure, naming rules and habits that move internal project conversation into team chat without turning chat into a second inbox.

What email is bad at

Email works for messages that go outside the company. It is poor at the quick back and forth inside a team. Replies get split across threads, people are dropped from the "To" line, and the latest decision sits under six layers of quoted text.

Here is a hypothetical example. Say a six-person agency runs 5 active projects and each project generates 8 internal emails a day. That is 5 x 8 = 40 emails a day, or 40 x 5 = 200 a week. If each email takes 2 minutes to read and answer, that is 200 x 2 = 400 minutes, or 6 hours 40 minutes a week.

Now say the same exchanges happen as short chat messages at 1 minute each. That is 200 x 1 = 200 minutes, or 3 hours 20 minutes. The saving in this example is 400 - 200 = 200 minutes a week. The numbers are assumptions you can replace with your own, but the method shows you what the habit costs.

The channel structure

Start with fewer channels than you think you need. A small team can run on four types:

  • One channel per active client project. This is where the work gets discussed.
  • #general. Announcements only: holidays, new hires, office closures.
  • #ask-anything. Questions that do not belong to one project, such as "who has the brand fonts."
  • #billing. Questions about invoices, expenses and approvals so they do not scatter across project channels.

Add a fifth, #wins, only if people will actually use it. An unused channel is clutter.

Do not create a channel per task, per person or per department. Projects have a start and an end, which makes them easy to open and archive. Anything else tends to drift.

Naming rules

Names let people find a channel without asking. Pick a pattern and keep it.

  • Prefix by type: client- for client projects, team- for internal topics, ops- for admin.
  • Use the client or project short name after the prefix: client-harbor-rebrand.
  • Keep names lowercase with hyphens, no dates in the name.
  • Archive the channel when the project closes. Do not delete it, since someone will want the history.

Write the pattern down in #general where new people can find it.

Rules that stop chat becoming noise

A good structure fails if everyone posts anything anywhere. Agree on a handful of rules and pin them.

  1. One topic, one place. If a message is about the Harbor rebrand, it goes in that channel, even if it is a quick question.
  2. Decisions get a marker. When something is decided, post a line starting with "Decision:" so it can be searched later.
  3. Files and links go where the work lives. Chat points to the file, it does not replace the file store.
  4. Reply in the thread. Side conversations in a thread keep the main channel readable.
  5. Use mentions sparingly. Mention a person when you need an action from them, not to make sure they see something.
  6. Urgent means a call. Chat is not a pager. State how someone reaches you for a true emergency.

Pick a response expectation too. For example: "Chat messages get a reply within half a working day." Without a stated window, people either check chat all day or feel guilty when they do not.

What stays in email

Do not try to move everything. Keep these in email:

  • Anything to or from a client, unless you have given the client access to a shared channel on purpose.
  • Contracts, formal approvals and anything you may need as a record outside the team.
  • Messages to suppliers and freelancers who are not in your chat workspace.

A common compromise is to discuss in chat and then send the client one clear summary by email. The internal channel holds the thinking, and the email holds the outcome.

Keep billing questions together

Money questions are the ones that go missing. A line item that looks wrong, a missing purchase order number or a question about a client's tax details can sit in someone's inbox for a week. A single billing channel lets whoever sends invoices see every question in one place.

It also helps to agree on what a complete invoice looks like before anyone asks. The checklist in what to include on an invoice is a handy reference to pin in that channel, so questions get answered against a shared standard instead of opinion.

Tie chat to dates and decisions

Chat is fast but forgetful. Meetings, milestones and deadlines need a home that is not scrolling away. Put them in a calendar and link the calendar entry from the project channel. The post on keeping client meetings, milestones and deadlines in one calendar covers how to do that, and it pairs well with a channel per project.

If your project management tool has team messaging built in, as HireOrSell does, you can keep the conversation next to the project itself, which removes one tool from the pile. That is a convenience, not a requirement. A standalone chat tool and a simple naming scheme will get you most of the way.

Signs your setup needs more structure

Watch for these:

  • People ask "which channel is this in" more than once a week.
  • Important decisions are only in someone's direct messages.
  • Channels have more than 10 or 12 active people and few of them post.
  • The team keeps a private spreadsheet to track what chat has promised.

That last one is common. If you keep patching holes with spreadsheets, the problem may be bigger than chat, and 5 signs your agency has outgrown spreadsheets is a useful checklist to read through.

A one-week rollout

Do not announce a new system and hope. Run it as a short trial.

  1. Monday: Create the four channel types and post the naming pattern and rules.
  2. Tuesday: Move the live projects into their own channels. Add the right people only.
  3. Wednesday to Thursday: Whoever starts an email thread about a project internally restarts it in the channel instead.
  4. Friday: Spend 15 minutes asking what was confusing and adjust the rules.

Review again after a month. Archive unused channels and merge duplicates.

Next step

Open your inbox and count the internal project threads from the past week. Use that number in the calculation above with your own minutes per message, and set up the four channel types before the next project starts.

Free plan available

Ready to run it all in one place?

Projects, clients, time tracking and invoicing in one platform.