How to Craft a Better UX Design for Blockchain

You can hardly find a person today who hasn’t heard of blockchain with its promise of security, immutability and transparency. Decentralised, distributed and tokenised networks are now top of mind for nearly every business leader. We can see businesses, and even entire governments, investing in blockchain initiatives. As more and more decentralised apps are entering the market, we decided to take a closer look at what it takes to create a UX design for blockchain and how to do it right.

“Business leaders need to be thinking about and they should be worried about and they should be getting excited about the fact that the internet is entering a second era, and they need to transform their businesses around that”, says Don Tapscott, the Founder of Blockchain Research Institute.

Committed advocates of blockchain technology, some of whom joined the game back in 2008, don’t find distributed ledgers extraordinary or mysterious. They completely understand decentralisation’s potential and know how it can be put to work for businesses.

However, there are still many who have only heard the buzzwords like distributed ledger, tokens and smart contracts, and have a very vague understanding of blockchain as a practical solution. Naturally, they can’t trust a technology that they don’t understand. As blockchain aficionados are in the minority, businesses should be cautious when introducing blockchain into their clients’ everyday experience.

“A successful blockchain application returns a validated chaincode. A successful UX in a blockchain application makes it seamless for someone to start using the application, regardless of the technology behind it.” — Vanessa Colina.

Designing for trust

To make the most out of decentralisation, UX design for blockchain should focus on the spheres where this technology can create the biggest value, such as facilitating purchasing flow or improving transparency and security of legal contracts. That is what we highlight to our clients: new technology itself won’t help you attract more customers unless you offer them a new level of efficiency or experience they can’t find elsewhere.

The basic principles of UX design for blockchain focus on the concept of ‘designing for trust’. This concept makes sense as the technology is still new to many industries and there aren’t many examples of its practical adoption by businesses. IBM’s article offers a simple yet extensive overview of the design principles for blockchain.

As there is plenty of information available on blockchain’s theoretical approaches and general design principles, we decided to focus on some practical stuff instead. In this article, we’ll share our experience of creating a user experience for our internal blockchain-based employee loyalty rewards app.

How the design workshop looks likeHow the design workshop looks like

User testing, prototyping and MVP

We recently decided to run a blockchain-based project to support our internal employee rewards programme. 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.

As we already had an internal employee recognition programme that rewarded outstanding performance at work, we decided to make this one socially oriented, to help us improve communication and promote social consciousness among ELEKS staff. We also aimed to boost our staff’s interest in blockchain. It was crucial to create a simple and intuitive interface as its users would all have different technical backgrounds.

We conducted a few surveys which helped us to understand what kind of rewards our staff expected, so as not to disappoint them with unnecessary rewards. In addition to coffee and sweet treats, there were some interesting suggestions like having lunch with the CEO or earning some extra days off.

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

Based on our survey results, we created a job map (see below) and made a number of useful findings:

  1. We need to create an easy way to add a story.
  2. People would like to have an opportunity to share their own opinions on the stories of others.
  3. Both sides need to be rewarded, as this is a kind of cyclic activity.

UX design for blockchain job map The job map

We took map outcomes and created our first prototype and conducted usability testing. As expected, these sessions helped us spot 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 improvement to cover user needs and requirements.

The best practices for building a blockchain-based UX

While creating an interface that is suitable for a diverse audience, we followed the blockchain design best practice, and this allowed us to reach our goal: populate the technology among ELEKS’ employees and promote social consciousness inside the company.

  • Ensure consistency. Especially when developing a new experience, we need to ensure consistency to make users feel comfortable when interacting with our product.
  • Add gamification. Gamification won’t fit into a serious enterprise blockchain-based financial application using cryptocurrencies or smart contracts, but for our needs, it suited perfectly.
  • Mind the irreversibility. There is no way you can revert or cancel a transaction when using blockchain, and so it is essential to make sure your users are aware of blockchain irreversibility.
  • Guide your users. The balance between assisting your users and making them feel stupid may be more fragile than you think; however, gentle guidance can help users reach their goals from the outset and prevent them from making mistakes down the line.
  • Encourage feedback. When you offer a new experience, you will most likely lack approved patterns of users’ behaviour, so create a place for users’ propositions or complaints.

ux design for blockchain ELEKS Coin iOS appELEKS Coin iOS app

Several critical blockchain features and how you can use them

The app we’ve described above was developed for non-commercial use; however, developing commercial products with blockchain, using smart contracts or crypto-wallets, is a whole different story. Here are the key blockchain features you need to consider to create a positive experience with your product:

From the very first interaction with your product, your users need to be assured that blockchain will keep their data protected. You will need to keep this in mind when designing your product, as very often the data that users provide to decentralised apps is sensitive, such as legal documents or other personal information. An average user probably won’t be able to verify that information is stored in blockchain and therefore is secured. You can make your users feel safer by using messages that confirm their security during important steps.

The average blockchain transaction takes much longer than it does on a centralised network: one-second transactions can become one-minute transactions. As your audience won’t be used to this, they’ll need to be kept in the loop at each step, showing them the transaction’s progress and providing constant feedback on its status.

Personal blockchain keys or the document hashes are very long. Sometimes we need to shorten them, but more often than not users operate with the whole number. Give them an opportunity (and don’t forget to tell them about it) to copy the whole hash in the easiest way possible.

Personal keys
People are used to having the option of recovering their passwords when lost or forgotten. The time taken to reset a forgotten password can vary, but it’s always possible. Blockchain disrupts this UX pattern completely. It’s vital that you make sure that your on-boarding process informs people about blockchain’s distinct constraint. Your users need to know that losing a personal key is a serious issue.

Let’s sum things up

Decentralisation introduces many opportunities, but also increases a user’s responsibility, especially in terms of irreversibility or losing a personal key. Having said that, we expect users to get to grips with the advantages and security of blockchain in the long-term.

Despite all the new features, limitations and constraints, blockchain user experience is still a user experience, so there is no need to reinvent the wheel. The majority of well-known design principles and patterns are still relevant and applicable.

“While you craft a user experience for blockchain, the design is not the only thing that matters,” says Mariya Hrabovska, User Experience Designer at ELEKS. “Outstanding results are possible only in close cooperation within a cross-functional team. Designers shouldn’t be afraid to tap into chain code, peers or a distributed ledger.”

The more you get engaged in the development process from the very start, the easier it is for you to deal with a new technology’s constraints and the better experience you can offer to your end users as a result.

Are you looking for a way to implement blockchain as a practical solution for your users? Start smoothly with our whitepaper covering the risks and rewards of blockchain adoption.

If you are struggling with the challenges of blockchain-based user experience, the ELEKS Product Design team will be happy to give you a hand. Get in touch!

9 responses to “Secure Document Transfer Built on Top of Blockchain Technologies”

  1. Robert Cass says:

    Very nice experiment. I would like to discuss using your strategy for healthcare and a virtual notary service here in the US. Please feel free to contact me. Very Best, Robert

  2. kunal bansal says:

    Hey, this seems like a very interesting architecture for blockchain, Is there a followup post for this or where you are heading?

    I wanted to know what’s your view with new consensus algorithms like proof of stake can solve the scalability in your infrastructure, especially since we do not have any concerns of transaction finality in this usecase

    • Tanya Dalik says:

      Hello! We are happy to hear from an enthusiast interested in disruptive tech. We’re now considering a few more applicable business cases and are working on connecting a certain business process (described on BPMN) with Smart Contracts. This allows us to experiment with various business processes since usually Blockchain as technology requires the process to be changed. As for the proof-of-stake, there is no clear vision yet. Certainly, as a step forward, it ‘d be good to see how this consensus works in Ethereum. From the technical point, we’re looking at Hyperledger (as a possible platform) and Cryplets concept (as an evolution of Smart Contracts).

  3. InfoNet Toronto says:

    I just wondering, how the user personal password used to open the document is stored:
    If Client A sends protected document (say, medical record) to Client B and then Client B replies back to Client A with another document, where and how those documents are encrypted and how key exchange works?

    • Tanya Dalik says:

      Hello! We used a mixed encryption methods. There is no single place where we encrypt document, we do it twice:
      – First, we encrypt a document with single key (key is randomly generated and saved on Client A, since he wants to send the document). Then this encrypted document is stored in some storage (we used Github in our case, but it can be also IPFS)
      – Second, we take encryption key from step one and encrypt it with public key of Client B (receiver). Worth mentioning that there is pair of private-public keys, one is used for encryption, second – for decryption, this is asymmetric encryption method. Ad finally encrypted key is sent as part of smart contract to Client B.
      When Client B sees that there is a contract addresses to him, where encrypted key is stored, he: takes that key, decrypts it with his private key, then use decrypted key to decrypt file. Relatively simple 🙂
      Thank you for a good question.

      • InfoNet Toronto says:

        Thanks Tanya,
        Your explanation was very helpful!
        One more question: You wrote: “we take encryption key from step one and encrypt it with public key of Client B (receiver)”.
        The key encryption is done on the Server or in the Client side?

        • Tanya Dalik says:

          On the client side. We’ve developed a desktop application which does that. And actually, there is no server, in classical understanding. Only blockchain nodes, which expose RPC. So client app does everything rest.

  4. Zubaile Abdullah says:

    Love the idea.
    I believe this technology can be applied to distribution of ebook.
    So we know who purchased the ebook and track if he/she tried to send it to other non buyer party.

    • Anatoliy Lytovchenko says:

      Right. Actually the approach can be applied to any digital assets (ebooks, music, photos, etc).

Leave a Reply

Your email address will not be published. Required fields are marked *