> For the complete documentation index, see [llms.txt](https://innowayit-1.gitbook.io/framework/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://innowayit-1.gitbook.io/framework/use-cases/initiative-prioritization.md). # Initiative Prioritization An initiative is a: > a new plan or process to achieve something or solve a problem - Cambridge Dictionary An initiative can be a project, a program, a demand, a proof of concept or simply a change request. Initiatives are time-limited undertakings and are primarily intended to improve existing or develop new people, process and technological capabilities that will help the organization achieve its business objectives. Not all initiatives are equal with some having priority over others. Initiatives should be evaluated and prioritized to ensure that those with clear business value are treated as more important and take precedence over others. An objective prioritization model is needed that uses the following factors to prioritize initiatives. 1. Alignment of business and IT 2. Impact on capability 3. Technology impact 4. Risk mitigation 5. Clear business benefits A score is assigned to categorize initiatives based on the score. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://innowayit-1.gitbook.io/framework/use-cases/initiative-prioritization.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.