PAW: Post-research tasks

[cindymerrill]

Description

User story

AS A researcher
I WANT to wrap up my research study
SO THAT I can share it with others and then move on

Tasks

• Share research report with Amanda for review prior to sharing with team
• Work with @jilladams and @FranECross to schedule readout
• Incorporate Amanda's feedback into report
• Share research report with team, stakeholders for feedback/prep for readout
• Present readout to team
• Revise report per read out
  • Incorporate any additional async revisions from Danielle
  • Incorporate any additional suggestions from @aklausmeier (including comment about "R1 results")
  • Talk with @aklausmeier re how to share specific recommendations that will be removed from the report
• When done making changes, tell Danielle so she can share report w/526-EZ team
• Message Naomi Marcussen to schedule presentation for VA weekly design sync meeting
• Make longer readout presentation for VA weekly design sync meeting
• Remove PII from notes and post on Github, along with any other synthesis documents
• Get readout presentation reviewed by Amanda, and incorporate feedback
• Make short readout presentation for Sprint Demo
• Copy findings into card in research repo and move to Completed column
• Delete recordings -- WAIT until after recommendations discussions w/teams
• Close out ticket once once completed

Acceptance criteria

• All above tasks completed

[cindymerrill]

Shared draft research report with @aklausmeier for review: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/pact-act-wizard/research/research-findings.md

[cindymerrill]

Updated tasks in ticket FYI @jilladams @FranECross

[cindymerrill]

After I hear back from @aklausmeier re her timing for giving me feedback, I'll work with @jilladams and @FranECross to schedule the readout.

[aklausmeier]

@cindymerrill In general, the insights are written well and like seeing participant quotes.

A few areas that need revisions:

1. The recommendations are long and detailed and get too far into solutions. I know this is a fine line and can be difficult. Should be vague and open ended for the writer or designer (possibly in collab with SME) to make a decision on how to solve for the confusion/problem area.

• Example: "Consider adding more information to provide clarity around... confusion area description here." (might be helpful to think of this as 1-2 sentences)

2. Key Findings - we should not include any that only impacted 1-2 people

• Better suited for the "Additional Findings" section and opportunity to share quotes

3. These research reports can be referenced years down the road by researchers and SMEs in other departments so we need to be careful about the level of detail in recommendations. It can give the impression that they were already collaborated on by SMEs or UX areas of expertise when they may not have.

Note: These revisions should not hold up a readout with our internal team if scheduling doesn't give enough time for edits, they can be done after if necessary.

[jilladams]

@aklausmeier - @FranECross and I have connected with Cindy about feedback / timing. Fran has gone ahead to schedule readout, Cindy will work on revisions. If we need to further iterate, let's discuss with you, me, Fran, Cindy and @DanielleThierryUSDSVA (and Dave?) after or at the end of readout to figure out how to get aligned on expectations. That'll help for this project, and Sitewide research projects in general.

[cindymerrill]

Thank you for your feedback, @aklausmeier !

Re your comment on the recommendations, I will work on rewriting them to be less solution-oriented.

Re your comment about findings that impacted only 1-2 people, I normally do avoid including the feedback of small numbers of people in key findings when I'm doing a regular usability test focused on user interaction, but I've found that usability testing content results in less consensus in the feedback from research participants. I'm reporting all the results because they seem valid and relevant to the research goals, and I want to document as much user feedback as possible on the content. Many of the findings and beliefs were from small numbers of participants, and if I were to move them all to the "Additional Insights" section, there wouldn't be many key findings and "Additional Insights" would be super long.

More importantly, in the case of the questions that were confusing to some participants, some were seen only by small numbers of participants, and so the 1 or 2 people might be a sizable percentage of the few who saw a specific question. In the table below, you can see in yellow highlighting how the only participant who saw question S2.1.1 was confused, and 2 of 5 participants who saw question S2.2.2 were confused. I'll add into my report the total number of participants who saw each question that was confusing to some people because it wasn't everyone.

FYI @jilladams @FranECross

[aklausmeier]

@cindymerrill Seeing that chart above and understanding how many folks saw each question is insightful and a good reminder that there were several paths through content. Would be helpful to have that chart in the research folder if it's not already.

[cindymerrill]

@aklausmeier I just created that chart in my notes/analysis spreadsheet yesterday, and I was already planning to upload the new version to github.

[cindymerrill]

@aklausmeier I just finished revising the recommendations per your feedback, and now I'm going to share the report with everyone in preparation for Monday's readout.
FYI @jilladams @FranECross

[aklausmeier]

@cindymerrill on adding screenshots inline... not sure this is the solution. I was pointing out that additional clarity might be helpful in providing context for what "R1 results pages" are. Other teams will be reading this report who may not understand how results screen differed. You can decide on best solution but additional clarity in first mention and for each listed in bulleted list in Methodology section would be beneficial for those outside our team who need the additional context.

[cindymerrill]

@aklausmeier I will clarify my use of "R1 results pages" or might go back to using "You may be eligible" results page instead. I revised the task above.

[cindymerrill]

I revised report per feedback received during the readout and from Amanda afterwards. Only revisions left are if Danielle requests any more, as she said she might.

Now I'll start making slides to present at the VA UX Design Sync meeting...

[cindymerrill]

Revised report again with additional feedback from Amanda, which takes the place of Danielle's feedback. Shared out to both Amanda and Danielle.

[cindymerrill]

Finished drafting readout presentation for Monday's VA UX Design meeting and shared it with @aklausmeier and an Ad Hoc researcher for feedback. Will practice it tomorrow to see if it's an appropriate length.

[aklausmeier]

reviewed readout presentation and provided minor revisions to @cindymerrill

[cindymerrill]

Incorporated feedback from @aklausmeier and also from an Ad Hoc researcher.

[cindymerrill]

Made short readout presentation for Sprint Demo, copied findings into card in research repo and move to Completed column, and deleted recordings. I just need to run through my presentation slides for Demo tomorrow after I find out how much time I can have to present.

[cindymerrill]

FYI @jilladams @FranECross Finished in this sprint!