Hi, I’m Brian Dys — a photographer from the inside looking out · a composer entangled in electronic music · a UX designer · a spouse, a parent, & everything in between.
Introduction to Information Architecture 1
How spaces and structures are designed in the information level.
To empower designers in working in the Interaction Design stage.
- Information Architecture
- Information, Data, Content
- Information Architecture
- Nouns and Verbs
- Controlled Vocabulary
- Types of Relationships
- Things that are present
- Facts, Observations, Questions
- Information is not Content
The arrangement of the parts to make sense of the whole.
The language that we use and the meaning that we intend.
Nouns and Verbs
Where to look for Nouns?
- People – who are involved?
- Features – what are the distinguishing aspects of the thing?
- Paths – what do people look to accomplish?
Parts of a Controlled Vocabulary
- Approved Terms
- Approved Synonyms
- History of Term
- Words We Don’t Say
- Relationship Between Terms
Exercise: Ontology Framework
- Classification, organization of things
- Structure is a rhetorical tool
- Taxonomy should depend on intentions (e.g., we want people to call us, we want people to refer other people)
In order to begin organizing, use facets:
- Personality – what is it about?
- Matter – what is it made or or not made of?
- Energy – what are the related activities?
- Space – where does it exist?
- Time – when does it exist?
Types of Relationships
These are the common taxonomic patterns:
- Equivalence – is the same as
- Hierarchy – is a part of; is a type of
- Sequential – is a predecessor or; is a successor of
- Associative – is related to; is used with (not necessarily within the same family)
5 Ways to Organize things:
- Block Diagram (wire framing)
- Association Diagram (mind mapping)
- Swim Lane (shows different responsibilities within the same process)
- Steps user can or can not take across contexts and channels
- Setting the rules for realizing intentions
- Different UX in desktop and mobile
- User access based on role
- Different UX for novice user and expert user
How does the language (ontology) change based on the context and channel?
How does the structure (taxonomy) change based on the context and channel?
- Communicating intentions to users in a holistic manner
- Considering the ecosystem to objects
Deciding meaningful differences of taxonomy and ontology across contexts and channels
The ability to zoom in and out of an experience to ensure you are serving your users
IA is collaborative.
IA is not a process, it is a result.
In finding the best term for separating a collection of items, which to use—list or group?
List implies linearity, structure.
Group implies randomness.
In generalizing the semantics of all items in a collection—in an HTML document—go for group.
<ul class="list group">…</ul> <div class="group">…</div> <dl class="list group">…</dl>
It is important to note that the all HTML elements in the examples could express hierarchy by nesting other elements—but it is in the collection of items that list or group provides semantics.
Use list for collection of items that implies order (yes, even for <ul>).
Use group for collection of items that does not imply order.
Information Architecture & Interaction Design
- Human–Computer Interaction
- Cognitive Psychology
- Ubiquitous Computing
- Urban Informatics
- Urban Computing
- Human Factors and Ergonomics
- Social Computing
- User Experience and Experience Design
- Visual Representation
- Industrial Design
- Bifocal Display
- Contextual Design
- Mobile Computing
- End–User Development
- Philosophy of Interaction
- Affective Computing
- Requirements Engineering
- Context–Aware Computing
- Usability Evaluation
- Activity Theory
- Disruptive Innovation
- Open User Innovation
- Visual Aesthetics
- Tactile Interaction
- Card Sorting
- Wearable Computing
- Social–Technical System Design
- Aesthetic Computing
- Computer Supported Cooperative Work
- Formal Methods
- 3D User Interfaces
- Action Research
- Experimental Methods in Human–Computer Interaction
- Data Visualization for Human Perception
- Human–Robot Interaction
- User Interface Design Adaptation
- Emotion and Website Design
- Human–Data Interaction
- Design for All
- Research through Design
- Semi–Structured Qualitative Studies
But I know every rock and tree and creature
Has a life, has a spirit, has a name
Colors of the Wind
The Name—Description—Purpose Information Structure or NDP becomes a tool in identifying any UI element within a system. The Designer would have a glimpse of what it is called (Name), what it does (Description), and why it exists (Purpose).
Be a jack of all trades and a master of none or a master of one (and more)? It is an age-old question.
It depends on the environment where you want to focus on:
- in a one-man band freelancing: jack of all trades
- in a company with team members with specializations: specialize
- in a company with “all-around” team members: jack of all trades
In general, be the best at one thing and not so best or at least familiar with other things.
There are many default usability styles designed by the browser.
Sometimes it is best to leave it alone because it covers a lot of area that you might not be able to cover if you nitpick it.
Now if the color of the outline clashes with your branding like “blue is really banned from your UI” then change it.
Or if the outline color is the same as the background color, it won’t be seen, of course, so change it.
It’s important to note that styles whose main purpose is usability must be left alone especially if your purpose is to simply comply with color schemes.