Meta Fundamental AI Research

Robotics.

First & only designer on a team of scientists — I defined design's role in human–robot interaction from scratch, then invented the method to prove it.

Unpublished research · abstracted, no confidential hardware or data shown
Why it matters
First & only
designer on a team of robotics scientists — no playbook for what design does here.
Wizard of Oz
I invented a 1:1 VR study — a hidden human puppeteers the robot — so we could test robots that don't exist yet.
Cross-org
What I built became a platform other teams adopted — and earned its own booth at the FAIR '25 Conference.
How it started
First, I made a robot's mind visible.

My first assignment: showing what a robot dog was about to do, rendered in VR above its head. It shipped publicly — and did two things that shaped everything after. It proved VR could make a machine legible (the foundation for my method), and surfaced a question I couldn't shake: people badly want to know what a robot will do next.

The ambiguity
No brief. No precedent.
No idea what I was for.

Once the demo shipped, the team went back to the models and the hardware — and there was nothing defined for a designer to do next. Neither my manager nor I knew what design was even for here. A genuinely lost stretch.

Instead of waiting for a brief, I sat down and asked myself two questions:

Question 01
What value can I actually bring this team?
Question 02
As a designer — what am I most curious to know about robotics?
The reframe
Everyone studied the robot.
No one studied living with it.

The team — like most of the field — was racing on the technology: better movement, better dexterity. How people would actually communicate with and trust a robot at home was a blank — and it matters just as much. Studied early, it surfaces real problems in time to steer model training. So I turned that into a research agenda — six dimensions of the human–robot relationship the team could see, fund, and build around.

01
Human interaction
How people give a command — and know the robot understood, through speech, motion, and what it signals next.
02
Performance expectation
What people expect it to do, and how they expect it done.
03
Proactivity
When helpful initiative is welcome vs. intrusive.
04
Trust & safety
Which actions earn trust — and how height, manner and risk change whether people feel safe.
05
Real-world environment
Labs are clean; homes have kids, clutter and chaos. What actually breaks the interaction.
06
Personalization
How the relationship adapts as familiarity grows.
The method I built to answer it
A robot made of a human.

There was no robot mature enough to test, and surveys only collect opinions. So I invented one: a 1:1 immersive VR study with a Wizard-of-Oz robot. Because the user never knew a person was behind it, the operator could improvise any behavior we wanted to test that day — with no code and no hardware.

The two-room setup

The user meets a life-size robot in VR. In an identical room next door, a hidden operator stands in the very same spot — the whole study runs as one mirrored space.

How VR headset tracking maps the operator's body onto the robot

How the body maps

The headset tracks the operator's hands, head & motion, and location. Each signal drives the robot in real time — it reaches, gestures and walks exactly as the operator does.

It made the six dimensions testable, not theoretical — and demo-able enough to spread. The honest caveat: a human-driven robot moves more smoothly than a real one, so I read results as relative preferences, not absolute performance.

Proof it worked
My study changed the roadmap.

The clearest sign design's new role mattered: the team was betting on cooking as a flagship use case — until my study.

Survey said
"I want a robot that cooks."
In questionnaires, cooking ranked among the most wanted tasks. An obvious flagship on paper.
In VR
People recoiled.
Facing a robot with hot pans and knives at arm's length, users felt the danger — something no survey surfaced.
So the team
Dropped cooking from training priorities.
Because of the study, the roadmap reprioritized toward low-risk, high-trust tasks.

People also cared not just whether the robot could pick up a cup, but how it reached for one — which spun off a second study to steer training away from motions users disliked.

Abstracted · specific roadmap decisions generalized for confidentiality
Influence
From a blank slate
to a platform.

I made the study demo-able — one operator, one user, instantly legible — then took it on the road. Interest snowballed: other orgs hit the same "no hardware, need real feedback" wall, wanted in, and kept asking to collaborate.

Spread across orgs
Teams well beyond mine adopted the platform for their own robotics questions — it sold itself once they'd seen it run.
FAIR '25 booth
A dedicated booth at Meta's internal research conference — people lined up to try it, and left wanting to collaborate.
The takeaway

The robots aren't here yet — but how we'll live with them is the part worth figuring out first.

Next: AR / MR Back to all work