Case Study
Creating a map-first booking and wayfinding experience
From the start, Robin helped people find and book places to work in the office. So if you’ve seen a tablet mounted outside a conference room, it’s probably Robin.
Robin maps provide real-time availability of the office to answer questions like What’s going on in the office? What room is available for my next meeting? Where is my team working today?
Before maps, users booked spaces and desks from a list. Users lacked visual context to understand the location of desks, conference rooms, and their teammates. Additionally, enterprise customers have hundreds of desks and spaces – booking from a list was a nightmare.
Maps evolved throughout my time at Robin. I was fortunate to lead design by providing direction for multiple teams and personally designed the map experience, patterns, and design system below. In addition, I worked closely with a few engineers to ensure technical feasibility and performance at scale.
Design Principles
Design as a System
Design the map with the fewest parts and create a consistent experience across all platforms.
Jakob's Law
People are familiar with established mental models. Maps are part of everyday life, utilize established patterns and principles.
Adapt Context
Organize information into map layers that can be shown or hidden depending on what the user is trying to understand.