Meta · Browser / Autofill product audit
Building a shared strategy for a complex Autofill ecosystem
As our team prepared to inherit Autofill - a global product and critical revenue driver - much of its history lived as institutional knowledge.
I led a cross-functional audit that mapped core Autofill flows across five conversion-critical areas in Facebook and Instagram, then synthesized research, performance data, competitive analysis, and cross-platform gaps into a visual decision framework. The work identified five strategic opportunities and became the team’s source of truth for product prioritization.
Role, scope and partners
Senior Content Designer. Led the content strategy and cross-functional synthesis in partnership with Product Design and UXR, incorporating product, engineering, legal, privacy, and compliance requirements into a shared strategic baseline.
Goal
Give Browser an evidence-based foundation for identifying and prioritizing the highest-value Autofill opportunities as the team took ownership.
Outcome
Browser began ownership with a shared source of truth, five strategic opportunities, and 15 recommendations that shaped approximately 85% of its planned H1 priorities.
Results
Trust emerged as more than a content or messaging problem. The audit showed that confidence depended on accurate stored data, meaningful user control, clear security signals, and deliberate decisions about when to reduce friction and when to introduce it. That finding directly informed my later Autofill consent and disclosure work.
The challenge
Autofill’s history was embedded in the product - not documented as a shared system.
- Years of engineering, product, research, design, content, legal, privacy, and compliance decisions had accumulated across Facebook, Instagram, and multiple user journeys.
- Individual sources captured only part of the picture: technical implementation without product rationale, product decisions without design and content context, or language without a traceable record of the requirements that shaped it.
- As ownership moved across teams, experiences were extended or recreated without full visibility into the decisions that came before.
- Overlapping and sometimes conflicting patterns made it difficult to identify systemic problems, avoid duplicated work, or determine what the team should repair, improve, preserve, or create next.
Design thinking
An opportunity before ownership changed. As Browser prepared to take ownership, I saw the transition as an opportunity to make the product legible before the team started changing it.
More than an issue list. I did not want to produce another inventory of isolated issues. The team needed a model that connected user journeys, language and information structure, system behavior, research, performance data, competitive patterns, and technical and regulatory constraints.
Five principles from the research. UXR’s jobs-to-be-done research provided the user lens. I translated those findings into five shared design principles: usability, security and trust, user control, user value, and user support.
One yardstick for every comparison. Using the same principles to evaluate our internal flows and six competing and adjacent products would make comparisons more consistent, reduce subjective debate, and expose recurring gaps across the system.
Balancing now and later. The approach also needed to balance immediate fixes with longer-term product possibilities. I therefore organized the evidence into strategic opportunities and recommendations rather than presenting a disconnected list of findings.
What I did
-
01
Mapped the current state
Mapped core Autofill flows across five conversion-critical areas - entry points, login, lead generation, checkout, and settings and credential management - spanning Facebook and Instagram, new and returning users, and contact and payment credentials.
-
02
Built a shared evaluation framework
Organized UXR’s jobs-to-be-done research into five design principles the team could use to assess internal experiences and competing products consistently.
-
03
Evaluated content and competitive patterns
Deconstructed consent and onboarding flows across Meta and six competing and adjacent products, examining not only what they said but how they sequenced information and decisions.
-
04
Synthesized the evidence into strategy
Combined flow mapping and content analysis with research, performance data, prior experiments, competitive patterns, and technical, legal, privacy, and compliance requirements. Consolidated recurring patterns into five strategic opportunities and 15 recommendations.
-
05
Drove cross-functional prioritization
Partnered across disciplines to organize the recommendations into near-term, long-term, and blue-sky roadmap opportunities while preserving the evidence and rationale behind each decision.
The solution
A shared visual decision framework that connected Autofill’s current-state flows, five evaluation principles, supporting evidence, five strategic opportunities, and 15 recommendations in one source of truth for product prioritization.
Reflection
- Use ownership transitions as opportunities to understand a complex system before changing individual screens.
- Evaluate language, information structure, system behavior, and end-to-end journeys together - not as separate problems.
- Preserve the evidence and rationale behind decisions so teams can distinguish what to repair, improve, preserve, or create next.