Evolyst Design Process

An insight

Evolyst Design Process

Our design process follows the ‘Double Diamond’ model.

In all creative processes, several ideas are created; we call this ‘divergent thinking’; these are then narrowed down to the best concept or solution; ‘convergent thinking’.

In the Double Diamond approach, this occurs twice; once to define the problem and once to create the solution.




Our Double Diamond approach is split into four phases;


Discover: Identify possibilities and gather insights.  Understand and question the problem and the audience’s needs.’

Initial meetings with stakeholders will be used to gather insights and knowledge of the project; the design team will then undertake their own information gathering and market research to determine how best to tackle the project.

In terms of our own research, we will need to gather insights into user’s experiences, behaviours and needs; activities we use to get to this stage can include;


-          User Diaries: aimed at building an image of what the ideal user is like.

-          Day in the life: The design team map the potential user’s typical day, observing and recording events to build up a realistic picture of what happens.

-          User Shadowing: The design team will ask users to think out loud whilst performing a given set of tasks, observing how they react to obstacles.

-          Focus groups: An interactive session between designers and users where all attendees contribute to the dialogue and express their opinions


Define: ‘Make sense of what was discovered, identify what is feasible and develop a clear creative brief by defining and interpreting the problem.’

This phase acts as a filter where we review, select and discard idea to take forward. Each persona should bring together information about similar people into one character, representing a group of users.


-          User Personas: Archetypes which have been created to represent user research in an easily understandable way.

-          User stories: Used to describe a feature from an end-user perspective.


Develop: ‘Ideas are created, prototyped, tested and iterated.’

Design-led solutions are developed, iterated and tested during the develop phase. The brief should be properly addressed, and ideas will be generated and prototyped.

Concepts will be created and discussed within the design team before presenting the most relevant concept/s to stakeholders. During this process the design team may work with user focus groups to gain feedback on concepts.

During the develop phase concepts will be presented to stakeholders, discussed and revised. When all parties are happy with a concept and it is signed off, we can move forward to the next stage.


Deliver:This is when the features are defined and developed, the Development team will normally become involved at this stage and at the end of this stage Development work will begin.’

During the deliver phase everything we need to start the physical development of the product (writing the code) will be created. This can include wireframes, style guides, prototypes, proof of concept and full designs for initial features.


-          Wireframes: Wireframing is a way to design a product at a structural level, laying out content and functionality. They are used to describe the user journey and layout before visual designs and content are added.

-          Prototypes: The design team will create a user experience prototype. This prototype represents enough of the appearance and functionality of the product that it can be used for user research. This prototype can be shared with user focus groups, stakeholders and the project teams.

-          Acceptance criteria: The acceptance criteria is a document which consists of a set of statements, each of which has a clear pass/fail result, that specify the functional and non-functional requirements of the product. The acceptance criteria will be used to test the developed features against.

-          Kick-off meeting: Before the development of the product can begin a meeting will be held between the design team and the development team to create a backlog of all the features. This will list all the features in order of maximum business value/time to implement.


What’s next?

Here at Evolyst, we work in two-week sprints; at the end of each sprint, the product will be presented and delivered to the stakeholder.

If you have any questions about our design process or wish to inquire about the development of your digital health project, get in touch.