Oops Reminder Content

[sydneywalcoff]

Overview

If you use browser navigation like (refresh, forward and backward) while in the letter generator, the app forgets all your previous answers. And because it uses your previous answers to determine the flow and eventually to form the letter, the app breaks and shows a blank white page.

We should:
a) Warn users not to use browser navigation like (refresh, forward and backward) while in the letter generator before they start #1152
b) If a user does refresh, we should show a little Oops reminder (similar to the #1136, but smaller) reminding the user not to use browser navigation

Action Items

• UXR support for Content
• Create content for a little doodle or something telling the user not to use browser navigation
• Add doodle content to Design Oops Reminder #1141
  • Remove dependency label
  • Move to 'new issue approval' column

Resources/Notes

• User flow journey on Figma
• Sitemap on Figma

[github-actions]

Hey @SamHyler, @emmathrash! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

[cjankowski23]

Update
Progress: First set of content explorations have been written and will be shared with content team for feedback.
Estimated Time to Completion (ETC): Approximately one week
Blockers: Team feedback to ensure the message fits voice & tone as well as purpose.

[cjankowski23]

Progress: First set of content explorations have been shared with content team. Currently revising content and developing strategies to enhance error notifications overall, to ensure a consistent tone and voice.
Estimated Time to Completion (ETC): Approximately one week
Blockers:

[github-actions]

Hey @cjankowski23! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

[cjankowski23]

Progress: Strategizing to enhance error notifications and ensure a consistent tone and voice throughout.

[cjankowski23]

Progress: Met with Ellynna from the Design Team to discuss possible template ideas for the warning strategy.
Estimated Time to Completion (ETC): Presenting iterations to group on Friday all teams meeting.
Blockers: Contingent on feedback.

[cjankowski23]

Progress: Iterations in progress
Blockers: Spoke with Sydney, "Return Home" means returning to the landing page. Discuss with team if we would like for users to return home (landing page) or the beginning of the letter generator from the oops page.

Double check if we would like to take the opportunity to use the new language "declaration letter" or use the previous terms for now, until the next update.

[cjankowski23]

Progress Shared user action/ flow questions regarding call to action at the bottom of oops page with the Design and Content team.

Utilize [Site Map] as a spring board to creating user flows for potential user actions. (https://www.figma.com/file/hYqRxmBVtJbDv9DJXV6nra/Expunge-Assist-Main-Figma?type=design&node-id=2982-24928&mode=design&t=c8fnUyJlJeg5Ug2N-0)

Blockers Create and present different user flow diagrams and provide the content that would lead to each action for returning home, returning to onboarding, returning to the start of the letter generator, or providing two button options, for returning home or the start of the letter generator.

Estimated Time to Completion ETC Present ideas next Friday

[sylvia-nam]

Added user flow journey to resources, added task item on UXR support for Content. I will work with Claudia with issue updated once we chat, map out research support request.

[github-actions]

Hey @cjankowski23! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

[github-actions]

Hey @cjankowski23! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

[github-actions]

Hey @cjankowski23! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

[cjankowski23]

Time for an update! Please comment the following update:
Progress: Content has been updated and brought up at standup.
Estimated Time to Completion (ETC): 1 week
Blockers: Verifying next steps

[cjankowski23]

Progress:

Defined the Destination and Function of the CTA Button
The "START AGAIN" button will lead to the start of the letter generator titled "Introduce Yourself." This action will help reduce cognitive load and frustration after losing progress.

Error Message: Created a clear, empathetic error message that provides a call to action for users who have lost their work.

Content:

The Page Refreshed

To protect your privacy, all information has been cleared.
Button: START AGAIN

---

The content in the past tense to reflect the finality of the user's lost progress.

[SamHyler]

@sydneywalcoff asked a question about this issue, @cjankowski23 is going to have a new look in regards to those questions

[cjankowski23]

Feedback received from @sydneywalcoff
Re: Oops Reminder.
I was looking at the Figma before prioritizing it and I realized that it’s not completely accurate.
(this one is less of a big deal) We’re not clearing the information because of privacy reasons. This is a side effect from not saying any data in the first place and it just happens to conveniently fall in line with our values regarding privacy.

The bigger deal being that it only references refreshing when this problem can be caused by any browser navigation (refreshing, and using the browser forward and back buttons). I’m thinking this might confuse people who use the browser navigation vs the app navigation and end up in the same place. I think the content should reference all the ways you can do this and should instead encourage the user to use the app navigation (the purple forward/back buttons that we added)

progress
Shared new iterations during standup.
Somethings we've discussed as a team:
Concerns on stating purple forward back buttons are related to color blindness and accessibility.
Maintaining a supportive, straightforward, trustworthy, mentor like voice.

Estimated Time to Completion (ETC):
Will share new iterations during standup next week.

Blockers
none

[github-actions]

Hey @cjankowski23! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

[cjankowski23]

Progress: Completed, updated content on design.

---

The page refreshed
Your letter was erased.

Only use the forward and back buttons for navigation to prevent losing your work.

START AGAIN

---

Estimated Time to Completion (ETC): 1 week
Blockers: Ask design to check spacing is correct, if correct hand over to dev.