Facilities UX Sync Agenda & Notes (2024 - contract end)

[davidmpickett]

Jump link to latest agenda

https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16586#issuecomment-2023110872

Meeting Purpose and Structure

This is a weekly meeting where we focus on the following actions:

• Presenting UX work for feedback / signoff
• Roadmapping UX work for prioritized initiatives
• Refining cards for upcoming UX work

Meeting logistics

• Thursdays at 3:05 - 4:00 pm ET
• Zoom link: https://civicactions.zoom.us/j/92401043958?pwd=bUw1VDFDQ3poM0dZclBqblN1ZWNMQT09
• Scheduled via Drupal CMS Outlook Calendar
• The second Thursday of every month, @mmiddaugh and @aklausmeier have a conflict for the second half hour of the meeting so we need to be sure to prioritize those agendas accordingly

Agenda

• The agenda is updated on a weekly basis by @davidmpickett
• Draft agenda will be sent out ~24 hours in advance via Slack
• If you have an item you would like to add, you can always add a comment to the ticket async
• Agenda items should have clear action-oriented language. Why are we looking at this item? What is the desired feedback or next step?
• Agenda items should ordered from highest priority to lowest priority
• Agenda items should have a rough time box

Attendees

• Core attendees
  • Facilities UX team members (@davidmpickett, @thejordanwood, @ALogsdon3, @laflannery)
  • Facilities PM / DM / PO (@xiongjaneg, @jilladams, @mmiddaugh)
  • Sitewide UX Lead (@aklausmeier)
• All other attendees are optional and may choose to join or skip based on agenda
  • Facilities Devs (@swirtSJW, @omahane, @eselkin, @maxx1128)

[davidmpickett]

Notes for 1/4/2024

• [x] 5 min - Housekeeping notes on meeting structure
  • Goal: Identify notetaker and timekeeper volunteers

content model options for VA Police phone numbers

• Goal: Create shared understanding of artifact and discuss any high-level questions

Goal for MVP is to be able to handle multiple paradigms for system phone numbers (one, many). Reviewed mural.

• Decided: Needs to be at the facility level, we already anticipated editor involvement, so this points to Option 2, using the VAMC Facility Non-Clinical Service.
• Contact csv: we don't know if there are other consumers of that. Michelle to work on confirming.

Discussion around VBA names (#15752)

• Goal: Refine to reflect current state and identify specific blockers for:

  • 11628

  • 15155

We previously suggested shortname treatment in #15490 (vba_short_names.xlsx) Notes updated in #15752

• Complex names should not be in H1s, should not be in breadcrumbs
• Complex names, in this case, come from Sandy's DB. That pushes to VAST and comes back to Drupal to be processed. We may want to consider splitting the complex names upstream (as far upstream as possible).
  • We may consider a "display name"
  • We need a technical SPIKE for the technical options for how to manage the name splitting, in Sandy's DB vs. in CMS, and how we want to maintain the full official name / split it / manage it downstream (@davidmpickett to stub )

[davidmpickett]

1/11/2024 Notes

Character Counts

• Agreed that proposal on 16253 is good to move forward
  • Erika has signed off from CMS perspective
• Experimental design epic next steps are to review with Amanda after her PO, and to close out the tiny PR(s) for help text

Error messages

CMS Collab Cycle says we must show error messages. Jordan has proposed updates. Michelle / Erika haven't had time to discuss. Michelle to follow up & we can revisit next UX sync, when design ticket is in review state.

VBA RO editor research

Alexis / Jordan to follow up offline re: refining tickets / getting organized. Alexis to try and attend as many training sessions as possible. Alexis / Jane to sync on tickets.

Next projects for Jordan:

• Sketch > Figma migrations
• Public Websites doesn't have any large design projects scheduled Q1
• Jordan has capacity for Police follow up. Michelle to be thinking bigger picture re: potential next priorities.

VA Police midpoint

Police Midpoint feedback Captured in tickets.

[davidmpickett]

Agenda for 1/18/2024

• [ ] 15 minutes - VBA Error Messages - @thejordanwood
  • Goal: Create shared understanding of artifact and discuss any high-level questions
• [ ] 10 minutes - VBA terms to add to Service Taxonomy - @davidmpickett
  • Goal: Approve easy-peasy terms and establish next steps for thinky-slinky terms
• [ ] 10 minutes - FL mobile map research plan and conversation guide - @ALogsdon3
  • Goal: Review current state of artifacts and discuss next steps

If time allows

• [ ] 5 min update on VBA Regional Office IA implementation from @davidmpickett
• [ ] Cleaning up VBA sections in advance of editors getting in Drupal?

VBA Error Messages

• Related ticket: #16068
• Related artifact: VBA content specs in Figma

Notes:

• CMS feedback was to show error states
• Jordan using VA Design System recommendations, have a clear CTA
• Error messages and guidance when required are shown in the design on pages it applies to
• If needed on specific fields, design shows error message in the field
• Jordan is not ignoring Dave's recommendation, holding for additional feedback to implement
• From Dave: currently CMS Design System has nothing on error messages, Dave created ticket for specific guidance and requirements for CMS Design System on error messages
• From Michelle: Where's the best place to put feedback for implementation? Answer: @xiongjaneg will create an implementation ticket
• From Steve: On fields that are required, there's two levels of complexity:
  • default is handled by Drupal Core
  • on fields there's server side validation (e.g., submitting an empty field) in the browser itself, varies by browser, can't be overridden, consideration for future specs.
• From Michelle: It might be good feedback for CMS Team, letting them know when we're getting a default that we can't influence.

VBA terms to add to Service Taxonomy

• Related ticket: #16269
• Related artifact: Proposed term labels in Github comment

Notes:

• Second batch of adding terms that are net new for VBA
• Easy peasy terms, five of them, the label has gone through copyediting, vetted by CAIA, vetted by VBA stakeholders
• The label is straightforward, shown in Drupal, people will see
• The machine is in URL slugs, removed spaces and unnecessary words
• health service API ID uses a matching API ID, Dave recommended best match for existing IDs for going forward, may come from Sandy's database
• Question about health service API ID: is anyone using them?
• Two terms don't have an existing health service API ID
• Thinky slinky terms may be suggesting a new label, not yet vetted by CAIA
• We likely want to confirm these terms with CAIA before adding to Drupal

FL mobile map research plan and conversation guide

• Related ticket: #16293
• Related artifact: Facility locator mobile map research mural

Notes:

• Review Mural for template sections and design visuals
• This work will be parked for a bit as other priorities take precedence, so this is a draft that will be updated when picked up again
• Includes draft plan, task in the brainstorm section
• There are questions and sub-questions
• This will be ported into Github today. Feedback may be more helpful when this work is picked up later.
• Question from Michelle: Is there anything we can help with or you would do differently since this is the first solo effort? Answer: the biggest challenge is that it's not been sequential. It's had stops and starts. Context switching has made things less streamlined. It's more challenging to do a conversation guide when trying to create tasks for a prototype that doesn't exist yet. There's a lot of curvy moments happening here. Ask that folks take that into account with where things are. It takes more time.
• From Amanda: it's about getting everything over to Github and Amanda may add learnings directly to Github as Alexis moves to the next study.

VBA Regional Office IA implementation

Notes:

• From a previous UX sync, there weren't clear steps on recommendation. This is a spike to map out the technical implementation and make decisions about history, potential paths forward and problems with them, and documents and acceptance criteria.
• Jordan's designs show what we're doing with Vet Center names (Vet Center "located at..."), separating this part and removing from H1 and URL
• For VA regional satellite offices, this doesn't work because those don't have prefixes and wouldn't be helpful. For these, may need to add a region prefix (e.g., Albany VA Regional Satellite Office located at...). There's an existing list.
• Edge case: Maui, there are two Maui locations that, when shortened, would have the same name and not be unique. What do we do with these?
• Edge case: Fresno, Regional Satellite Office at Fresno, which doesn't follow general pattern.
• Edge case: city name may need a state/region to specify which city.
• Edge case: military bases
• Edge case: two instances of the same facility
• Attached to ticket a static version of the spreadsheet, source of truth on SharePoint, and a local copy, color coded for problematic issues
• Will discuss in next engineering refinement

[davidmpickett]

Agenda for 1/25/2024

• [x] 10 min - Police transparency design updates from @davidmpickett and @thejordanwood
  • https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16329
  • Goal - Review updates and note any remaining open questions
• [x] 10 min - VBA RO editor facing research update from @ALogsdon3
  • https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16295
  • Goal - Discuss current state and next steps
• [x] 10 min - VBA error states cart and horse
  • https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16906
  • Follow up conversation from Refinement about how we want to move forward
• [x] 10 min - Service Taxonomy process @davidmpickett
  • https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16269
  • Goal - Answer any lingering questions and decide on what to sent to CAIA & VBA

Police transparency design updates

• Ticket: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16329

Notes:

VBA RO editor facing research update

• https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16295

Notes:

VBA error states

• https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16906

Notes:

Service Taxonomy process

• https://github.com/department-of-veterans-affairs/va.gov-cms/issues/16269

Notes:

[davidmpickett]

Agenda for 2/1/2024

• [x] 5 - Review agenda and pick notetaker
• [x] 15 - Facility Locator mobile map design
• [x] 10 - VBA Facility content type
• [x] 10 - VAMC mental health phone numbers
• [x] 5 - CMS Content Style Guide
• [x] 10 - VBA & Vet Center events

Facility Locator mobile map design (15 min) - @thejordanwood

Goals

• [ ] Review changes to design for feedback and comment
• [ ] Refine error and empty states ticket

Links

• 16855

• 17074

• 15935

• Design in Figma

Notes Map design tickets

• No updates to actual design since last review in UX Sync.
• This needs a coded prototype, which has full functionality, in staging for usability testing.
• Problem: current mobile map isn't interactive. We want to change that.
• To help front end developers, Jordan added annotations to call out components used, when to use V3 component, comments about what should happen on an interaction.
• The phone number and aria-described-by components being noted is especially helpful.
• Michelle will add comments in design file or ticket.
• View list has V3 pagination, but the design doesn't show that on View map. The map only shows one result at a time based on the number that the user clicked.
• Amanda requested a mock up for the View list, which Jordan has ready.
• Laura will add a comment about focus.

Error states ticket

• Jordan started reviewing this ticket while getting designs ready for the prototype and will continue to add more edits and comments, particularly those that apply to mobile map.
• This could pertain to the overall Facility Locator error states, but the scope of this ticket may be confined to the mobile map. There may be larger issues that should be covered elsewhere.

VBA Facility content type (10 min)

Goals

• [ ] Opportunity for discussion / clarifying questions between engineering and design - @omahane

Links

• 16327

• Design in Figma

Notes

• This ticket contains all the review and updates over the last few months, current vs. how it should be (from research, style guide, collab cycle).
• Large amount of primarily site building in scope.
• In the Figma file, the best view is Current and New.
• Dave resolved any comment threads that no longer apply.
• Any comments requiring a link includes the link to insert.
• VBA editor training on Tuesday. Keep communication open for impact of the work on this ticket on training.
• There is a related ticket on operating status changing from dropdown menu to radio button.

VAMC mental health phone numbers (10 min) - @davidmpickett

Goals

• [ ] Review options and make decision on desired direction

Links

• 16655

• Mural

Notes

• Current state is there are a few places where editors can edit phone numbers related to mental health.
• New state is that there is one central place editors can edit phone numbers and can be more specific at the health facility level.
• Diagram shows future possibilities, having one mental health phone number for each VAMC system because currently not every facility has a specified phone number. A specified system phone number could be inserted as the default for facilities that don’t have one and for the mental health detail page.
• There is a related ticket to require mental health phone number on the mental health detail page
• Where to attach this system number
  • Option 1: VAMC system content type, one field, one phone number, small lift, solves only the specific problem in question
  • Option 2: VAMC system health service content type, each health service could have an associated phone number, advantage: this could be used for other services (possibly Police) if needed
  • Option 3: VAMC system mental health care page (would be new type)
  • Option 4: Service region, information related to a service and the places we want it to show up. Considered differences in hierarchy between VBAs and VAMCs. Allows flexibility for services between local and national level. Could be used for other types of contact information at varying hierarchy levels.
• Other use cases:
  • National hotline (e.g., suicide prevention, intimate partner violence) would not be benefited by option 2, might be more likely to be served by centralized content
• Editor experience: which option may be easiest for the editor?
  • Option 4: bad idea for editors, cognitively terrible
  • Option 3: similar to what they’re doing for top task pages like Billing and insurance
  • Option 2: would be new to VAMC system health service and would need some change management, as with all options
  • Option 1: unknown how much editors interact with VAMC system, doesn’t prevent switching to option 2 at a later point
• This is primarily for editors who don’t have a facility mental health phone number, so this is a backup option that may not apply to every facility, though it is a legislative requirement to have a mental health phone number per facility

CMS Content Style Guide (5 min)

Goals

• [ ] Overview of artifact & explanation of how it came to be and how to contribute going forward

Links

• GitHub link

Notes

• New CMS content style guide is here
• Compilation in Github so it’s all in one place and publicly accessible
• Current focus on help text
• Potential additions like KB articles
• Massively driven by Jordan (workshops supported by Alexis, much of the UX writing) - kudos to Jordan
• Amanda will reach out to Erika to schedule a meet and greet with our UX team members and the new CMS Team UX team member

VBA & Vet Center events (10 min)

Goals

• [ ] Refine 15349

Links

• 15349

Notes

• On the radar for the future, Jordan and Amanda will work on it together after facility locator work
• This should be an epic for the brain dump
• Dave will work with Jordan and Alex to stub tickets under this epic
• Important to VBA and Vet Center stakeholders
• Blocked by content build limitations
• Menu placement is a consideration

[davidmpickett]

Agenda for 2/8/2024

First 30 min before @aklausmeier and @mmiddaugh leave

• Review agenda and pick notetaker (2 min)
• VBA Editor research - @ALogsdon3 (15 min)
• VAMC Police transparency content model - @davidmpickett (10 min)
• Events (5 min)

Second half

• Refining 13804 - @laflannery
• Refining 15349 - @davidmpickett and @thejordanwood
• Refining 16012 - @ALogsdon3

Notes:

• 13804: Jordan will create design ticket to explore the spotlight pattern.
• 15349: Jordan and Dave will take a look at this before next refinement.
• 16012: Alexis is going to casually look at this ticket and casually pull it into future sprint, but will keep it casual. She will talk about this with Jane more.

VBA Editor research

• 17096

• Updates on editor research procedurals questions?
• Discussion on "Getting insights early and often as opposed to waiting till synthesis at the end"?
• Would a pilot run-through with one of us playing the role of the editor be helpful for Alexis?

Notes:

• Updates on editor research procedurals questions
  • Conversation guide is more or less done.
• Alexis has been attending training sessions and recruiting for research sessions.
  • One person has signed up.
  • Would like to get more people after the 2/20 training
  • Questions are designed to get insights along the way, even if training isn’t complete.
  • Alexis has a wide range of availability to hopefully encourage everyone from different time zones to attend.
  • She would like more time to pitch the research sessions if possible.
• Insights early and often
  • Working on determining a cadence to show highlights from sessions. Every 2 weeks?
  • Will work on topline throughout the process and include in final readout
• How to let team know about those sessions so they can sit in?
  • Alexis created a new ticket for this sprint that will address how to get notetakers and getting people to observe.
  • Would it the better to reach out to team as we go and invite them to observe sessions? We’re unsure how many sessions there will be.
  • Dave’s suggestion: Let Facilities team know in Slack and in the UX sync that there are sessions open.

VAMC Police transparency content model

• 16812

• Overview of functionality and identifying any open questions

Notes:

• Dave says this is straightforward and proceeds to show scary Mural board conspiracy chart.
• Overview of functionality:
  • We shipped with 1 number per system, but need to expand the model to allow for multiple contact numbers
  • VAMC facility non clinical service will house this information in Drupal
  • Migrated data from CSV to Drupal. Should the CSV be deprecated now?
  • What we have now: The data in Drupal is locked down. Editors can’t change the 1 number for the system.
  • What we want to move to: Local VAMC editors will be able to edit the 1 number and add more contact info via non clinical services.
  • Will contact info be filterable (under search) or static (above search) on the FE page?
  • How should we frame this to editors so they understand what we want to display on the FE?
  • Reviewed this in Drupal with Christian and Michael.
  • Drupal terms: Adding a location adds a non clinical service. (I don't understand this, but Christian and Dave seem to.)

Events

• Should @laflannery do the audit?

Notes:

• Will bring this up in Monday meeting to ask more questions and go from there.

[davidmpickett]

Agenda for 2/15/2024

• 16652 - @maxx1128 (10 min)

  • https://dsva.slack.com/archives/C0FQSS30V/p1707762373114469
• Design / engineering collaboration retro - @davidmpickett (10 min)
• VBA Editor Research updates - @ALogsdon3 (5 min)
• Health Chat context - @mmiddaugh (20 min)
• Multiple images (10 min)

[davidmpickett]

Agenda for 2/22/2024

1. Review agenda and assign notetaker - 2 min
2. VAMC Police expanded contact info design - @thejordanwood - 10 min
3. VAMC system mental health number design - @thejordanwood - 10 min
4. CMS Collab Cycle update - @aklausmeier - 3 min
5. Weekly update on VBA editor research - @ALogsdon3 - 10 min
6. Health Chat research update - @ALogsdon3 - 5 min
7. Add VA health connect and VA health chat to VAMC page - @mmiddaugh - 5 min
8. VBA Names - @davidmpickett - 10 min

2. VAMC Police expanded contact info design

• Ticket: #16810
• Design: https://www.figma.com/file/B5EbL9aismadYhQqJFnPaB/Police-Transparency?type=design&node-id=36%3A5851&mode=design&t=QAE99QJBQWxVV0tt-1
• Goals: Present design for discussion

  Notes:

  Proposing breaking up #s into 2 sections:

  1. Main contact numbers as card components, with a label.
     • Q. Will there be more data we need to handle? A. Michelle says: we're talking to VHA DM to figure that out. We don't know the answer yet.
     • If we do need hours / location, can keep in a card component. If not, could show the numbers without the card component.
  2. Other Services: Proposing a card component within an accordion, with additional numbers / location data / hours. Dave noted we may need to handle like we do on VAMC content model, so there aren't multiple facilities within an accordion.(Design has 1 facility per accordion.)

Billing & Insurance treatment: For Pay in Person section on Billing pages, e.g. https://www.va.gov/gulf-coast-health-care/billing-and-insurance/, want to break up the presentation when multiple locations have hours / contact info under Pay in Person. (e.g. main location + Cashier's cage.) Jordan's design proposes using card component again. Alt treatment proposes using an accordion per location.

Amanda to review. Concerned re: card treatments, and wants to make sure accordions are consistent with VBA.

3. VAMC system mental health number design

• Ticket: #17169
• Design: https://www.figma.com/file/bwnxdqh3b7W7Xp6KuQ4Sab/VAMC-facilities?type=design&node-id=6%3A2431&mode=design&t=PEGfJrwRabOSrvoA-1
• Goals: Present design for discussion

  Notes:

  Also proposing putting this into an accordion. States:

  1. System # exists / "Use system" checkbox displays, is checked = we display a locked field for displaying the system phone #.
  2. System # exists / "Use system" box is not checked = display editable input field, with help text that provides notes for phone number entry.
  3. No System # exists = proposing: hide the checkbox in this case. (Drupal says that's technically possible.) Input field would be editable to enter a number, with the helptext. TBD here, based on where the Editor conversations go.

Next step:

• Refine the Drupal ticket
• Close loop with Jordan to update the design with final answers.

4. CMS Collab Cycle update

Notes:

99% sure the CMS Collab Cycle will change again, now that they're on Platform. Check with Grace / Michelle before moving on any CMS Collab Cycle action steps.

5. VBA editor research

• Ticket: #17220
• Mural: https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1697569400651/92298ea4aa3b0e64d71b6305a7d95e56261f4cf1?wid=0-1708353312306
• Goals: Share learnings from first week

  Notes:

• Alexis has a Mural with weekly updates from research at https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1697569400651/92298ea4aa3b0e64d71b6305a7d95e56261f4cf1?sender=u3f35bedf61955cb051f44770
• So far 1 participant who has attended all training sessions so far.
• Participant uploaded a facility photo.
• Key findings from this session:
  • The Description field is higher up than the Alt text field, which is confusing since Description isn’t required but Alt text is.
  • Does photo help text need improvement?
  • Participant was unsure what button to use between Save and Select and Save and Insert.
  • Participant was unsure where to look for when the photo was saved.
  • Participant asked about the process for submitting content for review.
  • Short training videos might be nice (but creates tech debt for Facilities team).
  • Content is infrequently updated, so editors will be re-learning every time they need to go back in.

6. Health Chat research update

• Ticket: #17282
• Mural: https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1699650112593/672d59e5ac915c73c1dfd8d6326fcff277bc28db?sender=u9c899abc4fe36c9a698b1647
• Goals: Status update

  Notes:

• Alexis reviewing lots of documentation. More to come soon.

7. Add VA health connect and VA health chat to VAMC page

• Ticket: #17308

  Notes:

• How can Veterans find these services
• The campaign landing page will highlight these services
• Michelle found a few places where Facilities, not editors, could direct Veterans to these services
  • Manage your health online box (Health Connect already listed here, but this box is getting full)
  • Top task buttons (these are tools, not tasks, no not ideal)
  • Centralized content
  • If in the Spotlight, it is under editor control and would replace some other content editors might want.
  • If task-specific, could go on editor controlled pages:
    • Contact us page
    • Pharmacy page
    • Urgent care page
• Campaign landing page is being edited this week and may take some time to review, revise, and agree
• How does this fit with CAIA’s recommendation in the past about placement of Health Connect placement? That feedback was likely more about general information about these services rather than specific instructions to Veterans on how to communicate with their providers.
• What’s the order of operations or options and how will that affect research?
  • Tree test research is for menu navigation, so it might not be for a link.
  • The next step is take what we know and put the links where our best guesses are and then do usability testing (and skip the tree test).
  • Do both.
• If there’s already an idea of what the solution might be, research might not be ideal now, but rather data gathering or problem solving after we have some user interaction.
• Is accessibility testing going to be done?
• Codepen is also available if we want an option for testing.

8. VBA Names

• Ticket: #15752
• Mural: https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1707266192237/97f7666116d3fa72ccfe4b136a23a7f1e948432b?sender=u9c899abc4fe36c9a698b1647
• Goals: Talk through engineering details

  Notes:

  Dave to schedule meeting with engineers and product

[davidmpickett]

2/29/2024 notes

Facility Locator error states - @thejordanwood

Error states:

• Location sharing modal > new language proposed
  • Will need a CAIA ticket for review before launch
• No location is entered > remove "please", updated otherwise to match field label
• Invalid location > Proposing engineering change for an error to "Enter a valid location"
  • Needs Ruby / FE technical assessment for if we can do that at the field level vs. at results submission
• Choose facility type > remove "please"
  • Relocate facility type to be parallel to city/state picker, to alleviate blank space, and makes room for future fields
• No service type (when required / community care) > remove Please, rephrase to match field label.
  • "search" as the imperative next to the "Search" button may be confusing. Proposed in call: maybe Enter or Select
• Invalid service type > remove Please, swap the command verb from "search"
  • Need a way to solve for both an invalid service type and when no service is selected
  • Also updating the no results language
• No results found > Currently returns giant error message for all possible UI tweaks. proposing to shorten that
  • Error messages on list and map views for mobile need to vary. Needs FE vetting for feasibility
  • Laura noted: we don't use lists if they only have 1 bullet. If only one Suggestion, need to treat that differently.
• Map needs to zoom > propose keeping as is
  • Dave noted: these are non-functional/disabled buttons when you get to no results. Driven by our code, not mapbox.
• System error / no results > Currently presents an alert. Proposing using the content design system "we've run into a problem"
  • Should review use of "Please" and "sorry" in proposed update with CAIA.

VA Health Chat research - @ALogsdon3

Sitemap / tree based on Minneapolis has been developed in Google sheet. (Will move to SharePoint eventually.)

• Options for placing VA Health Chat are listed in bold.
• Need feedback on potential placements, within the structure.

@mmiddaugh to share analytics for entry point analytics to understand how people tend to arrive on VAMC sites (direct from google vs from Va.gov)

Q: Do more stable places make more sense than areas of the site that vary a lot? A: More stable areas might make most sense, to get a sense of valid results for testing

Q: Add to "Manage your health online" section? (System page) A: Seems like a viable option

Q: Is it smart to deliberately put it in some bad places, to prove out in the data that those are bad places? A: Yes maybe. Alexis will consider.

Amanda hopes by tomorrow to provide feedback on placements. Link for ref: https://mobile.va.gov/app/va-health-chat

Address line 3 - @laflannery

Bottom line: do we need the 3rd line? Seems no.

307 facilities in the Facilities API have some data in the 3rd address line.

• Less than half have something in Address 3 but not Address 2, which is weird.
• Sometimes a building name, mall, plaza
• We get the data from VAST, but squish it into 2 lines, or into 1 line that wraps

Will be very difficult to predict how these get used, or quality control that.

Hide for now, bc this is a config level change. Let's allow each product to expose it / use it correctly.

Questions about service locations and potential for editor instructions - @mmiddaugh

Amanda to brief Michelle on her discussion with Dave. Questions are around whether folks wh have more than 1 service location will have to go in and set their options within each service location. Q: are there other things we would like them to handle at the same time?

Do VAMC editors need a training on this in office hours? Maybe.

[davidmpickett]

3/7/24 Agenda

• Spotlight patterns - @thejordanwood (10 min)
• Research updates - @ALogsdon3 (10 min)
• Service locations deep dive - @davidmpickett & @thejordanwood (40 min)

Spotlight patterns

• Ticket: #17208
• Design in Figma

Notes: In the spotlight card Component: to replace blue spotlight boxes

• DS components
  • DS has suggested that we need to use the Major Links component, but not every spotlight includes links. Some spotlight cards use bullets, etc. The content irl is more complex than that component.
  • Instead: we would like to use gray card component. Card component also requires a link.
• Missing capabilities are part of why Spotlights are getting used the way they are:
  • Vet Center editors are using spotlights for Events, bc VC Events don't exist, for example.
  • "Contact us" type cards with no CTA don't make sense without a CTA
• Amanda wants to go through Design Intent with this change, to make sure we get DS blessing.

In the Spotlight links list:

• Can use the Related links component
• We'd like to revise the heading here to remove "in the spotlight" language to be something more clear / useful

For reference: on Health Services List, spotlight cards exist but are more scructured in Drupal. Named "Featured content on health-services page" (using Drupal paragraph "link teaser"): contains a link, link text, link summary.) There is a ticket for reviewing the Drupal interface to get aligned.

Next step:

• Get our use cases documented and mocked up
• Schedule Design Intent

Research updates

• Ticket: #16011

Notes:

• Health plan Conversation guide / research plan taking shape, reviewable with Amanda on Friday
• VBA RO research: no updates, no signups. Michelle to work with VBA RO national leadership to nudge to get signups.
  • @xiongjaneg to add Amanda to RO editor training invite for awareness

Service locations deep dive - part 1 - @thejordanwood

• Ticket: #17342
• Design in Figma

Notes:

1. “Name of office or location" field left blank:

   • Add Location subhead: #17414
   • Decide whether to group Facility address with these other fields above or below phone numbers

2. Labels show without other information: Update Drupal UI to be more clear about required info.

3. Hours

   • Short term: "Open 24 hours" plain language
   • Long term: consolidate days of the week to show a single line for: Mon-Fri: Open 24 hours, e.g.

4. 1 vs 2 service locations at one facility

   • Introduce conditional logic for this: When there’s 1 service location: No card / When there’s 2+ service locations: Yes cards

5. 1 vs 2 facilities listed on a page

   • If 1 facility: no borders, no accordions
   • If >1 facility: use accordions treatment

6. Visual hierarchy change - change headers to bold text.

   • This might be easier lift for FE
   • May reduce the need for cards for multiple service locations

7. Labels being duplicated: Hard. Not yet solved.

Next steps:

• Engineering conversations to understand LOE between short and long-term solutions, to make sure that short-term proposals are a win, or if we should just go for it.

Service locations deep dive - part 2 - @davidmpickett

• Epic: #17350

Notes

• Facility > Facility Service > Service Location is an ontological problem. (What are you doing, where can you do it?)
• We cracked this for VBA by starting with what you're doing.
• Service Location Header: figuring out how to get it into the VAMC content model might help solve this. Currently we are trying to design around it.

Summary

#17350 is the epic tracking Service Location UX work now.

[davidmpickett]

Notes for 3/14

VBA editor research debrief? @ALogsdon3

• 2nd VBA editor session: some connection issues, lot of opinions, lot of experience working in this realm
  • was focusing on operating status
  • didn't notice character counter
  • unorthodox use of operating status, putting in address information
  • knew stats about Veterans she served, really cares about the end user
  • mentioned some things were better in Drupal but worried about things in Teamsite that might not be possible (a link to Spanish version of a page, a document she wanted to upload)
  • need for change management, reassurance for editors that this will be better
  • not interested in looking at KB, glad it was there, but just wanted to edit
  • not interested in looking at error message
  • about adding links in help text to style guide and KB articles; editor said it would be nice to be right in that page
• Alexis will be focusing on documentation wrap-up, including brain dump of VBA research to date

Sample platter of Service Location tickets @davidmpickett

• 17503

  • Non-clinical services where there are multiple locations (only in 5 instances at this point) and not correctly used
  • Recommend limiting non-clinical services to 1 location
  • Michelle is finding out if this meets editors' needs and added to VHA DM sync
  • If this is limited, will need to do editor change management (Albany, in particular)
  • Michelle noted that it may be helpful to find police use cases before making a decision on this

• 17414

  • In Service Location field for Address, the first field (Name of office or location) can be left empty, which affects how it appears in front end (no header, orphan address)
  • The recommendation is to have the front end add a header
  • Doesn't have a header even if Use facility address is checked
  • Still needs refinement, this is to make front end defensive
  • Related ticket for Drupal to add required first field if subsequent fields have text

• 17489

  • Needs design focus on ideal editor experience, ideal help text, intent of the field, use cases

Open questions and tickets from ongoing VAMC/VBA testing?

• Are there blocker tickets? Yes, still need triaging and prioritizing by product.

[davidmpickett]

Agenda for 3/21

• Drupal designs for spotlights - @thejordanwood
• Will imposter spotlights block VBA launch? - @aklausmeier
• Research updates/handoff - @ALogsdon3
• Service location tickets - @davidmpickett

Drupal designs for spotlights

• 13804

• Figma design
• Notes: VBA and Vet centers use same interface. VAMC doesn't
• VAMC - "link text" is actually header
• Step 1 - align VAMC with Vet Center & VBA
• Possible future addition - restrict them to a single call to action using conditional formatting
• Update Call to Action interface to start with a drop down and have different options for Phone/Email vs Link

Will imposter spotlights block VBA launch?

• Slack thread
• No
• But if we can update this on VBA before launch, let's do it

Research updates/handoff

• Documentation is on MS Teams in Sitewide Facilities Team

• 17499

  • Showed us the Research analysis spreadsheet and how to enter data
  • Editor tracker has PII - Amanda is investigating best practices as it affects multiple teams

• 17498

  • Alexis ran pilots with Laura and Marisa
  • Removing the statement about being in north florida
  • Ready to send to research ops for review

Service locations tickets

• 17515

• 17514

• 17566

[davidmpickett]

Agenda for 3/28

• Removing IEF on Vet Centers - @omahane & @davidmpickett
  • Discuss options
  • Choose direction?
  • Stub out tickets for chosen path??
• Prefining Service Location launch tickets - @davidmpickett

  • 17605

  • 17600

  • 17632

[jilladams]

@davidmpickett @aklausmeier As I'm updating calendars, I'm penciling in process we've bandied about. This is not in stone and can be revised, but: I've spun up a ticket to convert this to become Sitewide UX Sync as of next week, and am framing the calendar invite that way. We can change this after kickoff discussions take place: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17669

[aklausmeier]

@jilladams @davidmpickett Does this thought process also include scrapping Public Websites UX refinement and rolling into the Sitewide UX sync?

[davidmpickett]

Follow up notes will be in https://github.com/department-of-veterans-affairs/va.gov-cms/issues/17669