I helped define the user need and jobs-to-be-done, compare product models, and shape the strategic narrative used with leadership.
I shape product strategy
Designing continuity into an in-app browser
People often left Meta’s in-app browser before they were finished exploring. Returning could mean finding the original link again, retracing their steps, or losing the context entirely. I helped define what continuity should mean for the browser and turn that need into a product model, investment case, and launched Android MVP.
Problem
Returning to something from the past and continuing something unfinished are not the same problem.
Outcome
A continuity concept became a funded, launched product.
The challenge
The browser already had ways to support previously visited content.
Tabs needed to solve a different job: preserving active browsing context so people could pick up where they left off.
The team first had to make that distinction clear enough to justify building a new product.
What I did
I turned an ambiguous return problem into a product teams could build.
Then I worked through the actual experience: naming, first-use education, entry points, core flows, edge cases, accessibility-ready content specifications, and launch adaptation.
The final language made the distinction concrete:
Open Tabs
Helped people continue browsing pages that were still open.
Link History
Helped people return to links they had visited previously.
Resolution
Tabs launched as a Facebook Android MVP after earning roadmap investment and leadership alignment around continuity as a distinct browser need.
When a later technical regression made retained tabs unreliable, I partnered with Design and Engineering to reduce feature visibility rather than continue promoting behavior the product could not consistently support.
Impact
Tabs impact
The work also established continuity as a legitimate browser problem and produced strategic and interaction models that remained useful after the interface itself disappeared.
Reflection
Good product strategy does not guarantee that a feature will survive.
It creates a clearer basis for deciding what to build, how to evaluate it, and what to carry forward when conditions change.