Draft lo-fi design of proposed changes

[shiragoodman]

User Story

As an OCTO lead on Platform, I want to be able to quickly and easily reference metrics on the Collab Cycle Staging Review process so that I can share trends and concerns with my own leadership.

Assignee: Peer Reviewer:

Description

Before we can begin making changes to the SR Dashboard, we must first create some mockups or low fidelity designs of the changes we're proposing. This is so OCTO-DE lead and Governance PO @humancompanion-usds can review and provide feedback before we commit to the changes in Domo.

On June 13, Matt shared his preferences on which Descriptive tags we prioritize in the dashboard. His top 5 priorities are:

• Accessibility defect severity
  • possibly track time to close based on severity
• Design System team review*
  • possibly track count or percentage of tickets per quarter that require DST review
• Modality
  • possibly track distribution of modalities across all issues
  • modality-screen-reader has been flagged significantly more than the other issues. Focus only on this?
• Context*
  • possibly track distribution of context across all issues
• Imposter component (yes/no)
  • possibly track count or percentage of tickets per quarter that are imposter
  • also include which components get flagged most often

*Do we have enough data at this time where the metrics would return anything of value?

Impacted Artifacts

Tasks

• [ ] Placeholder task

Peer Review

To be completed by peer reviewer

• [ ] User story and acceptance criteria are met

Acceptance Criteria

• [ ] We have drafted lofi designs of proposed cards for the SR Dashboard in Domo that feature descriptive tag data
• [ ] We have shared our proposed designs with Matt for his review/feedback

Team Notification

• [ ] Slack post on #platform-governance-team
• [ ] Presentation at Weekly Initiative Meeting
• [x] No notification needed

How to prepare this issue

Refinement

• [x] Ticket has user story, description, tasks, and acceptance criteria
• [x] Ticket has been sized
• [x] Once all above items are checked, add the 'Ready' label.

  Planning

  If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly

• [x] Ticket has been discussed as a team at Planning
• [x] Ticket has been assigned to appropriate initiative or quarterly epic
• [x] Ticket has been assigned to a Sprint
• [x] Ticket has been moved to the Planned pipeline in the Governance team board
• [x] Ticket as an assignee and peer reviewer

[shiragoodman]

@humancompanion-usds I ran some queries in github to get a better understanding of 2 of the descriptive tags that you prioritized - Design System Review and Context. At this time, there are only 5 Staging Review issues that we've flagged for DST review. Similarly, there are only 23 Staging Review issues that we've flagged with a context issue. .

I think we really need to have a better understanding of how the OCTO Practice area leads would use the context data before we prioritize building a card in our dashboard showcasing this data. With that said, I am asking the team to prioritize the accessibility defect severity, modality (possibly with a focus on screen readers) and imposter components.

Please let me know if you agree or if you'd like to discuss this further. Thanks!

[allison0034]

Created mural