[Health IA intake:] Discovery - SM in-product nav update

[sterkenburgsara]

Overview

Since the integration (6/17/24), the removal of the secondary navigation for SM required pivoting to hanging links that users are not understanding clearly based on Medallia feedback so far. We likely need to do some research to understand pain points more deeply with the SM navigation, and ideate on some things that might work better for this tool within the current structure and overall global navigation decisions that have been made for the MHV portal at this point.

We were discussing passing parameters instead of unique URLs to allow for hte use of buttons in the UI, but now want to zoom back out and look at the problems we are trying to solve and how we might simplify the product to focus on those problems more directly. Can we brainstorm a future where we possibly rely far less heavily on in-product navigation and where the inbox is able to take care of most of the needs that users come to this tool with? What might that look like?

Team

• Requester: @emilytaylorux @underpaid1ntern
• Team Name: Secure Messages

Description

This ticket relates to discovery work and digging into what we already know about SM to ideate on some potential solutions to increase the usability of SM for users based on these key problems:

• Users need to easily get to their inbox and see a list of messages, with the most recent ones first
• Users need to be able write a new message or reply to an existing thread
• Users need to understand which messages are new and/or unread
• Users need to be able to retrieve specific messages (i.e. I want to look up the interpretation of my lab & test results from last month - I want to find that message)

Links

• SM team Figma files with navigation ideation (with MHV-wide secondary nav applied)

Work needed

• Pros and cons of a variety of ideas have been drafted and are understood.
• We have a general direction that we can head toward for user testing within this PI

Timeline

When does IA review need to be completed by? TBD

Acceptance Criteria

• [x] Pros and cons of a variety of ideas have been drafted and are understood.
• [x] Designs have been shared with devs for feedback (if necessary)
• [x] A general direction is identified that team can move toward (possibly into research if prioritized)

[sterkenburgsara]

Update: prioritization of PHI/PII work took precedence over this ticket in sprint 38. Removing from my in-progress work and will try to get to this in the next sprint.

[sterkenburgsara]

Update: Kaitlin leaning toward keeping the hanging link in-product nav for now, possibly move toward eliminating drafts, trash, & custom folders down the road. Will continue to explore.