Sep 10, 2021
IronHack UX.UI: Final Project Ordotype
For the final projet of Iron Hack UX UI Bootcamp, we work alone with a company. I chose to work with Ordotype. We had two weeks.
Part I The brief
1.The brand
Ordotype is a French start-up, created in December 2020 by two doctors and an engineer. Ordotype means standard prescription. The goal is to help general practitioners in their daily practice by proposing a database of pathologies, standard prescriptions and information to be transmitted to patients.
2. The mission
My mission was to:
- Organize the pathology database
- Allow easy copying of prescriptions
- Organize the information for patients
3. The Market
The market of medical app is a growth of 26% in 2020 and a worth a 4.2 billionUSD (Research and Market, decembre 2020).
Initially, doctors used manuals to help them in their practice, such as Vidal or Dorosz. Digital versions have been developed such as Vidal reco. Then specialised sites such as ordoclic or gestaclic appeared. Finally, independent and generalist sites such as Recomédical or Doctofiches appeared.
We used a Feature competitive Analysis to understand which features are essential and which are secondary.
Part II The UX
We conducted a study to understand user habits.
Quantitative Research
Firstly, we conducted a survey of a wide audience to collect quantitative data. We present you with the significant figures:
Qualitative Research
We developed the issues that emerged from the survey in interviews.
We conducted 7 interviews, with 3 doctors, 2 pharmacists and 2 patients.
Affinity Diagram
From the data collected in the interviews we made an affinity diagram. We have noted on sticky notes all the main information that we have grouped into clusters. What underlined the pluses, the demands, the brakes.
The main information that we extracted from the affinity diagram, according to the categories of the interviewees, was classified into categories, information, prescription, practice.
Empathy Map
We made an empathy map to understand a deeper view of the customers and identify pains and gains.
Jobs to be done
To focus on the service and not on the product, we did a job to be done. The Jobs to be done is useful to center the attention in users motivation and desired outcome.
User Persona
Thanks to all these tools, we were able to create a typical user.
Our main user is Valerian, a young general practitioner who is running out of time.
Valerian wants to be supported in her daily practice, validating information on pathologies, prescriptions and to be able to easily transmit information to patients.
User Journey
Based on the Persona, we did the User Journey, to understand the stages of the user’s experience when using the service.
Valerian receives a patient with a rare pathology. She would like to validate her knowledge. What tool should she use to have complete, up-to-date, easy-to-use information so as not to waste time in consultation?
Problem Statement
These analysis phases allowed us to highlight the Problem Statement, which is the gap between the problem encountered by the user and the desired state. The problem statement:
Hypothesis Statement
After the prioritization, we now have a clear question in mind. It’s time to turn the question into a hypothesis.
How might we ?
How might we are short questions that launch brainstorms.
Part III Interaction Design
Ideation
Minimum Viable Product
Starting from the goal of our product, we have highlighted the one basic set of features.
Then we used the Moscow Method to rank the features by importance. Starting from the Minimum Viable Product and going to the ideas that we wouldn’t have.
Site Map
This allowed us to define the site map with the different parts of the site.
User Flow
We have transcribed the site map into a user flow, the steps the user takes to reach his goal.
Valeria receives a patient with a rare pathology.
She wants to review the clinical recalls,
validate the prescription and pass on informations to the patient.
She uses Ordotype.
Low-fidelity
We made low fidelity wireframes and decided of the organisation.
Mid-fidelity
Which we have transcribed into mid fidelity.
Usability Test Results
We had tested with 5 users our mid fidelity to gather feedback and improve our product.
One of the improvements we have made is to hide the sources to save space.
Or shift the buttons on the square to create space.
Part IV The UI
Visual Competitive Analysis
To start the UI part, we have a competitive visual analysis with the main competitors.
We can see that they have very different styles.
Brand attributes
The brand attributes are characteristics that the audience sees as an inherent part of a brand.
Our brand attributes are: Treatment, knowledge, confidence, clear, complete, organized.
Moodboard
The mood board is a collection of images to guide the work and give a coherent visual identity.
Style Guide
The Style Guide defines the identity of the brand. It includes colours, typography, components and logo.
We have chosen blue as the dominant colour to represent care. And as an accent colour, green to represent confidence.
High-fidelity
Thanks to the moodboard and the style guide, we have made the high fidelity wireframe.
Key Learnings
Through the final project, we learned to understand the client’s needs, to use Sigma to animate, and to always do component!
Takeaways
The next steps will be to develop terms and conditions, to offer online training and to develop subscriptions.
