[CST] [Design] Post-Study Iterations for Development Letters

[skylerschain]

Background Context

Now that we have finished the research synthesis for the Development Letters study, we need to decide what (if any) design iterations we want to pursure.

New Feature

• Why are we doing this work?
• Epic Link

Outcome, Success Measure, KPI(S), and Tracking Link

• Add here

Design

• Add here

Enablement team (if needed)

@jstrothman

Engineering

• Add here

Out of scope

• Add here

Open questions

• Add here

Tasks

• [ ] Articulate design iterations based on research findings
• [ ] Share design iteration ideas with broader team for feedback
• [ ] Document feedback and create final spec for any iterations we want to implement

Definition of Done

• [ ] Meets acceptance criteria
• [ ] Passed E2E testing (90% coverage)
• [ ] Passed unit testing (90% coverage)
• [ ] Passed integration testing (if applicable)
• [ ] Code reviewed (internal)
• [ ] Submitted to staging
• [ ] Team approved production verification process
• [ ] Design performs design QA and verifies the implementation matches the design spec
• [ ] Accessibility specialist performs accessibility review (in code or design)
• [ ] Engineering identifies staging users required to test and shares account and credentials with design and product
• [ ] Product performs functional QA and verifies acceptance criteria was met

Acceptance Criteria

• [ ] We have documented design iterations based on research study findings and team input
• [ ] AC
• [ ] AC

[uxgary]

Closing this to create in epic in its place since the research shareout recommendations will result in multiple tickets.

[skylerschain]

@uxgary You can also just convert this to an Epic (if you didn't already create a new one). See screenshot.