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

# Supervision

Preview the action plans available for Supervision 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 immediate manager inspires the people in my team

| Plan                                                      | Approach  | Focus                                                                                           |
| --------------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------- |
| **Leading with Purpose, Not Just Tasks**                  | Behavior  | Connects daily work to meaning so the team sees why their contributions matter.                 |
| **Building a Leadership Rhythm That Energizes Your Team** | Structure | Replaces ad hoc management with consistent practices that give people direction and visibility. |

***

### My immediate manager does an effective job of leading our team

| Plan                                                          | Approach  | Focus                                                                                           |
| ------------------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------- |
| **Strengthening Day-to-Day Leadership Effectiveness**         | Behavior  | Targets the specific leadership behaviors that make teams feel well-led, not just well-managed. |
| **Building the Operating System Behind Effective Leadership** | Structure | Installs the structural practices that turn good intentions into consistent leadership.         |

***

### My immediate manager supports my growth and development

| Plan                                                             | Approach  | Focus                                                                                       |
| ---------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------------- |
| **Making Growth Conversations a Regular Habit**                  | Behavior  | Turns development from an annual event into an ongoing part of how you lead.                |
| **Embedding Growth and Development Into How Your Team Operates** | Structure | Builds development into team structures so growth isn't dependent on one-off conversations. |

***

### My immediate manager does a good job of coaching and guiding me

| Plan                                                           | Approach  | Focus                                                                                   |
| -------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------- |
| **Shifting From Telling to Coaching in Everyday Interactions** | Behavior  | Builds coaching into daily management so people develop while getting work done.        |
| **Building a Coaching Culture Within Your Team**               | Structure | Creates team-wide coaching structures so guidance doesn't depend solely on the manager. |

***


---

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