Back to the blog

Shared memory

Connected tools. Shared history still fragmented.

Our digital tools communicate better and better with each other. Yet the history of work often remains scattered.

6 min read

Because connecting tools does not mean bringing together their memories.

Information retained
A story to bring together

Today, our tools are increasingly connected.

A document can be shared in a conversation.
A task can be created from an exchange.
A file can be found from several applications.
A notification may appear in different spaces.

Everything seems connected.

And yet, when we ask a very simple question —

“Where is the full story of this project at”

— the answer becomes much less obvious.

Because connecting tools does not mean bringing together their memories.

The same project can live in several locations

Let's take a very concrete project.

  • A first request arrives by email.
  • The team starts talking about it in Teams.
  • A document is deposited in SharePoint.
  • A task is created in Planner.
  • An important clarification is given in another exchange.
  • A few weeks later, a new version of the document appears.

Everything works.

Each tool does its job correctly.

But gradually, the history of the project is divided.

  • Part of the story is in the messaging.
  • Another one in the conversations.
  • Another one in the documents.
  • Yet another one in the tasks.

The tools are connected.

But their histories remain separate.

The problem appears when we have to understand the past

As long as the project is progressing and everyone is present, this dispersion may seem bearable.

People remember the context.

  • They know why a document was created.
  • They know that a task follows a meeting.
  • They remember that an important decision was taken three weeks previously.

But a few months later, the situation changed.

  • A new collaborator joins the project.
  • A manager takes over the file.
  • A decision must be justified.
  • An old version must be found.

A simple question appears:

Why did we make this choice?

And that’s when the research begins.

  • You have to open several tools.
  • Reread conversations.
  • Find emails.
  • Compare documents.
  • Search for a task.
  • Reconstruct the order of events.

In other words:

the system has preserved the information, but it has not necessarily preserved its history.

To preserve is not to tell

This is probably one of the great confusions in today’s digital world.

We store a lot of information.

  • We keep the messages.
  • We archive the documents.
  • We save the tasks.
  • We keep the exchanges.

But an accumulation of information is not yet a memory.

A memory becomes really useful when we can find:

  • what happened;
  • in what order;
  • with whom;
  • why;
  • with what decision;
  • with which document;
  • and what action resulted from it.

In other words, memory does not consist only of retain elements.

It consists of retain their links and context.

A connection between tools does not automatically create a common memory

This is where the subject becomes important.

When a document is visible from a conversation, this obviously makes work easier.

When a task can be linked to an exchange, this is also useful.

But this does not necessarily mean that the entire project now has a unique story.

Each environment often continues to maintain its own history.

The conversation tells the conversation.

The documentary tool narrates the documents.

The task manager narrates the tasks.

Messaging tells messages.

These are several memories that coexist.

The user still has to make the connection.

The user becomes the link between the tools

This is probably the most important point.

When the histories remain separate, it is the user who reconstructs the continuity of the project.

  • It is he who remembers that a document corresponds to a previous discussion.
  • He is the one who knows that a task results from a decision.
  • It is he who finds the email which explains why this task exists.
  • It's him again who tells the story to a new person.

In a way, the employee himself becomes the linking system between the different tools.

As long as he knows the file perfectly, it works.

But when projects become long, complex or collective, this dependence becomes fragile.

What if the project directly had its own memory?

There is another way of thinking about digital work.

Instead of asking:

“What tool should I work in”

we can start with another question:

“What project and subject does this information belong to”

In this logic, messages, tasks and documents no longer exist as independent elements.

They become different stages of the same story.

  1. A request leads to a discussion.
  2. The discussion leads to a decision.
  3. The decision results in a task.
  4. The task produces a document.

And all these steps remain attached to the same context.

The project no longer simply has information.

It has a memory.

This is the principle of FaceCollectivité

FaceCollectivité was designed around this simple idea:

organize before exchanging.

Each project has its own workspace.

Within the face-to-face thread, the exchanges are organized by theme.

Each exchange can have its own audience: private, subgroup or collective.

Messages, tasks and documents remain associated with the story in which they appear.

The General channel, intended for communications for the entire project, retains its own memory.

The objective is therefore not only to bring together more functions in a platform.

The objective is different:

maintain the continuity of the work.

The next step in digital may not be to better connect tools

We have worked a lot in recent years to connect applications.

It was necessary.

But a new question now appears:

where is the project memory located?

Because an organization can have perfectly connected tools while continuing to disperse its history.

The real evolution could therefore be to move on to:

of tools connected to each other to work organized around a common memory.

Because at the end of the day, what we have to find several months later is not just a message, a task or a document.

It is the story that connects them.