🎨 Community participatory process for contributing to the Decidim redesign
Hierarchy of actions
Over the past few weeks, we've had some discussions with the redesign team that we want to share with the community.
When we have started to review the detail page of the “Proposals” component, we have realized that we need to establish another hierarchy between the different actions that can be enabled.
We start from the analysis that the current layout of the buttons generates confusion and saturates the interface. Therefore, we think that we have to establish a hierarchy and perhaps rename some of the actions. All this with the aim of simplifying the interface and clarifying what each action is for.
The hypotheses* with which we are working are:
- That some actions lose weight and move to a more secondary level.
- Rethink the name of the “endorsements” and change it to a more intuitive one.
- Remove the counter for the number of "Followers" and rename it, since we have detected that it can be confused with the number of supports and/or adhesions.
- Separate the “Turn on notifications” action from the “Mark as favorite” action.
*These are hypotheses we are working on and are not definitive. Soon we will share a mockup with the latest advances in the redesign.
The debate was closed on 05/09/2022 11:27 with these conclusions:
Thank you all for your contributions!
- According to your experience, how do you understand the action of endorse? How would you improve it?
- Should endorsements and supports coexist?
- What action do you consider to be the most important within the proposal component?
- Do you think it should be possible to support without reading the description of the proposal?
List of Endorsements
Report inappropriate content
Is this content inappropriate?
What is the summary or conclusion of this debate?
You are seeing a single comment
View all comments
Yep, this is the problem with this feature that it is so context specific, depending how it is used. In some context, "vote" is more appropriate, in some context "support" is more appropriate and in some context "like" is more appropriate (i.e. showing there is interest for this particular proposal/idea, not "voting" on it).
The problem with the "vote" terminology would be in a standard PB process where the "voting" generally refers to the PB voting phase (=budgets).
In Finland we have used this feature once for the purpose of showing the city officials what type of ideas generate most interest. It caused confusion among the participants as some thought that "supporting" means "voting" the idea and then they later found out that there was a separate PB voting phase (=budgets) after the voting had already closed.
We listened to the people and later decided not to use this feature at all. The less different actions there are, the clearer it is for the users what is expected from them.
Loading comments ...