Case Study: A New 'Arrange View'
Studio's Arrange View, which allows users organise dynamic audio visually on a timeline, had several major problems;
• A cluttered user interface which was complicated for new users
• Built in a way which made iterating on it difficult and time-consuming
• Numerous bugs which impacted user confidence
I organised a design workshop with our Product Manager and the team of engineers who would be working on the project. I always like to extend the invitation to others who might be able to help, like people who were involved with building the original version. That usually helps to identify potential pit-falls early on. The main aim of the workshop was to map out our assumptions about what the Arrange View should allow users to do, and how we might be able to improve the experience for them.
It's not enough to just have a validated prototype. I had to work closely with our project manager and developers to ensure that every aspect of this feature had designs. There was a lot to consider - some of the major considerations were;
- What happens if a patient's record didn't contain all of their current repeat prescriptions?
- How should a patient request additional medication?
- How does a patient review their previous orders?
- How should we show the status of an order?
- How should we differentiate existing medication orders and new medication requests?
- What do prescription notifications look like?
I mapped out various journeys in Sketch and prepared these for a second, more rigorous round of user testing.