Origyn

What it is

Origyn is a new protocol and the first native token for the Internet Computer Protocol (ICP). It enhances NFTs by adding biometric data and unique ownership features. Origyn aims to help brands, creators, artists, marketplaces, consumers, and industries by offering secure, verifiable certificates of authenticity. It's working to change how we think about ownership and authenticity in the digital world.

Problem to Solve

The ICP protocol and blockchain technology are complex and confusing for novice users, creating a significant barrier to entry. Current products in this space often expose users to technical minutiae, making it difficult for them to navigate and use these systems effectively. This complexity limits adoption and prevents many potential users from engaging with and benefiting from the technology.

We need to develop a product that:

1. Simplifies the user experience of interacting with the ICP protocol and blockchain
2. Shields users from unnecessary technical details
3. Provides an intuitive interface that novice users can easily understand and navigate
4. Maintains the core functionality and benefits of the technology while reducing its apparent complexity

By solving this problem, we aim to increase accessibility, improve user adoption, and unlock the potential of ICP and blockchain technology for a broader audience.

My Role

I designed the wallet and governance platform from start to finish, working with the product and engineering teams. I analyzed competitors, mapped stakeholders, and organized our dApp ecosystem's structure. I created and refined the product's design and function through several iterations. I set up user testing and partnered with our social media team to run the company's first user tests. This approach gave us valuable insights to improve our product at minimal cost.

Baseline Understanding & IA

When I started, there was no documentation. The engineers were building based on the CTO's vision. I began by taking screenshots of the whole product to understand its structure.

Next, I asked questions to learn the product's purpose. Then, I focused on understanding our users and their needs.

With this information, I suggested an update with a more user-friendly layout to improve usability. This approach filled the documentation gap and set up a better product experience.

Understanding the Users

After understanding the product's scope, I tackled user research with no budget and limited resources. I used our Discord channel and social media to talk with users. I also consulted team members, investors, and my web3 contacts for insights.

Despite no budget, I created a survey to learn about user profiles and behaviors in web3. I also started a Usability Testing group for ongoing improvements.

With this initial data, I made stakeholder maps and use cases. Then, I defined specific user personas based on stakeholder input. This process helps us better understand our users and make informed design choices.

Understanding the Competitive Landscape

To understand our competitors, I analyzed various Web 3 products. I looked at different Web 3 protocols, noting similarities and differences.

This research was key in shaping my design approach. I used what I learned to guide my design choices, aiming to make our product stand out in the Web 3 market.