> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/centre-d-accompagnement/outils-concurrents.md).

# Identify competing tools to Steeple

### Diagnose what exists before centralizing

Reminding everyone to go on Steeple with no results? Often, it’s because a multitude of tools coexist and confuse teams. Before centralizing internal communication, **you need to diagnose what actually exists**.

### 1. Audit current internal communications

#### Objective

Get a **clear view of the internal communication ecosystem**. Many underestimate the number of channels actually used on a daily basis.

#### Concrete actions

* **Map the channels used** : emails, WhatsApp, notice boards, meetings, Slack, Teams…
* **Identify who communicates, about what, and to whom** : management, HR, QHSE, managers…
* **Detect redundancies, silos, irritants** : duplicate sends, forgotten information, confusion…
* **Diagnose the tools that are competing with Steeple today**

### 2. Examples of tools competing with Steeple

| Tool                 | Common problems                                | What Steeple brings                                            |
| -------------------- | ---------------------------------------------- | -------------------------------------------------------------- |
| Notice boards        | Only on-site, difficult to update, no stats    | Interactive digital display, accessible everywhere, measurable |
| Internal newspapers  | Cold information, not measurable, costly paper | Engaging digital publication, up to date, no printing          |
| Flyers and brochures | Non-interactive, no tracking                   | Digital distribution, reminders, stats, integrated sign-ups    |
| Paper suggestion box | Lost suggestions, no data                      | Digital module, voting, idea tracking                          |
| Verbal communication | No traceability, limited memory                | Searchable history, possible interactions                      |
| Internal emails      | Not very engaging, not universal               | Visual communication, measurable, no professional email needed |
| Dynamic display      | Limited to on-site screens, non-interactive    | Interactive multichannel distribution with stats               |
| HR/feedback tools    | Few responses, not integrated into daily life  | Integrated feedback, more participation                        |
| Intranet             | Rarely consulted, complex                      | Modern, intuitive interface, accessible to everyone            |
| WhatsApp groups      | Poorly controlled, mixing work and personal    | Professional, structured, traceable channel                    |
| Internal chats       | Information overload, loss of key messages     | Official, hierarchical communication                           |
| Shared drives        | Limited visibility and use                     | Highlighting key documents, integrated statistics              |

### 3. Centralize to better distribute

Carry out the audit. Identify duplicates. Measure what is polluting internal channels.

The challenge: that everything can be said **in the right place, at the right time, to everyone**. With Steeple, communication is simplified and structured.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.steeple.com/en/centre-d-accompagnement/outils-concurrents.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.