Microsoft AI · 2024 - 2026
Windows Recall: onboarding, the retail demo, and shipping under scrutiny
Recall is the on-device memory for Copilot+ PCs. I built its onboarding flows and its retail demo, ran guided search experiments to help people refine their searches, and tested ideas in my own user studies with interfaces I prototyped myself.
- role
- product manager
- teams
- 5+ across engineering, design, retail ops, content, partners
- worked with
- UX research, design, data science
- research
- my own user studies, AI-built prototypes
- shipped
- Insider preview Nov 2024, general availability Apr 2025
Recall on Copilot+ PCs, from the official Windows channel.
Context
Recall takes snapshots of your screen and lets you find anything you’ve seen on your PC by describing it, with all of the processing on the device. It was also one of the most closely watched features Windows has shipped. After its first announcement in 2024 drew public privacy and security concerns, Recall was reworked, previewed with Windows Insiders in November 2024, and reached general availability on Copilot+ PCs in April 2025.
A feature like that has to earn trust on the first screen a person sees, and again on the first shelf they see it on. Those were my two areas.
Onboarding
Funnel analysis showed 30% of first-time users dropping off during onboarding, which made it the biggest retention lever we had. I prototyped quickly and drove the experimentation with UX research, design and our data science partners, running 10+ experiments on the first-run flow.
One change stood out: letting people try Recall before committing to it. The try-before-you-buy onboarding raised opt-in 15% and engaged users 5%, and it shaped the onboarding redesign roadmap that followed. Along the way I also shipped search, enterprise controls and the first-run experiences themselves.

Guided search
Recall only works if people can find what they saw, so search is the product. In personal search tools like this, first-try search success usually sits around 10% to 15%, and it climbs to 50% to 60% once people refine their query and search again. Recall matched the first number, but its success after a re-search only reached about 30%. People who missed on the first try weren’t finding their way to a better query.
I ran guided search experiments to close that gap:
- Suggestions as you type. A small model suggests completions in the search bar while you’re still typing, so a vague query becomes a specific one before you hit enter.
- Dynamic filters. Filters that adapt to the results let people narrow a broad search instead of starting over.
- green jacket on a shopping site
- green jacket in an email
- green jacket last week
Research without waiting on engineering
I ran my own user studies with Recall users. To test ideas quickly, I prototyped with AI tools and built working interfaces myself, without engineering, then put those prototypes in front of participants. That let me test real interactions with users, not static mockups, before asking engineering to build anything.
The retail demo
Many people meet a new Windows feature on a store shelf before they ever use it at home, so the in-store experience is a product of its own with a very short attention span. I drove Recall’s retail launch across 5+ teams (engineering, design, retail operations, content and partners), landing on-device AI experiences on millions of in-store devices.
The demo experience reached 30M+ monthly demo interactions with a 2.5% sales conversion rate.
Responsible AI
I led the Responsible AI release for Recall. We built input, retrieval and output guardrails into the validation pipeline to block harmful use, and I created the risk taxonomies behind classifiers that reached a 98% true positive rate at 0.95 F1. Getting to launch also meant working through Responsible AI review, the EU’s Digital Markets Act and accessibility requirements, all while the product was under intense public scrutiny.
What I learned
For a privacy-sensitive feature, onboarding is where the architecture becomes something a person can actually feel. The security work had to be right, and the first-run experience had to make it understandable before anyone was asked to say yes.