> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/managers-and-leaders/take-action/action-planning-in-compass/action-plan-template-library/action-planning-library-preview/communication.md).

# Communication

Preview the action plans available for Communication survey questions. Each question offers a behavior plan and a structure plan. Full plans open inside Compass Action Planning.

{% hint style="info" %}
**Module required.** Your organization needs the Action Planning module enabled in Compass to open these plans.
{% endhint %}

***

### In general, information in our organization is communicated well

| Plan                                                          | Approach  | Focus                                                                                       |
| ------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------- |
| **Replacing Information Guessing with Communication Clarity** | Behavior  | Targets the everyday manager habits that leave people filling in the blanks.                |
| **Building a Communication Rhythm the Team Can Count On**     | Structure | Replaces ad hoc updates with a predictable communication structure that people can rely on. |

***

### Our organization has adequate procedures for sharing information

| Plan                                                       | Approach  | Focus                                                                                     |
| ---------------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------- |
| **Turning Information Hoarding into Information Sharing**  | Behavior  | Shifts everyday team behaviors so sharing becomes the default, not an afterthought.       |
| **Building a Team Knowledge Base That Actually Gets Used** | Structure | Creates a lightweight system so critical information is findable, not trapped in inboxes. |

***

### Information is widely shared so that everyone can get the required information when it's needed

| Plan                                                              | Approach  | Focus                                                                                                             |
| ----------------------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------- |
| **Making Sure No One Is the Last to Know**                        | Behavior  | Addresses the uneven information access that leaves some team members consistently out of the loop.               |
| **Designing Information Flow So Access Isn't Based on Proximity** | Structure | Restructures how your team distributes information so that access depends on need, not location in the hierarchy. |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talentmap.com/knowledge-base/managers-and-leaders/take-action/action-planning-in-compass/action-plan-template-library/action-planning-library-preview/communication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
