Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create high-level user journey #16

Closed
xmatthewx opened this issue Jan 18, 2017 · 13 comments
Closed

Create high-level user journey #16

xmatthewx opened this issue Jan 18, 2017 · 13 comments
Assignees
@xmatthewx
Milestone
February 24, 2017

Comments

@xmatthewx
Copy link
Contributor

Here's a quick whiteboard sketch. Fodder for discussion.

user-journey

cc @arlissc @taisdesouzalessa @sabrinang @HPaulJohnson
@taisdesouzalessa taisdesouzalessa mentioned this issue Jan 25, 2017
Closed
24 tasks
@xmatthewx xmatthewx modified the milestone: February 10, 2017 Jan 30, 2017
@taisdesouzalessa
Copy link
Contributor

taisdesouzalessa commented Jan 31, 2017 •
edited
Loading

Here is the doc with additional info @xmatthewx
screen shot 2017-01-31 at 1 28 06 pm

PDF: userjourney.pdf

@taisdesouzalessa taisdesouzalessa self-assigned this Feb 4, 2017
@taisdesouzalessa
Copy link
Contributor

taisdesouzalessa commented Feb 4, 2017 •
edited
Loading

@xmatthewx here is the simplified user flow. There are some parts that are unclear to me so we should sync to refine it.

simplified-user-flow

cc: @sabrinang

@xmatthewx
Copy link
Contributor Author

This is great. Let's discuss at the end of our next stand up to answer your questions and make a few adjustments.

@xmatthewx xmatthewx removed the design label Feb 21, 2017
@taisdesouzalessa
Copy link
Contributor

@xmatthewx we could discuss this overall experience when we have a meeting to talk about staff feedback. What do you think?

@xmatthewx
Copy link
Contributor Author

xmatthewx commented Feb 22, 2017 •
edited
Loading

thanks @taisdesouzalessa

Glad to discuss when we chat about feedback. Let's make a couple of small tweaks and then hand this over to the people working on engagement. They can fill out the details.

  • We can order the entry points. One end likely for existing members (email). The other end likely for new visitors (search). Doesn't need to be scientific, just a spectrum. I don't think we need hard separation between the two groups or more info.
  • Let's add existing member to the top towards on one side, new visitor towards the other
  • I wonder if we should relabel non-member to Site Visitor
  • Remove Pulse and hubs. These are represented by mozilla site & event/partner
  • Remove the notes, bulleted lists on email/segments/offerings.
  • Next to the Input field /Join us button let's put text + Referrer + Page URL + Feature ID to indicate info we'll capture.
  • Let's put email/social at the same level as Site Offerings

Let's also branch out from the site to:

  • Connect with Members (via Twitter LinkedIn)
  • Connect with Members (via Projects on Pulse)
  • these go left/right as alternatives to Email>Join>CRM

Again. Glad to discuss when we talk about feedback.

@arlissc
Copy link

arlissc commented Feb 23, 2017

@taisdesouzalessa @xmatthewx - just seeing these documents. Very helpful. Would like to understand the operational pieces of the data capture mechanisms for the CRM.

@xmatthewx
Copy link
Contributor Author

Hi @arlissc. I don't understand your question. If this is technical about input from the form, let's discuss with Gavin here: #8 and during the tech weekly call on Tuesdays. Beyond email address, we should be capture referring site, page URL, some sort of id to identify the "campaign" featured to gain members (e.g. Health Report 2016, Fellows Mar 2016, ). You can lookto Vojtech and Paul for how we track those sorts of things. If this is not technical, we're meeting tomorrow to talk with Will and 270 about engagement and email. Maybe we can clarify there.

@taisdesouzalessa
Copy link
Contributor

Here is the revised User Journey

simplified-user-journey-revised-v2

@xmatthewx I added the "event/partner" after "email" because in my understanding a person who goes to events or is our partner knows more about us (and it is more active) than a regular e-mail subscriber...let me know if I am missing something here.

@xmatthewx
Copy link
Contributor Author

This is excellent. Thanks! A couple of tiny things, and then i think we can call this done for now. I'll share this at a 1pm PT meeting today. Edits would be good before then, but they aren't critical.

Comments here: https://redpen.io/aea43c500e20d86dae

@taisdesouzalessa
Copy link
Contributor

Diagram revised:

simplified-user-journey-revised-v2

@xmatthewx
Copy link
Contributor Author

Thanks again. Let's remove the black dotted lines. They draw too much attention. Let's just point to a duplicate of the site. There's a small audience for this diagram ... they can handle it. One other correction in pink.

Sorry to ask you to do this. I'm having trouble getting typekit to sync on my new computer, otherwise I wouldn't bother you.

user-journey-revision

@xmatthewx
Copy link
Contributor Author

When done, let's drop in our summary deck here: https://docs.google.com/presentation/d/1nLLNCyp1JtrOdiKlFYoBMOa_VqpXFrbxeYRI5PgwB0A/edit#slide=id.g1cfefcff86_0_0

@taisdesouzalessa
Copy link
Contributor

Changes applied and added to the summary deck :).

Closing this ticket.

mmmavis added a commit that referenced this issue Jan 24, 2018
@mmmavis
# This is a combination of 17 commits.
2e24e4f 
# This is the 1st commit message:

fixed rebase conflicts

# This is the commit message #2:

fixed rebase conflicts

# This is the commit message #3:

fixed rebase conflicts

# This is the commit message #4:

updated elements on the page based on the latest comps

# This is the commit message #5:

added the last 2 sections in

# This is the commit message #6:

removed redundant code

# This is the commit message #7:

fixed rebase conflicts

# This is the commit message #8:

fixed rebase conflicts

# This is the commit message #9:

to match the updated comps

# This is the commit message #10:

fixed broken links

# This is the commit message #11:

named URL patterns

# This is the commit message #12:

custom template tag 'active_nav'

# This is the commit message #13:

applied custom template tag

# This is the commit message #14:

fixed linting error

# This is the commit message #15:

fixed linting error

# This is the commit message #16:

Related to #951 - fellowship type template & science fellowships

# This is the commit message #17:

featured fellow
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xmatthewx xmatthewx

Labels
None yet
Projects
None yet
Milestone
February 24, 2017
Development

No branches or pull requests
4 participants
@xmatthewx @arlissc @hannahkane @taisdesouzalessa