User journey - Fellowship pages

[taisdesouzalessa]

User journey

• [x] 1. from hearing about Fellowships to being in one cohort

• [x] 2. from belonging to a Fellowship to updating projects and connecting to other Fellowship members

• [x] 3. from learning about the existence of Fellowships to getting educated about it in order to use the info learned (media or internet activists).

[taisdesouzalessa]

Here are the journeys:

1. https://invis.io/GPDZCQDQJ#/258657198_1-From-Non-Member-To-Being-Cohort
2. https://invis.io/M5DZCXAN2#/258657199_2-From-Fellow-To-Ending-Fellowship
3. https://invis.io/VMDZD1IF4#/258657200_3-Media

To navigate that in the order, please click on the blue dot to the left(that should be the starting point) and hit next. It will guide you through the questions I had while thinking about the system. Please comment there, add your thoughts and paths that I may have missed.

@hannahkane @xmatthewx @jessevondoom - looping you 3 for feedback. Feel free to add more people as you see fit.

[taisdesouzalessa]

One curiosity:

Here is a real user journey from Christine Zhang (featured in Story Engine). She fits into our "Pepper, the Professional" persona and I think it is very cool that some of her pain points will definitely be solved with this page. Thought it was worth it to share.

[taisdesouzalessa]

I will be working on some MozFest materials with Sabrina - however, please feel free to comment, give feedback and discuss this issue :)

[hannahkane]

For some reason, InVision isn't letting me sign in to comment. :(

So I'll comment here!

Overall, these look pretty spot-on. Thanks for helping us all think through the journeys, @taisdesouzalessa.

Journey 1:

• You asked a great question about how much info potential applicants have by the time they come to the site. I think @auremoser might be a good person to help answer that.
  • Fellowship section on the homepage? I think yes, given how central they are to our strategy moving forward. But will defer to @jessevondoom, especially around the question of whether that homepage real estate is year-round, or just during application season.
• Good question about goals for refused candidates, though I'm not sure we need to answer it now (that may be something the Fellowships team is thinking about)
• Prompts to get people back to the site once applications are open - I think the Fellowships team will likely have a robust promotion plan to help get the word out.
• The question of whether we want potential Fellows to contact past Fellows is a great one. Maybe something @auremoser or @community-impact could weigh in on?

Journey 2:

• Can you clarify, are you thinking each individual Fellow would get a page on the site?
• I definitely think we should integrate with Pulse as much as possible - i.e. Fellows' profiles and projects
• One thing we might want to think through is what we mean by cohort. I can think of at least two ways of thinking about it. I think it definitely refers to the year of a Fellowship. Everyone who was a Fellow in 2016 is in the same cohort. But I wonder if there's also a need to distinguish based on the type of Fellowship. So, for example, "2018 Science Fellows" might feel a special kinship, though they might also feel connected to the rest of the 2018 cohort. If the program-specific identity is meaningful, perhaps we want to reflect that on the site in some way.

Journey 3:

• Your question about "who else besides media and internet activists" is a good one for @auremoser and @community-impact

[auremoser]

Hey there, I'm pretty toe up with Mozfest floor prep, host org onboarding and fellows arrangements for Mozfest, but I've tried to address your questions below

Journey 1:

You asked a great question about how much info potential applicants have by the time they come to the site. I think @auremoser might be a good person to help answer that.

To be honest, the majority will probably find this page through social media shares and blog posts from our comms team. I doubt many will fall into it, since it's not a topline nav item. It's possible people will hit "get involved" and get curious about our fellowships but I think that the terms are pretty self explanatory, most people will know what a fellowship involves and can read the FAQ or the kind of simple info we have on the science site.

When applications are open we add a banner to push people to the application, when the applications close we add "applications are closed for YEAR, check back in MONTH"; I imagine the network site will work the same way and point to our FLUXX application from the Network site.

The question of whether we want potential Fellows to contact past Fellows is a great one. Maybe something @auremoser or @community-impact could weigh in on?

We provide fellows with the master contacts of all fellows from previous cohorts so they can setup collabs; I think any alumns we feature are pretty willing to being contacted over Twitter or via any channels identifiable from their personal websites. We defintitely would love to see more collaboration between fellows, but I'm not sure the Network site needs to be the engine that enables those collabs particularly.

Journey 3:

Your question about "who else besides media and internet activists" is a good one for @auremoser and @community-impact

I'm not very clear on who this journey is intended for (is it folks who don't want to be fellows but rather want to reach out to fellows or learn more about our program?); if it's that, we'll probably get a mixture of scientists, educators, media, artists, activists, nonprofit folks and developers, given the fellowships we offer and the people who might be attracted to the program based on the demographic/thematic foci of those fellowships. I hope that makes sense and isn't too vague.

Let me know if I missed anything!

[taisdesouzalessa]

Thanks, @hannahkane for the thoughtful comments and linking to other people and thanks @auremoser for carving some time in your busy schedule to answer those questions. They are very valuable to design so I can put myself into the Fellows' shoes and make sure their main needs (and ours as an org) are addressed. Thanks a million!

[taisdesouzalessa]

Checked user journey with Amy and Jesse as well. Their observations, together with Aurelia's and Hannah's answered the questions I had. Closing this issue.