Streamline Mobile App - Case Study

Work Order App for Hospitals

Ideation & Design Workshop

postit-notes
postit-notes2
postit-notes3

This is the process we use to launch and continually improve our products for multiple clients.  Prior to introducing our process we as a design department faced several challenges: 1)There was a lack of understanding of UX from the wider business. 2)The lack of understanding meant it was difficult to get stakeholder buy-in and apply a user-centric approach to all projects. 3)It wasn’t clear what our role was to the wider business. Our aim is to solve problems, but we were mistaken as artwork-ers or wireframe-ers. 4)There was an inconsistent approach to different projects, making them a nightmare to manage and resulting in key stages being missed. By introducing our process we’ve reduced the impact of the challenges we faced

Once project goals have been identified we feel it is important that everyone has a chance to express their ideas. As well as giving the whole team a voice it is another great opportunity to get a diverse range of ideas and expert opinions as everyone comes together. This stage of the process is all about creating tangible outputs which can be shared with the team for discussion and furthermore used for usability testing. As famously quoted from David Kelley, our goal is “Fail Fast, to Succeed Sooner”.

Low Fidelity Prototype

prototype

This stage can range from low fidelity prototypes which could be quick sketches linked together to make a clickable prototype. Or high fidelity prototypes that mimic the final user interface, these are more suitable for usability testing and demonstrating ideas to developers or stakeholders. We can now put prototypes in our hands and our colleague’s hands. Most important, though, is the opportunity to get them into our user’s hands. This helps us spot issues before it’s too late as well as being able to validate ideas as we create them. Using our prototypes we can quickly perform usability tests, allowing us to iterate on our ideas/prototypes. Two methods we commonly rely on are hallway testing, and remote testing (via Userbrain), although we also contact users or perform usability tests in the streets to gather quick feedback. Other methods we use are quick data gathering tests to validate our decisions.

Design & Delivery

streamline_mockup4
streamline_mockup3
streamline_1_home

We validate our prototypes as much as possible before passing them onto the development team to build. This is our way of eliminating as much risk as possible.

We communicate our design via a high fidelity InVision clickable prototype. This gives a feel of how the product will work. Alongside this we also supply all our designs using Sympli. This allows the developers to click on the designed screens and get the specs for each individual element. With many of our development teams based around the world effective communication is essential.

Throughout the build we constantly communicate with the development team to address any issues as they occur and guide them to the finish line as smoothly as possible.  Once our product is out there and being used by users we take the time to review it’s performance. We use analytical tools such as Fullstory to review numbers/traffic and Hotjar to enable heat maps on our products — both are great ways to gauge user behaviours and check patterns. Getting feedback from users is essential. To validate the analytical insights we conduct further hallway tests or further remote user testing, this provides validation for our insights. Once we have our insights we discuss our actions as a team and our strategy to make the product better.