Help
A participatory process is a sequence of participatory activities (e.g. first filling out a survey, then making proposals, discussing them in face-to-face or virtual meetings, and finally prioritizing them) with the aim of defining and making a decision on a specific topic.
Examples of participatory processes are: a process of electing committee members (where candidatures are first presented, then debated and finally a candidacy is chosen), participatory budgets (where proposals are made, valued economically and voted on with the money available), a strategic planning process, the collaborative drafting of a regulation or norm, the design of an urban space or the production of a public policy plan.
Co-creating the roadmap
Propose and vote for the features you’d like to see in future releases!
About this process
Each year we open a community process to propose, discuss, and vote on new features for the roadmap. Everyone in Metadecidim can participate, while Decidim members and partners play a special role in refining and voting proposals. According to the internal regulations, during this cycle we define:
Strategic Directions: These are broad orientations on what we think are the most important aspects for the product and maintenance teams should focus on.
Features: Once we prioritize the main strategic directions, we will propose and vote (at least once a year) on the features aligned with them.
Here’s an overview of when and how you can take part:
Phase 1: Propose strategic directions
The Product Team kicks things off by suggesting a few starting lines, and everyone in the community is welcome to add their own ideas for additional directions.
Phase 2: Prioritize together
Members of the Decidim Association can vote to decide which directions matter most. Each member has up to 5 votes to distribute across proposals.
Phase 3: Share your feature proposals
Once the strategic directions are set, the whole community is invited to bring forward their best ideas for new features or improvements. Each participant can submit up to two proposals, with a maximum of two per organization.
Phase 4: Define sizes
The Product team will review the proposals and give an estimated effort in definition and development.
Phase 5: Vote on proposals
Association members then vote for their favorite proposals. Each member has up to 5 votes, and any proposal that gathers at least 10 votes will move forward for implementation.
Finally, the Product Team reviews the results and officially announces which proposals will be part of the next development cycle. These proposals are then prepared for implementation together with partners, developers, and funders. Progress and updates will be shared in the comments section of each selected proposal, so everyone can follow along.
.png)