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

Roll out Plan for Editor Survey #18443

Closed
3 tasks done
Tracked by #13312 ...
gracekretschmer-metrostar opened this issue Jul 2, 2024 · 3 comments
Closed
3 tasks done
Tracked by #13312 ...

Roll out Plan for Editor Survey #18443

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

Comments

@gracekretschmer-metrostar
Copy link

gracekretschmer-metrostar commented Jul 2, 2024

User Story or Problem Statement

The CMS team needs to create a plan to implement a quarterly survey to editors.

Description or Additional Context

A quarterly survey to editors has gotten approval from stakeholders and is ready to be sent out. The CMS team needs to work with OCTO stakeholders to come up with a plan of action on how to send the survey to editors and synthesize the results.

Reference Links

PO Requirements

  • This survey should likely be created in optimal workshop. The platform has licenses for our use.
  • We will need to create a rollout plan that includes distribution to all of the editor groups
  • POs will communicate the plan to our stakeholders to ensure it is being sent at an appropriate time and that they are aware of all the moving pieces
  • The survey should be sent from an official VA email and should ask for feedback within a timeframe we can indicate.
  • Once that time period closes we will need to synthesize the data and create a report/read out to be sent to our stakeholders and the union rep.
  • Responses will need to be stored in a secure location that Amanda has created as a repository.
  • As mentioned before, we will need to be mindful of sending it out quarterly and roadmapping time for ourselves to curate the feedback each quarter.

Steps of Implementation

  • Acquire a license to optimal workshop and begin learning how it works
  • Create a plan to send survey to editors
  • Meet with Erika and Amanda to get feedback on plan and finalize next steps

Acceptance Criteria

  • A plan of action to implement a quarterly survey to editors is created and gotten sign off from key stakeholders
  • The plan of action is represented in Github
  • Draft runbook is created in Confluence
@gracekretschmer-metrostar gracekretschmer-metrostar added Needs refining Issue status CMS Team CMS Product team that manages both editor exp and devops labels Jul 2, 2024
@gracekretschmer-metrostar gracekretschmer-metrostar changed the title Plan of Action for Editor Survey Roll out Plan for Editor Survey Jul 3, 2024
@gracekretschmer-metrostar
Copy link
Author

Implementing roll out plan via tasks within the Editor Survey Epic: #13312

@gracekretschmer-metrostar
Copy link
Author

Pilot survey: https://ows.io/qs/086ixfga

@gracekretschmer-metrostar
Copy link
Author

Met with Erika and Amanda to determine path forward. Will begin tasks on Sprint 15.

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

2 participants