Guide
Five common AEIOU framework mistakes

Five mistakes researchers make with the AEIOU observation framework (activities, environments, interactions, objects, users), from coding notes after the session to using AEIOU where a usability test fits better. Each one comes with a short reason. Use it when you plan a field study or train new researchers to observe.
Where this appears
What's in this guide
- Coding after the session: Memory fades within minutes. Codes added two hours later are reconstructions, not observations.
- Forcing every note into one bucket: A coffee cup can be an Object and a hint about the Environment. Allow cross-tagging.
- Dropping the Emotions extension: In consumer and service design studies, the emotional side is too important to leave out.
- Treating AEIOU as the whole method: It's a capture scaffold. It doesn't replace interview design, sampling or a research plan.
- Using it in place of a usability test: AEIOU is for behavior in context, not for judging an interface against task success.
Use this image
Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:
html
<a href="https://www.koji.so/visuals/aeiou-framework-five-common-mistakes"><img src="https://www.koji.so/visuals/aeiou-framework-five-common-mistakes/aeiou-framework-five-common-mistakes.png" alt="Listicle of five AEIOU mistakes: coding after the session, one bucket per note, no emotions, treating it as the method, skipping usability tests." width="1080" height="1080" /></a>
<p>Source: <a href="https://www.koji.so/visuals/aeiou-framework-five-common-mistakes">Five common AEIOU framework mistakes</a>, Koji</p>




