-
Notifications
You must be signed in to change notification settings - Fork 153
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
Create high-level user journey #16
Comments
Here is the doc with additional info @xmatthewx PDF: userjourney.pdf |
@xmatthewx here is the simplified user flow. There are some parts that are unclear to me so we should sync to refine it. cc: @sabrinang |
This is great. Let's discuss at the end of our next stand up to answer your questions and make a few adjustments. |
@xmatthewx we could discuss this overall experience when we have a meeting to talk about staff feedback. What do you think? |
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.
Let's also branch out from the site to:
Again. Glad to discuss when we talk about feedback. |
@taisdesouzalessa @xmatthewx - just seeing these documents. Very helpful. Would like to understand the operational pieces of the data capture mechanisms for the CRM. |
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. |
Here is the revised User Journey @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. |
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 |
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. |
When done, let's drop in our summary deck here: https://docs.google.com/presentation/d/1nLLNCyp1JtrOdiKlFYoBMOa_VqpXFrbxeYRI5PgwB0A/edit#slide=id.g1cfefcff86_0_0 |
Changes applied and added to the summary deck :). Closing this ticket. |
# 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
Here's a quick whiteboard sketch. Fodder for discussion.
cc @arlissc @taisdesouzalessa @sabrinang @HPaulJohnson
The text was updated successfully, but these errors were encountered: