> 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/innovation.md). # Innovation Preview the action plans available for Innovation 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 %} *** ### I am encouraged to make decisions that improve my work outcomes | Plan | Approach | Focus | | ------------------------------------------------------ | --------- | -------------------------------------------------------------------------------------------------------- | | **Giving Your Team Real Permission to Decide** | Behavior | Replaces the habit of seeking approval with clear signals that decisions belong to the team. | | **Building a Decision-Rights Framework for Your Team** | Structure | Creates a durable structure that clarifies who decides what, so empowerment isn't personality-dependent. | *** ### Our organization helps employees learn new skills as part of the job | Plan | Approach | Focus | | ---------------------------------------------------- | --------- | ---------------------------------------------------------------------------------------- | | **Making Skill Building Part of Everyday Work** | Behavior | Turns daily work into learning opportunities without adding programs or formal training. | | **Embedding Skill Development Into Team Operations** | Structure | Creates a repeatable system for learning that survives beyond any one manager's effort. | *** ### Our organization trains employees to use emerging technology (AI, new machinery, etc.) | Plan | Approach | Focus | | ------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------- | | **Learning New Technology by Actually Using It** | Behavior | Replaces passive training with hands-on experimentation the team controls. | | **Building a Technology Learning System for Your Team** | Structure | Creates an ongoing structure for technology adoption so training isn't a one-off event. | *** ### People are encouraged to test ideas that could make us better | Plan | Approach | Focus | | ----------------------------------------------- | --------- | ------------------------------------------------------------------------------ | | **Making It Normal to Test Ideas on This Team** | Behavior | Removes the informal barriers that keep good ideas from being tried. | | **Creating a Team Experimentation Practice** | Structure | Builds a repeatable process for testing and adopting new ideas as a team norm. | *** ### Failure is seen as a chance to learn and improve | Plan | Approach | Focus | | --------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------- | | **Changing How Your Team Responds to Failure** | Behavior | Shifts the team's default reaction to mistakes from blame to learning. | | **Building Failure-to-Learning Processes Into Team Operations** | Structure | Creates repeatable rituals that make learning from failure a structural default, not a personality trait. | *** ### We regularly adopt new and improved ways to work | Plan | Approach | Focus | | -------------------------------------------------------------- | --------- | ------------------------------------------------------------------------------------- | | **Breaking the Inertia of "How We've Always Done It"** | Behavior | Targets the habits and defaults that keep teams stuck in outdated work patterns. | | **Establishing a Continuous Improvement Rhythm for Your Team** | Structure | Creates a recurring system for evaluating and upgrading how the team works over time. | --- # 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/innovation.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.