Identifying the client’s needs

The University of Michigan’s Clinical Pharmacy Department was in development of an application that detected and monitored chemotherapy-induced peripheral neuropathy on cancer treated patients. This was done by analyzing how subjects walked – particularly gait and balance – and their finger coordination. We were invited to develop version 2 of the iOS app and its integration to the Medable platform that lived in the backend.

Thanks to iOS we were able to leverage Apple Research Kit for the assessments. However, this offered certain limitations on how we could customize the functionalities and workflow. Apple Research Kit constrained us to certain flows that did not match the client requirements.

‍

‍

‍

The Discovery Process

We started encompassing the exploration of the problem space, the collection of data for guidance, and the definition of the problem to be addressed. A comprehensive discovery process was undertaken in collaboration with a team of UX designers, conducting interviews with project stakeholders and iterating on the first flows to validate that we were both on the same page. But first, we mark the starting point of the design process, dedicating time to comprehend the context of the business, the problem domain, and our target users. This stage helped us define the problem and established a solid foundation for the subsequent stages of the process.Once we had collected a substantial amount of data to formulate the first product idea we started with the exploration and refinement of numerous potential solutions to our problem. This part of the process has helped us to devise innovative approaches that tackle user issues and elevate their overall experience.

‍

‍

Defining the problem in a tight deadline context

We were in a scenario where time was a limiting factor, and we needed to leverage it to our advantage. To achieve this, agile iteration and continuous engagement with various project stakeholders were crucial to ensure we were steering the product in the right direction. We carried out an iterative process, translating various ideas into wireframes and flows to keep the entire team on the same page. This allowed us to gather and document requirements for the development team while simultaneously creating the iOS UI kit, thus translating the initial flows into UI and generating the first interactive prototypes for testing.Once we gathered feedback for each type of flow, we progressively detailed the product while ensuring an optimal and accessible user experience.

‍

Our approach and solutions

The University of Michigan sought a development partner that comprehensively grasps their objectives and aligns with the same business values. Hence, the culture-first approach played a pivotal role in our collaboration.Another crucial aspect was Onetree's strong communication skills, enabling us to transform our collaborative work dynamic. Initially confined to mobile app development for iOS, Onetree gradually evolved into a trusted partner actively contributing to shaping Michigan's product strategy.All work is conducted in sprints adhering to the Agile methodology. During each sprint, dedicated time is allocated to explore new ideas and tactics. On these days, we engage in experimentation, prototyping, testing, and ideation to deliver the best possible value for the users.