Skip to content
Paul Sherman

Ethnographic Research for an In-Car Navigation Product

Generative field ethnography to identify personas and unmet needs for a next-generation navigation experience.

16
Field observations
2
Target personas
6
Behavioral motivators identified

The Problem

Telenav was developing an early version of what would eventually become its in-car navigation platform, a product that today ships as Vivid Nav, a cloud-connected, personalized navigation experience integrated into vehicles. When I engaged with product team, the product was pre-release. The team had a general sense of who they were building for: two target customer segments they called "Settle-Down Trendsetters" and "Young Venturers." But they had no field data about how those people actually behaved when they traveled. They didn't know what drove their decisions about routes, errands, and destinations. They didn't know what frustrated them. They didn't know what unmet needs existed in the gaps between what navigation tools offered and what real life demanded.

This is the stage where most product teams rely on surveys, focus groups, or competitive analysis. Telenav wanted something different: direct observation of real people, in real cars, making real decisions under real conditions. The goal was not to evaluate a prototype or test a feature. It was to build a foundational understanding of the target users' behavior and attitudes around driving, navigation, and wayfinding, and to bring that understanding to the product team early enough to shape design direction before commitments were made.

How We Worked

The study observed 16 individuals across two metropolitan areas, balanced for gender and split evenly between the two target personas. Participants were recruited through third-party recruiters and screened against Telenav's persona criteria. Geographic diversity was deliberate: two distinct metro areas gave us variation in driving culture, road infrastructure, and urban layout.

Each participant was observed in two sessions: a daily work commute and an errands trip. The protocol was primarily unobtrusive "fly on the wall" observation. I rode along as participants drove their normal routes, ran their typical errands, and made their real-world decisions. The goal was to minimize the observer's influence on the participant's behavior and let the natural rhythms of their travel emerge.

This required flexibility. Some participants narrated their thinking throughout the session, essentially running a concurrent think-aloud without being asked. Others were comfortable with long stretches of silence. I followed each participant's lead on how much conversation occurred, because forcing a structured interview protocol on someone who is navigating rush-hour traffic on the Kennedy Expressway defeats the purpose of observing natural behavior.

Interview questions were integrated throughout the observations rather than conducted as separate sessions. When a participant made a routing decision, I asked about it. When they expressed frustration, I probed. When they described a workaround they'd developed, I explored its history. I focused questions on behavior I was directly observing, because that produces the most concrete and realistic information. But I also asked about behaviors I couldn't observe, particularly pre-trip preparation, which turned out to be nearly invisible because participants completed their preparations before I arrived, despite my requests to be present earlier. I recorded audio and video during travel.

What We Found

Two Personas, One Shared Puzzle

The two target personas turned out to have distinct lifestyle orientations but overlapping behavioral patterns when it came to travel:

Settle-Down Trendsetters had shifted their attention from friends to family. They were mid-career professionals: a value-conscious technology enthusiast in Chicago who tracked prices at multiple stores and wondered whether his next phone needed to be a smartphone. A working mother balancing convenience against the pressure to get everything done. A Dallas planner who scheduled her time to the minute and had installed a car kit for her phone so she could be productive during her commute. A father who'd deliberately chosen a short commute and a small community with upscale amenities.

Young Venturers were more socially oriented and tech-reliant. A Chicago teacher who inhabited multiple distinct neighborhoods — he called them "pods" — and used Yelp and Groupon to optimize his choices within each one. A relaxed Chicagoan happy to stay in her comfort zone, who checked her phone within moments of waking. A Dallas woman in transition — engaged, new house, looking forward to her next phase of life — who enjoyed the hunt of finding just the right thing. A Dallas man new to smartphones who had only recently discovered mobile maps and navigation.

What unified them was that every single participant treated travel as a puzzle to be optimized. The commute to work was something to be solved through experimentation with routes and timing. The errands trip was something to be organized around primary goals with secondary stops folded in along the way. Even the most laid-back participants had developed personal heuristics for route selection, store choice, and trip sequencing.

Six Behavioral Motivators

Rather than describing the personas purely by demographics or lifestyle, the research surfaced six underlying motivators that explained why participants made the decisions they observed. These motivators cut across both persona groups and both genders. What made them useful was that each individual exhibited a unique combination — the motivators described the person, not the group.

Value. Participants motivated by value were highly price-conscious and willing to rearrange their behavior to maximize it. One participant completely restructured his errands trip to get plywood cut for free at Lowe's rather than paying at a closer store. Value-motivated individuals weren't necessarily looking for the cheapest option — they were looking for the best return on what they spent.

Efficiency. Those motivated by efficiency were optimizers. They planned, strategized, and took pride in squeezing every task into the available time. Efficient use of time was a point of personal pride. These individuals often showed strong overlap with value motivation, but the currency was time rather than money.

Ease. Participants motivated by ease wanted to get things done as simply as possible. They made choices — which route, which store, which meal — based on what minimized effort. One participant chose precooked grocery store food for dinner not because it was cheap or healthy, but because her husband and daughter would both eat it, and that was good enough.

Mastery. Those motivated by mastery enjoyed the process of figuring out the best way to do something. One participant turned his commute into a game, testing different highway exits at slightly different times and developing hypotheses about which combinations worked best. The end result mattered, but the puzzle-solving process was intrinsically rewarding.

Pleasure/Treasure. Participants motivated by pleasure and treasure were looking for something special and were willing to invest time and money to find it. The shoppers in the group enjoyed the hunt: finding the perfect brown suede boots, the best restaurant in an unfamiliar neighborhood, the coolest new thing at a good price.

Stress Reduction. This motivator was distinct from ease. Stress reduction was reactive: it kicked in only after a participant had experienced a problem and was now working to avoid it recurring. One participant took an indirect route to avoid a traffic circle she believed was dangerous. She'd developed evidence for her belief and could articulate it at length. The extra minutes were a deliberate investment in avoiding a known stressor.

These motivators were useful to Telenav because they suggested that navigation features aligned with a user's key motivations would be more likely to be adopted. A feature that helps a mastery-motivated driver experiment with new routes serves a different need than a feature that helps an ease-motivated driver avoid thinking about routes at all — even though both features involve routing.

The Work Commute vs. The Errands Trip

The observations revealed that the work commute and the errands trip were fundamentally different kinds of travel, each with its own optimization logic.

The work commute was a necessary, recurring event that participants treated as a solvable puzzle. They experimented with routes, tracked timing patterns, and developed personal theories about traffic flow. The pressure to optimize was highest on the way to work and increased with the length of the commute, the rigidity of the work schedule, the presence of children who also needed to be somewhere on time, and the degree to which the commute required highway travel. One participant left for work more than two hours early because traffic was more manageable at 6:15 AM. Another knew the likely time impact of taking each of three bridges across a river.

The commute home was less stressful but still optimized. Participants wanted to avoid wasting time, get home for family obligations, or find the most pleasant route. Several participants had deliberately chosen where to live and work based partly on minimizing their commute, which I interpreted as a proactive stress reduction strategy.

The errands trip operated on different logic. It was less urgent, less stressful, and organized around primary goals with secondary errands folded in opportunistically. Participants said versions of "while I'm here, I might as well…" to justify adding stops. The primary errand drove the route; secondary errands were fitted around it. The more errands someone had, the more pressure they felt to optimize the sequence.

The character of the primary errand shaped the trip. Errands that were essential, for a specific item, at a single location exerted the strongest pull on route planning. Errands that were discretionary, for a non-specific item, at any of several possible stores left the route more flexible and open to opportunistic stops.

Unmet Needs and Pain Points

The observations surfaced several unmet needs that pointed toward design opportunities for the navigation product.

Better last-mile directions. Multiple participants struggled with the final steps of navigating to an unfamiliar destination. One participant used Google Maps on satellite view to get most of the way to a shopping center, then made a wrong turn in the last stretch. Another printed MapQuest directions and found the street address but couldn't locate the store within the shopping center. A third couldn't find a specific building on a university campus. The common thread was that existing navigation tools gave adequate guidance at the route level but failed at the destination level. Participants wanted landmark-based directions and better visualization of their exact destination.

Smarter local search. Participants wanted to optimize their choice of store or restaurant based on multiple criteria simultaneously — ratings, distance, discounts, availability. One participant described wanting restaurant recommendations specific to whichever of his neighborhood "pods" he happened to be in. Another was frustrated at driving past acceptable restaurants on the way to a chain he knew, because he had no easy way to evaluate the alternatives.

Proactive, location-aware information. The shoppers in the group were motivated by coupons, discounts, and promotions. One participant went to Bed, Bath & Beyond but didn't buy anything because she'd forgotten her coupon. There was a clear appetite for push notifications tied to location and personal preferences — sales at favorite stores, events nearby, deals on items they were actively looking for.

Better in-car phone navigation. Several participants preferred their phone over a standalone GPS for directions but hit basic usability walls. The screen going dark during navigation was a universal complaint. Multiple participants wanted voice-guided turn-by-turn directions so they didn't have to look at their phone while driving. But others described standalone GPS units as "nagging" with repeated instructions, suggesting that the ability to pause or mute spoken navigation was important to get right.

What Made This Work

The value of this research was in its timing and its method. Telenav got field-based behavioral data about their target users before the product had taken shape: early enough to influence design direction rather than validate decisions that had already been made.

Surveys or focus groups would have produced self-reported preferences: what people say they want, what they think they do, what they believe matters to them. Ethnographic observation produced something different: what people actually do when they're running late for work and the bridge is backed up. What they actually do when they're driving past a strip mall and realize they need shampoo. What they actually do when their phone's screen goes dark in the middle of a navigation sequence and they're approaching a highway exit at 65 miles per hour.

The behavioral motivator framework gave the product team a vocabulary for talking about user needs that was richer than demographic segments. "Settle-Down Trendsetters aged 30-45" is a targeting category. "A mastery-motivated driver who treats the commute as an optimization puzzle and wants to know whether today's route is faster or slower than usual" is a design direction. The motivators translated observation into actionable product thinking.

The six motivators also carried an implicit design principle: different users want different things from the same feature category. Route guidance for an ease-motivated driver should minimize decisions. Route guidance for a mastery-motivated driver should enable experimentation. A navigation product that treats all drivers the same is leaving value on the table. This principle shows up clearly in the personalization capabilities of today's Vivid Nav product.

What I Learned

This was one of the projects that cemented my conviction that early-stage field research pays disproportionate dividends. The cost of observing eight people across two cities is modest compared to the cost of building features that miss the mark because the team's mental model of the user was based on assumptions rather than observation.

The fly-on-the-wall protocol was worth its logistical difficulty. Riding along in someone's car while they commute to work is awkward, intrusive, and hard to standardize. It also produces data that no other method can replicate. When a participant involuntarily grips the steering wheel harder approaching a merge point, or mutters under their breath when a GPS recalculates, or drives past their intended turn because they were glancing at their phone — those are the moments that reveal the real relationship between drivers and their tools. You don't get those moments from a survey.