Get through Collaboration Cycle before R&S user research starts

[davidmpickett]

Dependencies

This ticket is blocked by:

• Draft Resources & Support Redesign research plan #19491
• Draft R&S search filters conversation guide #19705

This ticket blocks

• Prep for R&S search filters research #19703

Description

User story

AS A Researcher
I WANT to go through the relevant Collaboration Cycle touchpoints before conducting user research
SO THAT any design prototypes will be reviewed

• Veteran-facing research must go through Platform's Collaboration Cycle
• Editor-facing research must go through the CMS Collaboration Cycle

The PM is responsible for creating the initial Collaboration Cycle ticket(s), but the Research Lead should initiate the Research touchpoint request.

Note: This step is a hard blocker for Veteran-facing research, but may be less so for Editor-facing research.

Acceptance Criteria

• Requested feedback from the team plus Amanda and Mikki
• Incorporated any feedback from the team, Amanda, and Mikki
• Initiated the Research touchpoint request
• Incorporated any feedback from Shane
• Discussed any significant changes with your Product Manager and Product Owner to keep them in the loop.

[FranECross]

@davidmpickett I added a link in the ticket body to the R&S Collaboration Ticket.

[cindymerrill]

Shared the research plan and conversation guide with the team + Amanda and Mikki for feedback by end-of-day Tuesday Feb 4. Feedback can go into the comments here.

[cindymerrill]

Feedback received from Amanda Klausmeier (copied from slack)...

Amazing work Cindy! Thank you for jumping in and knocking this out so quickly!
Research Plan:

• overall, replace, filter drawer to filter overlay modal, calling out the difference in behavior for mobile vs. drawer on desktop
• are dates in plan flexible if recruiting goes faster than expected?
  • maybe confirm during Perigean kickoff call if open to moving up dates

Conversation Guide:

• In research plan, goal 1, states the following but I am not seeing how this is tested in the conversation guide as it stops them once they get to target article page. I am curious to see how users interact with filter tags on detail pages or maybe I missing it.
  • "Do users understand how the filter chips on results/detail pages (w/X) work vs. on the landing page (w/o X)?"

Prototype:

• curious why drop down has a list of "Search term X" but when clicked upon fills search input with a specific term... why not have these match?

[cindymerrill]

My responses to @aklausmeier's feedback on the R&S research plan and conversation guide are below...

Research Plan:

• overall, replace, filter drawer to filter overlay modal, calling out the difference in behavior for mobile vs. drawer on desktop

I can make that change.

• are dates in plan flexible if recruiting goes faster than expected?
  • maybe confirm during Perigean kickoff call if open to moving up dates

If we get approval from Shane earlier than expected next week, then I'm open to moving up the dates. I believe that Perigean requires 5 working days to recruit, and if they're able to recruit faster than that (as they often do), at that point it's too late to start the research earlier because the sessions are already scheduled.

Conversation Guide:

• In research plan, goal 1, states the following but I am not seeing how this is tested in the conversation guide as it stops them once they get to target article page. I am curious to see how users interact with filter tags on detail pages or maybe I missing it.
  • "Do users understand how the filter chips on results/detail pages (w/X) work vs. on the landing page (w/o X)?"

I currently ask "What if this this page doesn't answer your question? What would you do next?" in two of the tasks, once the participant gets to a detail page. Then I observe what they do next--click on a filter/tag or go back to the landing page. I could add that question to a few more tasks, too. So we'll observe whether participants use the filter chips, and if so, whether they understand what's happening.

Prototype:

• curious why drop down has a list of "Search term X" but when clicked upon fills search input with a specific term... why not have these match?

We want to find out what participants would type as a search term if they use search, so we purposely don't have any visible options to choose from. After we ask them what they'd type, we'll ask them to select the one lettered option that corresponds to a specific search string that we provide for that task (which I could add to the convo guide).

Please let me know if you want any more details or have additional feedback, @aklausmeier

[cindymerrill]

Revisions have been made per Amanda's feedback.

I'm awaiting more potential feedback from Mikki, Fran, and Michelle.

[mmiddaugh]

Thank you for addressing previous feedback! I have only one other piece

From research plan:

Goal 1. Get user feedback on the new filter design and functionality to find information,
Do users understand the and/or logic between filters across/within filter groups?

Similar to Amanda's feedback, I'm wondering how we might get feedback from participants about whether or not the filters changed the result list as expected. (Perhaps a post-task follow-up question?)

Otherwise, I approve this research plan and conversation guide.

[cindymerrill]

Thank you for your feedback and approval, @mmiddaugh !

I can add a post-task question about that, and we may also hear feedback during the tasks from what participants say about whether the filters they tried helped or didn't with doing the task.