Web3 API
Redesigned the Team Management to enhance collaboration within more than 300 teams.
Web3 API
Redesigned the Team Management to enhance collaboration within more than 300 teams.
Web3 API
Redesigned the Team Management to enhance collaboration within more than 300 teams.
Web3 API
Redesigned the Team Management to enhance collaboration within more than 300 teams.
Web3 API
Redesigned the Team Management to enhance collaboration within more than 300 teams.
Years
Years
Years
2023 – now
2023 – now
2023 – now
Role
Role
Role
Senior product designer
Senior product designer
Senior product designer
Platforms
Platforms
Platforms
Desktop
Desktop
Desktop
Domain
Domain
Domain
B2C, B2B
B2C, B2B
B2C, B2B
Contribution
Contribution
Contribution
Prototyping, designing the product, testing
Prototyping, designing the product, testing
Prototyping, designing the product, testing
Web3 API (formerly mRPC) is the flagship Ankr's product providing more than 8B requests to more than 40 different blockchains monthly. It's a dashboard enables developers to connect their apps with different blockchains and gathers analytics.
I joined web3 API's team in June 2023. As the only designer I'm involved in all steps from a problem ideation to features release.
Web3 API (formerly mRPC) is the flagship Ankr's product providing more than 8B requests to more than 40 different blockchains monthly. It's a dashboard enables developers to connect their apps with different blockchains and gathers analytics.
I joined web3 API's team in June 2023. As the only designer I'm involved in all steps from a problem ideation to features release.
Web3 API (formerly mRPC) is the flagship Ankr's product providing more than 8B requests to more than 40 different blockchains monthly. It's a dashboard enables developers to connect their apps with different blockchains and gathers analytics.
I joined web3 API's team in June 2023. As the only designer I'm involved in all steps from a problem ideation to features release.
context
context
context
As the next logical step in evolving the web3 API dashboard functionality, the Team Management feature was introduced. It encourages collaborative work on the platform and is especially in demand by corporate clients and teams, rather than independent developers. Previously, there was no such functionality.
As the next logical step in evolving the web3 API dashboard functionality, the Team Management feature was introduced. It encourages collaborative work on the platform and is especially in demand by corporate clients and teams, rather than independent developers. Previously, there was no such functionality.
As the next logical step in evolving the web3 API dashboard functionality, the Team Management feature was introduced. It encourages collaborative work on the platform and is especially in demand by corporate clients and teams, rather than independent developers. Previously, there was no such functionality.
technical constraints
technical constraints
technical constraints
Before beginning, I set up a meeting with the development team to understand the technical constraints. We identified a critical issue: a personal account cannot be converted into a team account. This means users must create a separate entity within the platform. Current users who already have a project and currencies on their balances would need to replicate the same project structure within the new team account, which presented a significant challenge.
To overcome this, the backend team developed a ‘Assets Transfer’ functionality, enabling the migration of all projects and currencies to the newly created team account.
Before beginning, I set up a meeting with the development team to understand the technical constraints. We identified a critical issue: a personal account cannot be converted into a team account. This means users must create a separate entity within the platform. Current users who already have a project and currencies on their balances would need to replicate the same project structure within the new team account, which presented a significant challenge.
To overcome this, the backend team developed a ‘Assets Transfer’ functionality, enabling the migration of all projects and currencies to the newly created team account.
Before beginning, I set up a meeting with the development team to understand the technical constraints. We identified a critical issue: a personal account cannot be converted into a team account. This means users must create a separate entity within the platform. Current users who already have a project and currencies on their balances would need to replicate the same project structure within the new team account, which presented a significant challenge.
To overcome this, the backend team developed a ‘Assets Transfer’ functionality, enabling the migration of all projects and currencies to the newly created team account.
research
research
research
The Team Management feature is common across platforms. I categorized platforms into two groups: direct and indirect competitors. For direct competitors, I focused on investigating user roles and permission sets, whereas for indirect competitors, I examined team management workflows and the process of sending and revoking invitations.
Research takeaways:
Most competitors offer four distinct roles: Owner, Admin, Developer, and Finance, which align well with our needs.
By default, most competitors enable accounts that allow users to invite others into them, with no distinction between personal and team accounts.
The Team Management feature is common across platforms. I categorized platforms into two groups: direct and indirect competitors. For direct competitors, I focused on investigating user roles and permission sets, whereas for indirect competitors, I examined team management workflows and the process of sending and revoking invitations.
Research takeaways:
Most competitors offer four distinct roles: Owner, Admin, Developer, and Finance, which align well with our needs.
By default, most competitors enable accounts that allow users to invite others into them, with no distinction between personal and team accounts.
The Team Management feature is common across platforms. I categorized platforms into two groups: direct and indirect competitors. For direct competitors, I focused on investigating user roles and permission sets, whereas for indirect competitors, I examined team management workflows and the process of sending and revoking invitations.
Research takeaways:
Most competitors offer four distinct roles: Owner, Admin, Developer, and Finance, which align well with our needs.
By default, most competitors enable accounts that allow users to invite others into them, with no distinction between personal and team accounts.
process & result
process & result
process & result
The first task I accomplished was creating a document describing roles and permission sets, followed by a meeting where it was discussed and confirmed by all parties involved.
The first task I accomplished was creating a document describing roles and permission sets, followed by a meeting where it was discussed and confirmed by all parties involved.
The first task I accomplished was creating a document describing roles and permission sets, followed by a meeting where it was discussed and confirmed by all parties involved.
Testing
The first iteration was tested with three respondents. It revealed that the initial assets transfer feature, which acted as a fork between two flows—with or without transfer—was quite confusing for test users. After applying a different approach and making it an additional option, it worked out much better. The second user testing study with another group of three users confirmed these improvements.
Testing
The first iteration was tested with three respondents. It revealed that the initial assets transfer feature, which acted as a fork between two flows—with or without transfer—was quite confusing for test users. After applying a different approach and making it an additional option, it worked out much better. The second user testing study with another group of three users confirmed these improvements.
Testing
The first iteration was tested with three respondents. It revealed that the initial assets transfer feature, which acted as a fork between two flows—with or without transfer—was quite confusing for test users. After applying a different approach and making it an additional option, it worked out much better. The second user testing study with another group of three users confirmed these improvements.
Initial forked workflow iteration showcased
Initial forked workflow iteration showcased
Initial forked workflow iteration showcased
Second iteration: enhanced workflow
Second iteration: enhanced workflow
Second iteration: enhanced workflow
Setting up a team
My intention was to design a flow that allows users to set up a team as easily and quickly as possible. Essentially, if users skip editing the name and userpic, it requires just a few taps, meaning users can easily start using their team account.
Setting up a team
My intention was to design a flow that allows users to set up a team as easily and quickly as possible. Essentially, if users skip editing the name and userpic, it requires just a few taps, meaning users can easily start using their team account.
Setting up a team
My intention was to design a flow that allows users to set up a team as easily and quickly as possible. Essentially, if users skip editing the name and userpic, it requires just a few taps, meaning users can easily start using their team account.
Account popover
The account popover serves as an entry point into account management. It enables users to identify the team they are currently working with and includes a button that directs them to a page where they can manage existing teams or create new ones. This design ensures that essential team management features are readily accessible and straightforward to navigate.
Account popover
The account popover serves as an entry point into account management. It enables users to identify the team they are currently working with and includes a button that directs them to a page where they can manage existing teams or create new ones. This design ensures that essential team management features are readily accessible and straightforward to navigate.
Account popover
The account popover serves as an entry point into account management. It enables users to identify the team they are currently working with and includes a button that directs them to a page where they can manage existing teams or create new ones. This design ensures that essential team management features are readily accessible and straightforward to navigate.
Invite teammates
Each team can include up to 20 people. To simplify the invitation process, we’ve added batch invitation sending functionality. This allows users to invite teammates for specific roles by copying and pasting all emails.
Invite teammates
Each team can include up to 20 people. To simplify the invitation process, we’ve added batch invitation sending functionality. This allows users to invite teammates for specific roles by copying and pasting all emails.
Invite teammates
Each team can include up to 20 people. To simplify the invitation process, we’ve added batch invitation sending functionality. This allows users to invite teammates for specific roles by copying and pasting all emails.
next project
Web3 API
The Project feature implementation
next project
Web3 API
The Project feature implementation
outcomes
outcomes
outcomes
Business impact
For us as a business, one key metric we closely monitored was the creation of new user accounts. After introducing the Team Account feature, we tracked this metric to assess its reception. The results clearly indicate that the feature has been well-received and is providing significant value to our users, demonstrating its success from a business perspective.
Business impact
For us as a business, one key metric we closely monitored was the creation of new user accounts. After introducing the Team Account feature, we tracked this metric to assess its reception. The results clearly indicate that the feature has been well-received and is providing significant value to our users, demonstrating its success from a business perspective.
Business impact
For us as a business, one key metric we closely monitored was the creation of new user accounts. After introducing the Team Account feature, we tracked this metric to assess its reception. The results clearly indicate that the feature has been well-received and is providing significant value to our users, demonstrating its success from a business perspective.
+296%
+296%
+296%
growth in team accounts, second half 2023 vs. first half 2024
growth in team accounts, second half 2023 vs. first half 2024
growth in team accounts, second half 2023 vs. first half 2024
User benefits
From the users’ standpoint, this update significantly enhances flexibility in managing the dashboard by allowing the distribution of different roles with appropriate permissions. This improvement makes it easier for teams to operate efficiently and securely.
User benefits
From the users’ standpoint, this update significantly enhances flexibility in managing the dashboard by allowing the distribution of different roles with appropriate permissions. This improvement makes it easier for teams to operate efficiently and securely.
User benefits
From the users’ standpoint, this update significantly enhances flexibility in managing the dashboard by allowing the distribution of different roles with appropriate permissions. This improvement makes it easier for teams to operate efficiently and securely.
learnings
learnings
learnings
Some constraints may be impossible to overcome, but there are numerous strategies to reduce their impact on the final product. This requires the engagement of all parties involved in the process. While design can address some technical issues and limitations, it remains constrained in certain aspects.
I find it more effective to initiate sync-ups myself when designing. This approach allows me to focus on tasks without the pressure of daily check-ins, ensuring that I can meet deadlines more effectively.
next project
Web3 API
The Project feature implementation