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

# Collaboration

Preview the action plans available for Collaboration 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.&#x20;
{% endhint %}

***

### There is good cooperation between my team/department and other teams/departments

| Plan                                              | Approach  | Focus                                                                              |
| ------------------------------------------------- | --------- | ---------------------------------------------------------------------------------- |
| **Becoming the Team Others Want to Work With**    | Behavior  | Improves cross-team cooperation by changing how your team shows up as a partner.   |
| **Building Reliable Systems for Cross-Team Work** | Structure | Creates lightweight structures that prevent the most common cross-team breakdowns. |

***

### People in our organization share their knowledge willingly

| Plan                                                        | Approach  | Focus                                                                                                |
| ----------------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------- |
| **Making Knowledge Sharing the Team Default**               | Behavior  | Shifts the team norm from hoarding expertise to sharing it openly.                                   |
| **Creating a Team Knowledge System That Survives Turnover** | Structure | Captures institutional knowledge in lightweight formats so it doesn't walk out the door with people. |

***

### There is a strong feeling of team spirit and cooperation in our organization

| Plan                                                   | Approach  | Focus                                                                                             |
| ------------------------------------------------------ | --------- | ------------------------------------------------------------------------------------------------- |
| **Rebuilding Team Spirit Through Shared Wins**         | Behavior  | Strengthens connection and cooperation by making the team's shared accomplishments visible.       |
| **Designing Rituals That Build Lasting Team Cohesion** | Structure | Replaces one-off team-building with recurring structures that sustain cooperation and connection. |


---

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