Discovery for VBA RO editor facing research

[ALogsdon3]

Description

Research Discovery is a time to establish the fundamental approach for a research initiative.

Considerations

• Methodologies - what is the most appropriate and feasible approach to meet the research goal?
• Participants - do we have access to the right users?
• Timeline - how long will this take? how much time do we have?
• Recruitment strategy - what connection points with Editors can we leverage to encourage participation in research sessions?

Potential tasks

• Align with UX Lead & Product Owner on the high-level purpose and scope of the research
• Review Product outline to understand background context
• Review previous discovery work from October 2023
• Meet with CMS team researcher for background and info about editor-facing research considerations
• Draft big picture research questions

Acceptance Criteria

• High-level scope of research is drafted
• UX lead review has been requested (usually 48 hrs turnaround)
• Subsequent tickets are created

[ALogsdon3]

Adding this note to remind myself that Dave P started a ticket w/ specific questions for editor facing research.
#15484

[mmiddaugh]

@ALogsdon3 Additional questions to consider

How easy is it to get to the content they need to edit?

Related: Would these editors benefit from a Dashboard? If so, what need might it meet?

• How might we change the training (or the documentation) to better support new VBA editors?
• Do they have a sense for how often they'll need to return to Drupal to edit? (and if so, for which parts?)
• Any thoughts on the navigation between the editorial interface and the Knowledge Base?

[davidmpickett]

Here's another thing that we might want want to watch for / learn about during the Pilot phase:

• Are any problems created by granting editors permissions to VBA Facilities we are not asking them to update?

#15381 (comment)

[aklausmeier]

updated to include error messaging

[ALogsdon3]

I'm moving these sections to a comment for better tracking on my part. I need more clarity on the specific questions section.

General questions

• Do users understand the interface?
• Are labels, help text, error messaging, and other text in interface clear?
• Are widget interactions intuitive (buttons, checkboxes, etc)?
• Are the fields and content types configured correctly to meet their needs?
• How easy is it to get to the content they need to edit?

Specific questions

• What should the cardinality of the Service Locations on VBA Facility Service be?
• Does Anchorage use multiple?
• Is there a cap to impose?

[ALogsdon3]

Link to VBA RO editor research Mural

[ALogsdon3]

Scope of research:
This study will help us understand how the current design of the VBA RO CMS interface works for new editors, whether the training we're providing is effective, and how editors feel about the support documents available to them.

Since we have a limited number of participants available to us, we may meet with editors at different points in their editorial process. For instance, we might conduct some sessions after the February 20th training, and others after the March 19 training. 

[ALogsdon3]

All ACs complete, closing this ticket