Goals

Background and strategic fit

Adobe SDK (August 2018) changes have eliminated any control over the MVPD auth experience (users will be redirected to the provider site, no chrome). Longer term Jon Moze hopes Adobe will re-incorporate their partners back into the auth experience and is working towards that goal. Rona and Angela identified the Apple SSO issue as the only related dependency... today when you go to the TV Provider page it redirects into Adobe ... we need to introduce the Apple SSO Help prior to Adobe hijacking our user. (Leland Weeks)

Assumptions

Requirements

User interaction and design

Entry

• MVPD CTA on Navigation OR Home
• VOD Context Specific Screens
• On Now
• User > Settings > TV Provider

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Not Doing

Date

19 Dec 2018

Attendees

• Mitch Johnson
• Leland Weeks
• Kim Hicks
• Eric Olivencia
• Cathy Gallant
• Rona Sheen
• Doug Clark 

• Rona Sheen

Duration: 

Goals

• Review OneID and non-OneID flows with Kim before handing off to Research

Agenda

• Present OneID & non-OneID flows – Leland / Mitch
• Provide feedback on flows – Kim
• Discuss next steps with research – Cathy / Eric / Andrea

Notes

• Singular “I have a profile” on Make It Yours screen
• Don’t call the One ID feature as an “Upsell” — Account Discovery Moment
• Key is assuming everyone is under 13 so we just ask for “Parent Email"
• Discovery moment in Profile is not contextual enough in its messaging. Need tweak copy. 
• Info button about Disney Account
• For sub-head on Sign In, rework copy. 
• Investigate info screen for more info 
• Voiceover is important on Sign In screen
• K - Good with going with full modal since kids will notice that more
  • Opportunities for motion to be explored to explain benefits better
  • Sheet notifications won’t be good since we know kids miss it. 
• Need info from One ID if under 13 account holders can “Manage Account” 
• Kim: If users access Disney Account from Profile, should there be entry point from Profile? 
  • We should ask moms this. Make sure makes it into list of q
  • Have info on confirmation to manage it in Settings would also be simpler way to handle 

• “Sign out” is confusing
• Can it be one time use only? Does code need to be persistent? 
• Emailing—parents could forget
• K: Do a simple one-time use flow—ex: connecting new TV
• Can use current flow for feedback if we want...
• Note from Mitch: Code will be needed for OTT devices sign in
• K-ask for questionnaire beforehand of how available is syncing across multiple devices. If device is lost and no info, how bad is that. 
• Research will have users use rewards program for a week before study. Groups with kids themselves, moms. Sessions with kid and mom together.

Related Images

Action Items/Next Steps:

• Wires delivery still expected to be by 7th. Need for InVision/Clickable prototype links. 
• Revisions:
  • Verbiage on some screens
  • Lighter version of code for one-time use 
  • Add latest birthday confirmation screen to profile onboarding flow
• Comps in Color if possible. If not, it’s ok.