I identified three different places where the same functionality was needed and gathered the requirements from the different teams. After writing test cases for the usability test, I created a prototype in Figma and conducted a usability test with 5 participants. During the test, issues with the functionality were raised and I made some adjustments. After analyzing the results of the second round of testing, I finalized the concept and designed the user interfaces. Before implementation, I gathered feedback from the UI design department.
Find the problem -> talk about it with UX colleagues -> create a concept -> build a prototype -> collaborate with the team -> get user feedback -> revise the concept -> test again -> decide on a solution -> UI design -> development/solution.
My tasks:
In the end, I achieved my goals - I revised the plan, adapted it so that users understood it, and inconsistencies in the software were reduced.
During the concept work for an MVP project, I came across an issue that is not specific to this part of the software. After a brief discussion with my UX colleagues, we discovered three different places where the same functionality was needed. In the current implementation, it has a different UX/UI feel - it's not particularly consistent at the moment.
The challenge now is to gather all the requirements, design a prototype and run some small UXR tests to see if the user understands the new concept.
Gathering all the requirements was quite simple. I arranged a few meetings with the various product owners of the development teams. Then I connected again with the UX colleagues to review their requirements. I wrote some test cases for usability testing and made sure that their use cases were covered as well.
The next step was to deploy the prototype in Figma. I found some internal users who could help me test some small use cases for the schedule concept. I provided the participants with 3 scenarios in which they had to use the schedule.
For the usability testing I had 5 participants. Therefore, I scheduled some short meetings where I could provide my prototypes and give them the three scenarios in which they should prepare the schedule as they would do it in the software. I made some notes in Miro so that I could carry out the analysis afterwards and make it easy to compare.
When conducting the user tests, some problems with the functionality came up. That means some adjustments had to be made.
STEP 1: Choose “Starting date” and “Starting time”.
STEP 2
STEP 2.1 Repeat: every x hour(s), day(s), week(s), month(s).
STEP 3
I have to delete “custom” as an option, because it was quite misleading. The users were confused when to use custom and when directly “daily” or “weekly”.
I reworked the Figma prototype and restructured it. Now you can directly set all x hour(s), day(s), week(s)etc.
Scenario 1: Add a new schedule that starts at 20.10.23 11:00 and updates every day. It should end after 10 times.
Scenario 2: Add a new schedule that starts at 20.10.23 11:00. It should update every two hours during your office hours (9:00-17:00). It should just end when you end it.
Scenario 3:Add a new schedule that starts at 20.10.23 11:00. It should update every third week, on Mo and Wed. It should end at 12.01.2024 15:30.
The goal is to create a user-oriented, comprehensible concept. Compared to the first user test, the second prototype was quite easy for the participants to understand.
After analyzing the second round, I finalized the concept and designed the UI screens. Together with the UI colleagues and a few rounds of feedback, a holistic design was created. Since I am not a UI designer, I asked the UI design department for feedback to review my screens before implementation.
The schedule logic was implemented in a new functional way and the inconsistencies were removed. It was a continuous process of concept, testing, rework, retesting and designing.
What I personally learned: I gained deeper knowledge in Figma and the prototyping options. Now I have a clear understanding of what is easy and quick to do and what is more difficult to visualize in Figma.