All methods

A Day in the Life

Typical duration:
45m

An immersive research method where the team maps or experiences a user’s entire day to uncover context, routines, pain points, and unmet needs beyond a single interaction.

Purpose

A Day in the Life zooms out from a single product interaction to understand the full context of a user’s daily reality. By mapping or shadowing someone through their entire day, teams discover the routines, pressures, transitions, and emotional arcs that shape behaviour — revealing design opportunities that task-focused research misses.

At a glance

  • Group size: 2–6 (mapping workshop) or 1–2 (shadowing)
  • Duration: 45 minutes (mapping exercise) or full day (shadowing)
  • Difficulty: Low (mapping), High (shadowing)
  • Facilitation style: Guided storytelling or silent observation
  • Setting: Workshop room for mapping; user’s environment for shadowing

How to run

  1. Choose the approach (beforehand): Decide between a mapping exercise (the user tells you about their day) or shadowing (you observe the day directly).
  2. For mapping — Set up the timeline (5 min): Draw a horizontal timeline from wake-up to bedtime on the wall. Mark key moments: morning routine, commute, work blocks, breaks, evening.
  3. Walk through the day (25 min): The user (or a persona proxy) narrates their day. At each phase, capture: activities, tools used, people interacted with, emotions, pain points, and workarounds.
  4. Identify hot spots (10 min): Mark moments of high stress, frustration, joy, or unmet need. These are design opportunity zones.
  5. Extract insights (5 min): Summarise 3–5 key insights about the user’s life context that should influence the design.

Materials needed

  • Long roll of paper or whiteboard for timeline
  • Sticky notes and markers
  • Emotion stickers or colour codes
  • Camera (for shadowing variant)

Pitfalls & common mistakes

  • Focusing only on your product’s touchpoint: The value is in the full context. Map the whole day.
  • Assuming one day represents all days: Ask about variations — weekdays vs weekends, busy vs quiet days.
  • Projecting your own routines: Let the user describe their day; don’t prompt with your assumptions.
  • Ignoring transitions: The moments between activities (commute, handoff, waiting) are often the richest.

Inclusion & accessibility

  • Respect privacy boundaries — some parts of a day are not for observation.
  • Offer multiple formats: verbal narration, written diary, photo diary, or drawing.
  • Be sensitive to the emotional labour of sharing personal routines.

Variations

  • Photo diary: Give users a camera and ask them to photograph key moments over a week.
  • Day reconstruction method: Users fill out a structured diary at the end of the day, reducing observation bias.
  • Comparative day mapping: Map two users’ days side by side to highlight differences.

When NOT to use this

  • When the design challenge is narrow and contextual information is not needed.
  • When the user population is too diverse for a single "day" to be representative.
  • When shadowing would violate privacy or create ethical concerns.

Source & further reading

  • IDEO — *The Field Guide to Human-Centered Design* (2015)
  • Kahneman, Krueger et al. — "A Survey Method for Characterizing Daily Life Experience" (Science, 2004)
  • Stickdorn & Schneider — *This Is Service Design Thinking* (Wiley, 2011)

Turn the building blocks into an agenda

Create the day, drag the blocks into the order you have in mind, and let the times work themselves out. Or describe what you are planning to your AI and let it write the first draft.

Try it free for 14 days
A Day in the Life · GoodWorkshop