SlideShare ist ein Scribd-Unternehmen logo
1 von 55
Downloaden Sie, um offline zu lesen
spring 2012   introduction
the course team

➝  Prof.Jeffrey Huang (responsible)
➝  teacher: Hendrik Knoche
➝  teaching assistants: Michal Fok, Oscar Bolanos
➝  guest lecturers – tba
course basics               

➝  6   credits
   ➝  2 h lecture
   ➝  4 h studio/lab
   ➝  6 h home based preparation
   ➝  no written exam
the course structure
➝  1  design brief
➝  4 design reviews
➝  13 interactive lectures/seminars
➝  13 studio sessions (attendance mandatory)
➝  1 sketch book
➝  reading assignments
➝  interactive exercises

  
all in English
assessment
the final grade is based on:
 the grades of four mandatory reviews "
     (submitted documentation and its presentation):
1.   results and design ideas from requirements capture (i)"
     through sketches, scenarios, storyboards and personas
2.   design idea presentation through first (lo-fi) prototype (i)
3.   interactive prototype / demonstrator on device (g)
4.   final presentation interactive prototype on device (g)"
     and
5.   participation in the class/studio (i) 
6.  sketch book (i)
7.   final short video (produced in week 14) (i)"
     ✱(i) = individual
    
✱(g) = group
assignment dates
➝  10th   Mar 
– Microsoft Imagine Cup summary"
              
 round 1 competition deadline 
➝  19th Mar   
– 1st review (rc results + ideas)
➝  2nd April  
– 2nd review (design solutions)
➝  30th April 
– 3rd review (prototype)
➝  21st May   
– final review
 
documentation for each review is due on the
   Sunday before the review at 12:00
 
✱ late submissions are subject to penalty
how is your design evaluated? 

by a panel of experts
Q: 
how do you assess concepts or designs?
A: 
Scott Jenson (former director of Symbian):
     
“First I ll be asking ‘what’s the value of
     
this? , that is ‘Will people really want
     
it? [… the] second is simplicity.” Jones & Marsden (2006)
 

 
 
“…being humble as these [designs] are
     
evaluated and seen to fall short, and to need
     
refining.” 
  
   
Jones & Marsden (2006)
what is this course?
Personal Interaction Studio focuses on
  ➝  mobile  devices as the platform (personal) 
  ➝  interaction design
  ➝  studio as the teaching format



  ➝  the  idea is to generate, communicate, evaluate,
     iterate and improve design ideas through synthesis
     by re-defining problem and the solution

  ➝  it   is NOT a programming course
resources
➝  all communication and further readings, links etc.
   will go through moodle 
➝  please enroll with the key: persint


➝  http://moodle.epfl.ch/course/view.php?id=6881
syllabus
1.    introduction
2.    data collection
3.    analysis
4.    design techniques
5.    mobile i/o
6.    screen design
7.    prototyping
8.    -14. guest lectures and seminar
relation to design process
➝  understand   brief
➝  research background – refine problem
➝  ideate candidates
➝  prototype solution(s)
➝  select solution
➝  implement delivery
➝  learn from feedback
example
➝  Don’t   forget your friends!
   ➝  “Can’t   do it today. But I’ll call you next time.”
things you will learn (about)
➝  brainstorming, ice breaking
➝  interviewing
➝  qualitative analysis
➝  sketching
➝  personas
➝  scenarios
➝  storyboarding
➝  elevator pitch
➝  lo-fi prototyping 
➝  hi-fi prototyping
➝  designing, critiquing, re-designing
➝  communicating your ideas – show and tell, posters,
   presentation "
topics addressed in this class
➝  design  thinking 
➝  interaction design
➝  user experience
design brief
People’s physical and mental health are one of the most
precious goods available to them.

Mobile phones have become a large collection platform for
sensor data either direct through e.g. GPS and
accelerometer or indirectly by providing sensor data from
other sources, which can be used to inform people’s
decision making and daily life.

Your task is to design an application that empowers people
to leverage sensed data for their well-being in terms of either:
- personal health, "
- environmental health or "
- social health.
imagine cup 2011
attention
➝  http://www.youtube.com/watch?
  v=vJG698U2Mvo
more details…
✱
attribution: parts of these slides are based on Angela Sasse
  and Sven Laqua s course on interaction design at UCL
why mobiles?




“The most profound technologies are those that disappear.” Mark Weiser
mobile life
what is design?
    
hard to grasp – industrial design, graphic design,
     software design, interface design, product design
     …

 
in interaction design (Fallman 2003) :
➝  scientific/eng. process (conservative)
➝  art form (romantic)
➝  ad-hoc activity (pragmatic, bricoleur)
 
none are adequate – design is unfolding "
   both problem and solution evolve through sketching
   (prototyping)
why design?
➝  post  WWII declining American manufacturing
   quality disillusioned purchasers who, after being
   attracted by external style, found products
   unsatisfactory in use
➝  American industry got decimated from 1960s on
   from imports from Japan and Germany where
   greater attention to production quality and a more
   holistic approach to design were the norm.
➝  key differentiator for products
➝  key skill in IT – differentiator for employees
why design digital products
➝  digital   products shortcomings:
   ➝  requirecomputer-centred thinking
   ➝  poor behaviour, rudeness



➝  reasons
   ➝  ignorance  about users
   ➝  conflicting interests
   ➝  lack of process
the design funnel



  concept                                                                  concept
generation                                                                 selected




 iterative   overall concepts   exploratory   clarification   resolution
 granularity          general       coarse        medium            fine
sketchbook
➝  jotdown and annotate ideas (no idea is bad)
➝  explore & refine
➝  develop variations, alternatives and details
➝  refer back, reflect
➝  record other good ideas you see 
➝  collection material (pictures, screen shots), tape
   them
what is interaction design (IxD)? 

➝  it's   about the design of behavior"
  http://designmind.frogdesign.com/blog/behaving-badly-in-vancouver.html

➝  designing          the mechanisms for interacting with a
   product (Cooper 2007)
➝  …designing interactive products to support
   people in their everyday and working life 
  
(Preece et al, 2002)
interaction design within a company
➝  management
➝  marketing
➝  engineering
➝  design   team

How to achieve buy-in for your ideas? How do you
   communicate your ideas to them? What’s the
   language – same as yours? 
Scott Jenson: 
  
“Design is about semantics and syntax. First you
   need to see what people do and want – the
   semantics and then you have to find a way to
   make that possible – the syntax.”
jobs - interaction design
responsibilities include: 
➝    lead interaction design (entire product lifecycle), tools and deliverables,
     including:
      ➝    persona development 
      ➝    use cases, user task flows
      ➝    user interface concepts and interaction models 
      ➝    annotated wireframes
      ➝    information architecture
      ➝    documentation of design concept in detailed UI specs 
➝    effectively communicate interaction models and design ideas to the
     team, leveraging above tools / documents
➝    identify appropriate user research techniques and metrics for gauging
     success
➝    guide product direction and set UI requirements based on user
     research, functional requirements, and business goals
➝    recommend concepts for testing and interpret consumer feedback /
     results
design philosophy
➝  centred   on human needs
   ➝  individualor group
   ➝  support goals and activities
   ➝  design technology to fit human needs and
     characteristics
➝  involve users whenever possible
➝  mix analytical, creative and pragmatic approaches
➝  pick from range of design tools
➝  use existing best practices but not uncritically
➝  monitor design process and reflect on it
what is UX?
 “User experience encompasses all aspects of the end-
 user's interaction with the company, its services, and its
 products. The first requirement for an exemplary user
 experience is to meet the exact needs of the customer,
 without fuss or bother. Next comes simplicity and elegance
 that produce products that are a joy to own, a joy to use.
 True user experience goes far beyond giving customers
 what they say they want, or providing checklist features. In
 order to achieve high-quality user experience in a
 company's offerings there must be a seamless merging of
 the services of multiple disciplines, including engineering,
 marketing, graphical and industrial design, and interface
 design.”
                                              Nielsen, Norman Group
user-centred
 “User experience and interface design in the context
 of creating software represents an approach that
 puts the user, rather than the system, at the center
 of the process. This philosophy, called user-
 centered design, incorporates user concerns and
 advocacy from the beginning of the design process
 and dictates the needs of the user should be
 foremost in any design decisions.”
                                              Microsoft
product centred
 “The user experience for Mac OS X applications
 encompasses the visual appearance, interactive
 behavior, and assistive capabilities of software. With
 the Aqua graphical user interface, Universal Access
 features, and user-assistive technologies like the
 Address Book framework, Apple Help, and
 VoiceOver, you can deliver the cohesive and
 professional user experience that Macintosh users
 have come to expect. It's easy to leverage the user
 experience technologies of Mac OS X to make great
 Macintosh software.”
                                                   Apple
bad UX
➝  “Technology    that does not work the way they
   expect makes people feel stupid.” 
➝  “if you intend to drive people away from your site,
   it’s hard to imagine a more effective approach
   than making them feel stupid.”
➝  JJ Garrett: Elements of User Experience
impact on users’ lives
➝  User: “… so I have all these files and documents, all over
   my desktop, different versions of documents in different
   folders, and documents I don’t need any more. I never get
   round to tidying up. I keep emails because I might need
   because of the address, or the content. But I never get
   round to putting them into the address book and deleting
   the mails, so they just pile up. My electronic workspace is
   a mess.”
➝  Q: How does that make you feel?
➝  User: [thinks] “It makes me feel that I am a bad person.”



     From Richard Boardman’s (2005) PhD thesis on 
     Improving Tool Support for Personal Information Management
user experience (UX)

                     industrial/graphic
                          design

                          form


        behaviour                  content
                               information architecture,
       interaction designer        animation etc.

                                                           Cooper 2006
lived experience
 any account of what is often
 called the user experience
 must take into consideration
 the ‘felt’ experience:
 emotional, intellectual, and
 sensual aspects of our
 interactions with technology.
 
 “We don't just use
 technology, we live with it.”
 


 John McCarthy, Peter Wright 2004: Technology as experience. 
 MIT Press
framework for design
                                             and interaction takes place in a
   has general & specific characteristics                   CONTEXT

                                            physical
                                            incl. other
    USER                           SYSTEM   technologies



                  interacts with

      to attain                             social

                                            cultural
        GOAL


                                            temporal
Garret’s planes of UX
➝  strategy  – what user wants to achieve
➝  scope – what functions and features are required
➝  structure – navigation – how are screens linked
   and grouped
➝  skeleton – placement of buttons, tabs, blocks of
   text, pictures
➝  surface – series of pages in high fidelity
Garret’s planes of UX
                                        concrete

        surface
                                                      “When designers make choices that
                                                      do not align with planes above and
                                                      below, you end up with a jumble of
                   skeleton
                                                      components that don’t fit.”
                                                      
                           structure




                                         scope

Garrett’s planes Of UXP

                                                  strategy
              abstract
levels of interaction

user’s/corporate goals
   output in the real world
   GOAL LEVEL

user’s knowledge 
        computer’s representation   TASK 
of task domain
           of task domain
             LEVEL



user’s knowledge 
        computer command            DIALOGUE
of language
              language
                   LEVEL




user’s hands, eyes
       computer keyboard,          INPUT/
                          display
                    OUTPUT
                                                      LEVEL
human structures
         Computer structures
personas
➝  represent user groups 
➝  system may be used by
   one or several personas
     ➝    different characteristics
     ➝    different goals
➝    e.g. buyers of a new car
     ➝  Jean-David (playboy): "
        go fast, impress women
     ➝  Aurelie (soccer mum): "
        fit in many kids, be safe
     ➝  Bob (the Builder): "
        haul big loads, be reliable
scenarios
➝  persona-based     scenarios "
   concise narrative description of how persona
   interacts with system to achieve goals
➝  context-based scenarios "
   how product can serve needs of persona, created
   before any design is done
➝  to key path scenarios – refined with design
➝  to validation scenarios – based on ❛what … if❜"
   focus on illustrate requirements (the what), "
   top-down decomposition to functionality (the how)
storyboards
scenarios vs. use cases
 ❝… scenarios are an interactive means of defining
 the behaviour of a product from the standpoint of
 specific users (personas). This includes not only the
 functionality of the system, but the priority of
 functions and the way those functions are
 expressed in terms of what the user sees and how
 she interacts with the system. 
 use cases, on the other hand, are based on
 exhaustive descriptions of the functional
 requirements of the system, often of a transactional
 nature, focussing on low-level user actions and
 accompanying system response.❞
 Cooper 2006
eliciting UX requirements
➝  in-depth qualitative data
➝  interviews
➝  in-depth analysis such as Grounded Theory and
   Discourse Analysis
➝  ethnographic methods
   ➝  mostly observational
   ➝  can be combined with surveys, interviews, qualitative
     studies
general reading
➝  recommended     books (available at EPF-BIB)
  ➝  Cooper,Reimann & Cronin (2007) "
    About Face 3, Wiley
  ➝  Jones& Marsden (2004) "
    Mobile Interaction Design, Wiley
  ➝  ScottMcCloud (1993)"
    Understanding Comics, Harper Perennial (on order)
  ➝  Schneiderman & Plaisant (2010) "
    Designing the User Interface. Addison-Wesley. 
  ➝  Preece, Rogers & Sharp (2002)"
    Interaction Design, Wiley
summary
➝  focus  on design approaches, methods and tools
➝  learning by doing
➝  interaction design is a relatively young and rapidly
   developing field
➝  interaction designers have to address new
   technologies and adapt their methods and tools
➝  collect artefacts: "
   paper, pictures, audio, video
practical part – design techniques
brainstorming
➝  group  size <10 – ideally between 5-7 + facilitator
➝  find and set up comfortable space
➝  appoint recorder - up-coming ideas on shared
   display, flip chart, whiteboard
➝  ice-breaking exercise – to familiarize members of
   groups
➝  define problem clearly
➝  goal: generate as many ideas as possible

    
adapted from www.mindtools.com/brainstm.html
brainstorming – how to
➝  address  what, how, when, where and why
➝  give people time on their own (5 minutes silence)
   at beginning then ask to share them
➝  encourage 
   ➝  todevelop ideas of others further or use as new seeds
   ➝  enthusiastic, fun, criticism OK
➝  includeeveryone to contribute (practical and
  impractical ideas) and develop
ice breaker
➝  effective    to start a training, team-building event
➝  goal:    
   ➝  get to know each other 
   ➝  get into the event
   ➝  become comfortable contributing to event
   ➝  establish level playing field
   ➝  create common sense of purpose

➝  ingredients:    ice, a breaker (method), a facilitator
ice breaker – when to use
if participants
➝  come from different backgrounds
➝  need to bond quickly to work on common project
   or goal
➝  are unfamiliar with topic at hand
➝  don t know the facilitator but should and vice
   versa
the ice
participants have 
   ➝  not  met before
   ➝  different age, status or levels in an organization
   ➝  different backgrounds – different perceptions of each
     other
choose method accordingly &
don t try to uncover the whole iceberg
ice breaker – methods (introductory)
everyone draws name, nationality, focus of study
and one human element, e.g.:
   ➝  one  little known fact about me
   ➝  true/false - three to four short statements – the group
     guesses which one is false, or
   ➝  pair interview – interview and then introduce partner to
     the group
   ➝  trading cards



➝  lo-fi   social network
assignments
➝  fill   in questionnaire

Weitere ähnliche Inhalte

Was ist angesagt?

Ni week no designer, no problem
Ni week no designer, no problem Ni week no designer, no problem
Ni week no designer, no problem Jenica Welch
 
General UX activities & process overview
General UX activities & process overviewGeneral UX activities & process overview
General UX activities & process overviewBen Melbourne
 
User-centered UX: Bringing the User into the Design Process
User-centered UX: Bringing the User into the Design ProcessUser-centered UX: Bringing the User into the Design Process
User-centered UX: Bringing the User into the Design ProcessDave Cooksey
 
Introduction to ux
Introduction to uxIntroduction to ux
Introduction to uxBill Darby
 
ePortfolio Forum: Badge (l)Earner Journey Mapping #eportforum
ePortfolio Forum: Badge (l)Earner Journey Mapping #eportforumePortfolio Forum: Badge (l)Earner Journey Mapping #eportforum
ePortfolio Forum: Badge (l)Earner Journey Mapping #eportforumJoyce Seitzinger
 
Bringing the User Into the Process with Design Thinking
Bringing the User Into the Process with Design ThinkingBringing the User Into the Process with Design Thinking
Bringing the User Into the Process with Design ThinkingJacqueline L. Frank
 
Designing a Cohesive Customer Experience
Designing a Cohesive Customer ExperienceDesigning a Cohesive Customer Experience
Designing a Cohesive Customer ExperienceUsabilitySciences
 
What is UX Design?
What is UX Design?What is UX Design?
What is UX Design?Baris Erkol
 
Connected Design - ULearn 2016
Connected Design - ULearn 2016Connected Design - ULearn 2016
Connected Design - ULearn 2016Joyce Seitzinger
 
Creating an Online Community for User Research
Creating an Online Community for User ResearchCreating an Online Community for User Research
Creating an Online Community for User ResearchTom Vollaro
 
10 Learner Experience Powers from Experience Girl - #imoot16 Agents of Change
10 Learner Experience Powers from Experience Girl - #imoot16 Agents of Change10 Learner Experience Powers from Experience Girl - #imoot16 Agents of Change
10 Learner Experience Powers from Experience Girl - #imoot16 Agents of ChangeJoyce Seitzinger
 
UXSG2014 Lightning Talks - The MUDD Model - Marrying UX, Design and Developme...
UXSG2014 Lightning Talks - The MUDD Model - Marrying UX, Design and Developme...UXSG2014 Lightning Talks - The MUDD Model - Marrying UX, Design and Developme...
UXSG2014 Lightning Talks - The MUDD Model - Marrying UX, Design and Developme...ux singapore
 
LearningCafe Unconference - Mapping The Journey
LearningCafe Unconference - Mapping The Journey LearningCafe Unconference - Mapping The Journey
LearningCafe Unconference - Mapping The Journey Joyce Seitzinger
 
2014 Evolving Your UX Process 1up
2014 Evolving Your UX Process 1up2014 Evolving Your UX Process 1up
2014 Evolving Your UX Process 1upTom Brinck
 
UX Process — From Idea To Implementation
UX Process — From Idea To ImplementationUX Process — From Idea To Implementation
UX Process — From Idea To ImplementationDan Malarkey
 
Selling UX in Your Organization - Stir Trek 2012
Selling UX in Your Organization - Stir Trek 2012Selling UX in Your Organization - Stir Trek 2012
Selling UX in Your Organization - Stir Trek 2012Carol Smith
 
User Experience Roles Competencies
User Experience  Roles  CompetenciesUser Experience  Roles  Competencies
User Experience Roles CompetenciesSameer Chavan
 
Prototyping is the panacea
Prototyping is the panaceaPrototyping is the panacea
Prototyping is the panaceaMichael Meikson
 

Was ist angesagt? (20)

Ni week no designer, no problem
Ni week no designer, no problem Ni week no designer, no problem
Ni week no designer, no problem
 
Engineering UX
Engineering UXEngineering UX
Engineering UX
 
General UX activities & process overview
General UX activities & process overviewGeneral UX activities & process overview
General UX activities & process overview
 
User-centered UX: Bringing the User into the Design Process
User-centered UX: Bringing the User into the Design ProcessUser-centered UX: Bringing the User into the Design Process
User-centered UX: Bringing the User into the Design Process
 
Introduction to ux
Introduction to uxIntroduction to ux
Introduction to ux
 
ePortfolio Forum: Badge (l)Earner Journey Mapping #eportforum
ePortfolio Forum: Badge (l)Earner Journey Mapping #eportforumePortfolio Forum: Badge (l)Earner Journey Mapping #eportforum
ePortfolio Forum: Badge (l)Earner Journey Mapping #eportforum
 
Bringing the User Into the Process with Design Thinking
Bringing the User Into the Process with Design ThinkingBringing the User Into the Process with Design Thinking
Bringing the User Into the Process with Design Thinking
 
Designing a Cohesive Customer Experience
Designing a Cohesive Customer ExperienceDesigning a Cohesive Customer Experience
Designing a Cohesive Customer Experience
 
What is UX Design?
What is UX Design?What is UX Design?
What is UX Design?
 
Connected Design - ULearn 2016
Connected Design - ULearn 2016Connected Design - ULearn 2016
Connected Design - ULearn 2016
 
Creating an Online Community for User Research
Creating an Online Community for User ResearchCreating an Online Community for User Research
Creating an Online Community for User Research
 
Crafting Experience
Crafting ExperienceCrafting Experience
Crafting Experience
 
10 Learner Experience Powers from Experience Girl - #imoot16 Agents of Change
10 Learner Experience Powers from Experience Girl - #imoot16 Agents of Change10 Learner Experience Powers from Experience Girl - #imoot16 Agents of Change
10 Learner Experience Powers from Experience Girl - #imoot16 Agents of Change
 
UXSG2014 Lightning Talks - The MUDD Model - Marrying UX, Design and Developme...
UXSG2014 Lightning Talks - The MUDD Model - Marrying UX, Design and Developme...UXSG2014 Lightning Talks - The MUDD Model - Marrying UX, Design and Developme...
UXSG2014 Lightning Talks - The MUDD Model - Marrying UX, Design and Developme...
 
LearningCafe Unconference - Mapping The Journey
LearningCafe Unconference - Mapping The Journey LearningCafe Unconference - Mapping The Journey
LearningCafe Unconference - Mapping The Journey
 
2014 Evolving Your UX Process 1up
2014 Evolving Your UX Process 1up2014 Evolving Your UX Process 1up
2014 Evolving Your UX Process 1up
 
UX Process — From Idea To Implementation
UX Process — From Idea To ImplementationUX Process — From Idea To Implementation
UX Process — From Idea To Implementation
 
Selling UX in Your Organization - Stir Trek 2012
Selling UX in Your Organization - Stir Trek 2012Selling UX in Your Organization - Stir Trek 2012
Selling UX in Your Organization - Stir Trek 2012
 
User Experience Roles Competencies
User Experience  Roles  CompetenciesUser Experience  Roles  Competencies
User Experience Roles Competencies
 
Prototyping is the panacea
Prototyping is the panaceaPrototyping is the panacea
Prototyping is the panacea
 

Andere mochten auch

PxS’12 - week 4 - qualitative analysis
PxS’12 - week 4 - qualitative analysisPxS’12 - week 4 - qualitative analysis
PxS’12 - week 4 - qualitative analysishendrikknoche
 
PxS'12 - week 10 - screen design
PxS'12 - week 10 - screen designPxS'12 - week 10 - screen design
PxS'12 - week 10 - screen designhendrikknoche
 
PxS’12 - week 6 - conceptual design x
PxS’12 - week 6 - conceptual design xPxS’12 - week 6 - conceptual design x
PxS’12 - week 6 - conceptual design xhendrikknoche
 
PxS’12 - week 8 mobile - systems
PxS’12 - week 8 mobile - systemsPxS’12 - week 8 mobile - systems
PxS’12 - week 8 mobile - systemshendrikknoche
 
EPFL PxS - week 2 interviewing
EPFL PxS - week 2 interviewingEPFL PxS - week 2 interviewing
EPFL PxS - week 2 interviewinghendrikknoche
 
PxS’12 - week 8 - mobile i/o
PxS’12 - week 8 - mobile i/oPxS’12 - week 8 - mobile i/o
PxS’12 - week 8 - mobile i/ohendrikknoche
 
PxS'12 - week 2 interviewing
PxS'12 - week 2 interviewingPxS'12 - week 2 interviewing
PxS'12 - week 2 interviewinghendrikknoche
 
EPFL - PxS, week 5/6 - from requirements to design
EPFL - PxS, week 5/6 -  from requirements to designEPFL - PxS, week 5/6 -  from requirements to design
EPFL - PxS, week 5/6 - from requirements to designhendrikknoche
 

Andere mochten auch (8)

PxS’12 - week 4 - qualitative analysis
PxS’12 - week 4 - qualitative analysisPxS’12 - week 4 - qualitative analysis
PxS’12 - week 4 - qualitative analysis
 
PxS'12 - week 10 - screen design
PxS'12 - week 10 - screen designPxS'12 - week 10 - screen design
PxS'12 - week 10 - screen design
 
PxS’12 - week 6 - conceptual design x
PxS’12 - week 6 - conceptual design xPxS’12 - week 6 - conceptual design x
PxS’12 - week 6 - conceptual design x
 
PxS’12 - week 8 mobile - systems
PxS’12 - week 8 mobile - systemsPxS’12 - week 8 mobile - systems
PxS’12 - week 8 mobile - systems
 
EPFL PxS - week 2 interviewing
EPFL PxS - week 2 interviewingEPFL PxS - week 2 interviewing
EPFL PxS - week 2 interviewing
 
PxS’12 - week 8 - mobile i/o
PxS’12 - week 8 - mobile i/oPxS’12 - week 8 - mobile i/o
PxS’12 - week 8 - mobile i/o
 
PxS'12 - week 2 interviewing
PxS'12 - week 2 interviewingPxS'12 - week 2 interviewing
PxS'12 - week 2 interviewing
 
EPFL - PxS, week 5/6 - from requirements to design
EPFL - PxS, week 5/6 -  from requirements to designEPFL - PxS, week 5/6 -  from requirements to design
EPFL - PxS, week 5/6 - from requirements to design
 

Ähnlich wie PxS'12 - week 1 - Introduction

Open Minded? Software Engineer to a UX Engineer. Ask me how. by Micael Diaz d...
Open Minded? Software Engineer to a UX Engineer. Ask me how. by Micael Diaz d...Open Minded? Software Engineer to a UX Engineer. Ask me how. by Micael Diaz d...
Open Minded? Software Engineer to a UX Engineer. Ask me how. by Micael Diaz d...DEVCON
 
DIY Usability
DIY UsabilityDIY Usability
DIY UsabilityJan Moons
 
Design Thinking Dallas by Chris Bernard
Design Thinking Dallas by Chris BernardDesign Thinking Dallas by Chris Bernard
Design Thinking Dallas by Chris BernardChris Bernard
 
UX Evolution Mindset & Methods
UX Evolution Mindset & MethodsUX Evolution Mindset & Methods
UX Evolution Mindset & MethodsDanforth
 
1_Introduction to Interaction Design.pdf
1_Introduction to Interaction Design.pdf1_Introduction to Interaction Design.pdf
1_Introduction to Interaction Design.pdfOmarShahid15
 
Design process interaction design basics
Design process interaction design basicsDesign process interaction design basics
Design process interaction design basicsPreeti Mishra
 
EPFL - PxS, week 4 - UX design techniques
EPFL - PxS, week 4 - UX design techniquesEPFL - PxS, week 4 - UX design techniques
EPFL - PxS, week 4 - UX design techniqueshendrikknoche
 
User Experience: An Industry (Always) in Transition
User Experience: An Industry (Always) in TransitionUser Experience: An Industry (Always) in Transition
User Experience: An Industry (Always) in TransitionGino Zahnd
 
User Experience and Prototyping
User Experience and PrototypingUser Experience and Prototyping
User Experience and PrototypingKshitiz Anand
 
The Professional Design Process
The Professional Design ProcessThe Professional Design Process
The Professional Design Processugencarelle
 
eXtreme User eXperience (XUX) - How one team melded UX with XP
eXtreme User eXperience (XUX) - How one team melded UX with XPeXtreme User eXperience (XUX) - How one team melded UX with XP
eXtreme User eXperience (XUX) - How one team melded UX with XPMichael Rawling
 
Role of UX Design in Building Products: How I Stopped Designing and Started t...
Role of UX Design in Building Products: How I Stopped Designing and Started t...Role of UX Design in Building Products: How I Stopped Designing and Started t...
Role of UX Design in Building Products: How I Stopped Designing and Started t...Praneet Koppula
 
UI/UX Designer in the year 2020 | Developers Day Nov.19
UI/UX Designer in the year 2020 | Developers Day Nov.19UI/UX Designer in the year 2020 | Developers Day Nov.19
UI/UX Designer in the year 2020 | Developers Day Nov.19Lena Lekkou
 
The UX Toolbelt for Developers
The UX Toolbelt for DevelopersThe UX Toolbelt for Developers
The UX Toolbelt for DevelopersSarah Dutkiewicz
 
Richard Marsh, Enterprising User Experience - Flex and the city
Richard Marsh, Enterprising User Experience - Flex and the cityRichard Marsh, Enterprising User Experience - Flex and the city
Richard Marsh, Enterprising User Experience - Flex and the cityRichard Marsh
 
Intro to User Centered Design Workshop
Intro to User Centered Design WorkshopIntro to User Centered Design Workshop
Intro to User Centered Design WorkshopPatrick McNeil
 
24 Hours of UX - Agile + UX: Good, Bad, Ugly
24 Hours of UX - Agile + UX: Good, Bad, Ugly24 Hours of UX - Agile + UX: Good, Bad, Ugly
24 Hours of UX - Agile + UX: Good, Bad, UglyJoshua Randall
 

Ähnlich wie PxS'12 - week 1 - Introduction (20)

Open Minded? Software Engineer to a UX Engineer. Ask me how. by Micael Diaz d...
Open Minded? Software Engineer to a UX Engineer. Ask me how. by Micael Diaz d...Open Minded? Software Engineer to a UX Engineer. Ask me how. by Micael Diaz d...
Open Minded? Software Engineer to a UX Engineer. Ask me how. by Micael Diaz d...
 
DIY Usability
DIY UsabilityDIY Usability
DIY Usability
 
Design Thinking Dallas by Chris Bernard
Design Thinking Dallas by Chris BernardDesign Thinking Dallas by Chris Bernard
Design Thinking Dallas by Chris Bernard
 
UX Evolution Mindset & Methods
UX Evolution Mindset & MethodsUX Evolution Mindset & Methods
UX Evolution Mindset & Methods
 
1_Introduction to Interaction Design.pdf
1_Introduction to Interaction Design.pdf1_Introduction to Interaction Design.pdf
1_Introduction to Interaction Design.pdf
 
What is UX v1
What is UX v1What is UX v1
What is UX v1
 
What is UX v2
What is UX v2What is UX v2
What is UX v2
 
Design process interaction design basics
Design process interaction design basicsDesign process interaction design basics
Design process interaction design basics
 
EPFL - PxS, week 4 - UX design techniques
EPFL - PxS, week 4 - UX design techniquesEPFL - PxS, week 4 - UX design techniques
EPFL - PxS, week 4 - UX design techniques
 
User Experience: An Industry (Always) in Transition
User Experience: An Industry (Always) in TransitionUser Experience: An Industry (Always) in Transition
User Experience: An Industry (Always) in Transition
 
User Experience and Prototyping
User Experience and PrototypingUser Experience and Prototyping
User Experience and Prototyping
 
The Professional Design Process
The Professional Design ProcessThe Professional Design Process
The Professional Design Process
 
eXtreme User eXperience (XUX) - How one team melded UX with XP
eXtreme User eXperience (XUX) - How one team melded UX with XPeXtreme User eXperience (XUX) - How one team melded UX with XP
eXtreme User eXperience (XUX) - How one team melded UX with XP
 
Role of UX Design in Building Products: How I Stopped Designing and Started t...
Role of UX Design in Building Products: How I Stopped Designing and Started t...Role of UX Design in Building Products: How I Stopped Designing and Started t...
Role of UX Design in Building Products: How I Stopped Designing and Started t...
 
UI/UX Designer in the year 2020 | Developers Day Nov.19
UI/UX Designer in the year 2020 | Developers Day Nov.19UI/UX Designer in the year 2020 | Developers Day Nov.19
UI/UX Designer in the year 2020 | Developers Day Nov.19
 
Myth & fact - Designing for UX
Myth & fact - Designing for UXMyth & fact - Designing for UX
Myth & fact - Designing for UX
 
The UX Toolbelt for Developers
The UX Toolbelt for DevelopersThe UX Toolbelt for Developers
The UX Toolbelt for Developers
 
Richard Marsh, Enterprising User Experience - Flex and the city
Richard Marsh, Enterprising User Experience - Flex and the cityRichard Marsh, Enterprising User Experience - Flex and the city
Richard Marsh, Enterprising User Experience - Flex and the city
 
Intro to User Centered Design Workshop
Intro to User Centered Design WorkshopIntro to User Centered Design Workshop
Intro to User Centered Design Workshop
 
24 Hours of UX - Agile + UX: Good, Bad, Ugly
24 Hours of UX - Agile + UX: Good, Bad, Ugly24 Hours of UX - Agile + UX: Good, Bad, Ugly
24 Hours of UX - Agile + UX: Good, Bad, Ugly
 

Mehr von hendrikknoche

PxS'12 - week 12 - ux evaluation
PxS'12 - week 12 - ux evaluationPxS'12 - week 12 - ux evaluation
PxS'12 - week 12 - ux evaluationhendrikknoche
 
PxS’12 - week 10 - screen design
PxS’12 - week 10 - screen designPxS’12 - week 10 - screen design
PxS’12 - week 10 - screen designhendrikknoche
 
PxS’12 - week 6 - from requirements to design x.ppt
PxS’12 - week 6 - from requirements to design x.pptPxS’12 - week 6 - from requirements to design x.ppt
PxS’12 - week 6 - from requirements to design x.ppthendrikknoche
 
PxS’12 - week 4 - UX design techniques
PxS’12 - week 4 - UX design techniquesPxS’12 - week 4 - UX design techniques
PxS’12 - week 4 - UX design techniqueshendrikknoche
 
PxS'12 - week 3 - creative design
PxS'12 - week 3 - creative designPxS'12 - week 3 - creative design
PxS'12 - week 3 - creative designhendrikknoche
 
PxS'12 - week 2 - data collection
PxS'12 - week 2 - data collectionPxS'12 - week 2 - data collection
PxS'12 - week 2 - data collectionhendrikknoche
 
EPFL PxS week 12 - UX design techniques
EPFL PxS week 12 - UX design techniquesEPFL PxS week 12 - UX design techniques
EPFL PxS week 12 - UX design techniqueshendrikknoche
 
EPFL - PxS, week 8 - conceptual design
EPFL - PxS, week 8 - conceptual designEPFL - PxS, week 8 - conceptual design
EPFL - PxS, week 8 - conceptual designhendrikknoche
 
EPFL - PxS, week 3, studio, short qualitative analysis primer
EPFL - PxS, week 3, studio, short qualitative analysis primerEPFL - PxS, week 3, studio, short qualitative analysis primer
EPFL - PxS, week 3, studio, short qualitative analysis primerhendrikknoche
 
EPFL - PxS, week 3 - creative design
EPFL - PxS, week 3 - creative designEPFL - PxS, week 3 - creative design
EPFL - PxS, week 3 - creative designhendrikknoche
 
EPFL - PxS, week 2 - data collection
EPFL - PxS, week 2 - data collectionEPFL - PxS, week 2 - data collection
EPFL - PxS, week 2 - data collectionhendrikknoche
 

Mehr von hendrikknoche (11)

PxS'12 - week 12 - ux evaluation
PxS'12 - week 12 - ux evaluationPxS'12 - week 12 - ux evaluation
PxS'12 - week 12 - ux evaluation
 
PxS’12 - week 10 - screen design
PxS’12 - week 10 - screen designPxS’12 - week 10 - screen design
PxS’12 - week 10 - screen design
 
PxS’12 - week 6 - from requirements to design x.ppt
PxS’12 - week 6 - from requirements to design x.pptPxS’12 - week 6 - from requirements to design x.ppt
PxS’12 - week 6 - from requirements to design x.ppt
 
PxS’12 - week 4 - UX design techniques
PxS’12 - week 4 - UX design techniquesPxS’12 - week 4 - UX design techniques
PxS’12 - week 4 - UX design techniques
 
PxS'12 - week 3 - creative design
PxS'12 - week 3 - creative designPxS'12 - week 3 - creative design
PxS'12 - week 3 - creative design
 
PxS'12 - week 2 - data collection
PxS'12 - week 2 - data collectionPxS'12 - week 2 - data collection
PxS'12 - week 2 - data collection
 
EPFL PxS week 12 - UX design techniques
EPFL PxS week 12 - UX design techniquesEPFL PxS week 12 - UX design techniques
EPFL PxS week 12 - UX design techniques
 
EPFL - PxS, week 8 - conceptual design
EPFL - PxS, week 8 - conceptual designEPFL - PxS, week 8 - conceptual design
EPFL - PxS, week 8 - conceptual design
 
EPFL - PxS, week 3, studio, short qualitative analysis primer
EPFL - PxS, week 3, studio, short qualitative analysis primerEPFL - PxS, week 3, studio, short qualitative analysis primer
EPFL - PxS, week 3, studio, short qualitative analysis primer
 
EPFL - PxS, week 3 - creative design
EPFL - PxS, week 3 - creative designEPFL - PxS, week 3 - creative design
EPFL - PxS, week 3 - creative design
 
EPFL - PxS, week 2 - data collection
EPFL - PxS, week 2 - data collectionEPFL - PxS, week 2 - data collection
EPFL - PxS, week 2 - data collection
 

Kürzlich hochgeladen

Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...DianaGray10
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationIES VE
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesMd Hossain Ali
 
How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?IES VE
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostMatt Ray
 
Computer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsComputer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsSeth Reyes
 
20230202 - Introduction to tis-py
20230202 - Introduction to tis-py20230202 - Introduction to tis-py
20230202 - Introduction to tis-pyJamie (Taka) Wang
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Adtran
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024SkyPlanner
 
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfMachine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfAijun Zhang
 
Basic Building Blocks of Internet of Things.
Basic Building Blocks of Internet of Things.Basic Building Blocks of Internet of Things.
Basic Building Blocks of Internet of Things.YounusS2
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdfPedro Manuel
 
NIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopNIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopBachir Benyammi
 
UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6DianaGray10
 
OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureEric D. Schabell
 
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDELiveplex
 
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdf
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdfIaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdf
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdfDaniel Santiago Silva Capera
 
VoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXVoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXTarek Kalaji
 
Designing A Time bound resource download URL
Designing A Time bound resource download URLDesigning A Time bound resource download URL
Designing A Time bound resource download URLRuncy Oommen
 
Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)Commit University
 

Kürzlich hochgeladen (20)

Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
 
How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?How Accurate are Carbon Emissions Projections?
How Accurate are Carbon Emissions Projections?
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
 
Computer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and HazardsComputer 10: Lesson 10 - Online Crimes and Hazards
Computer 10: Lesson 10 - Online Crimes and Hazards
 
20230202 - Introduction to tis-py
20230202 - Introduction to tis-py20230202 - Introduction to tis-py
20230202 - Introduction to tis-py
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024
 
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfMachine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdf
 
Basic Building Blocks of Internet of Things.
Basic Building Blocks of Internet of Things.Basic Building Blocks of Internet of Things.
Basic Building Blocks of Internet of Things.
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdf
 
NIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 WorkshopNIST Cybersecurity Framework (CSF) 2.0 Workshop
NIST Cybersecurity Framework (CSF) 2.0 Workshop
 
UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6
 
OpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability AdventureOpenShift Commons Paris - Choose Your Own Observability Adventure
OpenShift Commons Paris - Choose Your Own Observability Adventure
 
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
 
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdf
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdfIaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdf
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdf
 
VoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXVoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBX
 
Designing A Time bound resource download URL
Designing A Time bound resource download URLDesigning A Time bound resource download URL
Designing A Time bound resource download URL
 
Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)Crea il tuo assistente AI con lo Stregatto (open source python framework)
Crea il tuo assistente AI con lo Stregatto (open source python framework)
 

PxS'12 - week 1 - Introduction

  • 1. spring 2012 introduction
  • 2. the course team ➝  Prof.Jeffrey Huang (responsible) ➝  teacher: Hendrik Knoche ➝  teaching assistants: Michal Fok, Oscar Bolanos ➝  guest lecturers – tba
  • 3. course basics ➝  6 credits ➝  2 h lecture ➝  4 h studio/lab ➝  6 h home based preparation ➝  no written exam
  • 4. the course structure ➝  1 design brief ➝  4 design reviews ➝  13 interactive lectures/seminars ➝  13 studio sessions (attendance mandatory) ➝  1 sketch book ➝  reading assignments ➝  interactive exercises all in English
  • 5. assessment the final grade is based on: the grades of four mandatory reviews " (submitted documentation and its presentation): 1.  results and design ideas from requirements capture (i)" through sketches, scenarios, storyboards and personas 2.  design idea presentation through first (lo-fi) prototype (i) 3.  interactive prototype / demonstrator on device (g) 4.  final presentation interactive prototype on device (g)" and 5.  participation in the class/studio (i) 6.  sketch book (i) 7.  final short video (produced in week 14) (i)" ✱(i) = individual ✱(g) = group
  • 6. assignment dates ➝  10th Mar – Microsoft Imagine Cup summary" round 1 competition deadline ➝  19th Mar – 1st review (rc results + ideas) ➝  2nd April – 2nd review (design solutions) ➝  30th April – 3rd review (prototype) ➝  21st May – final review documentation for each review is due on the Sunday before the review at 12:00 ✱ late submissions are subject to penalty
  • 7. how is your design evaluated? by a panel of experts Q: how do you assess concepts or designs? A: Scott Jenson (former director of Symbian): “First I ll be asking ‘what’s the value of this? , that is ‘Will people really want it? [… the] second is simplicity.” Jones & Marsden (2006) “…being humble as these [designs] are evaluated and seen to fall short, and to need refining.” Jones & Marsden (2006)
  • 8. what is this course? Personal Interaction Studio focuses on ➝  mobile devices as the platform (personal) ➝  interaction design ➝  studio as the teaching format ➝  the idea is to generate, communicate, evaluate, iterate and improve design ideas through synthesis by re-defining problem and the solution ➝  it is NOT a programming course
  • 9. resources ➝  all communication and further readings, links etc. will go through moodle ➝  please enroll with the key: persint ➝  http://moodle.epfl.ch/course/view.php?id=6881
  • 10. syllabus 1.  introduction 2.  data collection 3.  analysis 4.  design techniques 5.  mobile i/o 6.  screen design 7.  prototyping 8.  -14. guest lectures and seminar
  • 11. relation to design process ➝  understand brief ➝  research background – refine problem ➝  ideate candidates ➝  prototype solution(s) ➝  select solution ➝  implement delivery ➝  learn from feedback
  • 12. example ➝  Don’t forget your friends! ➝  “Can’t do it today. But I’ll call you next time.”
  • 13. things you will learn (about) ➝  brainstorming, ice breaking ➝  interviewing ➝  qualitative analysis ➝  sketching ➝  personas ➝  scenarios ➝  storyboarding ➝  elevator pitch ➝  lo-fi prototyping ➝  hi-fi prototyping ➝  designing, critiquing, re-designing ➝  communicating your ideas – show and tell, posters, presentation "
  • 14. topics addressed in this class ➝  design thinking ➝  interaction design ➝  user experience
  • 15. design brief People’s physical and mental health are one of the most precious goods available to them. Mobile phones have become a large collection platform for sensor data either direct through e.g. GPS and accelerometer or indirectly by providing sensor data from other sources, which can be used to inform people’s decision making and daily life. Your task is to design an application that empowers people to leverage sensed data for their well-being in terms of either: - personal health, " - environmental health or " - social health.
  • 18. more details… ✱ attribution: parts of these slides are based on Angela Sasse and Sven Laqua s course on interaction design at UCL
  • 19. why mobiles? “The most profound technologies are those that disappear.” Mark Weiser
  • 21. what is design? hard to grasp – industrial design, graphic design, software design, interface design, product design … in interaction design (Fallman 2003) : ➝  scientific/eng. process (conservative) ➝  art form (romantic) ➝  ad-hoc activity (pragmatic, bricoleur) none are adequate – design is unfolding " both problem and solution evolve through sketching (prototyping)
  • 22. why design? ➝  post WWII declining American manufacturing quality disillusioned purchasers who, after being attracted by external style, found products unsatisfactory in use ➝  American industry got decimated from 1960s on from imports from Japan and Germany where greater attention to production quality and a more holistic approach to design were the norm. ➝  key differentiator for products ➝  key skill in IT – differentiator for employees
  • 23. why design digital products ➝  digital products shortcomings: ➝  requirecomputer-centred thinking ➝  poor behaviour, rudeness ➝  reasons ➝  ignorance about users ➝  conflicting interests ➝  lack of process
  • 24. the design funnel concept concept generation selected iterative overall concepts exploratory clarification resolution granularity general coarse medium fine
  • 25. sketchbook ➝  jotdown and annotate ideas (no idea is bad) ➝  explore & refine ➝  develop variations, alternatives and details ➝  refer back, reflect ➝  record other good ideas you see ➝  collection material (pictures, screen shots), tape them
  • 26. what is interaction design (IxD)? ➝  it's about the design of behavior" http://designmind.frogdesign.com/blog/behaving-badly-in-vancouver.html ➝  designing the mechanisms for interacting with a product (Cooper 2007) ➝  …designing interactive products to support people in their everyday and working life (Preece et al, 2002)
  • 27. interaction design within a company ➝  management ➝  marketing ➝  engineering ➝  design team How to achieve buy-in for your ideas? How do you communicate your ideas to them? What’s the language – same as yours? Scott Jenson: “Design is about semantics and syntax. First you need to see what people do and want – the semantics and then you have to find a way to make that possible – the syntax.”
  • 28. jobs - interaction design responsibilities include: ➝  lead interaction design (entire product lifecycle), tools and deliverables, including: ➝  persona development ➝  use cases, user task flows ➝  user interface concepts and interaction models ➝  annotated wireframes ➝  information architecture ➝  documentation of design concept in detailed UI specs ➝  effectively communicate interaction models and design ideas to the team, leveraging above tools / documents ➝  identify appropriate user research techniques and metrics for gauging success ➝  guide product direction and set UI requirements based on user research, functional requirements, and business goals ➝  recommend concepts for testing and interpret consumer feedback / results
  • 29. design philosophy ➝  centred on human needs ➝  individualor group ➝  support goals and activities ➝  design technology to fit human needs and characteristics ➝  involve users whenever possible ➝  mix analytical, creative and pragmatic approaches ➝  pick from range of design tools ➝  use existing best practices but not uncritically ➝  monitor design process and reflect on it
  • 30. what is UX? “User experience encompasses all aspects of the end- user's interaction with the company, its services, and its products. The first requirement for an exemplary user experience is to meet the exact needs of the customer, without fuss or bother. Next comes simplicity and elegance that produce products that are a joy to own, a joy to use. True user experience goes far beyond giving customers what they say they want, or providing checklist features. In order to achieve high-quality user experience in a company's offerings there must be a seamless merging of the services of multiple disciplines, including engineering, marketing, graphical and industrial design, and interface design.” Nielsen, Norman Group
  • 31. user-centred “User experience and interface design in the context of creating software represents an approach that puts the user, rather than the system, at the center of the process. This philosophy, called user- centered design, incorporates user concerns and advocacy from the beginning of the design process and dictates the needs of the user should be foremost in any design decisions.” Microsoft
  • 32. product centred “The user experience for Mac OS X applications encompasses the visual appearance, interactive behavior, and assistive capabilities of software. With the Aqua graphical user interface, Universal Access features, and user-assistive technologies like the Address Book framework, Apple Help, and VoiceOver, you can deliver the cohesive and professional user experience that Macintosh users have come to expect. It's easy to leverage the user experience technologies of Mac OS X to make great Macintosh software.” Apple
  • 33. bad UX ➝  “Technology that does not work the way they expect makes people feel stupid.” ➝  “if you intend to drive people away from your site, it’s hard to imagine a more effective approach than making them feel stupid.” ➝  JJ Garrett: Elements of User Experience
  • 34. impact on users’ lives ➝  User: “… so I have all these files and documents, all over my desktop, different versions of documents in different folders, and documents I don’t need any more. I never get round to tidying up. I keep emails because I might need because of the address, or the content. But I never get round to putting them into the address book and deleting the mails, so they just pile up. My electronic workspace is a mess.” ➝  Q: How does that make you feel? ➝  User: [thinks] “It makes me feel that I am a bad person.” From Richard Boardman’s (2005) PhD thesis on Improving Tool Support for Personal Information Management
  • 35. user experience (UX) industrial/graphic design form behaviour content information architecture, interaction designer animation etc. Cooper 2006
  • 36. lived experience any account of what is often called the user experience must take into consideration the ‘felt’ experience: emotional, intellectual, and sensual aspects of our interactions with technology. “We don't just use technology, we live with it.” John McCarthy, Peter Wright 2004: Technology as experience. MIT Press
  • 37. framework for design and interaction takes place in a has general & specific characteristics CONTEXT physical incl. other USER SYSTEM technologies interacts with to attain social cultural GOAL temporal
  • 38. Garret’s planes of UX ➝  strategy – what user wants to achieve ➝  scope – what functions and features are required ➝  structure – navigation – how are screens linked and grouped ➝  skeleton – placement of buttons, tabs, blocks of text, pictures ➝  surface – series of pages in high fidelity
  • 39. Garret’s planes of UX concrete surface “When designers make choices that do not align with planes above and below, you end up with a jumble of skeleton components that don’t fit.” structure scope Garrett’s planes Of UXP strategy abstract
  • 40. levels of interaction user’s/corporate goals output in the real world GOAL LEVEL user’s knowledge computer’s representation TASK of task domain of task domain LEVEL user’s knowledge computer command DIALOGUE of language language LEVEL user’s hands, eyes computer keyboard, INPUT/ display OUTPUT LEVEL human structures Computer structures
  • 41. personas ➝  represent user groups ➝  system may be used by one or several personas ➝  different characteristics ➝  different goals ➝  e.g. buyers of a new car ➝  Jean-David (playboy): " go fast, impress women ➝  Aurelie (soccer mum): " fit in many kids, be safe ➝  Bob (the Builder): " haul big loads, be reliable
  • 42. scenarios ➝  persona-based scenarios " concise narrative description of how persona interacts with system to achieve goals ➝  context-based scenarios " how product can serve needs of persona, created before any design is done ➝  to key path scenarios – refined with design ➝  to validation scenarios – based on ❛what … if❜" focus on illustrate requirements (the what), " top-down decomposition to functionality (the how)
  • 44. scenarios vs. use cases ❝… scenarios are an interactive means of defining the behaviour of a product from the standpoint of specific users (personas). This includes not only the functionality of the system, but the priority of functions and the way those functions are expressed in terms of what the user sees and how she interacts with the system. use cases, on the other hand, are based on exhaustive descriptions of the functional requirements of the system, often of a transactional nature, focussing on low-level user actions and accompanying system response.❞ Cooper 2006
  • 45. eliciting UX requirements ➝  in-depth qualitative data ➝  interviews ➝  in-depth analysis such as Grounded Theory and Discourse Analysis ➝  ethnographic methods ➝  mostly observational ➝  can be combined with surveys, interviews, qualitative studies
  • 46. general reading ➝  recommended books (available at EPF-BIB) ➝  Cooper,Reimann & Cronin (2007) " About Face 3, Wiley ➝  Jones& Marsden (2004) " Mobile Interaction Design, Wiley ➝  ScottMcCloud (1993)" Understanding Comics, Harper Perennial (on order) ➝  Schneiderman & Plaisant (2010) " Designing the User Interface. Addison-Wesley. ➝  Preece, Rogers & Sharp (2002)" Interaction Design, Wiley
  • 47. summary ➝  focus on design approaches, methods and tools ➝  learning by doing ➝  interaction design is a relatively young and rapidly developing field ➝  interaction designers have to address new technologies and adapt their methods and tools ➝  collect artefacts: " paper, pictures, audio, video
  • 48. practical part – design techniques
  • 49. brainstorming ➝  group size <10 – ideally between 5-7 + facilitator ➝  find and set up comfortable space ➝  appoint recorder - up-coming ideas on shared display, flip chart, whiteboard ➝  ice-breaking exercise – to familiarize members of groups ➝  define problem clearly ➝  goal: generate as many ideas as possible adapted from www.mindtools.com/brainstm.html
  • 50. brainstorming – how to ➝  address what, how, when, where and why ➝  give people time on their own (5 minutes silence) at beginning then ask to share them ➝  encourage ➝  todevelop ideas of others further or use as new seeds ➝  enthusiastic, fun, criticism OK ➝  includeeveryone to contribute (practical and impractical ideas) and develop
  • 51. ice breaker ➝  effective to start a training, team-building event ➝  goal: ➝  get to know each other ➝  get into the event ➝  become comfortable contributing to event ➝  establish level playing field ➝  create common sense of purpose ➝  ingredients: ice, a breaker (method), a facilitator
  • 52. ice breaker – when to use if participants ➝  come from different backgrounds ➝  need to bond quickly to work on common project or goal ➝  are unfamiliar with topic at hand ➝  don t know the facilitator but should and vice versa
  • 53. the ice participants have ➝  not met before ➝  different age, status or levels in an organization ➝  different backgrounds – different perceptions of each other choose method accordingly & don t try to uncover the whole iceberg
  • 54. ice breaker – methods (introductory) everyone draws name, nationality, focus of study and one human element, e.g.: ➝  one little known fact about me ➝  true/false - three to four short statements – the group guesses which one is false, or ➝  pair interview – interview and then introduce partner to the group ➝  trading cards ➝  lo-fi social network
  • 55. assignments ➝  fill in questionnaire