Task and User Flow

[jenchuu]

Overview

As a UX Designer, we need a clear understanding of users' journey while using Civic Tech Jobs' website.

Based on the latest requirements, we will create a task flow to define the linear high-level steps all users must complete to accomplish their task.
We will also create a user flow to illustrate the path our main user-type may take.

Action Items

• Task flow
• User flow
• EDIT task and user flow

Resources/Instructions

Civic Tech Jobs' Task and User Flow

Civic Tech Jobs' Figma Prototypes

Meeting Notes for Bonnie's Feedback on Flow - 02/06/22

https://medium.com/erika-harano/ux-task-flows-versus-user-flows-as-demonstrated-by-pancakes-896e78a98026

[jenchuu]

task and user flow

[sharadgaurav7]

@jenchuu , let's discuss the dependency "Requirement Changes" you have mentioned in the issue before moving this in the prioritized backlog. Looks like this issue is nearly complete as you have already prepared the user flow

[jenchuu]

@sharadgaurav7 Sounds good; I unfortunately missed last weeks meeting so I put dependency as "requirement changes" in case there were any further changes to the Requirements that I missed. (I did check the updated Requirements google sheet)

[jenchuu]

V3 of task and user flow

@graceerya, @Dendorable (Helene), and I worked on this last night as a starting point and to highlight questions for our next meeting.

[jenchuu]

@sharadgaurav7 @sdimran. Is this flow approved as starting point for the MVP?

@Aveline-art Is it possible to change WHERE the "Join us" CTA on home page and CoP cards lead to when a user is LOGGED in? Aka can users be directed to FULL search page?
(These "Join us" CTAs lead to qualifier page when NOT logged in)

[Aveline-art]

@jenchuu That should be very possible!

[sharadgaurav7]

Team,
Since the first time users' details will not be captured without their login credentials being activated, they will have to login and go through the qualifier page again after they receive their login credentials (following the Onboarding session). The only way the website can remember previous inputs will be if we drop some cookies (this will not be permanent).

@Aveline-art , can you please comment on this thought process. We can discuss this on slack if needed. Or during our Tuesday meeting.

[Aveline-art]

@sharadgaurav7 A couple of points:

• Is there a specific reason why users are allowed access to the qualifier page without logging in?
• On a side note, in case there happens to be a specific reason, could we encourage (optional) user login through some warning text? Ex: "We encourage you to sign up so that we can save your input from this page! This will...[benefit to the user]."
• Cookies/localstorage are relatively stable. Cookies can expire, based on a set date (up to months/years), and localstorage can be manually deleted by a user.

[jenchuu]

Per discussion with @Aveline-art and @graceerya below is the revised task and user flow.
We would love to go over this task/user flow and the prototype flow we created with you tomorrow evening! @sdimran @sharadgaurav7

[sdimran]

@graceerya you can include the notes and feedback from bonnie regarding the proposed flow here. can we also include a link to the figma in the resources to indicate where the protoypes presented are?

Thanks!

[sharadgaurav7]

@jenchuu , I think this issue is complete. Can you please close it.

There's another issue ( #144 )that has dependency on this one, for the issue #144 to be active, this one has to be completed.

[jenchuu]

Yes done. Moved to Review column.
@sharadgaurav7 @sdimran

[sharadgaurav7]

@jenchuu , please make sure a copy of this is on the shared drive. Closing this issue, thank you for the works here!