> 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/belonging.md).

# Belonging

Preview the action plans available for Belonging 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 %}

***

### My colleagues make me feel included at work

| Plan                                                           | Approach  | Focus                                                                                                     |
| -------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------- |
| **Making Inclusion Visible in Everyday Team Interactions**     | Behavior  | Targets the small daily behaviors that signal whether someone is truly part of the team.                  |
| **Redesigning How Your Team Shares Information and Decisions** | Structure | Restructures communication and decision-making patterns so inclusion is built into how the team operates. |

***

### People in my team work effectively with each other regardless of our differences

| Plan                                                             | Approach  | Focus                                                                                                                 |
| ---------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------------- |
| **Building Effective Collaboration Across Differences**          | Behavior  | Focuses on the specific team interactions where differences create friction or disengagement.                         |
| **Restructuring Team Processes to Reduce Bias in Collaboration** | Structure | Redesigns assignment, feedback, and decision-making structures so collaboration quality doesn't depend on similarity. |

***

### Diverse identities, ideas and ways of thinking and working are valued at my organization

| Plan                                                                | Approach  | Focus                                                                                                        |
| ------------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------ |
| **Demonstrating That Different Thinking Is Actually Valued**        | Behavior  | Changes how the team responds to unfamiliar ideas, dissent, and different approaches to work.                |
| **Embedding Diverse Thinking into Team Decision-Making Structures** | Structure | Redesigns how the team makes decisions and evaluates contributions so diverse approaches get real influence. |

***

###


---

# 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/belonging.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.