EXPLORE UX experience for prioritizing templates

[yaelberger-commits]

Give your user story a simple, clear title

Description

As a (user), I need to be able to do (X) so that I can achieve (Y) outcome.

WHY are we building? WHAT are we building? VALUE created by our solution

Acceptance Criteria** (Definition of done)

To be refined through discussion with the team

Given some context, when (X) action occurs, then (Y) outcome is achieved

If this user story emerged from User Research insights:

• [ ] Link research insight back to hypothesis from Epic or Objective in Airtable

• [ ] Once change/fix/feature is implemented, mark insight as "resolved" in Airtable

• [ ] Once change/fix/feature is implements, link insight to design artifacts (Figma) in Airtable

• A11y

• Bilingualism

• Privacy considerations

• Security controls in place

• Measuring success and metrics

[yaelberger-commits]

Could surface first, but not yet allow users to request a change

[yaelberger-commits]

Acceptance Criteria for what templates would qualify for a priority change

[yaelberger-commits]

A user could edit a template after it's given higher priority so we might need to look at how to prevent that

[yaelberger-commits]

Maybe we don't surface priority lanes to them at all, but we ask more direct questions about their templates and then we match that to our own criteria