Lecture 1 — Human Computer Interaction | Stanford University

Main ideas / concepts conveyed

• Purpose of the course (Human-Computer Interaction, HCI)

  • The course introduces HCI as the design, implementation, and evaluation of user interfaces.
  • It synthesizes existing teaching materials and research from multiple sources.

• Core components of HCI

  • An HCI system involves:
    • People: the user and the other people they communicate or work with.
    • Computer(s): the machines and/or network running the system.
    • Interface: the representation of the system presented to the user.

• How real-world design often works

  • Designers may not know:
    • the exact problem
    • the full space of possible solutions
    • what the eventual solution should be
  • Therefore, real-world design is often iterative, using “fail fast” approaches—trying and comparing options to succeed sooner.

• Why good UI matters

  • Good design brings people joy
    • helps people do things they care about
    • supports connection to others
  • Good interfaces can strongly affect:
    • individuals’ ability to accomplish tasks
    • society as a whole
  • Graphical user interfaces enable large-scale capabilities (e.g., document creation, photo sharing, information access).

• Consequences of bad UI

  • Bad design is frustrating and can cost lives.
  • Examples cited include:
    • medical devices
    • airplane accidents
    • nuclear disasters
  • Many serious interface problems could potentially be avoided by following basic principles—notably consistency and feedback.
  • Even when not catastrophic, poor interfaces waste time (e.g., banking websites, Wi‑Fi issues, digital camera setup).

• Interfaces can become “invisible”

  • With practice and good design, users shift from:
    • manipulating the interface
    • to accomplishing the task
  • The talk compares this to a practiced physical tool (like a cane) becoming unnoticeable as perception adapts.
  • This creates an experience that feels automatic and intuitive.

• What the course will teach as a method

  • The development process is driven by:
    • people’s tasks
    • goals
    • values
  • The course emphasizes working with users throughout development to:
    • assess decisions from the user’s vantage point (their work and environment)
    • consider users’ abilities and situations
    • consult the real experts through direct user/stakeholder engagement
  • Users are framed as one stakeholder among many, with other stakeholders including those involved in:
    • easing development
    • reducing cost of production
    • support/maintenance
    • designing for users

---

Methodology / process described

• Design development should be driven by user-centered inputs

  • Identify and use:
    • users’ tasks
    • users’ goals
    • users’ values

• Involve users continuously rather than only at the end

  • Engage users throughout the process to evaluate decisions:
    • from the users’ perspective
    • in their real work context and environment

• Account for user diversity

  • Pay attention to:
    • different user abilities
    • different situations

• Consult a broad range of experts and stakeholder groups

  • Talk to:
    • different types of users (including “regular” and “extreme” users)
    • a variety of stakeholders beyond users

• Evaluate and iterate

  • Since the problem/solution space may be unclear:
    • iterate on design
    • try options early
    • fail fast to learn sooner and improve outcomes

---

Sources / speakers mentioned (credited in the subtitles)

• Scott Klemmer — Associate Professor of Computer Science; instructor/host
• John Zimmerman — referenced as a colleague (contextual reminder about stakeholders)
• James Landay — referenced source (books)
• Don Norman — referenced source (books)
• CHI / “kai conferences” papers — referenced source material
• Stanford University — institutional source/context for the course content