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

Create recurrent editorial survey for measuring trust with the CMS #12410

Closed
2 tasks
EWashb opened this issue Feb 1, 2023 · 2 comments
Closed
2 tasks

Create recurrent editorial survey for measuring trust with the CMS #12410

EWashb opened this issue Feb 1, 2023 · 2 comments
Assignees
Labels
CMS Team CMS Product team that manages both editor exp and devops

Comments

@EWashb
Copy link
Contributor

EWashb commented Feb 1, 2023

Background

As we explore feedback loops and baseline health metrics for the CMS, we must define and evaluate what trust looks like for editors. Trust as a metric is crucial to understanding the overall health of the CMS. We want to understand the editor's trust level so we might understand tasks/experiences they are having problems with and determine ways the CMS Team can help them through various improvements within product initiatives.

This survey should go out at least once per quarter but more often if deemed necessary. It should also go out to all editors of the CMS. We will want to create a frequency with similar questions. The midpoint of the quarter might be next, possibly every 5th sprint.

How can we measure editor understanding of the separation of content from display?

Questions we might want to ask and explore include:

  • How confident are you creating content (plain language/ for va.gov?
  • How confident are you when you reach out to the help desk, that I'll get help promptly?
  • What problems are editors trying to solve, and what is the confidence level in those actions?
  • Are you confident creating alt text for images?

This is not an exhaustive list of questions; it is a jumping-off point and example of the types of things we would like to learn about as a CMS Team. However, the questions may change each time depending on specific topics we would like to aggregate data on.

Hypothesis

  • Baseline trust metrics for the CMS will allow product teams to build solutions that advance the mission of providing quality content to Veterans.
  • Editors' trust levels vary by product.
  • Editors are accustomed to surveys and will participate in a quarterly survey via email.

Acceptance Criteria

  • A draft survey is created in Survey Monkey that measures trust in the CMS
  • Survey is shared with PM
@EWashb EWashb added CMS Team CMS Product team that manages both editor exp and devops Needs refining Issue status labels Feb 1, 2023
@EWashb EWashb removed the Needs refining Issue status label Feb 14, 2023
@joagnitti
Copy link

Doing some discovery work now!

@joagnitti joagnitti self-assigned this Feb 14, 2023
@EWashb EWashb mentioned this issue Feb 14, 2023
48 tasks
@EWashb
Copy link
Contributor Author

EWashb commented Feb 28, 2023

EditorTrustSurvey_1.docx

The survey will be emailed to Dave C for feedback and then distributed to editors.

@EWashb EWashb closed this as completed Feb 28, 2023
@productmike productmike added Epic Issue type and removed Epic Issue type labels Apr 14, 2023
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
Projects
None yet
Development

No branches or pull requests

3 participants