Design thinking process
Involving users in our design phases allows us to gain valuable insights into their requirements and expectations and empowers our decisions when selecting the types of technology and architecture.
Step .1
Understand user context (KIIs, primary and secondary sources of data)
We employ our skills to prepare extensive desk research diving through recent studies, literature reviews and recent innovations to get familiar with the context under consideration. This provides the theoretical base and the solid foundation that allow us to justify specific design alternatives.
Step .2
Listen to the voice of customer/user/citizen
Utilising multiple tools such as key informant structured and semi-structured interviews ‘KIIs’ as our primary source of data, we capture the voice of customers to understand their pain points. This is the step where we agree on the scope of our work.
Step .3
Translate the voice of customers into technical requirements
We internally translate the pain points into customer/user requirements and identify any gaps. Such requirements and gaps are then transformed into a set of questions that IF answered, would satisfy such requirements and bridge such gaps. Questions are then grouped together into sets based on several criteria such as type, target group, timeline or speciality to name a few.
Step .4
Innovate solutions
We transform the answers to the previous questions into what we consider the blueprints of our code. This is the stage where coding kicks in, and the developers do their magic to reflect requirements and solutions into innovative yet simple applications.
Step .5
Testing and evaluating solutions
We test our solutions using statistically designed experiments and evaluate them against certain performance measures through a strictly defined protocol. We also involve our customers/users in the testing and evaluation to ensure all stakeholders are involved, and the scope of the solution is being fully addressed. We test for various metrics and make sure we neutralise any biases or resulting negligence.
Step .6
Continuously adapt our approach to the ever-changing expectations
We adopt the Design-Measure-Analyse-Improve-Control ‘DMAIC’ strategy to ensure our solutions are effective, accurately addressing the pain points of our customers/users and at least meeting their expectations.
Step .7
Keep an eye on the market and set challenging milestones, benchmark against the best in class
We continually strive to improve our competitiveness by benchmarking our performance against those best in class. In case we are venturing into a new domain, we measure our performance against our best version and set new challenging milestones to push boundaries and explore new facets.
Step .1
Understand user context (KIIs, primary and secondary sources of data)
We employ our skills to prepare extensive desk research diving through recent studies, literature reviews and recent innovations to get familiar with the context under consideration. This provides the theoretical base and the solid foundation that allow us to justify specific design alternatives.
Step .2
Listen to the voice of customer/user/citizen
Utilising multiple tools such as key informant structured and semi-structured interviews ‘KIIs’ as our primary source of data, we capture the voice of customers to understand their pain points. This is the step where we agree on the scope of our work.
Step .3
Translate the voice of customers into technical requirements
We internally translate the pain points into customer/user requirements and identify any gaps. Such requirements and gaps are then transformed into a set of questions that IF answered, would satisfy such requirements and bridge such gaps. Questions are then grouped together into sets based on several criteria such as type, target group, timeline or speciality to name a few.
Step .4
Innovate solutions
We transform the answers to the previous questions into what we consider the blueprints of our code. This is the stage where coding kicks in, and the developers do their magic to reflect requirements and solutions into innovative yet simple applications.
Step .5
Testing and evaluating solutions
We test our solutions using statistically designed experiments and evaluate them against certain performance measures through a strictly defined protocol. We also involve our customers/users in the testing and evaluation to ensure all stakeholders are involved, and the scope of the solution is being fully addressed. We test for various metrics and make sure we neutralise any biases or resulting negligence.
Step .6
Continuously adapt our approach to the ever-changing expectations
We adopt the Design-Measure-Analyse-Improve-Control ‘DMAIC’ strategy to ensure our solutions are effective, accurately addressing the pain points of our customers/users and at least meeting their expectations.
Step .7
Keep an eye on the market and set challenging milestones, benchmark against the best in class
We continually strive to improve our competitiveness by benchmarking our performance against those best in class. In case we are venturing into a new domain, we measure our performance against our best version and set new challenging milestones to push boundaries and explore new facets.
