> 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/change-and-agility.md). # Change & Agility Preview the action plans available for Change & Agility 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 %} *** ### Recent changes show we are heading in the right direction | Plan | Approach | Focus | | ------------------------------------------------ | --------- | ----------------------------------------------------------------------------------- | | **Making the Case for Change Your Team Can See** | Behavior | Connects recent changes to outcomes your team has actually experienced. | | **Building a Change Scorecard for Your Team** | Structure | Creates a lightweight tracking system that makes change outcomes visible over time. | *** ### We plan for change before it becomes urgent | Plan | Approach | Focus | | ----------------------------------------------------- | --------- | ---------------------------------------------------------------------------------- | | **Getting Ahead of Change Instead of Reacting to It** | Behavior | Introduces forward-looking conversations so the team stops feeling blindsided. | | **Building a Team-Level Change Readiness Process** | Structure | Creates a repeatable planning step the team follows before any significant change. | *** ### Leaders listen to employees to make changes work better | Plan | Approach | Focus | | ------------------------------------------------------------ | --------- | ---------------------------------------------------------------------------------------- | | **Turning Employee Input into Visible Change Decisions** | Behavior | Demonstrates that employee input directly shapes how changes are implemented. | | **Embedding Employee Voice into Your Team's Change Process** | Structure | Creates a structured role for employee input in every significant change the team faces. | *** ### What I've seen here makes me trust future changes will be handled well | Plan | Approach | Focus | | ------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------- | | **Earning Trust Through Small Changes Done Well** | Behavior | Builds change confidence by demonstrating competence on changes within the team's control. | | **Creating a Team Playbook for Handling Change** | Structure | Builds a shared, repeatable approach so change stops feeling random and starts feeling managed. | *** ### Senior leadership will act on issues identified in this survey | Plan | Approach | Focus | | ----------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------- | | **Making Survey Follow-Through Visible to Your Team** | Behavior | Closes the gap between what was raised in the survey and what the team has seen happen since. | | **Building a Survey-to-Action Accountability System** | Structure | Creates a visible tracking mechanism that holds survey commitments to the same standard as business deliverables. | --- # 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/change-and-agility.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.