UX RESEARCH · ETHNOGRAPHY STUDY

Voice AI research for older adults navigating the world

An ethnographic diary study for Woven by Toyota.

ROLE
Research and strategy lead
TEAM
3 researchers
TIMELINE
3 months
OUTPUT
Guidelines for Voice AI use
Woven x Pratt diary tool on a phone

THE PROBLEM

How do we design experiences and environments for the "silver tsunami" headed our way?

~38%

of Japan projected to be 65 or older by 2050, up from about 29% today

UN World Population Prospects · Japan IPSS
19% → 33%

NYC's Senior Pedestrian Zones hold 19% of the city's seniors but account for 33% of senior pedestrian injuries

NYC DOT, Safe Streets for Seniors

Woven by Toyota is building a city designed around how people will actually live in it, and aging sits at the center of that in a country further into the shift than anywhere on earth. We studied it from New York because the same wave is moving through here, in a city already answering with talking crosswalks and AI companions in living rooms.

AN OPPORTUNITY WITHIN THE TOOLS

Three research directions explored: infrastructure and design, assistive technology, and policy and government
Three directions we scoped, each with its own literature, gaps, and How Might We. Assistive technology, in the middle, is the one we took forward.

A way to be there when it happened.

What Woven needed was how older adults actually navigate, not how they say they do, and that gap is where most research on this population fails. We had no budget, no clinical access, and no way to shadow anyone through a week of errands.

Voice AI closed that: participants could talk through a trip as it happened, and we would be there for it without being in the room.

THE DRIVING QUESTION

How can voice AI help older adults get where they are going without taking the decisions away from them?

THE SOLUTION

CUSTOM GPT DIARY TOOL

We built a CustomGPT that participants could talk to while planning a trip, mid-errand, or right after. It played three roles at once.

  • Study device that helped them get somewhere
  • A facilitator that asked reflection questions without feeling like a survey
  • Research assistant that structured every conversation into data

Nobody filled out a form, they just had a conversation.

They spoke to it through ChatGPT’s voice mode.
1. It starts like a notebook, you talk through what you’re planning.
2. Ask about a place and it gives you what you actually need to get there.
3. A few short questions at the end to reflect on the trip.
4. Submit the entry, or delete it if you’d rather not.
Sheet of entries gets filled after each submission and we analyze it.

THE PIPELINE

The pipeline of how it works.

Study device role definition for the CustomGPT

Study device.

Supports errands conversationally, generates map links on request, and clarifies anchors before suggesting places.

Prompt facilitator role definition for the CustomGPT

Prompt facilitator.

Shifts naturally from planning into reflection questions, then exits cleanly on “Submit entry.”

Research assistant role definition for the CustomGPT

Research assistant.

Keeps a hidden scratchpad with metadata, seven reflection ratings, and seven interpretive notes for every entry.

The Zapier webhook that caught each structured export
The webhook that carried each entry into the sheet.

Backend logic.

Every entry became a clean record, automatically. At submission a Zapier webhook caught the structured export and wrote it to the master sheet. The participant never left the conversation, and nothing got lost.

PARTICIPANTS & INITIAL FINDINGS

The participants we recruited

We recruited across four age groups rather than only 65+ to have a complete picture, bringing in people in their forties and twenties that are next in line.

Comfort with the voice assistants ranged from daily use to no experience.

Six participants plotted by age and comfort with technology
Six participants, plotted by age against comfort with technology
Navigation is the last step

People spend weeks planning an activity, not a destination. The route came last, so leading with “where to?” is already a step behind.

Autonomy is non-negotiable

Discovery could be delegated, but the decisions could not. Trust dropped the moment the assistant made decisions for someone.

Let me just try it first, okay, and then you can correct me.
Navigation is a social orchestration

Most trips were planned around a group, where the destination was secondary to who would be there.

Trust seemed to run in reverse

Older adults trusted the tool first with their information, while younger ones verified before they opened up. (In my head it was the other way around.)

Landmarks beat using coordinates

Street names and distances caused friction every time.

When you said Ohio Street, I was just like, what? I don’t know where that is.
Brevity is a safety requirement

Over-explaining to someone while they are mid-crossing causes more information overload and it becomes unhelpful.

I think you were just rambling. I would have liked a quick response.

WHAT WE HANDED OVER

Foundational pillars and guidelines for voice AI design

We gave the Woven team a set of three pillars and ten guidelines to have for future voice AI solutions. These are based on the quotes, patterns and solutions of participants during the study.

All ten belong to Woven and stay with them, so the three pillars they hang on are as far as this page goes.

Autonomy
The AI assists. The human leads.
Trust
Earned through accuracy and silence, lost with one wrong answer.
Personalization
It speaks your language, knows your landmarks, and feels temporarily yours.

THE HAND-OFF

The hand-off to the Woven team.

We presented the study, the tool, and the guidelines to the Woven team in Tokyo, who left us with their read on where this could go next.

“The guys took on an interesting challenge with AI in the intersection of UX research and showed us how feasible it can be for our company to try it out.”

UX Researcher at Woven by Toyota

“The findings really help us see we can prepare better and scale our practice here.”

UX Researcher at Woven by Toyota

MY ROLE WITHIN THE TEAM

Prioritization matrix, synthesis framework, and the participant onboarding document
The pieces I owned: the prioritisation matrix, the synthesis framework, and the onboarding document participants started from.

From the city's paperwork to AI voice guidelines.

I ran the desk research to see what New York was already setting in motion through its plans and regulations, and that is where voice came from as our focus. Once we knew that, I shaped how the tool should feel to talk to and what it should give back when someone asked for help.

I also wrote the onboarding for people using it on their own phones and walked two participants through their first entry before they kept going solo.

When the entries came in I owned the pillars and guidelines, clustering quotes against findings so every rule traced back to something a participant actually said.

THINGS THAT DIDN'T WORK OUT ¯\(ツ)/¯

Concept of the street pillar
The street pillar we nearly built, animated in Midjourney from our sketches.

We had ideas that kept shifting as the project went on.

For a while we were designing a physical object, a pillar on the street that connected you to the city like an old phone booth reimagined. The research pointed elsewhere, so we landed on guidelines that could take any shape, and spent the rest of the study patching the CustomGPT every time ChatGPT broke it.

WHAT I LEARNED FROM THIS EXPERIENCE

Guidelines and new tools in a time of AI uncertainty is appreciated.

I went in assuming behavior would sort by age and it did not. Older participants trusted the tool first while younger ones verified before opening up, the opposite of what I expected, and that inversion shaped the trust pillar more than anything else.

I also had to accept that research can be the deliverable, and that guidelines which travel were worth more to the Woven team than one solution they could not reuse.

¡Gracias!

Thank you for stopping by!

If you want to explore any part of this further, let me know.

Special thanks to my team, Merlyn and Conor, for building the backend logic of the pipeline through many conversations and rounds of iteration.

IN ORBIT

¿HABLAMOS?

Let's make contact

Have a project or a role in mind?
I'd love to hear about it.