> For the complete documentation index, see [llms.txt](https://docs.opencollective.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencollective.com/help/product/roadmap.md). # Roadmap You'll find below guidelines for prioritizing features and projects as well as a template for new projects. [View our Roadmap updates on our Github](https://github.com/opencollective) ## **Key questions for prioritization** **This is what we ask ourselves to decide what gets done and what doesn't.** * Does this serve our mission? * Will this help to make us financially sustainable within a year? * Can this make us move faster? * Does this increase quality? * Does this add technical debt? * Is it feasible to build and maintain with our current team and runway? * What insight or research is this project based on? * Is this problem already solved elsewhere? * How will we measure our success? Do we have a baseline today that we can compare this against? * How well do we understand the complexity of the problem, feature to be added or user needs to be addressed? * What is the estimated timeframe for delivering this project? ## Template for new projects * Github issue * explains the feature. * Link to other opened issues or data. * Include details below. * Kickoff * Organize a special meeting or a scheduled one. * Project owner. * Role: Facilitator, decision-maker, producer. * It's ultimately responsible for (needs to do or organize who does) * Delivery * Q\&A * Docs & Comms * Post-ship plan for maintenance * Success metric(s) * Timeframe - kickoff and delivery, main milestones/roadmap --- # 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.opencollective.com/help/product/roadmap.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.