Closed jilladams closed 2 months ago
@thejordanwood I just slapped the template contents in here. Customize at will.
Previous Vet Center Research
@thejordanwood For scope clarity, research discovery is focused on a broad Vet Center redesign, Epic - Vet Center design 2.0 #17661 and VBA Events #17665.
One hypothesis we should explore: Vet Centers have their own logo, likely this may need to stay present in some form on the redesign as Veterans have a sense of trust and safety in seeking mental health support.
@thejordanwood has capacity this sprint to look broader than just events, so this may cover https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17661 as well
@thejordanwood There is no right or wrong way to summarize secondary research findings but what might be helpful if this is handed off to another researcher is a one pager in a GitHub research folder which we could always link to a Mural. Let me know if you have questions along the way!
VBA Events - Honolulu use case example, scroll down to see the type of events they hold
Note from this morning's UX Scrum. Because #17713 was injected into this sprint and is time sensitive, @thejordanwood may not be able to complete this ticket in Sprint 1. Will have a better sense at mid-sprint next week, but communicating early and often for no surprises. cc @mmiddaugh @jilladams @aklausmeier
I've compiled this research discovery work into a Sharepoint doc while it's being reviewed.
This is now in a Github folder that everyone will have access to.
@thejordanwood thank you for diving headfirst into these topics!
For background on the Veteran journey and the services provided by Vet Centers, I highly recommend the following short videos:
Knowledge gaps from the secondary research synthesis on expanding satellite locations
Knowledge gaps from the secondary research synthesis on Vet Center & VBA RO events
@davidmpickett see Michelle's comment above regarding satellite locations and IA, this will likely be most of what you are looking for regarding #17696
An interesting event use case: Some of the Phoenix ones are VAMC events but VBA list them as events they will have presence at. One event but ability to populate across multiple facilities: VAMC and VBA RO.
@thejordanwood @aklausmeier @davidmpickett @jilladams At this time, this redesign should limit event scope to determining how Veterans will navigate from the main Vet Center page to Events (which is being handled by PW) - this part of the design can be implemented in the front end once we are able to open events to Vet Center editors
Thanks for the additional context @mmiddaugh! This is all very helpful.
@mmiddaugh @jilladams @aklausmeier @thejordanwood
In the interest of scoping this ticket to close in Sprint 1, I'm recommending we strike the following ACs
My rationale is that these two actions are more properly Product / UX Lead actions as a follow on from Jordan's initial Research Review documented here. Some of the clarifications on Scope and open questions should probably be migrated to Product Artifacts like the Initiative Brief and relevant epics before we get into drafting tickets.
I'm going to put this on the Agenda for UX Sync later this week.
@davidmpickett I am ok with that if Amanda is, with the understanding that you own next steps for UX Sync discussion. Holler if you need support on ticketing / initiative brief edits.
From discussion with Amanda / Dave: next steps:
Given staffing and competing priorities, I encourage us to design with best bets based on what is known when we return to this initiative. If there are critical gaps, we can leverage Vet Center office hours and limited interviews with identified stakeholders.
I discussed this with both @aklausmeier and @thejordanwood today and we are going to close this ticket to represent that Jordan's research synthesis was delivered. @thejordanwood are jointly working on defining follow-up steps and creating tickets for them.
We'll talk through this more in UX Sync tomorrow
Description
User story
AS A Researcher I WANT to review what we learned in past Vet Center, VBA, and VA research SO THAT we can identify knowledge gaps
Discovery is a time to establish the fundamental approach for a research initiative. Potential tasks may include the following:
What do we want to know?
Has anyone else researched this before?
How might we learn more?
Note: This discovery work covered a wide range of potential updates to Vet Centers/VBA regional offices. Knowledge gaps have been identified. Further consideration for methodologies, participants, and timelines can be explored at a later date when this work is prioritized.
Acceptance Criteria
High-level scope of research is drafted and agreed uponSubsequent tickets are created