The Conversation Room: talking beside the work, without the noise of chat groups
Why WhatsApp and Telegram groups, Discord servers and Slack wear down careful work, and what the LeraLink Studio's Conversation Room deliberately leaves out
Nine people are preparing a report in three languages. The week's key decision, to shorten part two and move the tables to an appendix, was taken on Tuesday in a WhatsApp group. On Friday the colleague who was on leave comes back to three hundred unread messages: a lunch photo, two links, "did you see?" three times, and somewhere among them, that decision. The file called "final-7" is in email, the comments are in the margins of a shared document, and the lead's voice note is in Telegram. Nothing has been lost; it has been scattered. This article is about that scattering, and about the place we built to prevent it.
What chat groups do to serious work
The trouble is not the people. Messaging tools are built for continuous conversation, and knowledge work needs the opposite: long stretches of attention and a known place for decisions.
Research has measured the price of that mismatch. Gloria Mark and her colleagues showed that interrupted work gets done faster, but at the cost of more stress, frustration and time pressure, and in their field study getting back to interrupted work took more than twenty-three minutes on average. Sophie Leroy called it attention residue: the mind does not let go of an unfinished task, and the next task is done worse. Every notification is an interruption, and a group with a hundred messages a day pays that price a hundred times a day.
The second price is social. Mazmanian, Orlikowski and Yates studied professionals who saw their mobile devices as a sign of their freedom. The same people ended up working everywhere, all the time, because everyone expected everyone else to be reachable. Cross, Rebele and Grant found that in many organisations close to eighty per cent of working time goes on meetings, calls and replies, and that the load falls on a few. In Microsoft's survey of thirty-one thousand people, nearly seven in ten said they lacked uninterrupted time to focus. Cal Newport has a name for all of this: the "hyperactive hive mind", work organised around unstructured, unscheduled conversation.
WhatsApp and Telegram
They are excellent for quick coordination: a family, an event, "when do you arrive?". For work that runs for weeks they are one endless stream. Decisions, jokes and files follow one another in a single column. Telegram's topics help in large groups, but the group stays apart from the work: the conversation about the text is here, the text is somewhere else. Every message stays on everyone's phone for as long as each of them likes. In an ordinary WhatsApp group every member sees every other member's phone number. Telegram group chats are not end-to-end encrypted either; only its two-person "secret" chats are.
Discord
It was built for large communities of games, fandom and entertainment, and at that it has no rival: hundreds of channels, live presence, voice. The same design is heavy for a group of ten working on a report. Channels multiply, the "online" light is always on, and Discord's text messages are not end-to-end encrypted. Discord itself has said it has no plans to change that.
Slack
It is a work tool, and the closest to what we need: threads, channels, connections to other tools. Its harm is a culture of immediacy, where a faster reply comes to stand for more work. Channels multiply without account. On the free plan only the last ninety days of messages can be seen and searched. In 2024 the question of how customer data was used to train its models became a controversy. And what is said in Slack stays in Slack, away from the work itself.
Word and Google Docs
They are made for one shared text, and they are good at it. But when the conversation moves into the margins too, the document fills with comments, half of them about the direction of the work rather than that sentence. Everyone changes everything at once, and the "final-7" version is born from exactly that lack of boundaries.
What each tool is made for, and where it wears down serious work
| Tool | Good for | In careful, sustained work |
|---|---|---|
| WhatsApp and Telegram | Quick, personal coordination | Decisions buried under the stream; conversation apart from the text; everything stays on every phone |
| Discord | Large, live communities | Countless channels, constant presence, text without end-to-end encryption |
| Slack | A team's daily coordination | A culture of immediacy, scattered channels, conversation apart from the knowledge |
| Word and Google Docs | Writing one shared text | Conversation and text mixed; everyone everywhere at once |
| LeraLink's Conversation Room | Talking about the making of knowledge | No instant messaging by design, a day when it is removed, right beside the work |
What the Conversation Room is
The Conversation Room is in the installation's Studio, under "Collaboration and editorial", wherever it has been switched on for that installation. Threads open in it, each with its own title and its own people: two for a private conversation, or a group for a piece of work. Anything published can be brought into the conversation by typing "/": a Piece, a Project or a group, as a live card with its picture, title and author.
The Conversation Room is not knowledge, and that is its most important rule. No message becomes a Piece or a Block, is indexed, appears in public search or leaves with the installation's content. No model reads it: no translation, no summary, no suggestion.
The editor of a research journal opens a thread called "Spring issue: reviewers" adds three section editors, and brings in last issue's published Pieces with "/", so everyone talks about the same thing. The decision is taken, and the work itself goes on in the Pieces and the editorial desk, not in the thread.
The middle-out approach: where we left things open and where we closed them
There are two familiar ways. One is the rigid process from the top: forms, stages, approvals. The other is free conversation from the bottom: a group where anyone writes anything at any time. The first keeps people away from the work, and the second buries the work under noise. We chose a third way, which we call the middle-out approach. The work is at the centre: the Piece, the Project, the version. Conversation stays as close to it as possible, inside boundaries that keep it calm.
No instant messaging. The room holds no live connection. While a thread is open it fetches what is new every five seconds; when it is closed, it asks for nothing. That is a choice: the room does not want to call you outside the time you set aside for the work.
Every thread has a day. The room has a term of one to one hundred and eighty days. On each thread's day everything written in it is removed, even a message written a minute before: words, pictures, voice. The thread and its people remain, and a new term begins. The owner and administrators extend any thread as often as needed, and before the day the owner may download a thread or the whole room. The people of a thread are told a day before.
Why remove it? Because conversation is scaffolding, not the building. Scaffolding goes up to build and comes down afterwards; if it stays, you cannot see the building. A decision worth keeping belongs in its own place: in the Piece's text, in a new version, in an editorial note. The day of removal turns that move into a habit. Beyond that, messages kept for years on servers or phones are a risk no group needs.
Being seen has limits too. An ordinary member sees how many people are in the room and in a thread, not who they are. The owner and administrators read every thread, and every private thread always says so: this is a place to coordinate the work, not for anything sensitive. Whether each member may send words, pictures and voice is set member by member. A thread in which a group may only read is an announcement channel.
The Conversation Room is not a safe. Messages stay inside your installation, no model reads them and they are removed on their day, but the installation's owner and administrators can read them. Passwords, medical details or anything confidential belong somewhere else.
Reminders, and the "important" button
Each person chooses what mail the room sends them: none; as it happens; a summary at eight in the morning; or at eight and at six in the evening, in the installation's time. The as-it-happens letter comes once per thread, until you come and read it. It also waits two minutes, so that if you were reading at that moment you get no letter. The summary is a few sentences: who wrote, who answered, what was opened and what is about to be removed. No letter ever carries a word of the conversation; it only says where to go.
Anyone who may write in a thread may mark a message "important". The message is marked, and everyone in the thread is written to at once, even those who switched letters off. It is the only way the room calls someone without their own leave, and that is why it should be used sparingly.
Important: "Part three needs a legal review before tomorrow's publication." Not important: "I've put up the new draft." For the second, each person's ordinary letter is enough.
How it differs from writing together in the editor
LeraLink has writing together in the editor itself, but not in the way of Google Docs. Each Block of a Piece is in one person's hands at any moment, and the boundaries are visible. There is one draft and one version history, and each person's contribution is recorded separately. Comments sit on the very sentence they are about. So no "final-7" appears, and two people never rewrite the same paragraph at once.
The Conversation Room is the place for something else: for what to do. The editor is the workshop, and the room is the table beside it where tomorrow's plan is laid out. A comment about a sentence belongs in the margin of the text. A question like "shall we split this chapter?" or "who takes the Arabic translation?" belongs in the room. When the two are kept apart, the text stays clean and the conversation stays close to it.
For which groups
For small to medium groups carrying serious, careful and sustained work, each with a familiar pain:
- Knowledge-based nonprofits, whose knowledge stays in the messages of volunteers who leave.
- Civic initiatives of professionals, who must decide carefully and do not want their group to become an endless debating floor.
- Work that needs focus and safety, which cannot spread its members' phone numbers across a large group or leave messages on everyone's phone for years.
- Community projects, where building momentum and culture matters and every discussion has to lead to a piece of work.
- A start-up's knowledge hub, where what is learned spreads across Slack and is gathered nowhere.
- Multilingual international organisations, where each paragraph finds its own direction and Persian, English and Arabic read correctly side by side in one thread.
- A key department in a large organisation, which wants a place beside its own work instead of one more channel among hundreds.
It is not for everything. A community of thousands, friendly chat, an emergency line or a permanent archive of decisions needs another tool. The Conversation Room is small and calm by design.
Unless we change how we work, we get the same results
The chat-group habit has taken root in us over years: we pick up the phone, write, and wait for an instant reply. The Conversation Room works against that habit, and it is natural for the first days to feel unfamiliar. Our experience with the groups that have worked with it is that it takes about two weeks for people to settle in; after that, few want to go back to the old group.
Week one: give every ongoing task a thread with a clear title, and set everyone's letters to "summary". Every decision taken in a thread goes into the Piece or an editorial note the same day. Week two: use "important" only for what matters before tomorrow. At the end of the week, ask yourselves how many times you had to search for an old message. If the answer is "almost never", the decisions have gone to their proper place.
A home for focused groups
LeraLink is built for a group that wants to carry serious, careful, continuous and considered work, from a few people to a few dozen: people as close as possible to the knowledge and the content, and not buried for nothing under instant messages and the clutter of groups. The Conversation Room is that balance. In every installation that has the Conversation Room, a thread with the LeraLink team is already open; you can bring any question and any knot to us there.
Works cited
- A World Without Email: Reimagining Work in an Age of Communication OverloadCal Newport · 2021
- The cost of interrupted work: more speed and stressGloria J. Mark · Daniela Gudith · Ulrich Klocke · Association for Computing Machinery · 2008
- The Autonomy Paradox: The Implications of Mobile Email Devices for Knowledge ProfessionalsMelissa Mazmanian · Wanda J. Orlikowski · JoAnne Yates · Institute for Operations Research and the Management Sciences · 2013
- Will AI Fix Work? 2023 Work Trend Index: Annual ReportMicrosoft WorkLab · Microsoft · 2023
- Collaborative OverloadRob Cross · Reb Rebele · Adam Grant · 2016
- Why is it so hard to do my work? The challenge of attention residue when switching between work tasksSophie Leroy · Elsevier BV · 2009