Create UXImprovementProcess

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/zkSNACKs/zIPs/blob/master/UXImprovementProcess.md) | Company | UXImprovementProcess | cosmicbutterglue | Process | Proposal |

UXImprovementProcess.md

@@ -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.