Propose new features
Designing Decidim together
User flow / guidance tool
This proposal is being evaluated
This proposal is affected by the redesign process and will be used as feedback for the design team.
Report inappropriate content
Is this content inappropriate?
You are seeing a single comment
View all comments
Conversation with Pierre Mesure
Hi Antti, I fully agree with you. It's especially relevant when we talk about participatory budgets because they are have many different phases and require different functions/views at each step. Expecting someone to click the right tabs/buttons is delusional.
I guess a way to guide them a bit better is to rename the tabs of a process each time you change phase to give the relevant one (e.g voting module) more importance. But it requires the civil servants to master the admin page, which they do not always do. In general, there should be a better way to hierarchize the tabs of a process. Right now, it's all the same font, same size and removing the icons made them really hard to see for new users.
I guess the CTA button should help to direct your users where they can perform an action but I'm not sure if it's used so much right now?
Hi Pierre! Yes, guidance within a single process itself is already a challenge - most of the time the hard part is the "Process" tab which rarely adds much value to the process itself. In my opinion, the first tab should always be the phase that is active, the information tab could be the last tab.
The problem, however, is wider when you have an active budgeting phase in multiple components at the same time. This is the case e.g. with Helsinki where they have separated each major district of the city to their own processes because all the areas have their own budgets, ideas, etc. In this particular case, the desired user flow would be:
1. Select a district (process in this case)
2. Perform the action of the active step (ideation, budgeting, etc.)
The second level navigation of the process is just confusing the users since it can distract them away from what they came to do. They came to do the budget and they already selected an area - the user's attention should be focused there.
And also, since the user is anyways required to authorize themselves to perform budgeting, why not already require them to do that when they select an area (a process).
The combiled budgeting module we built for this purpose sets the flow as follows:
3. Area/process selection (only the ones where you are allowed to vote based on the authorization)
4. Perform the action
This prevents the user from getting lost in the system for the preferred action they want to perform. The only problem with the module is that it is tied to the budgeting module (because of the mentioned limitations), so it can only be applied to the budgeting process.
Loading comments ...