[UXR] Understand user needs around date range selection
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem Statement
When executives or managers use VSM, they spend too much effort aligning custom date ranges to match the time frames that their organizations use to measure productivity. For example, quarters, milestones, iterations.
It would be good to understand how users think of milestones or iterations in terms of due dates.
Currently, this would make sense for GitLab since our releases are tied to milestones but would this also apply to other orgs?
Hypothesis: Providing managers easier ways to filter date ranges by milestones or iterations will decrease to need to use the custom option on the date range picker. It should also speed up their workflows.
Reach
Estimate: 3.0 = Significant reach (~25% to ~50%)
Impact
1.0 = Medium impact
Confidence
n/a
Effort
TBD
Definition of Done
- [ ] The problem is well understood by the PM to have an understanding summarized in a RICE score
- [ ] The problem is well understood by the PM to decide if they want to move forward with this idea or drop it
- [ ] The problem is well described and detailed with necessary requirements for product design to understand the problem
- [ ] The problem is well described and detailed with necessary requirements for engineering to understand the problem