> 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/my-team.md). # My Team Preview the action plans available for My Team 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 team continuously strives to improve our performance | Plan | Approach | Focus | | ------------------------------------------------------------------ | --------- | -------------------------------------------------------------------------------------------------------- | | **Making Continuous Improvement a Team Habit** | Behavior | Turns performance improvement from a manager-driven initiative into a visible, recurring team behavior. | | **Building a Performance Improvement Rhythm into Team Operations** | Structure | Embeds structured improvement cycles into existing team routines so they persist without manager effort. | *** ### People in my team take personal ownership of their work responsibilities | Plan | Approach | Focus | | ------------------------------------------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------- | | **Building Real Ownership, Not Just Task Completion** | Behavior | Surfaces unclear expectations and makes ownership visible across the team. | | **Redesigning Work Structures to Make Ownership the Default** | Structure | Changes how work is assigned and tracked so personal ownership is built into the system, not dependent on individual initiative. | *** ### People in my team frequently go above and beyond the requirements of the job | Plan | Approach | Focus | | ---------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------- | | **Recognizing and Reinforcing Discretionary Effort** | Behavior | Makes above-and-beyond contributions visible and valued so they become a team norm, not a personal sacrifice. | | **Removing the Barriers to Discretionary Effort** | Structure | Addresses the structural reasons people stop going the extra mile by fixing workload, autonomy, and incentive misalignments. | --- # 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/my-team.md?ask=&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.