Deprecating or Redefining the use of Researched and Product Discovery labels
We have a few labels that I think can be deprecated or redefined.
1 - The first and most straightforward is ~"researched". This label indicated that UX research had been done as part of the issue. We will now use ~"problem validation" and ~"solution validation" instead, so this label should be deprecated. Unless anyone has an objection I'll go ahead and deprecate the label.
- Teams seem to use the product discovery label in different ways, and so in practice, it's not communicating the stated intent, which is that design activities are needed and deliverables will be produced. For example, it seems that only 'larger' UX efforts get this label, while many other UX issues also have some kind of output regarding design direction.
- ~"problem validation" and ~"solution validation" labels are now a good indicator that there will be collaboration and discussion on the problem and potential solutions, making product discovery redundant.
- ~"UX Ready" is used to indicate that UX deliverables are ready, which again seems somewhat redundant to product discovery.
- This label might be less necessary as teams move to more continuous releases - at the least the definition should be updated.
So I have a few questions about this:
- Do you need product discovery anymore and if so, how are you using it? How can we make the definition more accurate/clear?
- Can we drop this label and use ~"UX Ready" to communicate that an issue is ready to move beyond UX?
- Do we need a workflow/progress marking label like ~"designing" or ~"solutioning" to indicate we're in the process of creating the solution?