Accounts center

Project: Build a new contact-point management experience

I worked across teams and functions to develop a new experience in Meta’s Accounts Center to help users manage their contact points on Meta’s family of apps. This required deep product knowledge, an understanding of backend complications, and the ability to clearly explain to our legal and privacy partners any functional complications and how they impacted user-facing language.

Goals

For the company, the goal was to create a central hub for people to safely and seamlessly control all account-level settings across one or multiple Meta accounts and profiles, simplifying how people manage their accounts and associated settings while removing redundancy across apps.

For the team, our goal was to create a flow within Accounts Center that allows users to manage their contact points across their hard-linked accounts with clarity and ease — without introducing additional legal or privacy risks.

Major blockers

  • Differences in app logic impacted contact point states
  • Visibility options were owned by an outside team
  • Needed new labeling system for statuses requiring action vs. informational states
  • Negotiations with IG and Security teams were required to bring parity across experiences
  • SCPs were being simultaneously migrated
  • Status inconsistencies broke the Accounts Center mental model
  • Some functionality solutions fell outside project scope
  • Needed to account for future scalability (more Meta apps, more user profiles)

Examples of Contact Point States

  • Visibility
  • Reachability
    • Pending
    • Shared
    • Recycled
  • Security contact points
  • Last contact point

Examples of User Actions

  • Adding a contact point
  • Deleting a contact point
  • Replacing a contact point
  • Adding an existing contact point to an existing account

UX Solutions

  • Deletion variations depending on contact point state
  • Elimination of dead-end actions
  • Easier ways to remove unwanted contact points
  • Scalable behavior for overlapping account states
  • Interim solutions for reachability goals
  • AC-specific disclosures for initial launch (pre-CAA)
  • Additional risk mitigation for highly scrutinized flows
  • Clearer surfaced information about contact point and SCP states
  • Fail-safe solutions for edge cases
  • Dynamic messaging
  • Consistency across the broader Accounts Center experience

Adding a contact point (progressive disclosure):

Adding an existing contact point to another account:

Incorporating visibility settings:

Deleting a contact point:

Replacing a contact point:

Indicating state that requires action:

Indicating contact point states, like those used for only security purposes:

Final disclosure copy:

Disclosure approval process (using Figma):

Team feedback: