Exposure Hours

WHY IT EXISTS Research insights traditionally flow to the team through reports and presentations, which strip away the visceral reality of watching a real person struggle. Teams reading a summary rarely internalize the pain. Exposure hours exists as a deliberate metric to ensure the whole team, not just researchers, builds genuine empathy from direct observation.

THE MENTAL MODEL Think of empathy as a battery that drains over time and must be recharged by firsthand contact. A report is a photo of someone else's experience; an exposure hour is being in the room. The model treats observation time as a leading indicator of design quality, something you schedule and track like any other team commitment.

HOW IT WORKS UIE's research surfaced a rough threshold: teams whose members each spent at least two hours observing users every six weeks made better decisions and innovated more. Crucially, exposure must be direct, watching sessions live or via recordings, not reading a researcher's writeup, and it must include engineers, designers, and product managers, not only researchers. Organizations operationalize it by inviting the team to usability sessions and tracking hours per person.

WHEN IT MATTERS It matters most when a team is far from its users, when decisions are driven by internal opinion, or when research findings keep getting ignored. Building shared firsthand conviction breaks the cycle of debating whose assumption is right.

ONE CONCRETE EXAMPLE An engineering team kept dismissing a reported onboarding problem as edge-case. After each engineer watched two users abandon signup live during a session, the fix was prioritized the same sprint, because the pain was now their own observation, not a slide.