FamilySearch is exploring how to connect members to more records through new partnerships and access models.
I helped design and test early experiences that connect users to external record providers, including MyHeritage Matches and Storied.com Newspaper Search. These prototypes tested ideas such as third-party hinting, cross-site attachment flows, and external search handoffs—helping the organization learn what a future record access model might look like.
In parallel, I mapped the lifecycle of a record to help leadership visualize how our current features fit within this evolving problem space and where future opportunities might emerge.
As FamilySearch evolves, the organization is shifting from a record acquisition—owning and hosting data—to record access, connecting members to records wherever they live. This change is driven by increasing storage costs, global privacy laws, and the opportunity to scale access through trusted partnerships.
My work focused on designing small, testable examples that could inform this larger transition:
MyHeritage Matches – surfacing external record hints within FamilySearch.
Storied.com Newspaper Search – starting a record search on FamilySearch that continues seamlessly on a partner site.
Record Lifecycle Mapping – visualizing how current features fit into the larger record ecosystem.
These prototypes didn’t aim to solve record access entirely—they were experiments to help FamilySearch learn what trustworthy, user-centered integration could look like.
This project required designing within strategic uncertainty. FamilySearch was still defining what “record access” meant—so our work had to both function today and inform tomorrow.
We faced three major challenges:
Designing trust into cross-platform experiences – helping users understand when they were leaving FamilySearch, while still feeling guided and supported.
Ensuring a cohesive experience across brands – blending FamilySearch’s design language with external systems without confusing users.
Communicating our evolving role internally – helping leadership and teams see how small product experiments fit into the larger shift from acquisition to access.
The challenge wasn’t just to design a feature—it was to design for learning. Each prototype needed to generate insight that would guide future strategy.
The MyHeritage Matches prototype tested how third-party record hinting could feel native to FamilySearch. My goal was to maintain trust and usability while integrating external data.
We planned a small, “hunt and peck” experiment where users could discover hints for their own ancestors. This limited rollout will save development time and help us validate assumptions early.
Through testing, users strongly preferred this model because it felt personal. They adapted easily to slight data differences and loved using FamilySearch’s Source Linker to attach external records. Most notably, every participant asked when the feature would be released — a clear signal of excitement and demand.
One major design decision was not storing record indexes locally, allowing us to reduce maintenance costs and ensure the most current data. This model is now shaping how we think about future integrations.
The Storied.com Newspaper Search explored how a record search could begin on FamilySearch and continue on a partner site.
Instead of using outdated search-page templates, I designed a new, SEO-optimized landing page with the Zion UI library, balancing discoverability with a modern FamilySearch look and feel. Sharing this direction with the Search Team sparked interest in tracking engagement metrics to see if this pattern could influence other search pages.
User testing showed that design fundamentals were strong—participants easily found the page and appreciated its clarity—but trust hinged on transparency. Users wanted to know up front if they’d encounter paywalls or redirects. When expectations were clear, they described the experience as “trustworthy” and “worth exploring.”
To connect these prototypes to a broader vision, I created a visual map of the life of a historical record—from creation to temple submission. The diagram illustrated how FamilySearch, archives, and partners interact across each phase, revealing gaps and overlaps in our ecosystem.
This framework helped leadership see record access as a system, not a set of features, and continues to guide conversations about where FamilySearch can deliver the most value.
While these prototypes were not final solutions, they provided tangible insights and frameworks for FamilySearch’s ongoing evolution toward record access.
Through MyHeritage Matches, we validated user excitement and confidence in third-party hinting. The Storied.com integration launched as a live test, driving engagement and demonstrating that cross-site experiences can maintain user trust. Finally, the Record Lifecycle Map helped leadership contextualize current features within the broader ecosystem.
Together, these efforts turned abstract strategy into testable, learnable experiences—helping FamilySearch understand how to navigate the future of record access.
This project taught me how to use design as a tool for learning when the path forward isn’t yet defined. Working in a shifting strategic environment required balancing near-term usability with long-term flexibility.
Key takeaways:
Design for learning. When the future is uncertain, prototypes create clarity faster than presentations.
Clarity builds trust. Transparent labeling and consistent patterns help users feel safe across systems.
Zoom in and out. Mapping the record lifecycle helped connect UI design decisions to the larger organizational vision.
Through these early experiments, I helped FamilySearch take its first steps toward a more connected, sustainable model for record access—turning exploration into progress.