Eleks design process

That’s where we met 

There are enough articles about design principles for , majority’s main point of which is design for trust. This is pretty logical, because of technology’s novelty and previous experience absence with it in mass. Quiet simple and clearly you can read it in IBM’s article

Since there is plenty of information available about the theoretical approaches and general design principles for blockchain, I decided to focus on my own experience.

Recently ELEKS decided to run a blockchain-based project to support the internal employee rewards program. The project included desktop and mobile applications, where employees earn tokens for their social and charitable activities. The app works as a blockchain-based rewards system and allows employees to vote for their colleagues.

Since we already had an internal employee recognition program intended to reward outstanding performance at work, we decided to make this one socially-oriented, to help us improve communication and promote social consciousness among ELEKS people. We also aimed to boost the interest in blockchain inside the company. It was crucial to create an interface that is simple and intuitive, as its users would have a different technical background.

We did a few surveys, which helped us understand what kind of rewards people expected, so as not to disappoint them with unnecessary things. Besides such common variants like coffee and sweet treats, there were some interesting suggestions like having lunch with the CEO or getting some extra days off.

As the audience was very diverse, I decided to use the JTBD approach for this project, so the job looked like: «When someone has helped me, I want it to get recognised by others so that it can be rewarded».

Based on this we created a job map (see below) and made a number of useful outcomes:

  1. We need to create an easy way to add a story.
  2. Make possible sharing own opinion on the stories of others.
  3. Both sides need to be rewarded, as this is a kind of cyclic activity.
Job Map

Based on the outcomes, we created our first prototype and conducted usability testing. As expected, these sessions helped us spot the unclear moments in the user flow. After the prototype had been adjusted according to these insights it was ready for MVP development, followed by continuous improvements to cover all the user needs and requirements.



Source link

LEAVE A REPLY

Please enter your comment!
Please enter your name here