Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Define the expected improvement (ie funnel conversion, frequency, app stability, UI/UX, user satisfaction) and the evaluation metric for the feature ( ie dollar sales, number of purchases, number of new users, app ratings). If the expected improvement is quantifiable, please list all base value assumptions. If the feature is expected to improve an existing funnel, please provide a link to that funnel.

Priority

Assign based on priority to the brand. Note this may change after the feature is evaluated by the team.

  • Highest: Required within the next quarter

  • High: Required within the next year/strong preference within the next quarter/significant expected benefits

  • Medium: Strong preference within the next year/moderate expected benefits

  • Low: Some expected benefits with no pressing need

  • Lowest: Should remain in discussion, but not a priority

Feature DescriptionFeature Description

Describe the issue that you’re trying to solve with as much detail as possible. Focus on the problem, not the solution.

Our product and engineering teams are better suited to provide specific solutions give they have wider knowledge of our platform.

...