Creating and launching a new experience for Roomba owners to map their homes, customize rooms, and clean selected spaces — designing the spatial intelligence that made Roomba i7 the first robot to truly know your home.
Overview
The Smart Mapping project was to create and launch a new experience for Roomba owners to send a robot to clean and map their homes, customize their maps, and clean selected rooms. I was a member of the core team that researched, designed, and launched the smart mapping functionality. We conducted several rounds of user research, iterated design, and led Alpha, Beta, and product launch in 2018.
Existing robots could only show a one-time clean map per job. Smart Mapping robots remember a persistent map of the user's home.
Problem to solve
Existing Roombas could not be directed to clean specific areas or rooms. Users often wanted to clean high traffic areas, but those robots could only generate a one-time coverage clean map for each job. A clean map could only show where a robot visited during a job — making clean maps not helpful or easy to orient.
Roomba i7 was the first consumer robot that could remember a persistent map of a user's home. The Smart Mapping project goal was to create an intuitive map training experience and enable users to clean selected rooms.
End-to-end journey map identifying key user touchpoints, unknowns, and risky assumptions across the mapping experience.
Process
We brainstormed the user journey based on the latest technology and identified unknowns and risky assumptions. I led UX/UI design for the entire mapping journey, but this case study selectively showcases the map customization design process.
Interviewed 8 Roomba 900 series owners in their homes to understand their mental models and pain points.
Interviewed 8 Roomba 900 series (non-smart mapping robot) owners in their homes.
Participants sketching their home layouts to reveal their spatial mental models.
Three persistent map visualizations generated from users' own clean map data.
Evaluated usability of existing one-time clean maps. We utilized users' clean map data to generate 3 different persistent map visualizations for each participant — testing which representation felt most legible and actionable.
We tested the internal engineering prototype with users to identify friction before committing to a design direction. Four critical issues surfaced:
Testing the internal engineering prototype revealed four critical usability issues before any design work began.
Step 1: Set up rooms with direct divider manipulation and spatial landmarks.
Step 2: Label rooms with a clear list and custom naming, separated from divider editing.
I created an initial prototype to test the ideal interaction model — addressing the pain points head-on before engineering constraints entered the picture.
😊 "The 3-step flow was easy to follow. The interaction of direct manipulation of the room dividers was intuitive. Participants appreciated the white clutter on the map."
⚠️ Engineering: "This is awesome! So much better!" — However, "we can't build this for MVP. The ideal interaction you want is out of scope."
The iterated design reduced interaction complexity while preserving the core UX insight: separate divider editing from room labeling.
With the ideal experience validated but out of MVP scope, I adapted the design to work within engineering constraints — preserving the key UX wins while fitting the build timeline.
Final Design
Outcomes
The work resulted in two US patents: Mapping interface for mobile robots and Map based training and interface for mobile robots.
Lessons learned