User story & summary:
As the Growth team, I want to know why an image isn't a good fit, because then we can consider further task improvements.
Background & research:
Structured tasks break down editing workflows into a series of steps that newcomers can accomplish easily. Newcomer tasks increase newcomer activation (+11.6%), which flows on through to increased retention (1). Initial data shows that structured tasks help improve activation and retention even further (2).
Design:
New rejection reason: Section should not have an image
Desktop:
- A difference from the rejection dialog in Add an image structured task, is that we are adding a new reason specific to this task which is “Section should not have an image”.
- Users can select multiple rejection reasons
- Re-uses desktop dialog.
Mobile:
Mobile Figma designs
- A difference from the rejection dialog in Add an image structured task, is that we are adding a new reason specific to this task which is “Section should not have an image”.
- Users can select multiple rejection reasons
Acceptance Criteria:
Given I'm completing a section-level "add an image" task,
When I decide that "No" the image is not a good fit,
Then I receive rejection reasons that are identical to the article-level image rejection reasons, but include a "Section should not have an image" reason.
