diff --git a/.github/ISSUE_TEMPLATE/ideas--irritations-and-needs.md b/.github/ISSUE_TEMPLATE/ideas--irritations-and-needs.md index 977d41cf8..c8296014e 100644 --- a/.github/ISSUE_TEMPLATE/ideas--irritations-and-needs.md +++ b/.github/ISSUE_TEMPLATE/ideas--irritations-and-needs.md @@ -20,17 +20,10 @@ _When , I want to , so I can _ ## How are they currently doing this? -
- Triage Template (core team only) +## How well understood is this problem? + - This template is for members of the team to triage for prioritisation. For more guidance see https://www.loom.com/share/369ab467fbc64dec848085d38ff57ca0: - - P1 high frequency, high impact - P2 low frequency, high impact - P3 high frequency, low impact - P4 low frequency, low impact - - Examples of high impact - a problem affects users during an essential process (expenses and payments > onboarding and registration > contributing) with no workaround. - - High frequency - >10% of users affected (measured as a proportion of total potential users for this case). -
+ - [ ] Surfacing: if you feel this is a seed of an idea that needs to be researched. + - [ ] Understanding: if you've done some research and feel it is already well understood and ready for shaping. + - [ ] Shaping: if you feel a solution is clearly defined and can be made into a pitch ([read more about shaping](https://basecamp.com/shapeup/1.1-chapter-02)) + - [ ] Pitching: if you feel that it is ready to be presented for prioritisation ([read more about pitching](https://basecamp.com/shapeup/1.5-chapter-06))