Aug – Dec 2025 · PM & UX Designer (academic project)
Retaining older adults with early dementia as Windows customers
Product ManagementStrategyAccessibility
What I'm proud of
I scope by saying no: pick the few problems worth solving, and plan what it takes to solve them.
- Context
When computers get hard to use, older adults quit Windows for iPads, Chromebooks, and GrandPads.
- Insight
Needing help made them feel dependent. They wanted to keep doing things themselves, for as long as they could.
- Result
A focused MVP, a roadmap for the next six quarters, and a resource plan for Microsoft.
What we delivered
A simpler mode inside the Windows computers people already own.

Cognitive Accessibility Mode
A switch in Settings that turns the Start menu into a simpler version of itself, with fewer options and larger targets.

A PRD built around one objective
Reduce the effort it takes to find and open things. Sign-in moved to the roadmap.

A roadmap and resource plan
Six quarters, with the teams, testing access, and OS rollout it would take.
How I got there
Families were writing their own Windows manuals.
On Reddit, one family described printing step-by-step flashcards in huge bold type, laminating them, and hanging them on a ring beside a parent's desk (u/allquixotic, r/dementia). Others taped notes to the monitor. These workarounds showed Windows was losing older adults with early signs of dementia. Our goal: help these users keep using their own computer, independently, for as long as they can.

Most families were switching to an iPad, a GrandPad, or a Chromebook.
Across Reddit threads, most care partners recommended moving a family member to an iPad, a GrandPad, or a Chromebook because they were simpler. We saw the same in person: in a dementia-friendly community group, Chromebooks were the common choice. For Windows, this was a pressing retention problem, not an edge case.
Every simple option on the market worked by taking things away.
Our competitive analysis mapped the market as a spectrum. Purpose-built devices like GrandPad and Komp are simple because they strip the computer away. Voice assistants help, but can't do real work. Tablets and laptops keep everything, even with their accessibility settings (Apple iPad and Chromebook accessibility features), but assume the user is fluent. No one offered a full computer that becomes simple on demand.

Our first ideas added more help. Time in a dementia-friendly community changed that.
Early exploration went toward help: voice agents inside Windows, a chatbot that spanned the whole OS, and a simpler tile-based navigation with fewer options (yes, a little like Windows 8). Then we spent time in a dementia-friendly community, and the way people talked about support changed our thinking. Dementia isn't a phase where someone needs help for a while. It's a lifelong change, and people want to keep working and living a normal life. Some days are better than others, so the same person may welcome help one day and be frustrated by it the next. In one session, someone said they had stopped visiting a friend who no longer recognized them, because they couldn't help. The facilitator's answer: your presence still means a lot. One couple put it plainly. A former engineer living with dementia wanted his life to stay as it was. His wife said she sometimes watches him struggle until he asks for help, because stepping in too soon makes the frustration, and the sadness about what he's lost, worse. That became our design principle: let users try on their own, and support them without taking over.
Research showed us many problems, so I had to pick a few.
Discovery combined Reddit threads (r/dementia, r/dementiaresearch), subject-matter experts, a care-partner interview, a community co-design group, and a documentary about a companion robot (Remembering the Future with IRIS).
What we heard
Too many choices overwhelm, and app and file names are hard to recall
Users fear breaking the computer with one wrong click
Key decision
I said no to the most painful problem: logging in.
Forgotten passwords hurt the most, but users already had a workaround (a written note), and a real fix needs deep security work. Starting work, getting to the first app or file for the task at hand, had no workaround, and it happens every session. So I scoped the MVP to search and navigation, written as an OKR: reduce the cognitive effort it takes to find and open things, measured by misclicks and time to decision. The team pushed back: sign-in felt like the first barrier. My answer lived in the numbers. Sign-in happens once a session, a sticky note already solves it, and a computer doesn't strictly need a password. The Start menu opens again and again. The numbers convinced them.
Every idea had to pass these questions
Is it core to our objective and key results?
Is it a deal-breaker for our users if we skip it?
Does it hurt the experience for existing users?
Can we reuse data or patterns Microsoft already has?


Key decision
We built a simpler mode into the Windows people already own.
Cognitive Accessibility Mode is a toggle in Settings. It turns the Start menu into a simpler version of itself, with larger targets and previews of recent work. It runs on existing hardware, not only new devices. In testing it cut on-screen options by 30%, and two of the three participants said they'd use it. We also framed cognitive accessibility beyond dementia: the same mode helps people with learning disabilities, or anyone working under stress, like a parent juggling kids. So it scales well past the group we started with.

Key decision
We laid out the teams and resources it would take.
An OS-level change touches many teams, so the proposal spelled out the people, partner teams, and rollout it would need. Microsoft's PM and engineering judges ranked it #1 for three reasons: deep primary research with experts and care partners, treating care partners as a secondary user group, and realistic resource planning across teams.
What it would take
A dedicated team: designers, developers, accessibility experts, and PMs with Windows experience
Buy-in and hours from the Edge, Office, and Windows OS teams
Ongoing access to older adults with dementia for testing at scale
An OS-level update, which means a slower, careful rollout
The roadmap starts on the device and ends with help from family.
Six quarters, from early 2026 to mid 2027, each feature moving through research, build, beta, and release.
Now: simplified navigation
The MVP, customized on the device itself.
Next: voice control and more ways to interact
Some forms of dementia also affect movement and fine motor control, so a mouse alone isn't enough.
Later: remote setup and help
Family can guide a user from their own device.
Later: a simpler sign-in
Finally taking on passwords.
Exploring: a lower-cost Windows laptop
Built around this mode.

What I'm proud of
I scope by saying no: pick the few problems worth solving, and plan what it takes to solve them.
Research surfaced many problems, and forgotten passwords hurt the most. I scoped the MVP to the Start menu instead, because people open it many times a session but sign in only once, and wrote it as an OKR measured by misclicks and decision time. Then I laid out the teams and resources the change would take. Microsoft's PM and engineering judges ranked the proposal #1, in part for realistic resource planning across teams.
If I had another chance, I'd lead with data.
Convincing the team that passwords weren't the right target took more than one round. As a PM now, I'd open with the numbers: how many people actually complain about passwords, how often sign-in happens per session compared with opening the Start menu. Lead the discussion with data, then make the decision.
Read more about how we designed the interactions for this menu
Case study