> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v1.5/community/committee/idea-management-process.md). # Idea Management Process Idea Management Process for Digital Product Advisory Committee ## Introduction This document outlines a systematic approach to manage and evaluate new ideas for product development coming from the members of the DPAC. It is meant to serve as a guide for product managers to effectively assess and decide whether to implement these ideas into the product. ## Process Overview #### Step 1: Idea Submission and Documentation The DPAC members are encouraged to use the [Idea submission form](https://forms.gle/M3RABxBBRNTHRtFN6) to submit new ideas which will be documented in a central repository. #### **Step 2: Initial Review** All submitted ideas will undergo a preliminary review to check alignment with the overall goal, outcomes, problem addressed and the product’s roadmap. Any idea that does not align with the strategic objectives of the product will be dropped after deliberation with the DPAC. #### **Step 3: Prioritisation and Feasibility Analysis** The remaining ideas that pass the preliminary review are then prioritised based on their potential to solve a specific problem and deliver impact on the ground. --- # 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.digit.org/health/v1.5/community/committee/idea-management-process.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.