Blockchain is now regarded as serious stuff, as lots of its projects deal with people’s identities, sensitive information, large amounts of money, and replacing legacy systems that we may not understand fully. Furthermore, blockchain technology is gradually redefining the concept of trust and changing the way we think about issues ranging from our identity to our economy.
It also forces blockchain designers to think in an orderly fashion, considering things from a wider perspective and rethinking their role in building a decentralized crypto future. Despite the media hype about the rise and fall of cryptocurrencies, blockchain technology is still in its infancy, making it the perfect time for blockchain designers to build new systems.
This article will break down everything you need to know about blockchain designs, from how you can design for trust to the design principles.
Designing for Trust 1.0
Blockchain designers need to address a wide range of challenges when it comes to blockchain design. It can be used to help people like the undocumented, the on-the-edge cases, the trafficked, and those with stolen identities. Design Trust 1.0 offers designers the chance to give people back control of their data and even help them monetize their data.
When you remove all the barriers and give control to the people, it will be easy for small businesses to compete with the big fish. Some design ethics when designing for trust are:
◉ Avoid jargon and non-actionable data.
◉ Use existing UX patterns.
◉ Be consistent and have a design system that you use.
◉ Create active guidance and feedback.
◉ Design for the global nature of blockchain.
◉ Allow for and anticipate mistakes.
A big part of designing for blockchain is to make it look legitimate. This can be done via consistent visual design. Avoid the use of pointless animations and excess amounts of guiding users through a process.
Designing for Trust 2.0
When it comes to design Trust 2.0, designers must utilize a human-centered design process before incoporating mechanism design, system thinking, and game theory. Nowadays, designers are urged to get to the interfaces quickly and make them look slick. While this is understandably the result of a high-pressure environment, it is a mistake to jump through hoops so quickly.
Some of the things you can do to design for trust are:
◉ Design thinking
◉ Low-fidelity
◉ User research
◉ Collaboration
Design Principles for a “Trustless” Machine
Although blockchain technology is designed to eliminate the reliance on trust, this does not mean that users will trust the network or machine. This is why it is important for a blockchain designer to build interfaces that feel more trustworthy. However, many designers usually confuse user needs with network or system needs.
Here are some ways that a designer can use design for trust.
Trust the Machine
You can use the first design layer to mitigate the aspects of why users can trust the blockchain. You can do this by creating a blockchain design around an existing system that helps the user interact with the machine as easily as possible, while educating users about what is happening.
However, designers must understand the way blockchain works to better understand what can and cannot be changed before designing experiences around things such as wait times, gas, smart contracts, and private key management.
Trust Others
After creating trust in the blockchain, designers also need to help users have trust in the mechanisms that they use to collaborate with one another. Apart from smart contracts, some ways a designer can use to foster trust with others are:
◉ Micro-tipping
◉ Staking
◉ Token curated registries (TCRs)
◉ Governance
◉ Crowdsourcing
Indicate Trust
Blockchain designers need to create an overt demonstration of trust, i.e., things that humans perceive as trustworthy. These blockchain design principles are usually from design Trust 1.0. Some of the ways you can signal trust are:
◉ The user interface should behave in a way the user expects.
◉ It should reduce anxiety and cognitive load.
◉ It should respect the established conventions.
◉ The guides should have consistency.
0 comments:
Post a Comment