Study participants saw a number of charts in six different color palettes. Just like the first study, users shared first impressions, preference, and value feedback, and the speed and accuracy with which they made decisions were captured. Source
Working on a new WordPress Theme called NTT (entity).
[applicator_percept “Applicator: Style”]
Product Design Journey
|User Research||Interaction Design||User Interface Design||Visual Design||Front–End Development|
Mini DesignEx2 (Exchange & Experience)
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.
A new take on choreography!
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.
It is, after all, a hypertext document.