Skip to content
This repository was archived by the owner on Jul 2, 2024. It is now read-only.

Commit ad221b2

Browse files
authored
clarifying priority definitions (#2755)
## Test Plans not applicable -- handbook update
1 parent d5bffcd commit ad221b2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/departments/product-engineering/product/process/surfacing_product_feedback.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ If you have gotten a specific feedback request that a customer(s) would like to
2525

2626
To create a Product Gap, navigate to the impacted customer(s) most recent Opportunity, whether it's a net new opp or a renewal. When viewing the Opportunity, you should see a related list labeled "Product Gap Submissions". Create a new Submission, and search in the field Product Gap to see if a gap already exists for what you wish to log. If no gap exists, create one, and then continue creating your submission that will tie your customer to the Product Gap. A gap submission should include the following:
2727

28-
- Severity - P0, P1, P2
28+
- Severity - P0: Dealbreaker, P1: Significant Pain Point, P2: Nice to Have
2929
- Use Case - _if relevant_ tie your submission to one or multiple core use cases to help with prioritization
3030
- Description
3131
- Impact

0 commit comments

Comments
 (0)