I have added a new label “ux-surprise” on github. This tracks problems that a casual DB/SQL user would be “Surprised” with if they don’t know much about CockroachDB and are working from public information published on the web.
The label should be used for things like discrepancies between our docs and product; discrepancy between our product and other products that we don’t explain/document properly; and corner cases of our functionality that may cause a headache for users to understand properly. It can target both functional problems (“this does not produce the expected outout”) and extra-functional problems (“this is slower than I expected”).
I initially thought about using the name “ux-bug” but I feared that some people would come and say “‘ux-bug’ is too close to ‘bug’, so let’s merge them”. I really think that a ux bug is categorically different from our other product bugs in that a “fix” may in some cases be a matter of improving our docs.
Also as a side effect I predict that the process of addressing “UX surprises” will increase the feeling of users that our product is “polished”.