Review User Experience Midterm

Introduction to User Experience

 User Experience is how a person feels when interfacing with a system. The
system could be a web, application, or desktop software, generally by some
form of human-computer interaction.
o UX design is a concept that includes a bunch of different disciplines
such as interaction design, information architecture, visual design,
usability and human-computer interaction. UX design is a process for
designing systems that offer great experience to users.
o Elements that users can :
 Touch (Tangible products and packaging)
 Hear (Commercials and audio signatures)
 Smell (The aroma of freshly baked bread in a bakery)

 User Interface is the series of visual elements (screens, buttons, icons) that you
use to interact with a device.

 Wireframe is a visual representation of user interface, without visual design or

branding elements. (Sketch / template)
o The purpose is to define what the items on the page should be based
on user needs.

 UX Usability
o UX Look (Credibility, Trust, Harmony)
 How to create a site that inspires a sense of trust and credibility.
o UX Feel (Interaction, Reaction)
 User needs to have that sense of satisfaction that they can get
around without hassle.
o Usability (Functionality, Predictability)
 A site must give great functionality to deliver a good user
experience.

UX Design Methodology

 Good UX Design should be

o Learnability : A system should be easy to learn for user so user can get
things done rapidly.
o Memorability : A system should be easy to remember so user can return
to the system without learning it all again.
 o Reduced Error rate : A system should have low error rate and user can
easily recover if an error does occur.
o Efficiency : Expert user should be able to use the system efficiently.
o Satisfaction : Users should have motivating and entertaining experience.
o Trust : A system should enable users to trust the quality and validity of
the information and services.
o Enjoyment : A system should be enjoyable to use.

 In house methodology, PURITE

o Prepare – Understanding the industry and competitors.
o Understand – Work with experts and/or users to define the
requirements of the project correctly.
o Render – Develop all the pieces of the product. Must be focused and
have good communication with the team.
o Iterate – Create iteration through the entire lifecycle of the project.
o Test – Test every product to ensure the best quality.
o Enable – Make the product live and communicate with clients.

 Prototype is a simulation of the final product. Interactive mockup with any

degree of fidelity. The main purpose is to test whether the flow of the product
is smooth and consistent or not. Prototype is not the final product.

 Project Approach to UX Development

o Waterfall approach
 Treating steps of the project as separate.
 Needed approval of one phase before the next phase begins.
 Example: Design phase does not start until the define phase is
approved by stakeholders.
o Agile approach
 More flexible than waterfall model.
 Treating steps of the project as iteration to minimize overall risks
and allow the product to adapt to changes quickly.
 Multiple iterations are required to release a product or new
features.
o Modified approach
 A mixture between waterfall and agile approach.

Project Objectives and Approach & Requirements

 Objectives are precise tasks that need to be completed for the goal to be
achieved
  Solid Objectives must be
o Easy to understand : Avoid insider terminology.
o Direct : Use useful wording when prioritizing requirements.
o Measurable : Make concrete statement that can be measured to
determine your success.

 Project approach
o Plan the overall strategy and team structure.
o Define the project requirements.
o Design interaction and visual concepts.
o Develop, test and refine the solution.
o Deploy the solution via messaging, training, and planned launch.
o Extend the project by making recommendations for improvements.

 Process of Heuristic Analysis

o Gather product and project background knowledge.
o Choose the heuristics to use.
o Identifying areas where the heuristics are followed well or missed.
o Present your findings to the project team and stakeholders.

 Design challenge of UX projects

o The research phase is where you gather the project background
knowledge to make design decisions later.
o The design phase is where you work out which design will work and
how it will if together.
o The validation phase is where you identify which design actually works
with its intended audience.

 Gather ideas from stakeholders

o Outline roles and responsibilities
o Gather the right stakeholders
o Create plan for the meetings
o Run meetings efficiently

User Research

 Qualitative research is research that can be measured numerically.

 Quantitative research is research that helps understand why people do the

things they do and find knowledge based on the truth / real world events.
  Research techniques
o Interview
o Survey
o Group discussion
o Observation
o Card sorting
o Usability

Personas

 Personas are documents that describe typical target users.

o The purpose of personas is to create reliable reference of key audience
segments.
 To ensure personas are accurate representation of users
o Conduct user research : Who are your users and why are they using
your system?
o Condense the research : Look for characteristics that are relevant to the
system and its users.
o Brainstorm : Organize elements into persona group that represent your
target user.
o Refine : Combine and prioritize rough personas.
o Make them realistic : Develop the appropriate descriptions of each
personas background.

Content Strategy

 Content strategy plans for the creation, publication and governance of useful,
usable content.
o Substance refers to the types of content.
o Workflow explain the tools and process to ensure content appears to
the right people in the right time.
o Governance refers to the team structure.
o Structure refers to the metadata and structure of contents.

 Content Lifecycle
o Audit and Analysis
o Strategy
o Plan
o Create
o Maintain
Site Maps and Task Flows

 Site Maps

 Task Flows