PCI summary findings/Iteration pitch deck [10/5/2022]

[Cmjones233]

• [x] Create draft summarizing PCI user research findings and prosing phase 1 and 2 of iterations

• [x] Have Allison or Chris review

• [x] Revise

• [ ] Final review

• [ ] Present

• [ ] Implement Iterations

[Cmjones233]

went through references and currently working on draft

[Cmjones233]

Posted deck to slack for review from Chris, Allison, Lindsay

[Cmjones233]

Notes for Revisions:

A few notes... 1) Semantics to modify: We technically did not conduct dedicated user interview zoom calls with Patrick and Robert Tow.

• Patrick’s desired KPI’s were shared with leadership at a team presentation, which we adapted from his PDF.
• I was previously on a few calls/chats with Robert Tow and documented findings of what he was tracking on his daily PCI reports. Maybe we just modify the ‘Our research methodology’ to clarify we also gathered user feedback from open channels like email, chat and leadership presentations. 2) Minor typo: “There will need to two phases of iterations for updates to the dashboard:” 3) For phase 2 or 3 additions, the following would be good to also include:
• Reasons for not completing a pre check-in or eCheck-in (EX: too early, too late, insurance review needed, etc). Nicole Kleist mentioned this and then we shared how we originally included these stats but were asked to remove for MVP.

• Adoption/Utilization tracking for PCI and VSECS usage. Patrick March mentioned and Shawn Adams also shared the VETLink methods of tracking it. We can reference the Git doc under staff interviews for these details: https://github.com/department-of-veterans-affairs/chip/blob/master/docs/reporting-dashboards-research.md 4) With UX research I always like to share quotes or interesting findings directly from the people we spoke with. We can sprinkle in a few highlights from your notes or the above Git doc to add the human element to our human centered design approach. Tanita had some excellent points about segmenting our data/filters. I also love Danny Smith’s “Change the game with memos” quote... Not specifically related to reports but a good call out to share how our interviews also gathered ideas for improving the product itself. 5) We’ll want to add the Git doc link to the deck for easy reference of the research details for those who want to dig deeper… maybe at the end of deck or wherever we think it makes the most sense.

  We have not been deep in the phase 2 ticket documentation. Will work on these once we’re past the current prod challenges and reporting updates are prioritized.

[Cmjones233]

currently revising

[Cmjones233]

Revisions applied and posted for review

[Cmjones233]

this is no longer necessary