Commit c49b5b7f authored by Mark Pundsack's avatar Mark Pundsack
Browse files

Update design.md

parent 581bffde0bde
......@@ -27,13 +27,10 @@ The initial issue should be about the problem we are solving. If a separate [pro
In order to complete a product discovery issue in a release, you must complete the following:
1. UXer removes the ~UX label, adds the ~"UX ready" label
1. UXer removes the ~UX label, adds the ~"UX ready" label.
1. Modify the issue description in the product discovery issue to contain the final design. If it makes sense, the original information indicating the need for the design can be moved to a lower "Original Information" section.
1. Update the delivery issue for which the product discover issue was created. Do not simply refer to the product discovery issue as a separate source of truth.
1. In some cases, a product discovery issue also identifies future enhancements that will not go into the issue that originated the product discovery issue. For these items, create new issues in the backlog containing the designs to ensure they are not lost.
Product discovery issues can not be closed or considered complete until each
of these steps have occurred.
1. Copy the design to the description of the delivery issue for which the product discovery issue was created. Do not simply refer to the product discovery issue as a separate source of truth.
1. In some cases, a product discovery issue also identifies future enhancements that will not go into the issue that originated the product discovery issue. For these items, create new issues containing the designs to ensure they are not lost. Put the issues in the backlog if they are agreed upon as good ideas. Otherwise leave them for triage.
## Style guides
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment