Matt Reynolds

Meta2022 — 2024

Consent Platform & Design Library

Reusable consent infrastructure across Facebook, Instagram, Messenger, WhatsApp.

Role
Staff Product Designer, Privacy

Problem

Every team at Meta that needed a consent experience built one. Different flows, different language, different disclosure logic, four apps, dozens of regions, and a regulatory deadline attached to each.

When I took ownership, implementation covered roughly half of the design specification. The platform was real, the promise was not.

My scope

  • 01Ownership of the Consent Platform, Consent Simulator, and the design system behind both.
  • 02Reconciliation of the design spec against what engineering had actually built.
  • 03Partnership with Facebook, Instagram, Messenger, and WhatsApp product teams plus legal and policy.
  • 04Documentation so the work continued without me in the room.

The decision

The decision that mattered was auditing implementation before designing anything new.

I catalogued the gap component by component, then derived 32 reusable components from validated patterns already shipping rather than inventing a fresh system. That gave product teams a familiar path onto shared infrastructure.

I defined the configuration workspace with engineering, legal, and policy partners so teams could preview a consent flow by brand, surface, language, and regulation before implementation.

What shipped

  • 01A 32-component consent library with specification and implementation in agreement.
  • 02A configuration and preview workspace for teams building consent experiences.
  • 03Downstream consent experiences live across the four apps.
  • 04Handoff documentation and a decision record for continued execution.

Result

6 wks → 4 days
typical time to stand up a compliant flow
32
components covering ~90% of new consent requests
4
apps on shared consent infrastructure
100%
spec-to-implementation parity at handoff, from ~50%

Internal platform metrics; specifics generalized for public description.