Why we decided to go with the final idea?
Decision making factors
As we knew the objective of the Run analysis dialogue box and what exactly we would want the user to accomplish over there, we were quite a few steps closer to the solution. Check out the link first to understand this article better “UX evaluation of Run analysis_AIP Console”
Through this dialogue box, basically we are processing or publishing the data/results to some tools.
The first point was to change the title name and button name to make the action more clearer.
The second point was to just show the current version. Hence decreasing one step for the user and making it more efficient by allowing the user to accomplish the task sooner. #Efficiency #Minimalism
The third point was to give the user choice and flexibility of keeping the back up through the interface. By displaying the estimated time, it will make it easier and quicker to decide whatever choice he wants to make. #Flexibility
The fourth point was to make user aware of the actions and what’s happening behind it by using information icon. #Awareness
The fifth point was to show the steps in progressive way based on the users’s goals. #Less_cognitive_load #Focus #Minimalism
The sixth point was to include the redo and undo action for the user if they want to retake the specific action. #Clarity #Familiarity
There were 3 ideas after a bit of iteration and discussion.
The point which has to be considered from the team’s side was to keep it consistent in terms of component as it’s a part of the existing product.
1.The first idea was to maintain the familiarity and then improve upon the UX /UI points as mentioned above. Reference image IDEA1
2. The second idea was from “execution perspective”. By dividing it into clearly different sections based on the schema where we would like to process or publish the result. Schema is a logical representation/grouping of data in a database. There are 3 schemas :
1. Local schema where we process the result of analysis.
2. Central schema where we process the result of snapshot.
3. Measurement schema where we have multiple snapshots stored.
4. Management schema where we have technical information of the source code and it contains all the above three schemas.
The problem with this idea was specially with the title name. As local, central and measurement schema are very technical name and the user might not understand it. Reference image IDEA 2(a)
So we decided to make it more functional and replaced the titles by the service name as Analysis service, Dashboard service, Measurement service, Imaging solution. The specific tools (where we publish the results) fall under these categories. Reference image-IDEA 2(b)
In this idea, the accordion has been used to display one task at a time and the user can choose to expand the accordion based on where he wants to process/publish the data.
The good part here was to clearly distinguish/group the information on the basis of the tools. But the bad part of it is space consumption and the use of more ink even when the first few tasks are same for all.
3.In the third idea, three cards have been used and placed parallely to make it easier for the user to see all the info in chunks and take the action accordingly.
The problem in the third idea is that it was a bit far from what we have right now. So people might have taken time to get used to it, hence reducing the task efficiency. The other point is, apart from these three specific tools, the data is being consumed in some or other way which won’t be clear through this idea.Reference image- IDEA 3
From UI perspective as well, the issue was the first few steps are same for all three. Let’s say, I want to publish it in Engineering dashboard and I choose to go with the second card.
As you can see in the third card, to publish the result in Health dashboard, I need to follow the same step of taking the snapshot. If I have already taken the snapshot to publish it in the Engineering dashboard, in UI card it should reflect automatically in the third card which is Health dashboard. It might create confusion for the user.
Considering all the three ideas and their pros/cons, the decision has been made to go ahead with the first idea and discarding the other two ideas.
Stay tuned to explore the first idea.
