> 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/systems-and-resources.md). # Systems and Resources Preview the action plans available for Systems and Resources 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 %} *** ### The systems that I work with help me to do my job | Plan | Approach | Focus | | --------------------------------------------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------- | | **Identifying System Workarounds Your Team Has Learned to Live With** | Behavior | Surfaces the daily friction points in tools and systems that people have stopped reporting. | | **Redesigning How Your Team Evaluates and Adopts Tools** | Structure | Replaces reactive tool complaints with a structured approach to system decisions that includes the people who use them. | *** ### I have access to the information I need to do my job well | Plan | Approach | Focus | | ------------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------- | | **Eliminating the Information Bottlenecks on Your Team** | Behavior | Identifies where critical knowledge gets stuck with one person and makes it accessible to everyone. | | **Building an Information Architecture Your Team Can Actually Use** | Structure | Creates a sustainable system for organizing, sharing, and maintaining the knowledge your team depends on. | *** ### I receive enough training to do my job well | Plan | Approach | Focus | | ------------------------------------------------------------ | --------- | ------------------------------------------------------------------------------------------------------------------- | | **Closing the Training Gaps Your Team Isn't Talking About** | Behavior | Uncovers the specific skill gaps that make work harder and addresses them with targeted, team-led learning. | | **Building a Training Rhythm That Keeps Pace With the Work** | Structure | Creates an ongoing structure for identifying and closing skill gaps instead of relying on one-time training events. | *** ### Work processes in my department are highly efficient | Plan | Approach | Focus | | ------------------------------------------------------------- | --------- | --------------------------------------------------------------------------------------------------------------- | | **Finding and Fixing Your Team's Biggest Process Bottleneck** | Behavior | Targets the one recurring process that wastes the most time and fixes it with the team's direct input. | | **Building a Culture of Continuous Process Improvement** | Structure | Creates an ongoing mechanism for the team to identify, test, and implement process improvements systematically. | *** ### --- # 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/systems-and-resources.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.