AEIOU is a framework for structuring observational research. It sorts what you record in the field into five categories: activities, environments, interactions, objects and users. It was developed at the innovation consultancy Doblin in 1991 as a coding scheme for ethnographic data, and its value is that notes taken this way are comparable across sessions and across researchers.
When you can watch people do the work rather than only ask about it, and you want notes that are comparable across sessions. It is a capture structure rather than an analysis method, so it pairs with something that synthesises, such as an empathy map.
What AEIOU is
AEIOU is a framework for structuring observational research. It sorts what you record in the field into five categories: activities, environments, interactions, objects and users.
It was developed in 1991 at Doblin, the Chicago innovation consultancy, as a coding scheme for ethnographic data. The categories were chosen to be mutually exclusive and, between them, to cover a scene, so that two researchers watching the same session produce notes that can be compared rather than two personal essays.
It is a capture structure, not an analysis method. It tells you what to write down. It has no opinion about what any of it means.
- Five categories, no overlap By design
Activities, environments, interactions, objects, users. Chosen so a note belongs in exactly one.
- Sort live, not afterwards The whole benefit
Retrospective sorting reintroduces the selective attention the structure exists to remove.
- Objects hold the workarounds The productive category
The taped-up checklist, the private spreadsheet. Undocumented process made physical.
- It captures; it does not conclude Pair it
A stack of well-sorted notes is not an insight. Synthesis happens in a separate step.
Why it matters
Unstructured field notes are shaped by what you already expected to see. You write down the things that confirm your model of the work and skim past everything else, and you do not notice you are doing it.
Five fixed headings interrupt that. A column that stays empty is itself a finding: an hour of observation with nothing in Interactions usually means you watched someone work alone on a task that is actually collaborative, and you happened to catch the solitary part.
The empty column is also the one people quietly fill in from memory on the train home, which defeats the entire exercise. Leave it empty. An honest blank is worth more than a plausible sentence.
The five categories
Goal-directed sequences of actions. What are they trying to get done?
Reads inbox, tags by theme, copies three items into a doc for the sprint meeting.
The setting, and what it makes easy or hard.
Open-plan, interrupted roughly every ten minutes, works from a laptop in meetings.
Between people, and between people and systems. Who do they wait for?
Pings an engineer to check feasibility before committing. Waits two days for an answer.
Artefacts present, especially improvised ones.
A personal spreadsheet of recurring themes that exists in no official system.
Who is present, their role, and their relationship to the task.
Product manager, four years in role, inherited the process and did not design it.
An empty column is a finding. An hour of observation with nothing in Interactions usually means you watched the solitary part of a collaborative task.
When to run it
- You can watch people do the actual task, in the place they do it.
- Several researchers are gathering data and you need notes that compare.
- What people describe in meetings does not match the outcomes you see.
- You suspect there are workarounds nobody has mentioned.
- You are researching a workflow you have never performed yourself.
- You can only talk to people, not watch them. Use The Mom Test →
- You have notes already and need to make sense of them. Use Empathy Maps →
- You need to know why they would switch. Use Jobs to be Done →
- You need a profile the commercial team can act on. Use Buyer Persona Canvas →
AEIOU in practice: Airbnb in New York
Observation beating analytics, in a case where the analytics were working perfectly and reporting nothing useful.
Airbnb · 2009
Fixed a conversion problem by renting a camera and going to New York.
Bookings in New York were flat. The founders looked at the listings and formed a hypothesis that the photographs were bad enough to stop people booking, which is not something an analytics dashboard tells you.
They rented a camera, went to New York, and photographed the listings themselves. Revenue in the market is reported to have roughly doubled within a week or so.
This is often quoted as a story about hustle. It is more useful as a story about journey mapping: the failure was at a specific step, the step was invisible in aggregate data, and finding it required looking at what the guest actually saw.
- Method
- a rented camera
- Reported effect on New York revenue
- roughly doubled, within about a week
- Scalability of the fix
- none, initially
What it shows: The step that is failing is rarely the step being measured. A journey map is worth having because it names the steps nobody has instrumented.
AEIOU vs the alternatives
What do I write down while watching, so sessions compare?
Gives you: Structured field notes in five categories
What do these notes mean, and where do they contradict?
Gives you: Four quadrants and the gaps between them
How do I run the session itself?
Gives you: An interviewing-while-observing protocol. AEIOU is the note format inside it
What happens across time and touchpoints?
Gives you: A sequence. AEIOU captures moments within it
When it won’t help you
- It requires access you may not have
The whole framework assumes you can be present while the work happens. For most B2B software teams that access is difficult to arrange and, for regulated or sensitive work, impossible.
Instead: A screen share while someone performs the real task is a workable substitute. A description of the task in a meeting is not.
- It captures and does not interpret
Five columns of good notes is raw material. The framework has no opinion about what any of it means and provides no route from observation to decision.
Instead: Pair it with a synthesis step and a prioritisation step. Neither is included.
- Observation changes the behaviour observed
People tidy up when watched. The private spreadsheet may not appear, the shortcut may not get taken, and you will record the official version of the process.
Instead: Stay longer than is comfortable. The performance usually decays after the first half hour.
- It scales badly
Each session is an hour of someone's time plus travel plus transcription, and the structure does nothing to reduce that. Five sessions is a serious commitment.
Instead: Use it to work out what to ask, then use a survey to find out how common the answer is.
Further reading
- Rick E. Robinson’s writing on the origins of the framework at Doblin.
- Empathy Maps. Where AEIOU notes go to be synthesised.
- The Mom Test. What to do when you can only talk, not watch.
- Jobs to be Done. Turning observed behaviour into a reason for switching.
- Design Thinking. The wider process the empathize stage sits inside.
How to apply AEIOU Framework
- 1
Get into the room where the work happens
The framework assumes observation. If all you can do is a video call in which someone describes their process, you are running an interview and the categories will mostly stay empty. A screen share while they do the task is the minimum viable version.
- 2
Take a sheet with the five headings and use them live
Activities, environments, interactions, objects, users, as five columns. Sorting as you record is the point; sorting afterwards from memory reintroduces exactly the selective attention the structure exists to prevent.
- 3
Record Objects carefully, because they hold the workarounds
The printed checklist on the monitor, the second screen with a spreadsheet, the notebook. Objects are where undocumented process becomes physical, and people rarely mention them because they no longer notice them.
- 4
Note Interactions between people as well as with tools
Who they turn to, who they wait for, who they route around. In organisational settings the interaction map frequently explains a delay the person cannot account for themselves.
- 5
Separate what you saw from what you concluded
The five categories hold observations. Interpretations belong in a separate column, clearly marked. Blending them is how a field note becomes an opinion with a timestamp on it.
- 6
Converge with the team before you interpret
Two observers sorting the same session into the same categories will disagree, and the disagreements are informative. Compare sheets before anyone writes conclusions.
Common mistakes
- **Using it as an interview guide.** It is an observation structure. Asked as questions, the categories produce a description of the process the person believes they follow, which is the thing observation exists to check.
- **Skipping Objects.** The least intuitive category and usually the most productive, because it is where undocumented workarounds become physically visible.
- **Sorting afterwards from memory.** Recording live is what stops your existing beliefs deciding what was worth noticing. Retrospective sorting reintroduces the bias the structure removes.
- **Blending observation with interpretation.** The categories hold what happened. Conclusions belong in a separate, labelled column, or the note acquires more authority than it earned.
- **Observing one session and generalising.** Five categories of thorough notes from a single person is still one person. The structure makes sessions comparable, which only helps if there are several.
- **Treating the output as findings.** AEIOU captures. It does not synthesise, and a stack of well-sorted notes is not an insight.
How ShipFit operationalizes this
ShipFit runs the AEIOU Framework across Stage 2 (Who Pays?) and Stage 3 (What Hurts?). At Stage 2 it structures the buyer's context: the tools they already pay for map to Objects, their approval chain to Interactions, their working environment to Environments. At Stage 3 it drives behavioural observation, so problems are recorded against what buyers actually do rather than against what they report.
ShipFit runs 55 frameworks across 9 decision stages
AEIOU Framework is one tool in a bigger toolkit. The full library covers market sizing, buyer discovery, MVP scoping, pricing, and launch.
The Mom Test
Q3Rob Fitzpatrick
Validation question methodology, real interviews, not theater
Jobs-to-be-Done
Q2-Q4Clayton Christensen
Functional, social, and emotional jobs your product fulfills
7 Powers
Q4Hamilton Helmer
Strategic moats: Scale, Network, Counter-positioning, Switching, Brand, Cornered Resource, Process
Van Westendorp PSM
Q6Feature-weighted price sensitivity analysis without guessing
Blue Ocean Strategy
Q4Kim & Mauborgne
ERRC framework: Eliminate, Reduce, Raise, Create
Fake Door Testing
Q7Pre-build behavioral validation with landing pages and apology modals
+ 49 more: TAM/SAM/SOM Analysis, Porter's Five Forces, Market Timing Analysis, Unit Economics (LTV/CAC)...
Frequently asked questions
What does AEIOU stand for?
Who created the AEIOU framework?
How is AEIOU different from an empathy map?
Can I use AEIOU for interviews?
Why is the Objects category so important?
Keep exploring
The 9-step playbook from market verdict to ship-ready spec.
Kim and Mauborgne's framework in plain terms: the strategy canvas, the four actions, the six paths, and the tests that separate a blue ocean from a red one.
ICE scoring ranks ideas by Impact times Confidence times Ease. How to score it honestly, where the arithmetic misleads, and how it really differs from RICE.
Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.
Most founders pick a price by looking at competitors and shaving 20%. That's not pricing strategy, it's matching. Real pricing validation produces a price you can defend against your own ego and your buyer's pushback.
Founder equity that won't blow up the cap table in year three.
The first phase of Steve Blank's Customer Development methodology (2005). The work of finding out whether the problem you think exists actually exists, for the buyer you think has it. It precedes customer validation (proving the buyer will pay). Customer discovery uses interviews and observation; customer validation uses behavioral evidence (pre-orders, signed LOIs, paid pilots). Both are required before scaling.
Validation for solo founders with no cofounder to push back. ShipFit forces 9 decisions and argues with your idea in 2 minutes on real data. Start free.
PRD generators turn your input into a tidy requirements doc fast. ShipFit forces the decisions that make the doc worth writing, then exports the spec. A polished PRD for an unvalidated idea is just well-formatted fiction.
Ready to make your next product a success?
9 decisions between your idea and a product worth building.