Wireframe or quick mock up of initial choice with separate dashboard screens for email and text

An article on Hicks law explains the more options you offer, the longer it takes for the user to make a decision. On this basis, we could consider offering users who are about to send messages an initial choice of email or text message, that would land them on a separate screen for whichever message type they choose.

We would still need to ensure that users: (1) can easily navigate to the other message type's screen when they want to send that type of message. (2) can access a screen and download reports that display both message types - email and text - together

Notify generally logs users into the "Your services" screen which may be disorienting and make it hard for users to find the dashboard.

As a Notify user, I need to be able to easily find the various types of information that I need so that I can work without confusion or difficulty.

WHY are we building?

The article says: " Rely on a principle of progressive disclosure when designing user interfaces. When information is revealed progressively, users will be less overwhelmed with a large number of choices and instead adapt to more complex flows."

Currently the cognitive load of our dashboard is so high: it offers so many choices in terms of what info users could choose to focus on. And as we add more features like bounce rate and SMS v2, that is likely to increase.

WHAT are we building? A mock-up of an initial option screen and separate text and email dashboard screens.

VALUE created by our solution Changing the UI in this way could make the users progress easier. Alternatively it may slow users progress and be frustrating. Therefore, in order to consider whether this idea is worth exploring without using much of our resources, we could try a quick mock-up.

Documentation and Artifacts

Hick’s law: how to make choices easier for users: Hick's Law states that the more options you offer, the longer it takes for the user to make a decision.) Hick's Law states that the more options you offer, the longer it takes for the user to make a decision.

Acceptance Criteria

Given our users need to move smoothly and quickly through Notify, when they want to access a particular function of Notify, they can easily do that.

[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
A11y
Bilingualism
Privacy considerations
Security controls in place
Measuring success and metrics

Related Research Airtable records

(Ping Adrianne to add stuff here or find stuff yourself)

QA Steps

[ ] Tested in a realistic production scenario

cds-snc / notification-planning