User Experience UX/UI

user experience kyomedinnov

Our team accompanies you in each step of your UX roadmap to strengthen the alignment of your solution with the needs of your future users. The goal is to make your project a success that will meet its market and be optimally integrated into the care or life path of the targeted people.

Knowing the needs of your future users may seem obvious. But from experience, we know that these upstream phases are often carried out too quickly in order to arrive at a prototype as quickly as possible. It is therefore after the fact that project leaders discover difficulties that they had not anticipated.

6 key factors to adopt your digital health solution

The expectation of performance

Your product or solution meets users' expectations and makes a task easier or more efficient.

The expectation of effort

Your product or solution is easy to use and requires no special effort.

Social influence

The user's entourage influences his use of your product or solution.

The enabling conditions

The existing technical and organizational infrastructure to support user use of your product or solution.

Psychological ownership

The feeling of ownership and appropriation that the user feels when using your product or solution.

Perceived safety

The degree to which the individual believes that using your product or solution will be safe.

The ultimate goal of your project is to get your users on board. To do this, we will help you evaluate, test and improve the 6 factors key that impact the adoption of your solution by its future users.

Roadmap UX pour votre solution

Planning

Understand
Define
Prepare

Ideation

Converge
Find
Prioritize

Evaluation

Compare
Validate
Improve

Exploration

Get
Listen
Learn

Design

Formalize
Conceive
Concretize

Planning

Understand
Define
Prepare

Exploration

Get
Listen
Learn

Ideation

Converge
Find
Prioritize

Design

Formalize
Conceive
Concretize

Evaluation

Compare
Improve
Validate

The 5 UX steps for your solution

Planning / Discovering

Understand – Define – Plan

Every project starts with this preparation phase because it is essential to have a global understanding of your project and its different stakes in order to better manage it.

This step therefore allows you to frame together :

Your project, your knowledge, your solution, your users and the path ;

But it also allows us to define your needs,your objectives,our intervention,the methodology used and to plan efficiently the next steps of your projectbefore starting the exploration phase (phase 2).

Why call on us during this phase ?

Our accompaniment with a new look will allow us to bring a new vision to the project but also our expertise in order to solidify its bases, and that through :

Identification and/or validation of the different users of your solution

The construction of a typical user path for your solution, containing the different interactions between the users and the solution as well as the different steps of the path

A challenge of the path : questions, obstacles, or remarks

An elaboration of the UX development path of your solution (type of studies to be carried out, sequencing, users to be targeted, milestones, budget, …)

Deliverables :

  • Flowchart of your solution’s usage path (according to users and steps of the path)
  • UX roadmap with its different steps and milestones associated with the validation of your solution’s uses
Flowchart and UX Roadmap

This will allow us at the end of this first step to be in phase on your solution, its users and the course, but also to frame our support and the steps to come.

Exploration

Get – Listen – Learn

Often underestimated, this phase of empathy (putting yourself in the user’s shoes) and openness is a key step in the design process. It allows us to listen, to open up and to better understand the activity, the needs, the motivations, the obstacles of your future users, but also the contexts of use, the lived experiences, etc.

It is difficult when you have been working on a project for a long time to go “beyond the obvious. This phase will allow among other things, to bring you a “fresh” look at your targets and to challenge your vision to go further with yourfuture users before selecting one or several ideas in the ideation phase.

During this phase, we must be as close as possible to your future users. For that we can use different tools or methods specific and adapted to the needs and objectives of your project.

Here are a few of them below to illustrate our tools and what they show. For each of these methods, an exchange and co-design work with you and your teams will be necessaryto frame the information to be collected as well asthe issues and objectives of the study.

The observation
The interview
The survey
The focus group
An observation phase can be set up in order to apprehend the actual activity in the field (visible behavior in a specific environment) of a person or a group.

This also allows to map the environment in which the action takes place in order to detect differences between what a person declares to do (his/her task) and what he/she actually does (his/her activity).

Observation methods need to be framed by a professional (ergonomist, UX Designer, …) in order to collect the most useful information adapted to the project and to avoid as much as possible the bias induced by the observer. The fact that you are convinced by your idea is your biggest handicap at this key stage.

Depending on the context and the need, we will choose :

  • The most suitable observation method to collect the most useful data for your project
  • The posture and the interaction to have during the observation
  • The environment and the key moments to observe,
  • The audience to observe,
  • The duration of the observations,

Why conduct an observation?

Starting from the idea that your future users will not necessarily tell you the whole truth about their activity, our approaches allow you to :

  • Know their real activity in a specific environment
  • Discern the difference between the planned activity and the actual activity
  • Validate their real needs
  • Better understand their stakes via an emotional and behavioral approach
  • To get out verbatims

During these observations, photos and/or video excerpts may illustrate some important points.

  • Deliverables :
    • A customized observation grid
    • A report presenting the qualitative data observed (behaviors, verbalizations, attitudes, …) collected from users in their natural environment. This data will help enrich your project to find the best ideas or choices to make during the next steps of the design process.
To explore the future environment of your solution and the needs of your users, an approach via interviews (in person or remotely) can also be implemented.

An interview is prepared beforehand with the design of an interview guide that will allow to understand the elements, attitudes and opinions necessary for the project.

Calling on a specialized team allows us to make the most of this moment of exchange, which requires a precise framework adapted to the project. In this preparation, we will integrate the psychological dimension of the participants in order to ensure that they can speak freely. We will also set up a benevolent environment to free speech and allow everyone to express their point of view.

Why carry out an interview ?

This privileged moment of exchange with your future users will allow you to obtain :

  • Data and information relevant to your project
  • An opening to new opinions, ideas or needs,
  • A basis for conducting a questionnaire on a larger panel of users, if necessary
  • Deliverables :
    • An interview grid
    • A report that will present you with qualitative data accompanied by various verbatims resulting from an open and benevolent exchange.
The purpose of exploratory questionnaires is to obtain quantitative data. In other words, we are looking for a sufficient volume of responses either to complete another method used, or to enrich our knowledge, or to validate or invalidate hypotheses. Here again, it is important to master this type of tool in order not to bias the questions or formulations.

  • Deliverables :
    • The exploratory questionnaire
    • The report presenting the results and follow-up.

This type of method makes it possible to bring together several target users around a defined discussion topic. The facilitator will use appropriate and relevant facilitation techniques to stimulate debate and allow everyone to express themselves. The focus group is used to collect the opinions, attitudes, and needs of the participants in relation to the project’s problems or needs. This method is mainly used in the exploration phase.

By working with our UI/UX teams, you will be assured that :

  • The workshop will be best framed using a Focus Group facilitation methodology,
  • The facilitation will be conducted in a neutral manner without inducing debate or biasing the exchanges,
  • The exchanges will be oriented to the project’s issues and needs

What will a focus group do for you?

The group emulation generated by a focus group allows for richer data. Participants can bounce ideas off each other. We collect the opinions, attitudes and needs of participants regarding your system, your product, your services or simply your concept.

We can organize and lead focus groups either face-to-face or remotely thanks to adapted and efficient collaborative tools that allow all participants to interact and express their ideas in writing and orally.

  • Deliverables :
    • The focus group workshop protocol
    • The report that will present you with qualitative data (ideas, opinions, views) from the participants’ group discussions along with the different materials used during the workshop.

Depending on your needs, these methodologies can also be used to generate other types of informative deliverables.

  • Additional deliverables:
    • The empathy map allows you to present to the project team what the target user thinks, sees, hears, feels, does but also what he fears or expects about the future solution to be designed. This will also improve the understanding of the users’ needs for your project.
    • The experience map allows you to represent in a chronological way all the experiences that could be lived by the target user during his interaction with the solution to be designed. This experience map allows the project team to better understand the emotions generated and to anticipate possible problems or obstacles that could affect the quality of your solution.
closed
The observation

An observation phase can be set up in order to apprehend the actual activity in the field (visible behavior in a specific environment) of a person or a group.

This also allows to map the environment in which the action takes place in order to detect differences between what a person declares to do (his/her task) and what he/she actually does (his/her activity).

Observation methods need to be framed by a professional (ergonomist, UX Designer, …) in order to collect the most useful information adapted to the project and to avoid as much as possible the bias induced by the observer. The fact that you are convinced by your idea is your biggest handicap at this key stage.

Depending on the context and the need, we will choose :

  • The most suitable observation method to collect the most useful data for your project
  • The posture and the interaction to have during the observation
  • The environment and the key moments to observe,
  • The audience to observe,
  • The duration of the observations,

Why conduct an observation?

Starting from the idea that your future users will not necessarily tell you the whole truth about their activity, our approaches allow you to :

  • Know their real activity in a specific environment
  • Discern the difference between the planned activity and the actual activity
  • Validate their real needs
  • Better understand their stakes via an emotional and behavioral approach
  • To get out verbatims

During these observations, photos and/or video excerpts may illustrate some important points.

  • Deliverables :
    • A customized observation grid
    • A report presenting the qualitative data observed (behaviors, verbalizations, attitudes, …) collected from users in their natural environment. This data will help enrich your project to find the best ideas or choices to make during the next steps of the design process.
The interview

To explore the future environment of your solution and the needs of your users, an approach via interviews (in person or remotely) can also be implemented.

An interview is prepared beforehand with the design of an interview guide that will allow to understand the elements, attitudes and opinions necessary for the project.

Calling on a specialized team allows us to make the most of this moment of exchange, which requires a precise framework adapted to the project. In this preparation, we will integrate the psychological dimension of the participants in order to ensure that they can speak freely. We will also set up a benevolent environment to free speech and allow everyone to express their point of view.

Why carry out an interview ?

This privileged moment of exchange with your future users will allow you to obtain :

  • Data and information relevant to your project
  • An opening to new opinions, ideas or needs,
  • A basis for conducting a questionnaire on a larger panel of users, if necessary
  • Deliverables :
    • An interview grid
    • A report that will present you with qualitative data accompanied by various verbatims resulting from an open and benevolent exchange.
The survey

The purpose of exploratory questionnaires is to obtain quantitative data. In other words, we are looking for a sufficient volume of responses either to complete another method used, or to enrich our knowledge, or to validate or invalidate hypotheses. Here again, it is important to master this type of tool in order not to bias the questions or formulations.

  • Deliverables :
    • The exploratory questionnaire
    • The report presenting the results and follow-up.
The focus group

This type of method makes it possible to bring together several target users around a defined discussion topic. The facilitator will use appropriate and relevant facilitation techniques to stimulate debate and allow everyone to express themselves. The focus group is used to collect the opinions, attitudes, and needs of the participants in relation to the project’s problems or needs. This method is mainly used in the exploration phase.

By working with our UI/UX teams, you will be assured that :

  • The workshop will be best framed using a Focus Group facilitation methodology,
  • The facilitation will be conducted in a neutral manner without inducing debate or biasing the exchanges,
  • The exchanges will be oriented to the project’s issues and needs

What will a focus group do for you?

The group emulation generated by a focus group allows for richer data. Participants can bounce ideas off each other. We collect the opinions, attitudes and needs of participants regarding your system, your product, your services or simply your concept.

We can organize and lead focus groups either face-to-face or remotely thanks to adapted and efficient collaborative tools that allow all participants to interact and express their ideas in writing and orally.

  • Deliverables :
    • The focus group workshop protocol
    • The report that will present you with qualitative data (ideas, opinions, views) from the participants’ group discussions along with the different materials used during the workshop.

Depending on your needs, these methodologies can also be used to generate other types of informative deliverables.

  • Additional deliverables:
    • The empathy map allows you to present to the project team what the target user thinks, sees, hears, feels, does but also what he fears or expects about the future solution to be designed. This will also improve the understanding of the users’ needs for your project.
    • The experience map allows you to represent in a chronological way all the experiences that could be lived by the target user during his interaction with the solution to be designed. This experience map allows the project team to better understand the emotions generated and to anticipate possible problems or obstacles that could affect the quality of your solution.

Ideation

Converge – Find – Prioritize

In this ideation phase, the knowledge acquired from your future users during the exploration phase will allow us to generate ideas.

These will be in large quantities at first, then step by step, we will sort and prioritize them in order to keep the relevant and strategic ideas to be implemented. Once this choice is made, the prototype design phase (phase 4) can begin.

A typical methodology: Brainstorming

Following the focus groups, questionnaires or interviews conducted in the previous exploration phase, collaborative brainstorming workshops will produce many ideas related to the previous results.

Unlike the Focus Group, the Brainstorming is also framed but with more freedom in order to allow this important production of ideas which will be sorted afterwards.

These workshops can be conducted face-to-face or remotely using adapted and efficient collaborative tools that allow all participants to interact and express their ideas in writing and orally.

Deliverables :

  • List of all the ideas generated, sorted by category in the form of a mind map for a clearer representation, simplified reading, and easier sharing and communication of results.
  • Prioritization of the 2 or 3 most relevant ideas to focus on them for the next step.

Prototype Design

Formalize – Conceive – Concretize

This phase allows the design of a prototype or a tangible model (concrete and palpable by the project team and the final users) in order to formalize the chosen solution(s).

This model created in this way (at a lower cost) allows a better projection and interaction with your project team.

It also allows the simulation of the use of your solution with your future target users.

It must therefore be designed to evolve over the course of the project and the various iterations of the evaluation phase in order to be increasingly precise, adapted to needs and oriented towards the final version.

Deliverables :

  • Prototype or physical or digital model ready to be tested and evolve throughout the project to reach the MVP (Minimum Viable Product). This prototype will include the design, the functionalities, and the content of your solution.
  • Mind map with the selected usage tree. This mind map, which will evolve during the project, will be the basis of the final product’s tree structure, i.e., the possible user path according to the choices and clicks made by the user.
Usage Tree

Evaluation

Compare – Validate – Improve

This testing phase is very important in the design process as well as during the life of the product. A selected panel of target users or experts will test the mock-up or prototype that was designed during the previous prototyping phase or the product already on the market.

Measuring the results, understanding and analyzing these tests will allow you to improve your product and iterate with new tests until an optimal and adapted solution is found.

It is important to note that it is easier and much cheaper to modify a prototype (which can be retested later!) than to discover a problem once the solution is developed and produced.

We will accompany you in the realization of several levels of tests:

An expert evaluation by our UX/UI designers and specialists. This allows us to prepare the next test by ensuring that the prerequisites are good.

Then, user tests to validate the adequacy between the developed product and the users’ expectations and needs.
We can use the same panel as in the upstream phases or change according to your needs and objectives.
These tests also allow a more global evaluation of the user experience as well as a usability test of the solution.

Deliverables :

  • Test or evaluation report with screenshots to illustrate the various important points raised as well as the solutions to be brought to remove these brakes or blockages.
  • This report allows us to continue to learn and understand how users interact with the solution, but also to modify and improve the tested product in order to arrive at a final validated solution that can now be developed.
  • Graph of the data collected (qualitative and quantitative) thanks to the different scales used during the user tests. For example, the SUS (System Usability Scale) to evaluate the overall usability of the solution.

Engineering to suitability for use (E.S.U.)

This normative approach NF EN 62366-1:2015 is mandatory for the CE validation of your medical device.

It is part of risk management because it allows us to identify the risks related to the use of your solution under normal conditions. The various tests we will perform will demonstrate the safe use of your solution.

For this, we can accompany you on all the phases of this process:

Formative evaluations must take place throughout your development. For this we will use tools such as the “cognitive walk”, the “heuristic analysis”, semi-directive interviews or a panel of future users. All of this is done in an iteration loop to save time and to correct the problems identified in the user interface as soon as possible.

The summative evaluation, which is the final step, will allow us to evaluate the device with future users in conditions as close to real life as possible.

Contact us

If you have a digital health project, our entire team is here to help you.

Newsletter inscription

10 + 11 =

By submitting this form, I agree to the use of my personal information to contact me. I also accept the privacy policy.

04 11 95 01 39

contact@kyomed.com