UX Audit of Deletion Feature

[gracekretschmer-metrostar]

User Story or Problem Statement

To better understand the scope of impact of adding the deletion feature to Drupal CMS, the CMS team needs a UX audit around the editor workflow. We need to understand the complete impact of a delete feature at both a detailed and high-level perspective.

Why are we doing this?

• To better understand and prevent unintended misuse by VA editors, we need to mitigate the risk.
• To continue iterating around the editor's workflow, and consistently improving the process.

Description or Additional Context

• Currently, VA editors do not have a way to delete PDFs.
• OCTO requires the CMS team to retain a record of uploaded PDFs for a specified duration.
• The CMS team has improved the PDF audit experience and is developing a process to store deleted PDFs in a separate repository.

Steps to Implementation

UX to audit the current editor experience by performing discovery around:

• PDF Management with the output artifact = Editor mapping (Understanding the relationships between editors and their workflows)
• PDF Deletion with the output artifact = Six thinking hats (Understanding the delete feature from different perspectives or personas)

Acceptance Criteria

• [ ] A list of areas within the CMS that will be impacted by adding the deletion feature to the CMS
• [ ] Reporting around the feature's impact on Editor Personas

  
  ### Tasks

• [ ] Discovery: User Journey Flow > Editor PDF Usage [Research]
• [ ] https://github.com/department-of-veterans-affairs/va.gov-cms/issues/18124
• [ ] PDF Delete: Editor Process Map [UX Artifact]

[gracekretschmer-metrostar]

Erika's feedback: define the artifact as the outcome. Maybe a service blueprint?