0/ Summary
This case study covers adding a new administrative feature to the software. The design is still in use. Final prototype can be found here.
PROCESS
- Competitive analysis
- Desktop research
- Wireframing
- Prototyping
- Usability testing
- Designing UI
DELIVERABLES
- Design iterations
- Usability test reports
- UI designs
OUTCOMES
Multiple rounds of user testing gave us a confident design to lead with. In live the design performed well and was a part of a successful product launch.
1/ Understanding the need
NEW PRODUCT LAUNCH
Together with a new launch there was a need to add some additional functionality to the web app interface. One of the most important ones was adding a new administrative functionality for editing user groups and permissions.
This brief was given to me by the product manager, it was also added that we had a very strict deadline for the product launch.
RESEARCH
After gathering enough information from the product manager I started desktop research, first focused on looking at the industry by researching what solutions the competitors are using and then went forward with more broader desktop research to look at the current UI trends.
2/ Design phase
TEAM WORK
I sat together with the mobile app UX/UI designer and a design intern to quickly kick off a brainstorming session and come up with a feasible design solution with the tight deadline in hand.
USABILITY TESTING
Due to the time constraints first rounds of usability testing were done in house with 7 colleagues who had not seen the designs before. Collecting insights from these sessions another iteration of the design was created which again was put through usability testing. Third iteration of the design went through remote usability testing with 3 real users of the software. Only minor UI fixes were made for the final iteration.
3/ Final iteration
Final iteration of the design that was handed over for development and was successfully implemented for the product launch.
4/ Outcomes
As user group and permission administration was a new feature there were no numbers to benchmark the solution against. There was a need for the feature, because of growing number of different types of users of the software. After 3 iterations of usability testing in house and remotely the final iteration proved to be intuitive and fit the general design guides of the company. This feature was a part of a successful product launch and it is still in use today.
