Hi, I’m Jean
8+ years experience • San Francisco Bay AreaSF Bay Area
Senior product designer working across strategy and pixel-level craft. Previously at Meta, LegalZoom, and Evernote.





What it's like to work together?
As a XFN partner

As a Design peer

As a human

I started my career as a visual designer at an agency before moving into in-house product design, where I've focused on building consumer products at different scales, from 0→1 products to experiences used by millions of people. I'm most motivated when I hear from users that something I helped create is genuinely meaningful to them.
I find inspiration beyond the screen, too. I travel, cook, make coffee, and love exploring all the beautiful things happening in the world around me.
Designed and shipped core messaging experiences for 3B+ users worldwide
Streamlined creation journeys and resolved key drop-off points, driving a +X% boost in completion success rate at global scale.
Scaled cohesive design improvements across all key focus areas, driving measurable daily active engagement at global scale.
Uncovered re-engagement opportunities for unnotified chats, helping more users enable notifications and stay connected to key conversations.
*Data and specific metric values have been sanitized or relative-indexed for NDA compliance.
No team had systematically owned the notification experience as a whole, and we didn’t yet know what problem was worth solving. I led design and rapid experimentation to explore the ecosystem, uncover user needs, and work with cross-functional partners to define where we should focus and shape product direction.
Evolved WhatsApp’s core messaging experience, where even small changes can have broad impact. Focused on making it easier for people to start and continue conversations, while creating patterns that could scale beyond individual features and be applied across the broader product, such as link previews, composer and @mentions.
Led design across group creation and forwarding journeys, auditing the end-to-end experience to uncover friction and opportunities across key entry points. Partnered with cross-functional teams to test solutions through A/B testing, driving measurable improvements in product metrics.








I shaped product strategy and design from opportunity to launch, partnering closely with cross-functional teams to turn complex problems into thoughtful experiences.
Identified gaps and opportunities within my product area through product audits, research synthesis, and cross-functional insights, translating findings into initiatives that supported product and business goals.
Integrated AI into my design workflow to synthesize past research, rapidly prototype functional experiences, and test concepts in high-fidelity sandboxes, helping me explore more ideas and learn faster.
Partnered with PM, Engineering, Research, and Data Science to move ideas forward, leading workshops and working sessions to generate ideas, align teams, and drive decisions.
Considered how experiences fit into broader product ecosystems, building patterns that extend across surfaces and use cases. Stayed involved through implementation, testing, and bug bashes to ensure a high bar for craft and quality.
Designing a connected support experience for customers and tax experts.
I joined the team when LegalZoom decided to build its own messaging tool from the ground up. As the sole designer, I led the end-to-end design of the new experience, from concept and research through testing and launch.
My role was to figure out how messaging could integrate into existing customer and expert workflows, while establishing a scalable foundation that could eventually extend across other LegalZoom services.
Improved customer satisfaction with the tax expert experience.
Reduced average response time from 2 days to 0.5 days through a more efficient workflow.
The messaging and collaboration patterns became reusable components in the global design library and were later incorporated into other legal workflows.
LZ Tax is an online service that helps small business owners file their taxes with expert guidance throughout the process. Tax experts support customers along the way, from answering questions to reviewing their returns before filing.
Previously, customers and tax experts relied on email to communicate. Customers couldn't directly reach the expert working on their case, they had to email a general support address, while replies came from a no-reply email.
This fragmented experience made it difficult to maintain context and continuity, often leaving customers feeling like they had to repeat themselves to get personalized support.
To provide a better support experience for customers, I needed to improve more than the customer experience. The service also depended on how tax experts and Operations worked behind the scenes. I started by researching and mapping how communication flowed across all three groups customers, tax experts, and Operations and understanding the needs of each.
Operations needed a way to automatically route customer questions. Case-related questions could go directly to the expert already working on the case, while general questions could be assigned based on expert availability.
Customers wanted to know they were connected with an expert who understood their case. Keeping the conversation connected to the case meant they could receive more continuous, personalized support without repeatedly explaining their situation.
Experts often had to move between different tools to find case information and communicate with customers. We wanted to bring the relevant context and communication together so experts could respond more efficiently.
A unified messaging experience integrated into both the customer and expert portals, creating a consistent, seamless way for customers and their tax experts to communicate throughout the filing process.
Automatically route case-related questions to the expert already working on the case, while general questions can be assigned based on expert availability.
Connect customers with an expert who already understands their case, creating a more continuous and personalized support experience.
Bring customer conversations directly into the case workflow, giving experts the context they need to respond without switching between tools.
Reducing friction in task management by letting users set due dates as they type.

As the sole designer, I led the end-to-end design of the natural language due-date experience, from the core interaction to the monetization flow, in partnership with Product and Engineering across concept, research, and usability testing.
When it comes to task management, the ability to set a due date is essential. Users rely on due dates to plan their day and get reminders to complete tasks, making it the most-used feature in Evernote Tasks.
Due dates were also closely tied to product engagement. Our data showed that users who set more due dates tended to be more active in Evernote, while reminders gave users a reason to return and stay engaged.
Given the importance of due dates, we introduced advanced due date capabilities as a paid feature, creating more value for subscribers while turning a high-intent workflow into an opportunity to convert free users to paid plans.
Since due dates are such an important part of task management, even small amounts of friction can make the experience feel cumbersome.
In fact, one of the top reasons users stopped using Evernote Tasks was that setting a due date took too many clicks.
Users wanted to capture tasks as quickly as possible. While the existing flow took five clicks or fewer, it still felt like too much effort for a simple action.
Explored different visual treatments and interaction patterns, using user testing to validate and refine the final direction.


Users can simply type a date into the task title using their keyboard, without interrupting their flow.
Smart Due Date was accessible from both the note and task modal, creating a consistent experience across mobile and desktop.
The system recognized 35+ common ways of writing dates, allowing users to express due dates naturally without learning a specific format.




Natural language due dates were introduced as a paid feature, creating additional subscription value and a new monetization opportunity. I designed the paywall to appear when free users intentionally typed a due date, targeting users most likely to see value without interrupting those who didn't need the feature.
Reduced user clicks, improving overall task completion time.
Laid the foundation for adding more natural language processing features.
Bringing LegalZoom’s financial tools to life in a native app.
LZ Books is a financial management tool for small business owners, helping them manage everyday finances, from transactions and deductions to invoices.
At the time, LZ Books was web-only, while users were increasingly accessing it from their phones. As LegalZoom’s first designer dedicated to native app experiences, I led LZ Books from concept to launch, partnering with Product and Engineering and establishing the foundation for future native experiences.
34% of existing web users adopted the app within ~2 months of launch, actively using it to manage their finances.
Research showed users relied on the web for deeper financial tasks, but everyday actions like checking transactions or sending invoices were harder on the go.
With 25% of users already accessing LZ Books through mobile web, there was an opportunity to make these tasks faster and more accessible through a native app.
With a limited timeline, we couldn't bring the entire web product to mobile. We had to decide which workflows were most valuable to SMB owners on the go.
Existing web workflows were built for larger screens and different interaction patterns. They couldn't simply be scaled down for a native experience.
As the first native app, we needed to establish more than an MVP. The product needed a foundation that could support new workflows and future growth.
I rethought key workflows around mobile behaviors and native capabilities. The invoice creation flow is one example of how that approach came to life.
When creating an invoice, SMB owners wanted to know exactly what their client would receive. So they could edit directly on the invoice itself, the editing and final views shared the same visual structure.


1. Information hierarchy broke. On desktop, both users saw the whole invoice at once, so priority mattered less. On mobile, it became a long scroll, and the two jobs had different priorities: clients want the total due first; creators want to add services and details first. One hierarchy couldn’t serve both.
2. Inline editing didn’t scale down. Desktop used inline dropdowns to edit directly on the invoice. On a narrow screen, those interactions became cumbersome to navigate.
I kept the core user need “what you see is what you get” while breaking the web experience into two focused views.
Invoice edit view
A focused editing experience that lets SMB owners add services and invoice details in a natural sequence, without the long scroll and inline editing of the web experience.
Preview
A one tap preview that shows creators exactly what their client will see, preserving the “what you see is what you get” principle without making the preview itself the editing surface.
I also replaced web-specific interactions with mobile-native patterns, making common actions easier to navigate and reducing unnecessary scrolling.


Going native also gave us opportunities that weren’t possible in the web experience.
Instead of limiting invoice sharing to email, the native app could leverage the device’s sharing capabilities to give creators more ways to send an invoice.
And after an invoice was paid, real-time notifications brought the most important moment back to the creator, without requiring them to log into the platform and check.


I focused the MVP on the workflows that mattered most for managing finances on the go: home, invoice creation, transactions, mileage tracking, and onboarding.




Because LZ Books was LegalZoom’s first native app experience, I was starting from scratch. I built the design system from the ground up, from core components and patterns to documentation and team education, creating a shared foundation that made future features faster to design, build, and scale.
Connecting with people beyond saved contacts
I led end-to-end design, from auditing existing people search experiences and identifying cross-workflow gaps to designing the solution across four workflows. Because people search is a shared surface across WhatsApp, I collaborated with multiple feature teams to align on search patterns and result priorities, while partnering with PM and Engineering to drive the project from concept to launch.
WhatsApp was traditionally used to stay connected with close friends and family. But over time, it has also become a hub for real-world communities, from school parent groups to HOA chats. These communities can include dozens of people who know each other in real life but haven’t necessarily saved each other’s numbers.
As these communities grew, people increasingly wanted to create smaller groups with specific members to discuss topics without disrupting the larger conversation.
When users tried to create a smaller group with people from an existing community, they couldn’t find those people in the people picker unless they had saved them as contacts first.
Even though these people already shared a group and knew each other in real life, WhatsApp treated them as strangers simply because they weren’t saved contacts.
This added an unnecessary step to starting conversations with people users already knew, creating friction in one of WhatsApp’s core engagement behaviors.
From users
“I just wanted to set up a playdate group with a few parents from our school chat, but since we weren’t WhatsApp contacts, I had to save each person’s number before I could even get started…”
Looking beyond group creation, I found the same barrier across other core workflows. A user might want to forward a kids’ event to a parent from their child’s school group, but because that parent wasn’t a saved contact, they wouldn’t appear, even in a shared group.
Digging further, I found that each workflow also handled non-contacts differently: someone you’d chatted with one-on-one might surface in Forward or Share but not New Chat or Group Creation, and people from shared groups surfaced nowhere. Who you could find depended on which workflow you were in. WhatsApp had no consistent way to surface people users already knew through the app.
| Non contact type | Group creation | Forward | Share | New chat |
|---|---|---|---|---|
| People in shared groups | ❌ | ❌ | ❌ | ❌ |
| People with previous 1:1 chats | ❌ | ✅ | ✅ | ❌ |
Anyone users already have a relationship with on WhatsApp, whether through shared groups or previous conversations, should be discoverable across all four workflows. I made these relationship types consistently searchable, filling gaps in existing discovery.
| Non contact type | Group creation | Forward | Share | New chat |
|---|---|---|---|---|
![]() |
Newly available | Newly available | Newly available | Newly available |
![]() |
Newly available | Existing results | Existing results | Newly available |
Surfacing people users already know cuts the steps to start a chat, turning a dead end into one tap, and removing a barrier to a core engagement behavior.
The same types of people became discoverable across all four workflows, but their result groupings varied by workflow. Each workflow retained its data-backed result ordering and priorities, so expanding discovery wouldn’t compromise existing search relevance.
One of the biggest questions from stakeholders was how newly surfaced people would work alongside existing search results, each with different groupings and priorities.
To make these interactions easier to evaluate, I built an interactive, AI-powered prototype covering a range of user scenarios, including edge cases. Stakeholders could switch between scenarios, try different searches, and see firsthand how new results interacted with existing ones. This made the trade-offs tangible and helped stakeholders align on the approach before moving into implementation.
Now, a parent from the school group appears as soon as you search. No saving numbers, no dead end. Setting up a playdate group takes a tap instead of a chore.
By removing the need to save someone as a contact first, the feature made it easier to connect with people from real-world communities, relationships users already have but rarely save in their contacts. This supported WhatsApp’s goal of strengthening real-world connections and contributed to a lift in MAU, showing the engagement value of reducing friction in connecting with people users already know.