First-time �user flow
Sign-in flow content review
David Shuey | Jan 2025
MMDDYY
CONFIDENTIAL & PROPRIETARY
User flow content review
High-level summary of this flow
User problem:
Users need to sign in (not log in) to their machines, and are asked to provide their username (email) for Single Sign On.
They may feel confused by technical terms or jargon that may inhibit them from going forward, or putting in the right information to sign in correctly.
If they don’t have a “google.com” email, they may wonder what they need to do, as well.
To alleviate frustration or concerns (such as being locked out, or going through a longer flow), user wants to confidently sign in to their corp Workspace.��Key problems we’re trying to solve in this flow:
Simplifying all language to extend to all users in the Google space, eliminating jargon or technical terms.
e.g Establish if the language of “CorpSSO” accurately communicates the process of Google Single Sign On.
Key questions:
Can SSO be used instead of CorpSSO?
When can Corp be used? (And lowercase, too.)
What can replace “security code” for all-encompassing term for all codes?
�Status:
Visual completed, but working through UI
2
MMDDYY
CONFIDENTIAL & PROPRIETARY
Step 1: First time users - Login w/ security key (Username)
Purpose of screen: User logging in with username, password, and security key as new device sign in or 7-day sign in interval.
Next step for user: Input username & then click “Next.”
Key terms: CorpSSO, SSO, Use security code
Content approach: Simplify terms so user doesn’t get confused by jargon (e.g. “CorpSSO”). Make as clear as possible so user can know they can advance with security key.
Also, security code is one pathway, but there are rescue codes and security key rescue codes. Needs another term.
Link/screenshot to “before” version of this screen:�Figma UXW: Security Key - First Time Users
Step 1: Recommendation
Change: Cut “Core” before SSO in body copy. Also just have “Enter your username” in eyebrow text, removing “SSO”.
Also, instead of using “one-time password (OTP)” to cover all use cases that replace SK, go with “Use passcode instead” to show this is alternative.
Reason: SSO is defined as follows, which is the action taking place: “Generic term for single sign on. Both accounts.google.com and login.corp.google.com are SSO services.”
Also, “passcode” replaces “security code” and “One time password” as a catch-all term.
Update: “Use passcode/security code” eliminated from screen
Link/screenshot to “after” version of this screen:�Figma: Security Key - First Time Users
Step 2: First time users - Login w/ security key (Password)
Purpose of screen: User logging in with username, password, and security key as new device sign in or 7-day sign in interval.
Next step for user: Input password & then click “Next.”
Key terms: CorpSSO, SSO
Content approach: Minimal language to help user add password
Link/screenshot to “before” version of this screen:�Figma UXW: Security Key - First Time Users
Step 2: Recommendation
Change: See previous (No change)
Link/screenshot to “after” version of this screen:�Figma: Security Key - First Time Users
Step 3: First time users - Login w/ security key (touch security key)
Purpose of screen: User logging in with username, password, and security key as new device sign in or 7-day sign in interval.
Next step for user: Touch security key
Key terms: Security key, security code
Content approach: Allow option for security code if problems with security key.
Link/screenshot to “before” version of this screen:�Figma UXW: Security Key - First Time Users
Step 3: Recommendation
Change: “Use passcode” (no need for “instead”)
Update: “Use security code” is still appropriate, and changed back. Passcode may be used to be all-encompassing term for Security codes, Rescue codes, and passwords.
Link/screenshot to “after” version of this screen:�Figma: Security Key - First Time Users
Step 4: First time users - Login w/ security key (success landing page)
Purpose of screen: User has logged into Single Sign On and is ready to move to Workspace – e.g. Gmail, or other work area.
Next step for user: Continue to Workspace
Key terms: Corp Workspace, Continue to Workspace
Content approach: Simplify all content, and excessive words on CTA.
Link/screenshot to “before” version of this screen:�Figma UXW: Security Key - First Time Users
Step 4: Recommendation
Change: Only have “Continue” in CTA, as “corp Workspace” (lowercase “corp”) remains in body copy, to distinguish this has a corporate Workspace account.
Link/screenshot to “after” version of this screen:�Figma: Security Key - First Time Users
Step 4: Recommendation
Gemeni Suggestion: Corp Workspace is acceptable term in Google space.
Also validated on MOMA at Google.��Link/screenshot to “after” version of this screen:�Figma: Security Key - First Time Users