Back to the blog

Project management

Ending operational information overload in local authorities

How to move from the vertical flow which buries messages to the horizontal flow which reveals blockages.

June 9, 202610 min read

The problem is not the lack of information. The problem is the organization of this information.

Visible expectations
Measurable blockages

Communities have never communicated so much. Emails, Teams, internal messaging, EDM, documentary spaces, meetings and monitoring tables have multiplied to facilitate collaboration between elected officials, management and services.

However, one observation remains: projects remain difficult to manage. Information circulates quickly, but delays nevertheless appear, requests sometimes go unanswered and responsibilities become unclear.

FaceCollectivité was born from this observation. Its purpose is not to add additional messaging, but to structure exchanges in order to make responsibilities, expectations and blockages visible.

Infobesite is not an excess of messages

The real problem appears when information arrives without sufficiently structured context. Before acting, teams must reconstruct what the tool has not organized.

What project is this?
What mission is involved?
Who made the request?
Who should respond?
What documents are associated?
Is a response still awaited?
How long ago?
The infobesite is not too many messages. It's too much context to reconstruct.

The vertical flow reaches its limits

In traditional tools, messages are stacked one under the other. A question is asked, then more messages arrive, a document is shared, another topic appears, and the answer is found further down the thread.

The more projects there are, the more expensive the reconstruction of the context becomes.

The FaceCollectivité model

An important exchange should never be separated from its context. Each exchange is structured from its creation and becomes a real block of work.

ProjetMissionSujetEmetteurResponsible recipientPeople in copyDocumentsDateStatutPossible deadline

The horizontal flow retains the link.

Left

The request

The subject, project, mission, issuer, documents and deadline remain visible.

Right

The answer

Even several days later, it remains linked to the initial request and its context.

Unlike the vertical flow which gradually moves the elements of the same exchange further apart, the horizontal flow permanently maintains the relationship between the question, the answer and the responsibility.

Transform waiting into a control indicator

As long as the response space remains empty, the system knows that an action is expected. Time no longer makes problems disappear: it reveals them.

Messages sent unanswered

Messages received not processed

Outdated stains

Pending missions

Risky projects

Blocked projects

In traditional tools, time buries exchanges. In FaceCollectivité, time reveals the blockages.

Practical case: the Alexandre Dumas School project

The mayor wishes to know the status of the surface area intended for a future school. In a traditional channel, the question can be moved away from its answer by other messages. In FaceCollectivité, the request is immediately structured.

Project: Alexandre Dumas School
Mission: Urban planning
Subject: Status of the surface
Issuer: Mayor
Recipient: Service concerns

The request remains visible. The answer comes to position itself opposite. Follow-up becomes immediate.

Collaborate and capitalize

FaceCollectivité facilitates daily exchanges and builds a structured memory: who asked, who responded, when, in what project, in what mission and with what documents.

Benefits for the community

For the mayor

  • Clear vision of risky projects
  • Quick identification of blockages
  • Better arbitration capacity

For the DGS

  • Strengthened coordination between services
  • Visibility on delays
  • Monitoring simplifies projects

For agents

  • Reduction of mental load
  • Less unnecessary searches
  • Responsibilities better defined

For the IT department

  • Better traceability
  • Consolidated project memory
  • More efficient management of exchanges

In conclusion

The digital transformation of communities is not just about accelerating communication. It consists of better organizing exchanges to know who is waiting for what, from whom, in what project and for how long.

Maintain the link between the request and the response
Clearly identify the responsible recipient
Preserve the context of each exchange
Transform time into a control indicator

A successful organization is not the one that exchanges the most. She is the one who knows precisely where her expectations, her responsibilities and her obstacles lie.

Book a mapping meeting