Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design Spike: Content Build and Next Build Dashboard #19639

Open
1 task
Tracked by #20102 ...
gracekretschmer-metrostar opened this issue Oct 29, 2024 · 3 comments
Open
1 task
Tracked by #20102 ...

Design Spike: Content Build and Next Build Dashboard #19639

gracekretschmer-metrostar opened this issue Oct 29, 2024 · 3 comments
Assignees
Labels
CMS Team CMS Product team that manages both editor exp and devops UX

Comments

@gracekretschmer-metrostar
Copy link

gracekretschmer-metrostar commented Oct 29, 2024

User Story or Problem Statement

As a UX designer, I need to understand the content build dashboard problem space, so that I can come up with a research plan to inform next steps in the work.

Description or Additional Context

Trying to understand the audience for the content build dashboard and understanding what information is most needed for the audience.

Per Erika:

The origin of this request is that we need a sign source of truth so that we can understand the health of the system, so that we can better communicate with our stakeholders. Right now, I go to the monthly report dashboard within Data Dog, but I have a hard time knowing what dashboards to engage within data dog. I look at cms-notifications channel now, but it's hard to understand, so I'm starting to looking at it less. There's a lot of engineering language within the dashboard, which is difficult to understand.

Acceptance Criteria

  • A research plan (including a set of research questions) that defines how the UX research and it's outcomes will be implemented for the content build dashboard initiative.
@gracekretschmer-metrostar
Copy link
Author

Relevant slack threads:

Relevant dashboards:

The larger goal with improving dashboard over the next year is:

  1. Incorporate the 4 DORA metrics into reporting
  2. Demonstrate progress in the Next Build work (likely focusing on the time to deploy content reduction between Content Build and Next Build).

@gracekretschmer-metrostar
Copy link
Author

Tim's research on Content Build dashboard: #19469

@gracekretschmer-metrostar
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMS Team CMS Product team that manages both editor exp and devops UX
Projects
None yet
Development

No branches or pull requests

2 participants