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.

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

User jouney: from website to first e-mail #344

Closed
taisdesouzalessa opened this issue Apr 25, 2017 · 13 comments
Closed

User jouney: from website to first e-mail #344

taisdesouzalessa opened this issue Apr 25, 2017 · 13 comments
Assignees
Labels

Comments

@taisdesouzalessa
Copy link
Contributor

Issue:
Once our audience decide to sign up to our mailing list, they will receive an e-mail about our news and offers. Ideally, the e-mails would match the expectations they had when they clicked the "Sign Up" button. The challenge we have is that - at this moment - all the users will be sent to the same e-mail list even though their expectations differ from page to page.

Here is a diagram that illustrates the situation:
image

Proposed solution
One way to tackle this issue at the website level is to have a standard message close to the sign up button that explains to the audience that they will receive news about internet health, blended with others. I am not sure how we would do it since the CMS allows the editors to choose the copy they want. It is something we will have to think about.

@xmatthewx
Copy link
Contributor

@jessevondoom - The Salesforce CRM is very limited at this stage. SIgn-up, and you get an email with double opt-in on a very confusing page (#207).

We'll track pages that pull people into our list (fellowships vs mozfest) as raw URL (rather than friendly label), but users will get the same generic email reply. Staff should be able to get a report of people who join related to their programs, but will this be instant? Monthly?

This isn't critical for the launch next week, but is a thing we should look at soon. We should decide if we need a design solution as @taisdesouzalessa suggests b/c the tech will come too slowly.

@xmatthewx xmatthewx modified the milestones: June 2, 2017, May 19, 2017 May 19, 2017
@xmatthewx
Copy link
Contributor

We can roll this over to the next heartbeat. Probably requires a real-time discussion. We could turn off the feature for authors to customize the sign-up copy, or only allow them to add a short statement to the standard form.

@xmatthewx xmatthewx modified the milestones: June 16, 2017, June 2, 2017 Jun 6, 2017
@xmatthewx
Copy link
Contributor

This sprint we will hold a cross-team conversation on constraints and goals.

@taisdesouzalessa
Copy link
Contributor Author

Having a conversation in #503 with Stephanie to have a more detailed view of the current experience - it would be useful to have the complete diagram handy for our cross-team meeting.

@taisdesouzalessa
Copy link
Contributor Author

taisdesouzalessa commented Jun 14, 2017

Hey team, @stephaniemcv helped me figure out the missing pieces of the current journey (from website to e-mail...yay! Thanks, Stephanie). This is a snapshot of the journey as is now. RedPen: https://redpen.io/ws99a7bd530a91b791
double-opt-in

By looking at this diagram, some elements stood out to me:

  1. As we discussed before, there is an opportunity to align expectations in our website copy with what happens once users receive their first e-mail.
  2. If they are already subscribed to any Mozilla or Firefox mailing list, it seems they receive the Pulse e-mail. I think there is an opportunity of alignment in this flow.
  3. If they are already subscribed to the Mozilla Leadership Network mailing list there are currently no mechanism in place to let them know they are already registered. People may forget they registered so I think there is an opportunity improve this flow as well.

@xmatthewx @hannahkane @jessevondoom

@sabrinang you may like seeing this too, since we brainstormed (is this a verb?) this together!

@hannahkane
Copy link

@taisdesouzalessa will schedule a follow-up meeting to discuss with @jessevondoom @xmatthewx @stephaniemcv, etc.

@taisdesouzalessa
Copy link
Contributor Author

taisdesouzalessa commented Jul 7, 2017

Booked a 30min meeting Monday (July 17th) - In this milestone I'll do a click through slide presentation so everybody can go through the flow as the user. It seems the diagram above was a bit difficult to read due to its size on screen. Once I do the click through, I'll post it in the meeting agenda so everybody has a chance to go through the flow in advance and come up with opinions/feedback - what do you think about this plan @hannahkane?

@hannahkane hannahkane modified the milestones: Arrhythmic beat, July 14 Jul 10, 2017
@taisdesouzalessa taisdesouzalessa added this to the July 28 milestone Jul 11, 2017
@taisdesouzalessa taisdesouzalessa modified the milestones: July 14, July 28 Jul 11, 2017
@taisdesouzalessa
Copy link
Contributor Author

taisdesouzalessa commented Jul 14, 2017

Here is the click-through of the experience showed on the map earlier in this thread. I feel it is less confusing now, let me know what you think, ok? I'll attach it to our meeting agenda.
https://docs.google.com/a/mozilla.com/presentation/d/1tdxC1aqiJsEWC-k5ekQZpS1lbGJThZiNWtcnMfvH9L8/edit?usp=sharing

@jessevondoom @hannahkane @stephaniemcv @sabrinang @xmatthewx

@xmatthewx
Copy link
Contributor

Great conversation today. Thanks @taisdesouzalessa for the insightful deck. And thanks @stephaniemcv for all the expert info.

Next steps? I think we close this ticket after we open two new ones:

  • explore sign-up scenarios and welcome messages
  • refine existing forms and language on the site for more clarity

Anything else?

@stephaniemcv
Copy link
Contributor

Here is the deck I mentioned: The Need for Improved Audience Segmentation

@hannahkane
Copy link

@xmatthewx - how are #585 and #586?

@hannahkane hannahkane removed this from the July 14 milestone Jul 18, 2017
@kristinashu
Copy link

@xmatthewx can we close this ticket?

@xmatthewx
Copy link
Contributor

Closing. Follow up filed elsewhere as Hannah commented above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants