Skip to main content

Issue templates lean feature proposal

Problem Statement​

Problem to solve​

What is the user problem you are trying to solve with this issue?

Proposal​

Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the What does success look like, and how can we measure that? section.

Other sections to consider adding:

Intended users​

Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.

User experience goal​

What is the single user experience workflow this problem addresses?

Further details​

Include use cases, benefits, goals, or any other details that will help us understand the problem better.

Availability & Testing​

This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.

What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?

Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.

  • Unit test changes
  • Integration test changes
  • End-to-end test change

What does success look like, and how can we measure that?​

Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this.

Is this a cross-stage feature?​

Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt.