Comprehensive Study Notes: Foundations of UX Design, HCI History, and Design Thinking

Course Foundations and Pedagogical Objectives

  • Core Mission of the Course:

    • Intro to UX Design is offered through the Department of Information (School of Information), situated within the School of Computing.
    • The pedagogical model rests on three foundational pillars:
    • Explore: Apply the human-centered design process to rigorously uncover problem spaces and intuitively formulate functional solutions that directly address genuine, verified human needs.
    • Methods: Anchor interface and product decisions directly in empirical design research methodologies, emphasizing qualitative user research techniques such as contextual inquiries, semi-structured interviews, and naturalistic observations.
    • Present: Articulate design provenance and rationale with clarity, equipping designers to pitch, defend, and negotiate design choices across cross-functional teams comprising software engineers, marketing departments, peer designers, and executive management.
  • Project-Driven Structure and Career Readiness:

    • The course emphasizes hands-on user research, evaluative methods, and iterative design.
    • Assignments are scaffolded to produce an industry-ready portfolio asset:
    • Students develop individual artifacts including design analysis matrices, interview protocols, transcript syntheses, user personas, scenario storyboards, wireframes, user test reports, and interactive prototypes.
    • At the conclusion of the term, these artifacts are synthesized into an end-to-end, showcase UX case study designed to support recruitment for internships and entry-level UX positions.

Instructional Team and Background

  • Course Instructor Profile:

    • Dr. Han Lin Li is an Assistant Professor in the School of Information / School of Computing.
    • Academic pedigree: Earned a Ph.D. in Technology and Social Behavior from Northwestern University in 2022 in Chicago, Illinois.
    • Academic and research specialization:
    • Research intersects Human-Computer Interaction (HCI), Artificial Intelligence (AI), and Social Computing.
    • Studies the social mechanisms of online collaborative knowledge bases (e.g., contributor behaviors and incentive structures in Wikipedia and open Wiki platforms).
    • Examines data stewardship, specifically how distributed populations coordinate to generate, curate, and structure datasets leveraged to train modern AI models.
    • Industry background: Served professionally as both a UX Designer and UX Researcher across various corporate and technical settings.
    • Personal anecdote: Spent summer leisure time paddleboarding with a canine companion named Kiwi.
  • Teaching Assistants and Discussion Sections:

    • Studio sections on Mondays are facilitated by Teaching Assistants Angeline and Hilla.
    • Section assignments are divided strictly by course registration numbers:
    • Unique Course Number 330420: Meets in the designated studio classroom.
    • Unique Course Number 30423: Meets in the GAR Building.

Course Logistics, Modality, and Section Cadence

  • Meeting Modalities and Scheduling:

    • The initial two Wednesday lecture sessions are conducted remotely via Zoom due to mandatory academic travel constraints, with fully in-person instruction resuming in Week 33 in the primary lecture hall.
    • Remote Zoom access is pinned directly to the Canvas course homepage; the virtual room has no waiting room enabled, permitting seamless transitions between mobile devices and laptops.
    • Official shifts in course delivery modality are communicated via Canvas announcements.
  • Weekly Structural Cadence:

    • Wednesdays (Lecture Sessions): Dedicated to core theoretical foundations, methodological introductions, and interactive introductory exercises. All Wednesday lectures are recorded; recordings and slide decks are uploaded to Canvas files during remote weeks and under standard course recordings once in-person.
    • Mondays (Studio and Lab Sessions): Dedicated to applied follow-up activities reinforcing Wednesday concepts, dedicated group project collaboration, and structured Figma software labs led by the Teaching Assistants.
  • Figma Curriculum Integration:

    • Figma serves as the primary industry-standard prototyping tool throughout the course and across subsequent upper-division UX coursework.
    • Because this is an introductory course, the Figma curriculum is structured incrementally: Teaching Assistants provide weekly walk-throughs covering canvas navigation, project initialization, interactive component states, UI wireframing, button interactions, and user-testable click-through prototypes.
  • Communication and Inquiry Protocols:

    • Email communication must adhere to a standardized format: subject lines must include the exact tag I 310 U-inquiry to prevent communication from being lost in high-volume inboxes.
    • The instructional team maintains a standard turnaround response window of 22 working days.
    • Technical tool inquiries (specifically regarding Figma) and section-specific grading matters should be directed primarily to the student's assigned studio section TA.
    • Office hours are scheduled weekly: Dr. Li announces faculty office hours at the close of the first week, while TAs announce studio office hours during their initial Monday sessions.

Academic Policies, Generative AI Guidelines, and Late Submissions

  • Submission Deadlines and Slip Days:

    • Students are allocated a semester-long quota of 77 total slip days for project deliverables without penalty.
    • Slip days can be used flexibly across assignments (e.g., submitting one milestone 77 days late, or distributing them as 33 days on one milestone and 44 days on another).
    • Once the 77-day bank is exhausted, late submissions incur a fixed daily percentage grade deduction.
    • Assignments strictly exempt from slip days (no late submissions permitted):
    • Reading discussion posts (must be completed prior to the corresponding conceptual lecture).
    • Live midterm and final project team presentations.
    • Weekly sketch exercises.
  • Academic Integrity and Generative AI Policies:

    • Plagiarism carries a strict penalty resulting in automatic failure of the course; all submitted work must be prepared independently by the student.
    • Generative AI (GenAI) usage rules:
    • Partially Permitted: Brainstorming, refining initial design concepts, finding background references, or minor visual asset polishing. Any substantial conceptual inspiration or data sourcing derived from GenAI tools must be explicitly disclosed.
    • Strictly Prohibited: Completely prohibited for all individual written deliverables. Students must independently author all reading discussion responses, presentation slide decks, and spoken presentation scripts without GenAI assistance.
  • Classroom Engagement and Reflective Feedback Ritual:

    • Classroom laptop usage is strictly limited to active note-taking and designated interactive course exercises.
    • Remote interaction occurs via the Zoom Q&A panel (with community question upvoting) and hand-raising features.
    • Weekly Index Card Ritual:
    • Beginning in Week 33 with in-person sessions, physical note cards are distributed at the end of each class (replicated via end-of-class polls during the remote period).
    • Every card collects responses to three questions:
      1. What did you learn from the class today? (Used by the instructor to assess conceptual absorption).
      2. What are you confused about? (Used to curate and resolve the most common student misunderstandings at the start of the following lecture).
      3. Rotational question: Focuses on assignment rubrics, project logistics, or structural questions.

Project Architecture and Domain Tracks

  • Grading Weight and Collaborative Team Structure:

    • The cumulative team project constitutes 75%75\% of the total course grade.
    • Teams consist of 44 to 66 students, formed exclusively among peers enrolled within the same Monday studio section to ensure dedicated collaborative studio time.
    • Students operate independently for the initial individual research phases before being formally merged into project teams around the midterm presentation milestone.
  • The Five Project Domain Options:

    • Students choose one thematic focus area by September 1414 from five domains:
    1. Social Media Reimagining: Specialized communication environments (e.g., an alternative professional networking platform modeled after LinkedIn but tailored specifically to undergraduate students).
    2. Entertainment Experiences: Enhancing live engagement, such as concert navigation, venue wayfinding, or ticketing queue management.
    3. Shopping and Commerce: Digital retail, provisioning logistics, or online grocery fulfillment.
    4. Academic and Institutional Life: Administrative system overhauls (e.g., redesigning UT Direct, Workday, or course registration platforms) or campus navigation apps designed to assist students across expansive university campuses.
    5. Health, Wellness, and Fitness: Personal health record management, clinical appointment scheduling, or physical fitness tracking.
  • Sequential Project Milestone Deliverables:

    • Milestone 1: Design Analysis: Individual comparative evaluation of existing market solutions.
    • Milestone 2: Interview Protocol: Structuring qualitative inquiry questions targeted at real users.
    • Milestone 3: Interview Execution: Conducting user sessions and submitting raw audiovisual recordings.
    • Milestone 4: Interview Analysis: Coding transcripts to isolate critical behavioral patterns and user pain points.
    • Milestone 5: Persona Development: Modeling synthesized user archetypes.
    • Milestone 6: Midterm Team Presentation: Formal pitch of research findings and conceptual directions.
    • Milestone 7: Storyboarding: Illustrating contextual user narratives and product touchpoints.
    • Milestone 8: Wireframe Prototyping: Constructing low-fidelity interface architectures.
    • Milestone 9: User Testing and Usability Evaluation: Conducting guided user walkthroughs with the prototype to collect critical evaluative data.
    • Milestone 10: High-Fidelity Interactive Prototype: Iterating interface fidelity based on user testing critiques.
    • Milestone 11: Final Project Presentation: Culminating oral and visual presentation of the design solution (the course has no final exam).
  • Project Assignment 1 Specifics (Design Analysis):

    • Due Date: Tuesday, September 88 at 11:59 PM11:59\,\text{PM} (midnight), rescheduled from September 77 in observance of Labor Day.
    • Task Requirements:
    • Select 55 prominent products (either physical or digital) situated within the student's selected project domain (e.g., within social media: TikTok, YouTube, Reddit, Instagram, LinkedIn, or physical campus bulletin boards).
    • Interrogate their feature sets against four critical UX dimensions:
      • Desirable: Aesthetic and emotional appeal that attracts user engagement.
      • Useful: Functional capacity to solve an actual problem.
      • Accessible: Inclusivity for users with diverse physical, sensory, or cognitive abilities.
      • Usable: Ease of learning, operational efficiency, and error prevention.
    • Document findings via a provided Google Slides template by inserting annotated screenshots illustrating exemplar features that satisfy or fail these four criteria.

Weekly Coursework: Reading Discussions and Sketching

  • Reading Discussions:

    • Assigned across three designated weeks throughout the semester, utilizing Canvas-hosted PDFs of foundational book chapters or seminal research papers.
    • Responses are posted directly as comments to the Canvas discussion threads before class.
    • Response Structural Criteria:
    • Synthesis: Summarize core insights in 22 to 33 concise sentences, assuming the peer audience has already read the text.
    • Critical Analysis: Articulate specific points of conceptual agreement or disagreement.
    • Application: Connect the theoretical concepts to personal projects, professional work, or lived experiences.
    • Open Inquiries: Conclude with open conceptual questions for class discussion.
    • Word Count Requirement: Strict minimum of 200200 words.
  • Weekly Design Sketches:

    • Conducted across 1010 weeks of the semester, weighted at 11 point per week (1010 points total).
    • Students submit 22 distinct sketches per week.
    • Pedagogical Objective: Sketches prioritize quantity over artistic quality, aiming to build a cognitive habit of documenting observed usability friction or generative product concepts.
    • Annotation Rule: Every sketch must include clear descriptive textual annotations so that an external viewer lacking domain context can immediately understand the intended user, problem space, and interface mechanism.

Historical Foundations of Human-Computer Interaction and UX

  • Definition of Human-Computer Interaction (HCI):

    • HCI serves as the interdisciplinary parent field of User Experience design, structured around three analytical components:
    • Human: The end users, surrounding organizational teams, and social, cultural, and environmental contexts in which technology is situated.
    • Computer: Hardware devices, software systems, mobile phones, consumer electronics, connected vehicles, and pervasive ambient computing.
    • Interaction: The dialogic communication loop wherein a human provides input, the computational system processes and renders output, and systems facilitate computer-mediated collaboration (e.g., Google Docs, Wikipedia) and computer-mediated communication (e.g., instant messaging platforms).
  • Pre-1950s Computing Paradigm:

    • Hardware consisted of massive, room-sized mainframes with high operational costs and scarce computational resources.
    • Humans were forced to adapt to the constraints of the machine rather than systems adapting to human cognitive models.
    • Graphical interfaces were viewed as non-essential computational overhead; users submitted physical batch jobs to specialized operators whose sole goal was maintaining 100%100\% hardware utilization.
  • Vannevar Bush and the Conceptual Genesis of Personal Computing (1945):

    • Authored the landmark essay As We May Think, published in The Atlantic Monthly.
    • Proposed the Memex (memory and index): a hypothetical, mechanized, glass-topped personal desk capable of storing vast repositories of books, periodicals, records, communications, and photographic files.
    • Described associative indexing, allowing users to traverse interconnected trails of information, anticipating modern personal computing devices, smartphones, the World Wide Web, and hyperlinked encyclopedias like Wikipedia.
    • Bush's vision spurred institutional developments that culminated in the establishment of the National Science Foundation (NSF).
    • Anticipated cognitive-augmenting hardware including early automated speech-to-text recognition and wearable miniature cameras.
  • Grace Hopper and High-Level Languages (Early 1950s):

    • Developed the first operational compiler, translating human-readable programming language instructions into binary machine code.
    • Eliminated the requirement to write machine code directly, establishing high-level programming languages and democratizing software creation for broader populations of scientists and engineers.
  • The Mother of All Demos (1968):

    • Presented by Douglas Engelbart and colleagues from the Stanford Research Institute (SRI).
    • Marked the first public demonstration of the computer mouse, interactive hypermedia, structured video conferencing, dynamic file linking, and graphical user interface concepts, transitioning computing away from terminal-driven text interfaces.
  • The Paradigm Shift in Computing Metrics:

    • Historical performance metrics: Raw compute speed, processor throughput, and physical storage capacity.
    • Modern computing performance metrics: Usability, reliability, and security.
    • Real-world usability failure case: A payment terminal deployed at a USPS post office where a cashier had to affix a handwritten "swipe below" label because the card reader slot was hidden from the customer's line of sight, illustrating that poor hardware usability requires external manual instruction.

Core Principles of UX Design

  • Principle 1: Design is Empathy ("You Are Not Your User"):

    • Designers cannot substitute their personal perspectives, capabilities, or preferences for those of the actual target audience.
    • While a designer may identify an interface problem, users frequently experience distinct operational needs and mental models around that same problem.
    • Example: Highly technical system error messages. A raw terminal diagnostic code may be clear to a software engineer, but represents unhelpful, confusing output to an everyday user trying to recover from an error.
  • Principle 2: Design is User Advocacy:

    • UX practitioners operate in cross-functional organizational environments alongside software engineers, marketing specialists, business analysts, and executive teams.
    • Different roles hold competing functional priorities: engineering focuses on structural scalability and code robustness; business focuses on user acquisition, platform monetization, and customer retention.
    • The explicit mandate of the UX designer is to champion and protect the user's best interests against conflicting institutional priorities.
    • Example: Dark patterns in cancellation flows, such as multi-step Amazon Prime unsubscribe sequences. Business interests introduce artificial friction, confusing confirmation buttons, and defensive retention offers to prevent cancellations, directly opposing the user's clear goal of a straightforward, single-click account cancellation.
  • Principle 3: Design is Contextual:

    • There is no universal, context-independent design solution; an interface pattern that works well in one environment may fail in another.
    • Usability depends heavily on the situational, cultural, and operational contexts of the task.
    • Example: Instant messaging applications. A user relies on different platforms for distinct social and professional contexts: Slack serves corporate tasks with threading and workspace channels; Discord provides persistent voice and text channels for gaming communities; and SMS or WhatsApp supports personal communication. Interface features must align directly with the specific social context.

Design Thinking Frameworks and Research Methods

  • Formal Definition of Design Thinking:

    • An iterative, non-linear methodology centered on deeply understanding intended users, reframing complex problem spaces, and generating innovative solutions that can be rapidly prototyped and empirically validated through user testing.
  • Structural Visualizations of Design Thinking:

    • Double Diamond Model (British Design Council): Divided into four distinct phases balancing divergent exploration and convergent focus:
    • Discover: Divergent exploration to gather broad qualitative insights about the problem space.
    • Define: Convergent filtering to narrow insights down into an actionable design brief.
    • Develop: Divergent ideation of multiple potential interface solutions.
    • Deliver: Convergent testing, refinement, and final implementation of the chosen solution.
    • Cyclic Iteration Loop: A continuous, four-stage feedback loop comprising Observation, Idea Generation, Prototyping, and User Testing.
    • Non-Linear Jumping Model: Recognizes that designers frequently move non-sequentially between phases, such as moving directly from user empathy into rapid prototyping when an intuitive solution surfaces.
    • Nielsen Norman Group (NN/g) Lifecycle: Outlined across four recurring phases: Discover, Explore, Test, and Listen.
    • Stanford d.school Five-Stage Model: The central structural framework applied throughout the course project:
    1. Empathize: Conduct field research to understand user behaviors, emotional needs, and frustrations in their native environment.
    2. Define: Synthesize empirical qualitative findings through interview analyses to explicitly frame the core user problem.
    3. Ideate: Brainstorm diverse interface solutions, avoiding early focus on a single implementation.
    4. Prototype: Build tangible, interactive representations ranging from wireframe flows to clickable Figma screens.
    5. Test: Return the prototype to target users to observe interactions, uncover usability flaws, and guide subsequent design iterations.
  • Primary UX Discovery Methods:

    • Interviews: Semi-structured qualitative dialogues designed to uncover user perceptions, reasoning, and mental models.
    • Contextual Inquiries: Immersive observational field research conducted within the user's natural operational environment, paired with active inquiry.
    • Direct Observations: Systematic, non-interventional tracking of users interacting with tools or environments.
    • Supplementary Methods: Surveys, focus groups, and longitudinal diary studies.

Questions & Discussion

  • Interactive Poll on Bad Design Examples:

    • Student contributions regarding everyday usability failures:
    • UT Direct portal and UT course registration system: Criticized for complex site architectures, dated information hierarchies, and confusing navigation.
    • Workday enterprise platform: Highlighted as a common enterprise system with cumbersome multi-step workflows and poor visual affordances.
    • Government agency websites: Noted for infrequently updated visual styling, broken links, and confusing navigation compared to commercial web platforms.
    • Cluttered interfaces and Craigslist: Excessive button densities, dense text layouts, and weak visual hierarchy.
    • Visual accessibility failures: Inadequate text-to-background color contrast ratios.
    • Physical architecture: Physical university building entrances lacking accessible automated doors or clear accessible pathways.
    • Synthesis: Bad design introduces operational friction, increases task completion time, and causes cognitive disorientation.
  • Student Demographic and Course Interest Poll:

    • Over 50%50\% of enrolled students are in their second academic year.
    • Over 50%50\% enrolled primarily out of curiosity to explore user experience principles.
    • Approximately 33%33\% (13\frac{1}{3}) intend to pursue UX design or UX research as their professional career path.
    • Exactly 66 students enrolled specifically to satisfy general degree requirements.
    • Cohort representation consists heavily of Informatics majors and Informatics minors.
    • Summer activities reported by students included attending concerts, domestic travel to various cities, and international travel to India.
  • Audience Q&A:

    • Prompt from Reagan: Is there a word count minimum for the reading discussion post?
    • Response: Yes, every reading discussion post on Canvas must meet a strict minimum length of 200200 words.