Open Collective Docs
Go back to Open Collective
Search…
Welcome
About
Introduction
Documentation
Terminology
Company
Pricing
Team
The Open Collective Way
Hiring
Investors
Contributing
Product
Features
Roadmap
Comparison
User Profile
Currencies
Log-in System
Privacy Policy
Moderation
Security
Notifications
Two-factor Authentication
Collectives
Collectives FAQ
Creating a Collective
Quick Start Guide
Collective Settings
Add Fiscal Host
Change Fiscal Host
Open Source Collectives
Transparent Budget
Expenses
Updates & Comms
Custom Email
Moderation
Conversations
Events
Projects
Funding Options
Buttons & Banners
Connected Collectives
Contribution flow
Financial Contributors
Financial Contributors FAQ
Guest contributions
Payments
Crypto Contributions
Website Badge
Receipts
Collective to Collective
Organizations
Expenses & Getting Paid
Expenses FAQ
Submitting Expenses
Virtual Cards
Expense Comments
Edit or Download an Expense
Receiving payment through Payoneer or Wise
Tax Information
Fiscal Hosts
Fiscal Hosts FAQ
Becoming a Fiscal Host
Creating a Fiscal Host
Organisation Settings
Fiscal Host Dashboard
Receiving Money
Payouts
Host Fees
Local Tax Support
Agreement Templates
Independent Collectives
About Independent Collectives
Create an Independent Collective
Independent Collective Setup
Independent Collective Management
Close an Independent Collective
Developers
Contributing
Design
Development
Documentation
Translation
Powered By GitBook
Roadmap
You'll find below guidelines for prioritizing features and projects as well as a template for new projects.

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?

  • 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
Product - Previous
Features
Next - Product
Comparison
Last modified 1mo ago
Export as PDF
Copy link
On this page
Key questions for prioritization
Template for new projects