Organisation
What if our tools were causing information overload?
We often blame behavior. But what if the problem also came from the digital architecture itself?

Too many emails. Too many messages. Too many notifications. Too many documents. Too much information.
Faced with information overload, the diagnosis is almost always the same: we would communicate too much.
Fewer emails should be sent. Create fewer meetings. Better use Teams. Limit notifications. Better classify documents. Train employees in “best practices”.
What if we got some of the diagnosis wrong?
What if the problem was not only the quantity of information produced, but the way our tools disperse it?
Maybe we don't have too much information. We have too many places for them to be.
Let's take a very ordinary project.
- A decision arrives by email.
- A discussion continues in Teams.
- A clarification is given in a chat.
- A document is deposited in SharePoint.
- A task appears in Planner.
- Urgent information goes through WhatsApp.
- Another is given orally in a meeting.
Each tool can be used perfectly.
And yet, a few weeks later, a very simple question appears:
“Where are we at”
Then begins a job that we all know:
search, find, cross-reference, understand who responded to whom, find the latest version of a document, check if a task has been carried out, reconstruct a decision.
It’s no longer just communication. It's the reconstruction.
Multichannel mechanically disperses the history of work
The current digital organization is largely based on multi-channel logic.
Each use has its own space:
- email for certain exchanges;
- instant messaging for others;
- team channels for collective discussions;
- a task manager for monitoring;
- a documentary space for files.
This specialization seems logical.
But it has a consequence that is rarely questioned:
the same project finds itself fragmented between several memories.
The problem does not necessarily appear when we exchange.
It appears over time.
- When finding a decision.
- When welcoming a new person to the project.
- When understanding why an action was decided.
- When identifying who should do what.
- When resuming a file several months later.
The more time passes, the more the memory of the project becomes dispersed.
information overload is therefore not only a question of volume
One hundred pieces of information gathered in the same place, in their context, can remain perfectly understandable.
Thirty pieces of information spread across six tools can become difficult to use.
This is why we must distinguish the volume of information of the fragmentation of information.
What tires organizations is not only receiving information.
It is having to continually ask yourself:
- Where is she?
- Is this the latest version?
- Who received it?
- Does an answer exist elsewhere?
- This task arises from which decision?
- What is the context of this document?
Part of information overload could therefore be considered as a consequence of digital dispersion.
What if certain “bad behaviors” were only adaptations?
Users are often criticized for copying too many people.
Why do they do it?
Sometimes just to make sure no one loses the information.
Employees are criticized for keeping their own files.
Why?
Because they fear not finding the information later.
- We are multiplying the reports.
- We transfer the emails.
- We copy the documents.
- We create monitoring tables.
- We make summaries.
- We organize meetings to find out where the project is at.
These behaviors can themselves produce even more information.
But they often respond to a very concrete need:
compensate for fragmented digital memory.
We then produce additional information to try to find the previous information.
It’s a vicious circle.
The real challenge: moving from the circulation of information to its continuity
For years, digital technology has improved the speed with which we can transmit information.
But transmitting faster is not necessarily better organization.
The next challenge for digital collaboration could be elsewhere:
maintain the continuity of the work.
A project has a story.
- A request appears.
- People exchange.
- Responsibilities are assigned.
- Documents are produced.
- Tasks are carried out.
- Decisions are made.
All this belongs to one and the same story.
Why should this story be split between multiple tools and multiple channels?
What if, instead of multiplying channels, we organized information within the same space?
This is the principle that we chose with FaceCollectivité.
For each project, a face-to-face thread brings together targeted exchanges organized by theme.
In this same workspace, the audience for each exchange can be chosen à la carte: private, in a subgroup or more widely shared.
Messages, tasks and documents thus remain linked to the context in which they were created.
Next to the face-to-face thread, the General channel stores communications intended for the entire project team, with its own memory.
The user is no longer asked to constantly choose in which tool work.
We essentially ask him:
What subject are we talking about? Who is this exchange aimed at?
It’s an architectural difference.
Spread less so you have less to search for
For a long time, we have tried to solve information overload by asking users to better manage more and more tools, channels and information.
Perhaps we should now ask the opposite question:
What if we started by stopping spreading information?
Because the problem is perhaps not only that we produce too much.
It is perhaps also that our digital environment forces us to search, copy, transfer and reconstitute what we have already produced.
The challenge of tomorrow will therefore not only be to reduce information.
It will be to give it continuity.
Less dispersion.
Less research.
Less reconstruction.
And more collective memory.
