Increasing Feature Adoption from 8% to 50% within 3 Months
This project resolves user confusion and extreme drop-offs at the final reward claiming stage to increase daily active users, revive market demand, and compensate for the company's initial engineering costs.

Type: B2C
Industry: Fintech, Web3 & Crypto
Team: 1 Product Designer (me), 1 UX Researcher, Product Manager, Marketing Head
My Role: End-to-end UX ownership, leading discovery, comparative usability testing, and final UI execution
About FOCII
FOCII is an AI-driven verification tool designed to prove a YouTube viewer is an actual human being rather than a bot. It rewards you for your Youtube engagement, by passively tracking attention.

Target Audience
Over 25 million people worldwide are heavy daily internet users who also own crypto, making them a highly active and valuable audience.

Problem Statement
The FOCII browser extension has a severe 92% Adoption Failure Rate, where 173 downloads reduced to just >15 active users. Most users quit right before being able to collect their rewards, as there is a high "Rage Click" Rate on the “Claim” button and massive drop-offs at the same time.

Business Impact: The Token Collapse
A crypto token like BAAI needs three things to survive:
Without these, the token loses all value.
Big investors and crypto exchanges look at one main number: Active Wallets (how many people use the token daily).
The Damage Done:
Strategic Business Goals
To increase the FOCII extension’s Feature Adoption Rate from 8% to 50% within the next 3 months by reducing drop-offs at the adoption phase.
Technical Constraints
The company had already lost substantial capital launching this token ecosystem and could not afford a total code overhaul.
The company allocated a focused 2-week front-end engineering sprint specifically to fix the broken adoption funnel. Because the system was already tracking watch times and token counts behind the scenes, we did not have to build any new back-end tech. This allowed us to execute a complete front-end design, visually reorganizing the existing data that the engineering team could easily deploy within 10 working days.
Success Metrics (Quantitave)
Quantitative:

My Approach to Solve the Leaky Adoption
01
Find the Gap
Identified ambiguity in the user journey through moderated usability tests (n=10)
02
Explore Solutions
Tested alternative layout structures to determine which hierarchy improved clarity around eligibility (n=14)
03
Final Design
Implemented the variant which performed better in terms of productivity and usability
Pattern Observed in the User Journey

Primary Research: Qualitative (Multi-method)
Interviews + Concept Testing: Ran 10 moderated sessions to find why the users were dropping-off before they could claim their rewards.
User Type: Return and Repeat users (only the ones who were not eligible to redeem i.e. hadn’t collected 1000 BAAI tokens yet)

Insights we got from the Talking to the Users
01
Confusing balances
Users couldn't tell the difference between "Total Earnings" from "Available to Claim?”
02
Invisible Threshold
Redemption requirement (i.e. 1000 tokens) was not visible upfront
03
Unpredictable Earnings
Users had no idea how much they were actually making per hour

Strategic Design Interventions
Had to Restructure the Information Architecture
Original Information Architecture of the Dashboard

Updated Information Architecture of the Dashboard

Created 2 Mid-Fidelity Variations


Tested Both the Variants with Users
Criteria for Testing: How clear were the users with Current Balance Clarity, Redeem History, Threshold (1000 tokens) and Today’s Progress


Better Performing Design: Variant B

But again we received some common insights from both the variants which were:

Final Design: Variant B (with minor changes)

Designed for Critical Thresholds
➡️ Threshold 1: Daily Earning Cap (200 tokens)

➡️ Threshold 2: The Redemption Unlock (1000 tokens)

Projected Impact
✅ Increase in Feature Adoption
Increase from 8% to 50%
✅ Decreased Rage Click Rate
Reduced from a high % to almost 0%
✅ Increased DAU
Increase by at least 50% by turning the app into a daily habit for both new and returning old users.
Learnings and reflection
Designing for trust
Test early, save effort
Thank you for reading! Explore my other case studies below to see how I approach different product problems.
@Let’s build something together
Increasing Feature Adoption from 8% to 50% within 3 Months
This project resolves user confusion and extreme drop-offs at the final reward claiming stage to increase daily active users, revive market demand, and compensate for the company's initial engineering costs.

Type: B2C
Industry: Fintech, Web3 & Crypto
Team: 1 Product Designer (me), 1 UX Researcher, Product Manager, Marketing Head
My Role: End-to-end UX ownership, leading discovery, comparative usability testing, and final UI execution
About FOCII
FOCII is an AI-driven verification tool designed to prove a YouTube viewer is an actual human being rather than a bot. It rewards you for your Youtube engagement, by passively tracking attention.

Target Audience
Over 25 million people worldwide are heavy daily internet users who also own crypto, making them a highly active and valuable audience.

Problem Statement
The FOCII browser extension has a severe 92% Adoption Failure Rate, where 173 downloads reduced to just >15 active users. Most users quit right before being able to collect their rewards, as there is a high "Rage Click" Rate on the “Claim” button and massive drop-offs at the same time.

Business Impact: The Token Collapse
A crypto token like BAAI needs three things to survive:
Without these, the token loses all value.
Big investors and crypto exchanges look at one main number: Active Wallets (how many people use the token daily).
The Damage Done:
Strategic Business Goals
To increase the FOCII extension’s Feature Adoption Rate from 8% to 50% within the next 3 months by reducing drop-offs at the adoption phase.
Technical Constraints
The company had already lost substantial capital launching this token ecosystem and could not afford a total code overhaul.
The company allocated a focused 2-week front-end engineering sprint specifically to fix the broken adoption funnel. Because the system was already tracking watch times and token counts behind the scenes, we did not have to build any new back-end tech. This allowed us to execute a complete front-end design, visually reorganizing the existing data that the engineering team could easily deploy within 10 working days.
Success Metrics (Quantitave)
Quantitative:

My Approach to Solve the Leaky Adoption
01
Find the Gap
Identified ambiguity in the user journey through moderated usability tests (n=10)
02
Explore Solutions
Tested alternative layout structures to determine which hierarchy improved clarity around eligibility (n=14)
03
Final Design
Implemented the variant which performed better in terms of productivity and usability
Pattern Observed in the User Journey

Primary Research: Qualitative (Multi-method)
Interviews + Concept Testing: Ran 10 moderated sessions to find why the users were dropping-off before they could claim their rewards.
User Type: Return and Repeat users (only the ones who were not eligible to redeem i.e. hadn’t collected 1000 BAAI tokens yet)

Insights we got from the Talking to the Users
01
Confusing balances
Users couldn't tell the difference between "Total Earnings" from "Available to Claim?”
02
Invisible Threshold
Redemption requirement (i.e. 1000 tokens) was not visible upfront
03
Unpredictable Earnings
Users had no idea how much they were actually making per hour

Strategic Design Interventions
Had to Restructure the Information Architecture
Original Information Architecture of the Dashboard

Updated Information Architecture of the Dashboard

Created 2 Mid-Fidelity Variations


Tested Both the Variants with Users
Criteria for Testing: How clear were the users with Current Balance Clarity, Redeem History, Threshold (1000 tokens) and Today’s Progress


Better Performing Design: Variant B

But again we received some common insights from both the variants which were:

Final Design: Variant B (with minor changes)

Designed for Critical Thresholds
➡️ Threshold 1: Daily Earning Cap (200 tokens)

➡️ Threshold 2: The Redemption Unlock (1000 tokens)

Projected Impact
✅ Increase in Feature Adoption
Increase from 8% to 50%
✅ Decreased Rage Click Rate
Reduced from a high % to almost 0%
✅ Increased DAU
Increase by at least 50% by turning the app into a daily habit for both new and returning old users.
Learnings and reflection
Designing for trust
Test early, save effort
Thank you for reading! Explore my other case studies below to see how I approach different product problems.
@Let’s build something together
Contact me
LinkedInIncreasing Feature Adoption from 8% to 50% within 3 Months
This project resolves user confusion and extreme drop-offs at the final reward claiming stage to increase daily active users, revive market demand, and compensate for the company's initial engineering costs.

Type: B2C
Industry: Fintech, Web3 & Crypto
Team: 1 Product Designer (me), 1 UX Researcher, Product Manager, Marketing Head
My Role: End-to-end UX ownership, leading discovery, comparative usability testing, and final UI execution
About FOCII
FOCII is an AI-driven verification tool designed to prove a YouTube viewer is an actual human being rather than a bot. It rewards you for your Youtube engagement, by passively tracking attention.

Target Audience
Over 25 million people worldwide are heavy daily internet users who also own crypto, making them a highly active and valuable audience.

Problem Statement
The FOCII browser extension has a severe 92% Adoption Failure Rate, where 173 downloads reduced to just >15 active users. Most users quit right before being able to collect their rewards, as there is a high "Rage Click" Rate on the “Claim” button and massive drop-offs at the same time.

Business Impact: The Token Collapse
A crypto token like BAAI needs three things to survive:
Without these, the token loses all value.
Big investors and crypto exchanges look at one main number: Active Wallets (how many people use the token daily).
The Damage Done:
Strategic Business Goals
To increase the FOCII extension’s Feature Adoption Rate from 8% to 50% within the next 3 months by reducing drop-offs at the adoption phase.
Technical Constraints
The company had already lost substantial capital launching this token ecosystem and could not afford a total code overhaul.
The company allocated a focused 2-week front-end engineering sprint specifically to fix the broken adoption funnel. Because the system was already tracking watch times and token counts behind the scenes, we did not have to build any new back-end tech. This allowed us to execute a complete front-end design, visually reorganizing the existing data that the engineering team could easily deploy within 10 working days.
Success Metrics (for next 3 months)
Quantitative:

My Approach to Solve the Leaky Adoption
01
Find the Gap
Identified ambiguity in the user journey through moderated usability tests (n=10)
02
Explore Solutions
Tested alternative layout structures to determine which hierarchy improved clarity around eligibility (n=14)
03
Final Design
Implemented the variant which performed better in terms of productivity and usability
Pattern Observed in the User Journey

Primary Research: Qualitative (Multi-method)
Interviews + Concept Testing: Ran 10 moderated sessions to find why the users were dropping-off before they could claim their rewards.
User Type: Return and Repeat users (only the ones who were not eligible to redeem i.e. hadn’t collected 1000 BAAI tokens yet)

Insights we got from the Talking to the Users
01
Confusing balances
Users couldn't tell the difference between "Total Earnings" from "Available to Claim?”
02
Invisible Threshold
Redemption requirement (i.e. 1000 tokens) was not visible upfront
03
Unpredictable Earnings
Users had no idea how much they were actually making per hour

Strategic Design Interventions
Had to Restructure the Information Architecture
Original Information Architecture of the Dashboard

Updated Information Architecture of the Dashboard

Created 2 Mid-Fidelity Variations


Tested Both the Variants with Users
Criteria for Testing: How clear were the users with Current Balance Clarity, Redeem History, Threshold (1000 tokens) and Today’s Progress


Better Performing Design: Variant B

But again we received some common insights from both the variants which were:

Final Design: Variant B (with minor changes)

Designed for Critical Thresholds
➡️ Threshold 1: Daily Earning Cap (200 tokens)

➡️ Threshold 2: The Redemption Unlock (1000 tokens)

Projected Impact
✅ Increase in Feature Adoption
Increase from 8% to 50%
✅ Decreased Rage Click Rate
Reduced from a high % to almost 0%
✅ Increased DAU
Increase by at least 50% by turning the app into a daily habit for both new and returning old users.
Learnings and reflection
Designing for trust
Test early, save effort
Thank you for reading! Explore my other case studies below to see how I approach different product problems.
@Let’s build something together
Contact me
LinkedInIncreasing Feature Adoption from 8% to 50% within 3 Months
This project resolves user confusion and extreme drop-offs at the final reward claiming stage to increase daily active users, revive market demand, and compensate for the company's initial engineering costs.

Type: B2C
Industry: Fintech, Web3 & Crypto
Team: 1 Product Designer (me), 1 UX Researcher, Product Manager, Marketing Head
My Role: End-to-end UX ownership, leading discovery, comparative usability testing, and final UI execution
About FOCII
FOCII is an AI-driven verification tool designed to prove a YouTube viewer is an actual human being rather than a bot. It rewards you for your Youtube engagement, by passively tracking attention.

Target Audience
Over 25 million people worldwide are heavy daily internet users who also own crypto, making them a highly active and valuable audience.

Problem Statement
The FOCII browser extension has a severe 92% Adoption Failure Rate, where 173 downloads reduced to just >15 active users. Most users quit right before being able to collect their rewards, as there is a high "Rage Click" Rate on the “Claim” button and massive drop-offs at the same time.

Business Impact: The Token Collapse
A crypto token like BAAI needs three things to survive:
Without these, the token loses all value.
Big investors and crypto exchanges look at one main number: Active Wallets (how many people use the token daily).
The Damage Done:
Strategic Business Goals
To increase the FOCII extension’s Feature Adoption Rate from 8% to 50% within the next 3 months by reducing drop-offs at the adoption phase.
Technical Constraints
The company had already lost substantial capital launching this token ecosystem and could not afford a total code overhaul.
The company allocated a focused 2-week front-end engineering sprint specifically to fix the broken adoption funnel. Because the system was already tracking watch times and token counts behind the scenes, we did not have to build any new back-end tech. This allowed us to execute a complete front-end design, visually reorganizing the existing data that the engineering team could easily deploy within 10 working days.
Success Metrics (for next 3 months)
Quantitative:

My Approach to Solve the Leaky Adoption
01
Find the Gap
Identified ambiguity in the user journey through moderated usability tests (n=10)
02
Explore Solutions
Tested alternative layout structures to determine which hierarchy improved clarity around eligibility (n=14)
03
Final Design
Implemented the variant which performed better in terms of productivity and usability
Pattern Observed in the User Journey

Primary Research: Qualitative (Multi-method)
Interviews + Concept Testing: Ran 10 moderated sessions to find why the users were dropping-off before they could claim their rewards.
User Type: Return and Repeat users (only the ones who were not eligible to redeem i.e. hadn’t collected 1000 BAAI tokens yet)

Insights we got from the Talking to the Users
01
Confusing balances
Users couldn't tell the difference between "Total Earnings" from "Available to Claim?”
02
Invisible Threshold
Redemption requirement (i.e. 1000 tokens) was not visible upfront
03
Unpredictable Earnings
Users had no idea how much they were actually making per hour

Strategic Design Interventions
Had to Restructure the Information Architecture
Original Information Architecture of the Dashboard

Updated Information Architecture of the Dashboard

Created 2 Mid-Fidelity Variations


Tested Both the Variants with Users
Criteria for Testing: How clear were the users with Current Balance Clarity, Redeem History, Threshold (1000 tokens) and Today’s Progress


Better Performing Design: Variant B

But again we received some common insights from both the variants which were:

Final Design: Variant B (with minor changes)

Designed for Critical Thresholds
➡️ Threshold 1: Daily Earning Cap (200 tokens)

➡️ Threshold 2: The Redemption Unlock (1000 tokens)

Projected Impact
✅ Increase in Feature Adoption
Increase from 8% to 50%
✅ Decreased Rage Click Rate
Reduced from a high % to almost 0%
✅ Increased DAU
Increase by at least 50% by turning the app into a daily habit for both new and returning old users.
Learnings and reflection
Designing for trust
Test early, save effort
Thank you for reading! Explore my other case studies below to see how I approach different product problems.
@Let’s build something together
Contact me
LinkedInIncreasing Feature Adoption from 8% to 50% within 3 Months
This project resolves user confusion and extreme drop-offs at the final reward claiming stage to increase daily active users, revive market demand, and compensate for the company's initial engineering costs.

Type: B2C
Industry: Fintech, Web3 & Crypto
Team: 1 Product Designer (me), 1 UX Researcher, Product Manager, Marketing Head
My Role: End-to-end UX ownership, leading discovery, comparative usability testing, and final UI execution
About FOCII
FOCII is an AI-driven verification tool designed to prove a YouTube viewer is an actual human being rather than a bot. It rewards you for your Youtube engagement, by passively tracking attention.

Target Audience
Over 25 million people worldwide are heavy daily internet users who also own crypto, making them a highly active and valuable audience.

Problem Statement
The FOCII browser extension has a severe 92% Adoption Failure Rate, where 173 downloads reduced to just >15 active users. Most users quit right before being able to collect their rewards, as there is a high "Rage Click" Rate on the “Claim” button and massive drop-offs at the same time.

Business Impact: The Token Collapse
A crypto token like BAAI needs three things to survive:
Without these, the token loses all value.
Big investors and crypto exchanges look at one main number: Active Wallets (how many people use the token daily).
The Damage Done:
Strategic Business Goals
To increase the FOCII extension’s Feature Adoption Rate from 8% to 50% within the next 3 months by reducing drop-offs at the adoption phase.
Technical Constraints
The company had already lost substantial capital launching this token ecosystem and could not afford a total code overhaul.
The company allocated a focused 2-week front-end engineering sprint specifically to fix the broken adoption funnel. Because the system was already tracking watch times and token counts behind the scenes, we did not have to build any new back-end tech. This allowed us to execute a complete front-end design, visually reorganizing the existing data that the engineering team could easily deploy within 10 working days.
Success Metrics (for next 3 months)
Quantitative:

My Approach to Solve the Leaky Adoption
01
Find the Gap
Identified ambiguity in the user journey through moderated usability tests (n=10)
02
Explore Solutions
Tested alternative layout structures to determine which hierarchy improved clarity around eligibility (n=14)
03
Final Design
Implemented the variant which performed better in terms of productivity and usability
Pattern Observed in the User Journey

Primary Research: Qualitative (Multi-method)
Interviews + Concept Testing: Ran 10 moderated sessions to find why the users were dropping-off before they could claim their rewards.
User Type: Return and Repeat users (only the ones who were not eligible to redeem i.e. hadn’t collected 1000 BAAI tokens yet)

Insights we got from the Talking to the Users
01
Confusing balances
Users couldn't tell the difference between "Total Earnings" from "Available to Claim?”
02
Invisible Threshold
Redemption requirement (i.e. 1000 tokens) was not visible upfront
03
Unpredictable Earnings
Users had no idea how much they were actually making per hour

Strategic Design Interventions
Had to Restructure the Information Architecture
Original Information Architecture of the Dashboard

Updated Information Architecture of the Dashboard

Created 2 Mid-Fidelity Variations


Tested Both the Variants with Users
Criteria for Testing: How clear were the users with Current Balance Clarity, Redeem History, Threshold (1000 tokens) and Today’s Progress


Better Performing Design: Variant B

But again we received some common insights from both the variants which were:

Final Design: Variant B (with minor changes)

Designed for Critical Thresholds
➡️ Threshold 1: Daily Earning Cap (200 tokens)

➡️ Threshold 2: The Redemption Unlock (1000 tokens)

Projected Impact
✅ Increase in Feature Adoption
Increase from 8% to 50%
✅ Decreased Rage Click Rate
Reduced from a high % to almost 0%
✅ Increased DAU
Increase by at least 50% by turning the app into a daily habit for both new and returning old users.
Learnings and reflection
Designing for trust
Test early, save effort
Thank you for reading! Explore my other case studies below to see how I approach different product problems.
@Let’s build something together
Contact me
LinkedIn