From 018bae2f69718617cf63766fc713124f3c5304c3 Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Sun, 2 Oct 2022 20:12:30 +0200 Subject: [PATCH 01/14] Create UXImprovementProcess --- UXImprovementProcess | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 UXImprovementProcess diff --git a/UXImprovementProcess b/UXImprovementProcess new file mode 100644 index 0000000..61d789e --- /dev/null +++ b/UXImprovementProcess @@ -0,0 +1,39 @@ +## UX Improvement Process + +``` +zIP: 6 +Layer: Company +Title: UX Improvement Process +Author: cosmicbutterglue +Status: Active +Type: Process +Created: 2022-10-02 +License: lol +``` +## Motivation + +UX improvements are hard. Right now, we are gathering UX feedback from many different places (Twitter, contribution games, Bitcointalk, etc.). The problem: The UX research we gather is not reproducible. We may get many different opinions, but are unable to identify where exactly the user is encountering issues (and where they aren't). This results in improving UX in the dark. We may identify pain points and resolve them, but we may also identify them wrongly and make the user experience worse by accident. This results in a lot of wasted time for developers as well as unhappy users, which are both scenarios we should try to avoid as best we can. + +## Develop a Streamlined UX Improvement Process + +To avoid wasting time on developing UX solutions which may not be needed, or worse, make UX more complicated, we should develop a streamlined UX improvement process. This could look something like this: + +### 0. Form a pool of UX Testers + +Establish a pool of UX Testers comprised of advanced users and noobs. Ideally both groups are made up of 10-20 people or more. For every round of testing, Testers should receive small bounties to motivate participation. + +### 1. Identify the issue + +Often times we already have a good idea of what is hindering good UX. When such potential pain points are identified, an issue should be opened on GH explaining the perceived UX problem. + +### 2. Get User Feedback + +Present the perceived issue to the UX Testing groups. If the majority of the testing groups agrees with the issue, move to step 3. If the majority of the testing groups does not see the issue, mark issue as resolved. If results are inconclusive, widen testing groups. + +### 3. Develop a Solution. + +Develop a prototype for a solution. This does not yet need to be executable code, a click-dummy would suffice to save time. This would also solve the problem of noobs not knowing how to compile code from source and save time for the testing group. + +### 4. Test the Solution + +Present the testing groups with the solution in a screen-shared call. Let the testing group interact with the solution and give them tasks to perform to see if the solution solves the problem. This process should be documented (e.g. screen-recorded) to give insights into interactions with the product in general and clearly identify other potential pain points. If the majority of the testing groups sees the issue as resolved develop executable code and merge to master. If the solution does not solve the issue return to 3. From 09cc89cf8c8680d99b3353c0866212994f686a03 Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Sun, 2 Oct 2022 20:17:29 +0200 Subject: [PATCH 02/14] Rename UXImprovementProcess to UXImprovementProcess.md --- UXImprovementProcess => UXImprovementProcess.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename UXImprovementProcess => UXImprovementProcess.md (100%) diff --git a/UXImprovementProcess b/UXImprovementProcess.md similarity index 100% rename from UXImprovementProcess rename to UXImprovementProcess.md From 85209b212500d7c1e075b169439ec6c17631bfb7 Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Sun, 2 Oct 2022 20:38:51 +0200 Subject: [PATCH 03/14] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 4e37244..6500760 100644 --- a/README.md +++ b/README.md @@ -7,3 +7,4 @@ | [3](https://github.com/zkSNACKs/zIPs/blob/master/Wasabi2.0%20Screenshots.zip) | Communication | Wasabi Wallet 2.0 Screenshots | Norbert Lévai | Informational | Active | | [4](https://github.com/zkSNACKs/zIPs/blob/master/WasabiPressKit.zip) | Communication | zkSNACKs Press Kit | Norbert Lévai | Informational | Active | | [5](https://github.com/zkSNACKs/zIPs/blob/master/Controversy.md) | Company | Controversy | nopara73 | Process | Active | +| [6](https://github.com/cosmicbutterglue/zIPs/blob/patch-1/UXImprovementProcess.md) | Company | UXImprovementProcess | cosmicbutterglue | Process | Active | From 308b781729126585f7306d058da3e0c1f06c9407 Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Mon, 3 Oct 2022 12:12:48 +0200 Subject: [PATCH 04/14] Update README.md Co-authored-by: yahiheb <52379387+yahiheb@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6500760..049083d 100644 --- a/README.md +++ b/README.md @@ -7,4 +7,4 @@ | [3](https://github.com/zkSNACKs/zIPs/blob/master/Wasabi2.0%20Screenshots.zip) | Communication | Wasabi Wallet 2.0 Screenshots | Norbert Lévai | Informational | Active | | [4](https://github.com/zkSNACKs/zIPs/blob/master/WasabiPressKit.zip) | Communication | zkSNACKs Press Kit | Norbert Lévai | Informational | Active | | [5](https://github.com/zkSNACKs/zIPs/blob/master/Controversy.md) | Company | Controversy | nopara73 | Process | Active | -| [6](https://github.com/cosmicbutterglue/zIPs/blob/patch-1/UXImprovementProcess.md) | Company | UXImprovementProcess | cosmicbutterglue | Process | Active | +| [6](https://github.com/zkSNACKs/zIPs/blob/master/UXImprovementProcess.md) | Company | UXImprovementProcess | cosmicbutterglue | Process | Active | From afb87c6355a81dd0beaf8745506bb3e55f8556d0 Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Mon, 3 Oct 2022 23:47:17 +0200 Subject: [PATCH 05/14] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 049083d..f05f161 100644 --- a/README.md +++ b/README.md @@ -7,4 +7,4 @@ | [3](https://github.com/zkSNACKs/zIPs/blob/master/Wasabi2.0%20Screenshots.zip) | Communication | Wasabi Wallet 2.0 Screenshots | Norbert Lévai | Informational | Active | | [4](https://github.com/zkSNACKs/zIPs/blob/master/WasabiPressKit.zip) | Communication | zkSNACKs Press Kit | Norbert Lévai | Informational | Active | | [5](https://github.com/zkSNACKs/zIPs/blob/master/Controversy.md) | Company | Controversy | nopara73 | Process | Active | -| [6](https://github.com/zkSNACKs/zIPs/blob/master/UXImprovementProcess.md) | Company | UXImprovementProcess | cosmicbutterglue | Process | Active | +| [6](https://github.com/zkSNACKs/zIPs/blob/master/UXImprovementProcess.md) | Company | UXImprovementProcess | cosmicbutterglue | Process | Proposal | From 56d249dcc125d0ee80943d3c443c4ebb2fc8a98f Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Wed, 5 Oct 2022 13:56:31 +0200 Subject: [PATCH 06/14] Update UXImprovementProcess.md Co-authored-by: nopara73 --- UXImprovementProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UXImprovementProcess.md b/UXImprovementProcess.md index 61d789e..86eafbc 100644 --- a/UXImprovementProcess.md +++ b/UXImprovementProcess.md @@ -5,7 +5,7 @@ zIP: 6 Layer: Company Title: UX Improvement Process Author: cosmicbutterglue -Status: Active +Status: Proposed Type: Process Created: 2022-10-02 License: lol From e74c0b798c01bbeccf2e0de1d5ad6c4555e63034 Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Wed, 5 Oct 2022 13:56:52 +0200 Subject: [PATCH 07/14] Update README.md Co-authored-by: nopara73 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f05f161..1808820 100644 --- a/README.md +++ b/README.md @@ -7,4 +7,4 @@ | [3](https://github.com/zkSNACKs/zIPs/blob/master/Wasabi2.0%20Screenshots.zip) | Communication | Wasabi Wallet 2.0 Screenshots | Norbert Lévai | Informational | Active | | [4](https://github.com/zkSNACKs/zIPs/blob/master/WasabiPressKit.zip) | Communication | zkSNACKs Press Kit | Norbert Lévai | Informational | Active | | [5](https://github.com/zkSNACKs/zIPs/blob/master/Controversy.md) | Company | Controversy | nopara73 | Process | Active | -| [6](https://github.com/zkSNACKs/zIPs/blob/master/UXImprovementProcess.md) | Company | UXImprovementProcess | cosmicbutterglue | Process | Proposal | +| [6](https://github.com/zkSNACKs/zIPs/blob/master/UXImprovementProcess.md) | Company | UXImprovementProcess | cosmicbutterglue | Process | Proposed | From c21be9df6027e4070c7c8e0cab9123e75e5e5a6b Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Wed, 5 Oct 2022 14:00:07 +0200 Subject: [PATCH 08/14] Update UXImprovementProcess.md --- UXImprovementProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UXImprovementProcess.md b/UXImprovementProcess.md index 86eafbc..bb5062c 100644 --- a/UXImprovementProcess.md +++ b/UXImprovementProcess.md @@ -20,7 +20,7 @@ To avoid wasting time on developing UX solutions which may not be needed, or wor ### 0. Form a pool of UX Testers -Establish a pool of UX Testers comprised of advanced users and noobs. Ideally both groups are made up of 10-20 people or more. For every round of testing, Testers should receive small bounties to motivate participation. +Establish a pool of UX Testers comprised of 3/4 noobs and 1/4 advanced users. Ideally both groups are made up of 10-20 people or more. For every round of testing, Testers should receive small bounties to motivate participation. ### 1. Identify the issue From 01bf1933899e6e3722d4b10885aee2a1b8ae9f2e Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Wed, 5 Oct 2022 14:02:05 +0200 Subject: [PATCH 09/14] Update UXImprovementProcess.md --- UXImprovementProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UXImprovementProcess.md b/UXImprovementProcess.md index bb5062c..c06e003 100644 --- a/UXImprovementProcess.md +++ b/UXImprovementProcess.md @@ -20,7 +20,7 @@ To avoid wasting time on developing UX solutions which may not be needed, or wor ### 0. Form a pool of UX Testers -Establish a pool of UX Testers comprised of 3/4 noobs and 1/4 advanced users. Ideally both groups are made up of 10-20 people or more. For every round of testing, Testers should receive small bounties to motivate participation. +Establish a pool of UX Testers comprised of 3/4 noobs and 1/4 advanced users. For every round of testing, Testers should receive small bounties to motivate participation. ### 1. Identify the issue From 63213e72c5c2d1e27f511cd6c0e16f5c22d76bc8 Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Mon, 24 Oct 2022 12:42:58 +0200 Subject: [PATCH 10/14] Update UXImprovementProcess.md --- UXImprovementProcess.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/UXImprovementProcess.md b/UXImprovementProcess.md index c06e003..121967d 100644 --- a/UXImprovementProcess.md +++ b/UXImprovementProcess.md @@ -28,7 +28,7 @@ Often times we already have a good idea of what is hindering good UX. When such ### 2. Get User Feedback -Present the perceived issue to the UX Testing groups. If the majority of the testing groups agrees with the issue, move to step 3. If the majority of the testing groups does not see the issue, mark issue as resolved. If results are inconclusive, widen testing groups. +Present the perceived issue to the UX Testing groups and observe whether the issue exists for the users. If the issue exists for users, move to step 3. If the majority of the testing groups does not see the issue, mark issue as resolved. If results are inconclusive, widen testing groups. ### 3. Develop a Solution. @@ -36,4 +36,4 @@ Develop a prototype for a solution. This does not yet need to be executable code ### 4. Test the Solution -Present the testing groups with the solution in a screen-shared call. Let the testing group interact with the solution and give them tasks to perform to see if the solution solves the problem. This process should be documented (e.g. screen-recorded) to give insights into interactions with the product in general and clearly identify other potential pain points. If the majority of the testing groups sees the issue as resolved develop executable code and merge to master. If the solution does not solve the issue return to 3. +Present the testing groups with the solution in a screen-shared call. Let the testing group interact with the solution and give them tasks to perform to see if the solution solves the problem. This process should be documented (e.g. screen-recorded) to give insights into interactions with the product in general and clearly identify other potential pain points. If the issue is resolved for the majority of the testing groups develop executable code and merge to master. If the solution does not solve the issue return to 3. From 54f5d2a8e60c92f63ffd0671546b9627b95949c1 Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Mon, 24 Oct 2022 12:43:31 +0200 Subject: [PATCH 11/14] Update UXImprovementProcess.md --- UXImprovementProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UXImprovementProcess.md b/UXImprovementProcess.md index 121967d..efc323d 100644 --- a/UXImprovementProcess.md +++ b/UXImprovementProcess.md @@ -16,7 +16,7 @@ UX improvements are hard. Right now, we are gathering UX feedback from many diff ## Develop a Streamlined UX Improvement Process -To avoid wasting time on developing UX solutions which may not be needed, or worse, make UX more complicated, we should develop a streamlined UX improvement process. This could look something like this: +To avoid wasting time on developing UX solutions which may not be needed, or worse, make UX more complicated, we should develop a streamlined UX improvement process. ### 0. Form a pool of UX Testers From 4ed3dfe6c003022ea2ae0a26d2f7002c5225285f Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Mon, 24 Oct 2022 12:45:32 +0200 Subject: [PATCH 12/14] Update UXImprovementProcess.md --- UXImprovementProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UXImprovementProcess.md b/UXImprovementProcess.md index efc323d..61943ae 100644 --- a/UXImprovementProcess.md +++ b/UXImprovementProcess.md @@ -28,7 +28,7 @@ Often times we already have a good idea of what is hindering good UX. When such ### 2. Get User Feedback -Present the perceived issue to the UX Testing groups and observe whether the issue exists for the users. If the issue exists for users, move to step 3. If the majority of the testing groups does not see the issue, mark issue as resolved. If results are inconclusive, widen testing groups. +Observe whether the issue exists for the testing groups by giving them tasks to perform in a documented, screen shared call. If the issue exists for users, move to step 3. If the majority of the testing groups does not encounter the issue, mark issue as resolved. If results are inconclusive, widen testing groups. ### 3. Develop a Solution. From de23323e28228f279f2a3af794439bbc29656d49 Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Mon, 24 Oct 2022 12:48:59 +0200 Subject: [PATCH 13/14] Update UXImprovementProcess.md --- UXImprovementProcess.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/UXImprovementProcess.md b/UXImprovementProcess.md index 61943ae..f7bed8d 100644 --- a/UXImprovementProcess.md +++ b/UXImprovementProcess.md @@ -14,6 +14,8 @@ License: lol UX improvements are hard. Right now, we are gathering UX feedback from many different places (Twitter, contribution games, Bitcointalk, etc.). The problem: The UX research we gather is not reproducible. We may get many different opinions, but are unable to identify where exactly the user is encountering issues (and where they aren't). This results in improving UX in the dark. We may identify pain points and resolve them, but we may also identify them wrongly and make the user experience worse by accident. This results in a lot of wasted time for developers as well as unhappy users, which are both scenarios we should try to avoid as best we can. +In addition to resolvng UX issues, this process can help eliviate controversy with proposed UX improvements. Instead of debating internally what improvements are the best, we should be gathering reproducible user feedback on proposed improvements to clarify which proposals work best for the user. + ## Develop a Streamlined UX Improvement Process To avoid wasting time on developing UX solutions which may not be needed, or worse, make UX more complicated, we should develop a streamlined UX improvement process. From f84ec18088358ce2aba79b33166fdf149d385ef4 Mon Sep 17 00:00:00 2001 From: cosmicbutterglue <114531812+cosmicbutterglue@users.noreply.github.com> Date: Mon, 24 Oct 2022 12:53:26 +0200 Subject: [PATCH 14/14] Update UXImprovementProcess.md --- UXImprovementProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UXImprovementProcess.md b/UXImprovementProcess.md index f7bed8d..a2eb78f 100644 --- a/UXImprovementProcess.md +++ b/UXImprovementProcess.md @@ -18,7 +18,7 @@ In addition to resolvng UX issues, this process can help eliviate controversy wi ## Develop a Streamlined UX Improvement Process -To avoid wasting time on developing UX solutions which may not be needed, or worse, make UX more complicated, we should develop a streamlined UX improvement process. +To avoid controversy as well as wasting time on developing UX solutions which may not be needed, or worse, make UX more complicated, we should develop a streamlined UX improvement process. ### 0. Form a pool of UX Testers