Autoethnography turns the researcher into the research instrument. Instead of studying others, the designer systematically documents and analyses their own lived experience of a product, service, or context. It is a discipline borrowed from social science that has found a natural home in design — particularly when the designer belongs to the same community they are designing for, or when access to participants is limited.

What It Is

Autoethnography combines personal narrative with analytical distance. The researcher immerses themselves in the experience being designed for, keeps structured field notes, and then analyses those notes using rigorous qualitative methods. The goal is not self-indulgence but systematic insight: the researcher's experience serves as a proxy for broader patterns shared by many users.

When you are the user, you notice things no one would think to tell you.

How to Run It

  1. Define the experience boundary: which service, product, or context will you document.
  2. Immerse yourself fully — use the product or service under real conditions, not idealised ones.
  3. Keep a daily field log: what you did, what surprised you, what frustrated you, what worked.
  4. Note workarounds, emotions, and environmental factors alongside task completions.
  5. Review logs with a colleague to challenge your assumptions and surface blind spots.
  6. Code the notes thematically and compare findings with user research data.

When to Use It

Autoethnography is most useful early in a project when access to participants is restricted, or when the design challenge involves an experience the researcher can meaningfully and authentically inhabit. It is particularly relevant for accessibility design, service journeys, and social innovation work where personal proximity to the context is an asset rather than a bias.

Tips for Success

  • Document in real time, not from memory — immediacy is what makes autoethnography valuable.
  • Treat your experience as one data point: always triangulate with external user research.
  • Be explicit about your own identity and how it shapes the experience you are documenting.
  • Use autoethnography to generate hypotheses, not to validate them.