AEIOU: Five Buckets for Field Notes
AEIOU sorts notes into five buckets—Activities, Environments, Interactions, Objects, Users—so patterns emerge from chaos. Use it during field studies to categorize raw data. The footgun is treating its categories as rigid rules not editable heuristics.
Why it exists
Qualitative field research produces messy, unstructured notes. Without a shared taxonomy, teams drown in raw observations and struggle to spot patterns during analysis. AEIOU was created by Rick E. Robinson as a categorizing heuristic to give researchers a lightweight, common language for sorting what they see in the field.
The mental model
Think of AEIOU as a five-column spreadsheet you keep in your head. Every observation gets dropped into one of five buckets. Activities are the actions people take. Environments are the settings and contexts. Interactions are the exchanges between people, tools, and systems. Objects are the artifacts and details in the space. Users are the people themselves, their traits and behaviors. The goal is not perfect classification; it is forcing disparate notes into a structure that reveals gaps and themes.
How it works
Before a session, print or prepare a worksheet with five sections labeled A, E, I, O, U. During the observation, capture what you see, hear, and feel, routing each note to the relevant bucket. After the session, review the columns as a team. One column may be overflowing while another is empty, which tells you where to dig deeper or adjust your research questions. Because Robinson designed the framework as editable heuristics, teams should refine the definitions to match their project goals.
When to use it
Use AEIOU during contextual inquiries, usability tests, and ethnographic field studies where you need to convert live observations into categorized data quickly. It shines when multiple researchers are taking notes and you need to align everyone on what to capture. It also works as a cover-page reminder on discussion guides to keep observers focused.
When not to use it
Do not use AEIOU when you need strict statistical rigor or fully structured quantitative data. It is not a replacement for survey instruments or analytics. It also fails if the team treats the five categories as immutable laws; forcing observations into a bucket that does not fit distorts the data and hides context.
One canonical example
A software team is observing nurses at a hospital station. Under Activities they note frequent password re-entry. Under Environments they record poor lighting and noise. Under Interactions they see nurses asking each other for login help. Under Objects they list sticky notes with credentials taped to monitors. Under Users they describe shift changes and varying tech comfort. Reviewing the worksheet later, the team realizes the security-object and interaction columns tell a single story: authentication friction is forcing unsafe workarounds.
Interview question
A team plans to use AEIOU during an ethnographic field study to categorize live observations. Which approach aligns with how the framework is intended to be used?
- a.They replace their discussion guide with the AEIOU worksheet to keep observers focused solely on the five buckets
- b.They use the five categories as a starting structure but refine definitions to fit their specific study goalsCorrect
- c.They require every observation to fit into exactly one of the five preset categories without exception
- d.They treat the worksheet as a tool for converting qualitative notes into statistically rigorous quantitative data
Why? this is the answer
AEIOU was designed as editable heuristics, so teams should refine the five buckets to match project goals. Requiring every observation to fit rigidly into preset categories without exception is explicitly called out as a footgun that distorts data and hides context.
Just read this? Test yourself on what you have been reading.
Read the original → openpracticelibrary.com
- #ux research
- #ethnography
- #qualitative data
- #usability testing
- #framework
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on ux research — each one lists the topics its interview covers.
See open roles