1. STRUCTURE
1.1. interaction design (IXD)
1.1.1. structure experience of pattern and sequence that present appropriate option to users
1.1.1.1. user can interact with
1.1.2. dancing in step
1.1.2.1. user
1.1.2.2. system
1.1.2.3. moving along the same path
1.1.2.4. response
1.1.2.4.1. interact
1.1.2.4.2. functionality
1.1.2.5. help to meet user goal
1.1.2.6. inform state changes
1.1.2.7. prevent error
1.1.2.7.1. mistake
1.1.3. principles
1.1.3.1. consistent
1.1.3.1.1. visually remain same
1.1.3.1.2. context change only
1.1.3.1.3. link to other page inside
1.1.3.1.4. control pattern
1.1.3.1.5. behavior
1.1.3.1.6. voice
1.1.3.1.7. design pattern
1.1.3.2. predictable
1.1.3.2.1. preview
1.1.3.2.2. sense of place , expectation
1.1.3.3. learnable
1.1.3.3.1. learn from experience
1.1.3.3.2. single trial learning
1.1.3.3.3. gesture
1.1.3.4. visible
1.1.3.4.1. Discoverability
1.1.3.4.2. content hinting
1.1.3.4.3. opportunity to interact is avaliable
1.1.3.4.4. click and tap
1.1.3.4.5. touch and gesture
1.1.3.5. feedback
1.1.3.5.1. location
1.1.3.5.2. status
1.1.3.5.3. Future state
1.1.3.5.4. outcome/result
1.1.3.5.5. immediate reaction
1.1.3.5.6. acknowledge interactions
1.1.3.5.7. error prevention
1.2. information architecture
1.2.1. define volume of content , how to organized , arranged , prioritized
1.2.1.1. search
1.2.1.2. manipulate
1.2.1.3. organization
1.2.1.4. navigational
1.2.1.5. educating
1.2.1.6. infoming
1.2.1.7. persuading
1.2.1.8. flexible
1.2.2. type of information architecture
1.2.2.1. hierarchical tree
1.2.2.1.1. standard
1.2.2.1.2. organize complicate structure
1.2.2.1.3. multi-faceted navigation
1.2.2.2. hub and spoke
1.2.2.2.1. central index
1.2.2.2.2. start from central
1.2.2.2.3. can't navigate between spoke
1.2.2.3. nested list
1.2.2.3.1. linear navigation
1.2.2.3.2. quick
1.2.2.3.3. easy
1.2.2.3.4. strong sense of where we are
1.2.2.3.5. need to bear for exploring
1.2.2.4. dashboard
1.2.2.4.1. seem like hub and spoke
1.2.2.4.2. preview of chart
1.2.2.5. filters view
1.2.2.5.1. did search
1.2.2.5.2. get result
1.2.2.5.3. suitable for huge content
1.2.2.5.4. hub and spoke pattern
1.3. defining structure
1.3.1. how user get to given screen
1.3.2. where they can go when done each task
1.3.3. categories of information
1.3.4. good structure provide intuitive access to content
1.3.4.1. do it one time
1.3.4.2. remember forever
1.3.5. flexible
1.3.5.1. reorganize
1.3.5.2. expand
1.4. organizing principles
1.4.1. group
1.4.2. separated
1.4.3. relate to user need
1.4.4. relate to business objective
1.4.5. not too many option so user can't find it
1.5. roles and processes
1.5.1. someone have to do it
1.5.2. text online is enough to document architecture
1.5.3. make it simple
1.5.4. visual vocabulary
1.5.4.1. diagramming/hierarchy structure in
1.5.4.2. workflow diamgram
1.5.4.3. hub and spoke diagram
1.5.4.4. relationship between content diagram (from left to right)
2. SKELETON
2.1. interface design
2.1.1. how to arrange / present visual element for user to interact with
2.1.2. UI balance between visual form and technical function
2.1.2.1. give things people they want/need
2.1.2.2. give them when and why they want
2.1.2.3. format they can access all
2.1.2.4. form
2.1.2.4.1. organization
2.1.2.4.2. layout
2.1.2.4.3. audio
2.1.2.4.4. video
2.1.2.4.5. how hand/finger move through data
2.1.3. poor interface design
2.1.3.1. won't use
2.1.3.2. make another choice
2.1.3.3. go to other site
2.1.4. multiple device
2.1.4.1. same format
2.1.4.2. same action
2.1.4.3. same layout
2.1.4.4. prior experience
2.1.4.5. already know it should be like that
2.1.5. core principles
2.1.5.1. progressive disclosure
2.1.5.1.1. simple to complex
2.1.5.1.2. necessary information is displayed when request/need
2.1.5.1.3. reduce anything distract from the need
2.1.5.2. intuitive
2.1.5.2.1. learn behaviors from experiences
2.1.5.2.2. single try and remember
2.1.5.3. consistency
2.1.5.4. predictablility
2.1.5.5. context + hierarchy
2.1.5.5.1. group together visually
2.1.5.5.2. order of important
2.1.5.5.3. separate
2.1.5.6. hick's law
2.1.5.6.1. many of choices
2.1.5.6.2. time require to make decision
2.1.5.6.3. choose nothing
2.2. navigation design
2.2.1. allow user to move through task / information intuitively
2.2.2. start with site map
2.2.3. trunk test
2.2.3.1. can answer when lost
2.2.3.1.1. strong sense of place
2.2.3.1.2. correct expectation
2.2.3.1.3. predict outcome
2.2.3.2. blindfold and dropped of at random place
2.2.4. revealing depth
2.2.4.1. Dynamic sub-menus
2.2.4.1.1. hover state
2.2.4.2. search results
2.2.4.3. provide feedback
2.2.5. information scent
2.2.5.1. catagories
2.2.6. path
2.2.6.1. back out
2.2.6.2. navigate to a known location
2.2.6.2.1. back to home page
2.2.6.3. contextual links
2.2.6.3.1. clue to go somewhere
2.2.7. icon and labels
2.2.7.1. representation icons
2.2.7.1.1. learn by familiar
2.2.7.1.2. clear meaning
2.2.7.2. Abstract icons
2.2.7.2.1. learn by experience
2.2.7.2.2. require context
2.2.7.3. use solid navigation
2.2.7.3.1. use meaningful labels
2.2.7.3.2. reduce memory load
2.2.7.3.3. cognitive
2.2.8. be consistent
2.2.8.1. not do
2.2.8.1.1. rearrange order
2.2.8.1.2. appear and disappear
2.2.8.1.3. move to different location
2.2.8.2. stay in same layout
2.2.8.2.1. only content change
2.2.8.3. stay in same behavior
2.2.8.4. familiar
2.2.9. convention
2.2.9.1. be standard
2.2.9.1.1. what to look for
2.2.9.1.2. where to look for
2.2.9.1.3. easy to pick from everything
2.2.9.1.4. no more frustrating if link is broken
2.2.9.2. standard place
2.2.9.2.1. locate them quickly
2.2.9.2.2. used to see it before
2.2.10. metaphors
2.2.10.1. visual cues
2.2.10.1.1. explan
2.2.10.2. recognize
2.2.10.2.1. day to day life
2.2.10.2.2. same as real world object
2.2.10.3. game and entertainment app is great to use
2.2.10.3.1. show as bookself
2.2.10.3.2. show as DJ stand
2.2.10.3.3. show as credit card list
2.2.10.4. obvious
2.2.10.5. use with caution
2.2.10.5.1. culturally subjective
2.2.10.5.2. require mental effort
2.2.10.5.3. obscure
2.2.10.5.4. universal understanding are hard to come by
2.3. information design
2.3.1. tie everything together
2.3.2. invisible
2.3.3. group
2.3.4. arranged
2.3.4.1. context
2.3.4.1.1. order as expectation
2.3.4.1.2. alphabetical
2.3.4.1.3. categorical
2.3.4.1.4. continuum
2.3.4.1.5. location
2.3.4.1.6. time
2.3.5. appropriate form
2.3.5.1. easy to digest
2.3.5.2. easy to understand
2.3.5.3. presentation
2.3.5.3.1. bar chart
2.3.5.3.2. decision making
2.3.5.4. five path essay
2.3.5.4.1. introduction
2.3.5.4.2. narration
2.3.5.4.3. affirmation
2.3.5.4.4. negation
2.3.5.4.5. conclusion
2.3.5.5. inverted pyramid
2.3.5.5.1. reveal only the need information when request
2.3.5.5.2. most critical information
2.3.5.5.3. helpful but not critical
2.3.5.5.4. nice to know
2.3.5.6. occam's razor
2.3.5.6.1. simple model
2.3.5.7. progressive disclosure
2.3.5.8. hick's law
2.3.5.8.1. criteria filter is need
2.3.5.9. simple
2.3.5.9.1. maximize signal
2.3.5.9.2. minimize noise
2.4. wireframes
2.4.1. show priority on screen
2.4.2. how people go through the site/app
2.4.3. basic layout
2.4.4. how interact with
2.4.4.1. interaction sequence
2.4.5. navigate frame
2.4.6. finish looking rough sketch
2.4.7. level of details
2.4.7.1. don't care
2.4.7.1.1. images
2.4.7.1.2. font
2.4.7.1.3. color
2.4.7.1.4. look and feel
2.4.7.2. care
2.4.7.2.1. content
2.4.8. sketching
2.4.8.1. the must
2.4.8.2. quickly generate thumbnail
2.4.8.3. 60 second and move on
2.4.8.4. many different idea as possible
2.4.8.5. no think much
2.4.8.6. rapid prototyping
2.4.8.6.1. use appropriate tools
2.4.8.6.2. no "lorem ipsum" text
2.4.8.6.3. just label, button, navigate element
2.4.8.6.4. not final design
2.4.8.6.5. always change
2.4.8.6.6. create , go back , review
2.4.8.6.7. related content
2.4.8.6.8. match user's need or expectation
3. SURFACE
3.1. visual design
3.1.1. look and feel
3.1.2. guide user through data , task, information
3.1.3. reduce cognitive load
3.1.4. enable recognition
3.1.5. increase intuitive learning
3.1.6. culturally/socially appropriate
3.1.7. following the eye
3.1.7.1. F Pattern
3.1.7.2. Z Pattern
3.1.7.3. from top to bottom
3.1.7.4. just an idea, not accurate
3.1.8. contrast
3.1.8.1. draw user attention
3.1.8.2. understand relationship
3.1.8.3. stand out
3.1.9. uniformity
3.1.9.1. layout stay the same
3.1.9.2. content change
3.1.9.3. keeping element from overwhelming
3.1.10. consistency
3.1.10.1. external inconsistency
3.1.10.1.1. when time pass
3.1.10.1.2. same pattern or layout
3.1.10.1.3. same orientation
3.1.10.1.4. multiple device
3.1.10.2. internal inconsistency
3.1.10.2.1. same product
3.1.10.2.2. inside app/site
3.1.10.2.3. same feeling
3.1.11. color
3.1.11.1. emotional response
3.1.11.2. meanings
3.1.11.2.1. associated
3.1.11.2.2. confusion
3.1.11.2.3. symbolic
3.1.11.3. optical fatique
3.1.11.4. readablility
3.1.11.5. sustains visual interest
3.1.11.6. highlight
3.1.11.7. guide
3.1.11.8. one dominate neutral color
3.1.11.9. add some accent color
3.1.11.10. can interfere hierarchy and content
3.1.11.11. what about who color blind
3.1.12. typography
3.1.12.1. sans
3.1.12.2. serif
3.1.12.3. use it purposefully
3.1.12.4. different information , different style
3.1.12.5. weight
3.1.12.5.1. bold
3.1.12.5.2. regular
3.1.12.5.3. for catalog
3.1.12.6. draw user attention
3.1.12.6.1. contrast
3.1.12.7. consistent styling
3.1.12.8. apply styles consistently
3.2. visible language
3.2.1. layout
3.2.2. typography
3.2.3. color
3.2.4. imagery
3.2.5. sequencing
3.2.5.1. visual storytelling
3.2.6. visual identity
3.2.7. principle of UI design
3.2.7.1. Organize
3.2.7.1.1. clear
3.2.7.1.2. consistency
3.2.7.1.3. conceptual structure
3.2.7.1.4. visual hierarchy
3.2.7.2. Economize
3.2.7.2.1. least amount of cues
3.2.7.2.2. do most
3.2.7.3. Communicate
3.2.7.3.1. expectation
3.2.7.3.2. capablilities
3.2.7.3.3. pattern recognition
3.2.7.4. user
4. factor of plane
4.1. plane effect another plane
4.2. each plane need to be flexible
4.2.1. overlap each plane to see what plane effect what
4.2.2. two inform each other
4.3. content is the king
4.3.1. user want
4.3.2. relevant to the reason they are there
4.3.3. catalog , track , present on when , where, how the user want
4.4. technology support to delivery great experience
4.4.1. across multiple deice , OS , browser
4.4.2. inherit how we design
4.4.3. touchscreen have changed the way to navigate
5. STRATEGY
5.1. user needs
5.1.1. start here first
5.1.2. what they want
5.1.3. how to fit thier goals
5.2. business objective
5.2.1. define success
5.2.1.1. making money
5.2.1.2. ROI
5.2.1.3. Save money
5.2.1.4. measurable how we know if we succeeded
5.3. know what's we build
5.4. not about technology or design
5.5. research process
5.5.1. interviews
5.5.1.1. stakeholder
5.5.1.1.1. ask question
5.5.1.2. B2B user
5.5.1.2.1. ask question ( role )
5.5.1.2.2. ask question (need)
5.5.2. review
5.5.2.1. competitor
5.5.3. research
5.5.3.1. user
5.5.4. existing product
5.5.5. analyze and review
5.6. worth doing
5.6.1. importance and feasibility/viablity
5.6.2. what we creating
5.6.2.1. everybody understand in the same way
5.6.3. find value to provide
5.6.3.1. target customer
5.6.3.2. what experience they have
5.6.3.3. how is offer different from competitor / substitute
5.7. user expectations
5.7.1. first use
5.7.1.1. what is it
5.7.1.2. is this expect to see
5.7.1.3. look credible and trustworthy
5.7.1.4. offer what I want
5.7.1.5. 3 sec decision before quit
5.7.1.6. valuable enough to be stick around
5.7.1.7. what i can do when here
5.7.1.8. how do I learn more
5.7.1.9. how to contact someone
5.8. things to remember (conclusion)
5.8.1. clear roadmap
5.8.2. clear strategy
5.8.2.1. technology decision
5.8.2.2. screen look like/arrangement
5.8.2.3. arragement
5.8.2.4. function and look and feel
5.8.3. always experience driven by business gold and user need , not coding
5.8.4. design for user , not you
5.9. Determine strategic value
5.9.1. importance vs feasibility chart
5.9.2. plot value in the chart
6. SCOPE
6.1. function specification
6.1.1. feature set of product
6.1.1.1. new feature
6.1.1.1.1. must support strategy
6.1.1.1.2. often present as good idea
6.1.1.1.3. almost emerge after project underway
6.1.1.2. clear declaration
6.1.1.3. identify what to do right now
6.1.1.4. identify what "NOT" to do right now
6.1.1.4.1. sprint planning
6.1.2. what's we creating
6.1.3. too big
6.1.3.1. can't delivery in time
6.1.3.2. make another choices/bargain
6.1.3.3. Nervous design / dev
6.1.4. too small
6.1.4.1. unclear path to full vision
6.1.4.2. unimpressive feeling to do for customer
6.1.5. start from why to what
6.1.5.1. things people say they need
6.1.5.1.1. false need
6.1.5.2. things people actually need
6.1.5.2.1. false need
6.1.5.3. things they don't know they need
6.1.5.3.1. new idea
6.1.5.3.2. brainstroming
6.1.5.3.3. false need
6.1.6. create useful specification
6.1.6.1. user scenarioes
6.1.6.1.1. high level diagram
6.1.6.1.2. all scenario
6.1.6.1.3. can group if same
6.1.6.1.4. storyboard
6.1.6.1.5. share and discuss
6.1.6.1.6. generate to each requirement/feature
6.1.6.2. be positive sentense
6.1.6.2.1. system will suggest ..
6.1.6.2.2. not allow user to..
6.1.6.3. be specific word/feature
6.1.6.3.1. eg. specific people
6.1.6.4. be objective
6.1.6.4.1. hip and cool
6.1.6.4.2. follow brand guideline
6.2. content requirements
6.2.1. details what's required to provide value to users
6.2.2. text , data , images , audio, video
6.2.2.1. different type can work together
6.2.3. major impact on UXD decision
6.2.3.1. format
6.2.3.2. purpose
6.2.3.3. size
6.2.3.3.1. performance
6.2.3.3.2. bandwidth
6.2.3.4. resource
6.2.3.4.1. person in-charge of
6.2.3.4.2. video
6.2.3.4.3. images
6.2.3.4.4. need other people to involve
6.2.4. should be strategic
6.2.4.1. fit business
6.2.4.2. fit user
6.2.4.3. delivery method
6.2.4.3.1. streming
6.2.4.3.2. download material
6.2.4.4. style & structure
6.2.4.4.1. arrangement
6.2.4.4.2. formal or strict
6.2.4.4.3. culture or hip
6.2.4.4.4. organize
6.2.4.4.5. prioritize
6.2.4.5. subject & substance
6.2.4.5.1. tell something they need to know
6.2.4.5.2. value to customer / not us
6.2.4.6. 3 sec to delivery to customer
6.2.4.7. validate content feature against project's strategic objective
6.2.4.7.1. inappropriate content
6.2.4.7.2. content resource
6.2.4.7.3. do much more to save time of next plane
6.2.5. contextual
6.2.5.1. physical activity
6.2.5.1.1. device
6.2.5.1.2. disabilities
6.2.5.1.3. activity
6.2.5.1.4. habit
6.2.5.2. emotional
6.2.5.2.1. stress
6.2.5.2.2. desire
6.2.5.2.3. need
6.2.5.3. cognitive
6.2.5.3.1. ability to learn
6.2.5.3.2. suitable for all education
6.2.6. 3 attribute
6.2.6.1. useful
6.2.6.2. sellable
6.2.6.3. buildable
6.3. Define scope
6.3.1. all player address conflict before invest in design/building product
6.4. Document
6.4.1. reference for work to be done
6.4.2. common way to describe the work
6.4.2.1. easy to understand
6.4.2.2. understand in the same page
6.4.3. don't be epic, just common understand
6.4.3.1. scheduler
6.4.3.2. milestone
6.4.3.3. nobody read epic
6.4.4. clear descrpition
6.5. Lean/Agile
6.5.1. slow the stage of completeness
6.6. poor symtoms
6.6.1. we can do that
6.6.2. far from reality
6.6.3. put them all together
6.6.4. snowball symtom
6.6.4.1. problem grow
6.6.4.2. unable to control
6.6.4.3. nervous team
6.6.5. say "no" or we will look into it
6.7. tradeoffs
6.7.1. keep or toss
6.7.2. very important
6.7.3. create need for choice
6.7.4. limit the feature set/offer
6.7.5. define what to do/ what not
6.7.6. path of strategy
6.7.6.1. focus of what business do
6.7.6.1.1. ikea is the good example
6.7.6.2. constaint
6.8. delivering continuous value
6.8.1. versions
6.8.1.1. evolve and integrate
6.8.1.2. new experience
6.8.1.3. new feature/function
6.8.1.4. long WOW
6.8.1.4.1. identify touch point for delivery
6.8.1.4.2. keep adding new feature differ from competitor ( unmet need)
6.8.1.4.3. repeatable delivery process
6.8.1.4.4. plan and stage the wow experience
6.9. gathered requirement
6.9.1. give impression the job is take order
6.9.2. may not get real requirement
6.9.2.1. most of requirement are feature/solution , not problem/need
6.9.2.2. state the need first
6.9.2.3. brainstorming
6.9.2.3.1. objective
6.9.2.3.2. functional
6.9.2.3.3. non-functional
6.9.2.3.4. business rules
6.9.3. object as mush as possible to get the real answer
6.9.4. from session of executive opinion
6.9.5. customer claim they want
6.9.6. technology preference
6.9.7. not gathered, they generated
6.9.8. most of the time, they're negotiated