Which conversation belongs where
Most teams have one place to talk and use it for everything. That is why nobody can find anything six weeks later.
You have three ways to say something to a colleague in Lodos: a message in Social Hive, a MeMeet call, or a comment on the thing you are talking about. Teams that thrive on the platform are almost always the ones that made a deliberate choice about which goes where. Teams that struggle put everything in chat.
The split that works
Social Hive is for coordination that expires. "I'm pushing the fix now." "Anyone else seeing the staging site down?" "Lunch?" These have a short half-life and lose nothing by being hard to find later.
MeMeet is for the conversations that need faces — disagreement, ambiguity, anything where you have to read the room. Also for the first ten minutes of anything genuinely new, because typing is a terrible medium for a half-formed idea.
Comments are for decisions. Anything that answers "why is it like this" belongs attached to the thing it explains, not in a channel where it scrolls away.
The test is time. If it matters in six weeks, it does not belong in chat.
Channels: how many, and named how
Social Hive has public and private channels, direct messages and group chats. The failure mode is almost never too few channels.
Start with three or four public ones. General, one per active project, and something explicitly social — because if there is no channel for the non-work conversation, the non-work conversation happens in the project channel and buries the work.
Two rules that hold up:
Prefer public. A private channel is invisible to the person joining in three months who needed exactly that context. Use private for what is genuinely sensitive — compensation, hiring, a legal matter — and public for everything else, including the messy parts. Teams overestimate how much of their conversation needs protecting.
Name channels after the thing, not the team. "mobile-release" beats "mobile-team", because the release is what people search for. Channels named after teams accumulate every kind of conversation and become unreadable.
Making a meeting worth having
MeMeet has collaborative notes and integrated checklists, and those two features quietly decide whether a meeting produced anything.
Open the notes before the call rather than after. A shared document that exists when the meeting starts gets used; one created at the end gets a summary written by whoever felt most guilty. And because Notebook syncs with MeMeet in real time, what you write during the call is already where you keep everything else — you are not going to transcribe it later, and you were never going to.
The checklist matters more. Every meeting that ends without named actions with owners ends in the same place: three people each thinking one of the others is doing it. Add the items during the call, not afterwards. If nobody can name an action, that is real information — the meeting was a discussion, and you should say so rather than inventing follow-ups.
Recording exists and is worth using for anything a decision will be based on. Not to be watched — almost nobody watches a recording — but so that the one time someone disputes what was agreed, there is an answer.
The meeting that should have been three messages
The honest test, before you send the invite: can you write down the question you are trying to answer? If yes, and it fits in a sentence, send the sentence. You will usually have your answer before the meeting would have started.
Meetings earn their place when the question is fuzzy, when people disagree, or when someone needs to be convinced. Status updates are not a question. A round of "what is everyone working on" is a board you did not look at.
Talking to a community rather than a person
If you run a community in Social Hive, its inbox works differently from a DM and it is worth knowing why. A member writes to the community, and any admin can answer — but the reply goes out under the community's name and logo, not the individual's.
Read state is shared. When one admin opens a conversation it counts as read for all of them, and the others stop being notified. That is deliberate: five people getting an email about the same unanswered message is noise. It also means you should decide who is covering the inbox, because "shared responsibility" and "nobody's responsibility" look identical from the outside.
Questions people actually ask
Should channels be public or private by default?
Public. A private channel is invisible to the person who joins in three months and needed exactly that context. Reserve private for genuinely sensitive matters — compensation, hiring, legal — and put the rest in the open, including the messy parts.
Where should a decision be recorded?
As a comment on the thing it is about — the task card, the document, the file. A decision made in chat is gone in a day; attached to its subject it is still there when someone asks why six weeks later.
How do I know a meeting was worth holding?
It ended with named actions and owners in the meeting checklist. If nobody could name an action, it was a discussion — which is sometimes fine, but say so rather than inventing follow-ups nobody will do.
Why did my colleague stop getting notifications about a community message?
Community inbox read state is shared across admins. Once one of you opens the conversation it counts as read for everyone, and the unread reminder stops. Decide who is covering the inbox rather than assuming someone is.
