-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add relative links for table of contents
- Loading branch information
1 parent
6fa9542
commit a2196e0
Showing
8 changed files
with
201 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,111 @@ | ||
|  | ||
|
|
||
| # 🌐Overview | ||
|
|
||
| We will test the Staking Flow alongside with the Multiple Application Authorization Flow for existing stakers and new stakers. | ||
| The Staking flow has never been tested out before so it is an opportunity to bring improvements to this flow as well since the Stakers are the backbone of our network. | ||
| Additional Context: | ||
| * PRE application was believed it needs authorization, it turned out it’s already authorized for existing stakers. | ||
| * Existing Stakers who have set an Authorizer Address different from the Owner Address are required to take a separate route to authorize their stakes. | ||
|
|
||
| ## 🎯 Goals | ||
|
|
||
| * Map out thoughts and feelings about the Staking Process and the Staking Requirements | ||
| * Identify the possible issues and misalignments with the users’ mental models | ||
| * Uncover the friction points in the Staking and MAS User Journey | ||
| * Identify team’s blind spots on Staking and MAS | ||
| * Probe our assumptions with real data | ||
| --- | ||
| ### 🤼 Team | ||
|
|
||
| * 🐱 User Researcher: Sasha Tanase | ||
| * 👓 Observer: Liz Shinn, hopefully some other team members | ||
| * 🦄 Product Designers: Sasha Tanase, Liz Shinn | ||
| * 👾 Frontend Engineers: Rafal Cza, George Weiler | ||
| * 🚀 Status - Done | ||
|
|
||
| --- | ||
| ### 🎯 Study Goals | ||
|
|
||
| * learn more about possible future stakers | ||
| * learn more about Threshold Stakers | ||
| * discover pain points and turn them into opportunities | ||
| * test our current product flows | ||
| * probe our current User Journey Map | ||
|
|
||
| ### 💬 Methodology | ||
|
|
||
| The research study methodology is the following one: | ||
|
|
||
| * Define the user profile we want to talk to - node operators have been uncovered as the most important users for Threshold Network. We’ll talk to 5 existing Threshold Stakers and 5 participants who have the staker knowledge but currently are not Threshold Network Stakers. | ||
| * Design a screener for the recruiting announcement - screener | ||
| * Schedule interviews - 45 min or 60 min interviews - will define the exact duration after the script is finalised | ||
| * Topics - Hi level interview agenda | ||
| * General, warm-up | ||
| * Background in blockchain - experience, savviness, node operation experience/staker experience | ||
| * Non Threshold Staker | ||
| * Staker experience | ||
| * When did they start being a staker? | ||
| * Which network are they staker/node operator for? | ||
| * Why did they become stakers for x? | ||
| * What is the process to become a staker for X? | ||
| * What would they change from X staking process? | ||
| * What do they like the most from X staking process? | ||
| * What keeps them up at night as a staker? | ||
| * What would make them stop staking on X? | ||
| * 5 seconds test - Staking Banner | ||
| * Task 1 - Stake into the Threshold Network | ||
| * SEQ | ||
| * Task 2 - Authorize an/another app | ||
| * SEQ | ||
| * Task 3 - Decrease the authorization of an app | ||
| * SEQ | ||
| * Read out loud walkthrough - How it works page | ||
| * Threshold Staker | ||
| * Staker experience | ||
| * When did they start being a staker? | ||
| * Which network are they staker/node operator for? | ||
| * Why did they become stakers for Threshold? | ||
| * What is the process to become a staker for Threshold ? | ||
| * What would they change from Threshold staking process? | ||
| * What do they like the most from Threshold staking process? | ||
| * What keeps them up at night as a staker? | ||
| * What would make them stop staking on Threshold? | ||
| * 5 seconds test - Staking Banner | ||
| * Task 1 - Authorize an app for one of your existing stakes. | ||
| * SEQ | ||
| * Task 2 - Authorize an/another app | ||
| * SEQ | ||
| * Task 3 - Decrease the authorization of an app | ||
| * SEQ | ||
| * Read out loud walkthrough - How it works page | ||
| * Document | ||
| * Analyze | ||
| * Report | ||
| 🖇Scenarios for Usability Testing | ||
| 2 cohorts of 5-8 participants | ||
|
|
||
| ### Cohort 1 - First time stakers | ||
|
|
||
| * Task 1 - Stake into the Threshold Network | ||
| Prototype Link: | ||
| https://www.figma.com/proto/Tx1lZc7us4SqCeAgbt1hBV/Threshold-Dapp?page-id=4787%3A270648&node-id=4808%3A405782&viewport=48%2C393%2C0.02&scaling=min-zoom&starting-point-node-id=4808%3A405782&show-proto-sidebar=1 | ||
| * Task 2 - Authorize an/another app | ||
| Prototype Link:https://www.figma.com/proto/Tx1lZc7us4SqCeAgbt1hBV/Threshold-Dapp?page-id=4787%3A270648&node-id=4808%3A405857&viewport=48%2C393%2C0.02&scaling=min-zoom&starting-point-node-id=4808%3A405857&show-proto-sidebar=1 | ||
| * Task 3 - Decrease the authorization of an app | ||
| Prototype Link: | ||
| https://www.figma.com/proto/Tx1lZc7us4SqCeAgbt1hBV/Threshold-Dapp?page-id=4787%3A270650&node-id=4875%3A289027&viewport=-140%2C165%2C0.03&scaling=min-zoom&starting-point-node-id=4875%3A289027 | ||
|
|
||
| ### Cohort 2 - Existing stakers | ||
|
|
||
| * Task 1 - Authorize an app for one of your existing stakes. | ||
| Prototype Link: https://www.figma.com/proto/Tx1lZc7us4SqCeAgbt1hBV/Threshold-Dapp?page-id=4787%3A270649&node-id=4842%3A290201&viewport=56%2C341%2C0.02&scaling=min-zoom&starting-point-node-id=4821%3A413054&show-proto-sidebar=1 | ||
| * Task 2 - Authorize another app | ||
| Prototype Link: | ||
| https://www.figma.com/proto/Tx1lZc7us4SqCeAgbt1hBV/Threshold-Dapp?page-id=4787%3A270649&node-id=4821%3A411031&viewport=56%2C341%2C0.02&scaling=min-zoom&starting-point-node-id=4821%3A411031&show-proto-sidebar=1 | ||
| * Task 3 - Decrease the authorization of an app | ||
| Prototype Link: | ||
| https://www.figma.com/proto/Tx1lZc7us4SqCeAgbt1hBV/Threshold-Dapp?page-id=4787%3A270650&node-id=4875%3A289027&viewport=-140%2C165%2C0.03&scaling=min-zoom&starting-point-node-id=4875%3A289027 | ||
|
|
||
| ## 🦄 Report | ||
| [Report](./MAS%20Iterative%20User%20Study.pdf) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
|  | ||
|
|
||
| **🤼 Team** | ||
| - 🐱 User Researcher: Sasha Tanase | ||
| - 👓 Observer: Liz Shinn, hopefully some other team members | ||
| - 🦄 Product Designers: Sasha Tanase, Liz Shinn | ||
| - 👾 Frontend Engineers: Rafal Cza, George Weiler | ||
| - 🚀 Status - In progress | ||
|
|
||
|
|
||
| # 🌐Overview | ||
| We will test the Staking Flow alongside with the Multiple Application Authorization Flow for existing stakers and new stakers. | ||
| The Staking flow has never been tested out before so it is an opportunity to bring improvements to this flow as well since the Stakers are the backbone of our network. | ||
| Additional Context: | ||
| * PRE application was believed it needs authorization, it turned out it’s already authorized for existing stakers. | ||
| * Existing Stakers who have set an Authorizer Address different from the Owner Address are required to take a separate route to authorize their stakes. | ||
|
|
||
| ## 🎯 Goals | ||
| * Map out thoughts and feelings about the Staking Process and the Staking Requirements | ||
| * Identify the possible issues and misalignments with the users’ mental models | ||
| * Uncover the friction points in the Staking and MAS User Journey | ||
| * Identify team’s blind spots on Staking and MAS | ||
| * Probe our assumptions with real data | ||
|
|
||
| # 📚 Table of Contents | ||
| 1. [Usability Study](./iterative-user-study/readme.md) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,55 @@ | ||
|  | ||
| # 🌐Overview | ||
|
|
||
| ## 🎯 Goals | ||
|
|
||
| * Map out thoughts and ideas about the tBTC users | ||
| * Identify the whole possible range of users for tBTC users | ||
| * Narrow down the most important users for tBTC users | ||
| * Identify team’s blind spots on tBTC and BTC user behaviours | ||
| * Probe our assumptions with real data | ||
|
|
||
| ### 🎯 Study Goals | ||
|
|
||
| * learn more about BTC users | ||
| * learn more about potential tBTC users | ||
| * discover pain points and turn them into opportunities | ||
| * test our current product flows | ||
| * check if our product offers what the market needs | ||
|
|
||
| ### 💬 Methodology | ||
|
|
||
| The research study methodology is the following one: | ||
| * Define the user profile we want to talk to - node operators have been uncovered as the most important users for Keep | ||
| * Design a screener for the recruiting announcement - screener | ||
| * Schedule interviews - 45 min or 60 min interviews - will define the exact duration after the script is finalised | ||
| * Topics - Hi level interview agenda | ||
| * General, warm-up | ||
| * Background in blockchain - experience, savviness, why and how they become interested in blockchain, importance of decentralisation | ||
| * Bridges | ||
| * which bridges did they use? | ||
| * what’s the common destination when using bridge? | ||
| * BTC>ETH? which ones? | ||
| * | ||
| * Document | ||
| * Analyze | ||
| * Report | ||
|
|
||
| ### ⏲ Project Timeline | ||
|
|
||
| Date Task | ||
| Jul 25 Assumption Mapping with the team | ||
| Jul 25 Send out Interview recruitment announcement and screener | ||
| Jul 25 Interview Script | ||
| Jul 25 Schedule interviews | ||
| Aug 1 Conduct Interviews | ||
| Aug 8 Analyze Data (4-5 days) | ||
| Aug 8 Distill Data into a Report | ||
| Aug 12 Present the Report to the Threshold Team | ||
|
|
||
| After each interview there will be a debriefing session. | ||
|
|
||
|
|
||
| # 🦄 Report | ||
|
|
||
| [Report](./tBTC%20Iterative%20User%20Study.pdf) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters