Propose new functionalities for Decidim software
#DecidimRoadmap Designing Decidim together
**Need**
A client wants to configure a process so that from a set of proposals, users can evaluate its importance with a 1-10 scale, not just with a simple support action as now. This way, when aggregating all evaluations we have a better understanding of the grade of importance to the community.
**Implementation idea**
Extend the current support action (votes). You could configure the Supports as Normal (currrent), or Scale, which by default would provide a 1-10 scale.
**UX**
When configured as Scale, users would be shown something like:
----
"Evaluate the importance of this proposal"
[less important --------- more important]
1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10
----
**Admin**
for each proposal admins would be shown the average evaluation, and maybe the # of votes for each scale step. Also we could provide a way to export the results as CSV for further analysis in external tools.
If this is interesting, the extension of support modes ideally would support N modes, so others can implement other ways of evaluating. Although this would make more complex the implementation.
Also, ideas about the best way to implement this are more than welcome.
Funding available (for a basic implementation)
This proposal has been accepted and is under development
Report inappropriate content
Is this content inappropriate?
15 comments
Conversation with Pau Parals
I like it! Just to know, do u think that condorcet voting would fit betther rather than this? You can finde more info in this proposal: Condorcet voting
Thanks Pau! In our case we don't necessarily need to choose a winner, we just want to know how people feel about the presented issues with more granurality than a simple vote.
Thinking about how Condorcet could be implemented I also see it a little bit more cumbersome in regards to UX. Each option would be a proposal, and then you would assign the position for each? This calls for a specific UI ...
Conversation with álvaro ortiz
Here is a draft of how this could work: https://user-images.githubusercontent.com/24740/69743328-88dc3980-113e-11ea-8f32-c48856b2f1c0.png
@furillo Love the functionnality but I'm a bit confused by the mockup.
Why are they so many scales, Couldn't we make one card to rule them all ?
@virgile_deville I think @furilo's mockup is showing the different steps, but there will be just one card :)
Some feedbacks on the design:
- The mockup displays the Supports/Endorsements card on the bottom left. Do we agree the evaluation scale could be on the same one, back on the top right, isn't it?
- For accessibility reason, I fear the "- importancia +" text is too small/light. A darker grey would add more contrast.
- Another cool option could be to go from red to green when the grade is higher?
Yes, they represent the different states, and the bottom-left card is just a leftover (did I mention it was a quick-hacky test? ;)
Here is another iteration, with the 3 states that we would have:
- by default
- when you have voted
- when you hover the "evaluate this proposal"
https://user-images.githubusercontent.com/24740/69748203-1a03de00-1148-11ea-8b62-af13e97a088b.png
Valentin:
- yes, we would give more contrast to that text.
- red-green: I fear that playing with colors may cause some confusion?
thanks for your reply and mockups!
Conversation with Carol Romero
Hi @furilo, thank you for the proposal. Having different support systems is very useful, so it is very welcome!
A few comments:
- The mockup states that when evaluating a proposal, the counter will show the evaluation made by the participant. However, we need to think of a way to also show the average evaluation that the proposal has received, and that this is configurable. In the same way as the supports, the admin can decide whether to show the full evaluations during or at the end of the process.
- As for the graphic proposal, we agree to use only the primary color and not the color scale to avoid confusion.
- We have also thought about the interaction from card M, which could have a CTA called "Evaluate" but that button would open the detail of the proposal to perform the action from there (not from the general proposal browser).
If you decide to move forward with the development of this proposal you can open an issue in github and we continue discussing the technical details.
@carol the EU Commission would like to finance this development. Only difference is they might want to have stars instead of the bars for the scale.But that's small customization they can have on their own instances. I tried to look in the decidim issues but didn't find one, I took the liberty of creating one, let's continue discussions there : https://github.com/decidim/decidim/issues/6844
Thanks @virgile_deville! Let's continue the discussion there
Hi all. I'm new here and am amazed and inspired by the use and community support for Decidim.
I agree that 5-star (score-voting) would be most intuitive as it matches with user experience on many other platforms that invite user reviews. I also suggest not just showing the count and average, but also bar graphs to show levels of opinion. You can see clear illustrations of the rational here: https://www.linkedin.com/pulse/5-star-rating-better-than-likes-up-down-voting-jason-diceman/
It's very exciting to see this in progress! I think it could be a gamechanger for increased validity of measuring levels of support for proposals.
Hi, love the idea, to give feedback in a different way! I just messed up with this dualistic scale system of translating emotions - as you said, how do some people feel about the issue. I would follow this dimension of feelings: -1,0,1,2 The minus, is an obvious stepback, at 0 nothing changed, 1 is a little step forward and 2 is strong step forward. And about the UX. I would hide all not first step necesarry information at the begining. It means only the thermometer (it is more concrete, ur even a curve), the name and the button. So if you have several areas to measure, you will have space. It will appear on click or on touch (so the information becomes meta - embed, referencia, etc). But I would defenately outbrake a bit the current strucuture of the scaling - putting mobile first! So when the app comes, we can have a great UX mobile friendly scale framework! Just one more thing. Make it possible to have option - NOTA, none of the above. Sometimes we just don't feel like dualism...
This comment section is very twitter like. I have to count while writing. What is the reason for having only 1000 space here?
Add your comment
Sign in with your account or sign up to add your comment.
Loading comments ...