The UX team performs several investigations and design efforts for the UI dev team. We use these flows to work through how we shape the product to use-cases and design the new addition.
There are three types of UX flows today:
- The bug and feature request flow when it needs UX attention before development can act on it
- The ticket gets attention from the UX team after normal triage
- When the UX team has made a decision it will return to developers
- Decision-making can be made through collaboration with SMEs or external individuals that have domain knowledge
- UX feature design effort for larger feature efforts
- An internal UX flow
This flow is used when there is no reliance on a direct developer follow up. For those flows, see the bug and feature request flow.
This flow assists in both internal flows and flows to fit the larger feature efforts.
A larger feature effort flow:
- UX creates an issue via their internal UX template
- If this is for feature work, you'll need to do one more step and link it to your related feature Tracker
Note: If the issue is not mentioned in the tracker, artifacts associated to this effort will likely be hidden from easy access.
- If this is for feature work, you'll need to do one more step and link it to your related feature Tracker
- Change the status from
UntriagedtoUX Backlogand skip the triage team- If this is accidentally missed, the Triage team will move it along
- Process continues as the UX flows need until the ticket is completed and then it is closed