Internal communication tools: choosing them without adding noise

Internal communication tools accumulate. A team adds chat for speed, keeps email for anything external, adds a project tool with its own comments, a wiki with its own comments, and a video tool with a chat panel nobody reads. Nothing is ever retired, and the cost lands on the same person: whoever has to check five places before answering a question.

The problem is rarely the tools. It is that nobody has said what each one is for.

Give every channel one job

• Chat — anything that expects a reply today. Fast, informal, and explicitly not a record.
• Email — anything crossing the company boundary, plus internal messages that need to be forwardable or quotable later.
• Documents — anything that must still be true next quarter: decisions, processes, specifications.
• The work tool itself — comments about a specific task or document belong on that task or document, not in a channel where they lose their subject.
• Meetings — for the conversations that genuinely need synchronous thinking, with notes that land in documents afterwards.

The rule that removes most confusion: chat is where you ask, documents are where you decide. A decision that lives only in a channel is a decision nobody will find in three months — and the person who needed it will ask again, in chat.

The signals a tool is costing more than it gives

• The same question is answered in two places on the same day.
• New joiners cannot say where to look for something without asking.
• A channel exists that only two people read, and they also sit next to each other.
• Decisions are re-litigated because nobody can find the thread where they were made.
• People check chat during focus time because urgency has no separate signal — everything looks equally live.

Setting the conventions

1. Write one page: what each tool is for, what an urgent message looks like, and the expected response times per channel. One page, not a policy.
2. Set channel naming rules and keep the count small. A channel per project is fine; a channel per topic per project is how a team drowns.
3. Move decisions out of chat the same day: a message that decides something gets pinned and written into the relevant document.
4. Use threads by default. A ten-message reply chain in the main channel makes everything above it unreadable.
5. Agree quiet expectations: whether people are expected to reply outside working hours, and if not, say so where new joiners will read it.
6. Retire something every quarter. A tool nobody has opened in a month is a tab everyone still has open.

Ettex Chat is the fast half of that split: channels and direct messages, threads to branch any message, mentions and reactions, pinned messages so decisions and key links stay at the top of a channel, rich messages with formatting, code blocks, images and link previews, file sharing with previews, per-channel unread counters, and full searchable history rather than a window that expires. It lives next to the documents, boards and files it is about, and it works offline — history is readable and messages queue until the connection returns.

Threads beat inboxes for anything that needs an answer today. Teamchat keeps those conversations in channels a newcomer can read back through, rather than in a chain somebody forwards to them on day one.

What not to solve with tools

Two problems look like tooling problems and are not. If people are not sharing information, adding a channel does not change what they are willing to say. And if meetings are unproductive, moving them to a different platform does not fix the agenda.

The tool decision worth making carefully is the boundary one: what stays inside the company and what leaves it. Everything else is convention, and conventions cost nothing to change.

Two failure modes recur. Announcements sent as chat messages scroll away within a day, which is what an internal newsletter is for. And the calendar is a communication tool that nobody counts as one — half of the "we were never told" complaints are really a shared calendar app that only some of the team can see.

Internal communication tools work when each one has a job and someone is willing to retire the rest. Ask in chat, decide in documents, and keep the page that says which is which.