Tracking strategic and transactional UX work
However, another thing that is more specific to the UX department which may be more valuable to track is strategic vs transactional. Are we more generative or executing tasks as they come? Are we staying ahead or keeping up? This is one of the most important aspects that we need to improve collectively.
- We could track issue authorship, but it’s not representative. We might generate ideas ahead of a milestone in an issue that wasn't created by a UXer.
- We could also track the number of UX ready issues before milestone start, but even so some issues may be transactional and it's difficult to differentiate them.
- Add new
UX:strategic: issue with a high-level idea or a concrete proposal that has been initially generated or later developed by a UXer; issue must not be scheduled for a version milestone (e.g. %12.4); issue can be created by someone else.
UX:transactional: every other issue — essentially issues that haven't been generated/developed ahead of a version milestone by a UXer. These are the issues in a version milestone that we work on because someone else thought they are a good idea and need to be done. We are tasked with these issues.
- Research work should definitely be included.
- We can have a setup similar to the backend throughput graphs with these labels and generate reports each milestone (as suggested by @tauriedavis)
- Add new
- Research should involve 'gathering user feedback'. You could gather user feedback via a survey, UsabilityHub study, card sort/tree test, usability testing and/or user interviews.
- Ultimately, we want to distinguish solutions/problems that are not just gut feeling or assumptions from solutions/problems that have been researched.
- Instead of having 2 labels we can only use 1 label. We can consider that issues without this label weren't researched before being closed/shipped.