📘 Lecture 16 — HCI Process and Models
📖 Overview: This lecture examines why many software products fail despite technical soundness, emphasizing that poor user experience and usability are the root causes. It introduces the need for new software development models that prioritize user-centered design, and explains the importance of integrating interaction design into the development process to create successful, human-centered products.
🗂️ Topics Covered
The lecture begins by revealing shocking statistics about user failures in software, then explains the true cost of bad user experience versus the rewards of good design. It defines software quality with usability as a key characteristic, distinguishing strategic from tactical aspects. It identifies three core problems in the industry: ignorance about users, conflict of interest between programmers and designers, and the lack of a reliable design process. Finally, it traces the evolution of software development from programmers doing everything to the need for design to precede programming, concluding with the definition and three dimensions of interaction design (form, meaning, behavior).
📝 Lecture Summary
Learning Goals
The aim of this lecture is to introduce you to the study of Human Computer Interaction, so that after studying this you will be able to: • Understand the need of new software development models • Understand the importance of user experience and usability in design
The Cost of Bad User Experience
It has been said, “to err is human; to really screw up, you need a computer.” Inefficient mechanical systems can waste cents, but bad information processes can lose your entire company. Our digital tools are extremely hard to learn, use, and understand, and they often cause us to fall short of our goals, wasting money, time, and opportunity. The irony is that better products don’t take longer or cost more to build; they are difficult only because our process for making them is old-fashioned. Only long-standing traditions rooted in misconceptions keep us from having better products.
Consider a scenario: a website is aesthetically beautiful, technically flawless, and has wonderful animated content. But if a user cannot find desired information or products, it is useless from a business point of view.
📌 Statistics:
- Users can only find information 42% of the time – Jared Spool
- 62% of web shoppers give up looking for the item they want to buy online – Zona Research
- 50% of potential sales from a site are lost because people cannot find the item – Forrester Research
- 40% of users who do not return to a site do so because their first visit resulted in a negative experience – Forrester Research
- 80% of software lifecycle costs occur after release; of that, 80% is due to unmet user requirements, only 20% due to bugs – IEEE Software
- 63% of software projects exceed cost estimates; top reasons include frequent requests for changes from users, overlooked tasks, users' lack of understanding of requirements, and insufficient user-analyst communication – Communications of the ACM
- BOO.com, a $204m startup fails – BBC News
- Poor commercial web sites will kill 80% of Fortune 500 companies within a decade – Jakob Nielsen
All these facts reveal that products with bad user experience deserve to die!
The Reward of Good User Experience
The real importance is of good interaction design. If we design a system with good usability and good user experience, the result will be satisfaction and happiness. People will buy your product and recommend it to others, creating a chain reaction. The premise is simple: if achieving the user’s goal is the basis of our design process, the user will be satisfied and happy, and will gladly pay us money.
🔑 Why this matters: Most digital products emerge from the development process like a monster from a bubbling tank. Developers create technological solutions without planning with users in mind, failing because they have not imbued their creations with humanity.
Software Quality and Usability
We are mainly concerned with software quality, defined as: The extent to which a software product exhibits these characteristics: • Functionality • Reliability • Usability • Efficiency • Maintainability • Portability
Usability can be understood in two aspects:
- Strategic: guides us to think about user interface idioms – the way in which the user and the idiom interact.
- Tactical: gives us hints and tips about using and creating user interface idioms, like dialog boxes and pushbuttons.
Integrating the strategic and tactical approaches is key to designing effective user interaction. There is no objectively good dialog box; quality depends on the situation, the user, and their background and goals. Merely applying tactical dictums doesn’t make the end result better.
Three Reasons Why Products Fail
Ignorance about Users The digital technology industry doesn’t have a good understanding of what it takes to make users happy. Most technology products get built without much understanding of the users. Knowing market segments, income, or jobs does not tell us how users will actually use the product or why they might choose it over competitors.
Conflict of Interest There is an important conflict of interest: the people who build the products—programmers—are usually also the people who design them. Programmers are often required to choose between ease of coding and ease of use. Because performance is judged by coding efficiency and tight deadlines, most software takes the easy-coding direction. Just as we would never permit a prosecutor to also adjudicate a legal case, we should ensure that those designing a product are not the same people building it. It simply isn’t possible for a programmer to advocate for the user, the business, and the technology at the same time.
Lack of a Reliable Process The industry has no reliable, complete process for producing successful products. Engineering follows rigorous methods for technical quality; marketing follows methods for commercial viability. What’s left out is a repeatable, analytical process for transforming an understanding of users into products that meet their needs and excite their imaginations. Most software has never undergone a rigorous design process from a user-centered perspective. Programmers, deep in thoughts of algorithms, “design” user interfaces accidentally or not at all.
Many programmers embrace integrating users frequently (weekly or daily) into the programming process. Although this shares design responsibility with the user, it ignores a serious methodological flaw: a confusion of domain knowledge with design knowledge. Users can articulate problems with an interaction but are not often capable of visualizing solutions. Design is a specialized skill, just like programming. Programmers would never ask users to help them code; design problems should be treated no differently.
Evolution of Software Development Process
Originally programmers did it all In the early days, smart programmers dreamed up useful software, wrote it, and tested it on their own.
Managers brought order Professional managers were brought in. Good product managers understand the market and competitors and define the software product by creating requirements documents. However, requirements are often little more than a list of features, and managers find themselves having to give up features to meet schedule.
Testing and design became separate steps As the industry matured, testing became a separate discipline and a separate step. In the move from command-line to graphical user interface (GUI), design and usability also became involved, though often only at the end, and often only affecting visual presentation. Today common practice includes simultaneous coding and design followed by bug and user testing, then revision.
Design must precede the programming effort A goal-directed design approach means that all decisions proceed from a formal definition of the user and their goals. Definition of the user and user goals is the responsibility of the designer, thus design must precede programming.
Design
Design, according to industrial designer Victor Papanek, is the conscious and intuitive effort to impose meaningful order. Cooper proposes a more detailed definition: • Understanding the user’s wants, needs, motivations, and contexts • Understanding business, technical, and domain requirements and constraints • Translating this knowledge into plans for artifacts whose form, content, and behavior is useful, usable, and desirable, as well as economically viable and technically feasible.
This definition applies across all design disciplines. When performed using appropriate methods, design can provide the missing human connection in technological products.
Three Dimensions of Design & Interaction Design
Interaction design focuses on an area traditional design disciplines do not often explore: the design of behavior. It is only with interactive technologies—courtesy of the computer—that designing the behavior of artifacts and how this behavior affects and supports human goals has become a discipline worthy of attention.
One way to understand the difference is through a historical lens:
- In the first half of the 20th century, designers focused primarily on form.
- Later designers became increasingly concerned with meaning (e.g., retro forms in the 70s).
- Today, information designers include the design of usable content.
Within the last fifteen years, a growing group of designers have begun to talk about behavior: the dynamic ways that software-enabled products interact directly with users. Interactive products must have form, meaning, and behavior in some measure.
🔑 Definition — Interaction Design: Simply put, interaction design is the definition and design of the behavior of artifacts, environments, and systems, as well as the formal elements that communicate that behavior. Unlike traditional design disciplines focused on form and meaning, interaction design seeks first to plan and describe how things behave, and then to describe the most effective form to communicate those behaviors.
⭐ Key Takeaways
The most critical lesson from this lecture is that technical excellence alone guarantees nothing; a product must provide excellent user experience or it will fail in the market. Usability is a core dimension of software quality, and it must be treated strategically (designing how users interact) and tactically (applying specific interface guidelines). The industry’s three main failures are ignorance of users, the conflict of interest where programmers design interfaces, and the lack of a reliable user-centered design process. The solution is to separate design from programming and ensure design precedes coding, using a goal-directed approach. Finally, interaction design is a distinct discipline focused on behavior, not just form or meaning, and is essential for creating products that truly support human goals.
🧠 Quick Revision Questions
- What are the three main reasons why the digital technology industry fails to produce successful, user-friendly products?
- According to the lecture, what is the fundamental flaw in having programmers design user interfaces while also coding them?
- What is the key difference between the strategic and tactical aspects of usability in interface design?
- How does the evolution of the software development process explain the need for design to precede programming?
- Define interaction design and explain how it differs from traditional design disciplines that focus on form and meaning.
📘 Lecture 17 — HCI Process and Methodologies
📖 Overview: This lecture explores the design process in Human Computer Interaction and introduces various lifecycle models that structure software development. Understanding these models is crucial because they determine how user requirements are gathered, how design evolves, and how usability is evaluated throughout a project’s lifecycle.
🗂️ Topics Covered
The lecture begins with multiple definitions of design from different perspectives, then introduces the concept of lifecycle models for software development. It covers the traditional Waterfall model and its flaws, followed by the Spiral lifecycle model with risk analysis and prototyping. Rapid Application Development (RAD) and DSDM are discussed as user-centered approaches. The lecture then presents HCI-specific models including the Star lifecycle model and the Usability Engineering lifecycle, concluding with the Goal-Directed Design process that bridges the gap between research and design.
📝 Lecture Summary
Design Definitions
The term design, even used in the context of designing a computer system, can have different meanings. According to Jones (1981), design can be defined as: ‘Finding the right physical components of a physical structure’, ‘A goal-directed problem-solving activity’, or ‘The imaginative jump from present facts to future possibilities’. On engineering design, Jones found that it involves using scientific principles, technical information, and imagination to define a system that performs pre-specified functions with maximum economy and efficiency. Webster (1988) stresses the relationship between design representation and design process, stating that a design is an information base that describes elaborations of representations.
Design refers to both the process of developing a product and to the various representations produced during that process. Designers need to understand user requirements and represent this understanding in different ways at different stages. Selecting suitable representations is important for exploring, testing, recording, and communicating design ideas within the design team and with users. Two major activities must be undertaken: understanding the requirements of the product and developing the product.
17.1 Lifecycle models
The term lifecycle model represents a model that captures a set of activities and how they are related. Sophisticated models incorporate a description of when and how to move from one activity to the next and a description of the deliverables for each activity. These models allow developers and managers to get an overall view of development so progress can be tracked, deliverables specified, resources allocated, and targets set. Existing models have varying levels of sophistication — for small projects with experienced developers a simple process is adequate, but for larger systems involving tens or hundreds of developers with thousands of users, more formality and discipline is needed.
The waterfall lifecycle was the first model generally known in software engineering and forms the basis of many lifecycles in use today. This is basically a linear model in which each step must be completed before the next step can be started. For example, requirements analysis must be completed before design begins. The lifecycle starts with requirements analysis, moves into design, coding, implementation, testing, and finally maintenance.
🔑 Definition — Waterfall Model: A linear sequential software development lifecycle model where each phase (requirements analysis, design, code, test, maintenance) must be completed before the next phase can begin.
Flaws of waterfall model: One main flaw is that requirements change over time as businesses and the environment change rapidly, so it does not make sense to freeze requirements for months or years while design and implementation are completed. Some feedback to earlier stages was acknowledged as desirable, but the opportunity to review and evaluate with users was not built into this model.
The spiral lifecycle model was suggested by Barry Boehm in 1988. Two features are immediately clear from the model: risk analysis and prototyping. The spiral model incorporates them in an iterative framework that allows ideas and progress to be repeatedly checked and evaluated. Each iteration around the spiral may be based on a different lifecycle model and may have different activities.
🔑 Definition — Spiral Model: An iterative software development lifecycle model that incorporates risk analysis and prototyping, where each iteration may be based on a different lifecycle model and development is driven by plans focused on risks rather than just intended functionality.
💡 Why this matters: Unlike the waterfall, the spiral explicitly encourages alternatives to be considered and problems to be re-addressed. A more recent version called the Win Win spiral model incorporates identification of key stakeholders and their “win” conditions, including a period of stakeholder negotiation to ensure a “win-win” result.
Rapid Application Development (RAD) attempts to take a user-centered view and minimize the risk caused by requirements changing during the project. Two key features of a RAD project are: (1) Time-limited cycles of approximately six months (time-boxing), at the end of which a system or partial system must be delivered, breaking down large projects into smaller projects; and (2) JAD (Joint Application Development) workshops where users and developers come together to thrash out requirements through intensive requirements-gathering sessions with representatives from each stakeholder group.
A basic RAD lifecycle has five phases: project set-up, JAD workshops, iterative design and build, engineer and test final prototype, and implementation review. The popularity of RAD led to DSDM (Dynamic Systems Development Method), developed by a non-profit consortium. The first of nine underlying principles is that “active user involvement is imperative.” The DSDM lifecycle involves five phases: feasibility study, business study, functional model iteration, design and build iteration, and implementation.
17.2 Lifecycle models in HCI
Fewer lifecycle models have arisen from HCI than from software engineering, and they have a stronger tradition of user focus. The first model discussed is the Star model, derived from empirical work on understanding how designers tackled HCI design problems. The second is the usability engineering lifecycle, which shows a more structured approach.
The Star Lifecycle model was proposed by Hartson and Hix in 1989. It emerged from empirical work looking at how interface designers worked, identifying two modes of activity: analytic mode (top-down, organizing, judicial, formal, working from systems view towards user’s view) and synthetic mode (bottom-up, free-thinking, creative, adhoc, working from user’s view towards systems view).
🔑 Definition — Star Lifecycle Model: An HCI lifecycle model where activities are highly interconnected without specifying any ordering, and evaluation is central — you can move from any activity to any other provided you first go through evaluation.
Unlike other lifecycle models, the Star does not specify any ordering of activities. The activities are highly interconnected, and whenever an activity is completed, its results must be evaluated. A project may start with requirements gathering, evaluating an existing situation, analyzing existing tasks, or any other activity.
The Usability engineering lifecycle was proposed by Deborah Mayhew in 1999. Her lifecycle provides a holistic view of usability engineering and a detailed description of how to perform usability tasks, specifying how usability tasks can be integrated into traditional software development lifecycles. It is particularly helpful for those with little expertise in usability.
🔑 Definition — Usability Engineering Lifecycle: A structured HCI lifecycle proposed by Mayhew that has three main tasks (requirements analysis, design/testing/development, and installation) with usability goals captured in a style guide used throughout the project.
The lifecycle has essentially three tasks: requirements analysis, design/testing/development, and installation, with the middle stage being the largest involving many subtasks. It includes identifying requirements, designing, evaluating, and building prototypes. It explicitly includes the style guide as a mechanism for capturing and disseminating usability goals. Some sub-steps can be skipped if unnecessarily complex for the system being developed.
The Goal-Directed Design Process: Most technology-focused companies don’t have an adequate process for user-centered design. Even enlightened organizations face critical issues from traditional approaches. Quantitative market research and market segmentation falls short of providing critical information about how people actually use products. A second problem is that most traditional methods don’t provide a means of translating research results into design solutions — design remains a “black box.”
Bridging the gap: The role of design in the development process needs to change.
Design as product definition: When properly deployed, design identifies user requirements and defines a detailed plan for the behavior and appearance of products. Design provides true product definition based on goals of users, needs of business, and constraints of technology.
Designers as researchers: If design is to become product definition, designers need to take on broader roles. One problem with current development is overspecialization — researchers perform research and designers perform design. What is missing is a systematic means of translating and synthesizing research into design solutions. One powerful tool designers bring is empathy — the ability to feel what others are feeling. Direct exposure to users immerses designers in the users’ world and gets them thinking about users long before proposing solutions. Isolating designers from users eliminates empathic knowledge.
Between research and design: models, requirements, and frameworks: Few design methods incorporate a means of effectively translating research knowledge into detailed design specifications. Few methods capture user behaviors in a manner that appropriately directs product definition — most provide information at the task level rather than about user goals. Instead, explicit systematic processes are needed for defining user models, establishing design requirements, and translating those into a high-level interaction framework.
Goal-Directed Design seeks to bridge the gap between user research and design through a combination of new techniques and known methods brought together in more effective ways. The process flow is: Research (user and domain) → Modeling (users and use context) → Requirements (definition of user, business, and technical needs) → Framework (definition of design structure and flow) → Refinement (of behavior, form, and content).
⭐ Key Takeaways
A student must understand that different lifecycle models offer different approaches to software development, each with distinct advantages and limitations. The Waterfall model is linear and rigid, failing to accommodate changing requirements or user feedback, while the Spiral model introduces iteration through risk analysis and prototyping. RAD and DSDM emphasize user involvement through time-boxing and JAD workshops. The Star lifecycle places evaluation at its center with no prescribed ordering of activities, making it flexible for HCI design. Finally, Goal-Directed Design bridges the critical gap between user research and design solutions by having designers act as researchers and using systematic processes for defining user models, requirements, and frameworks.
🧠 Quick Revision Questions
- What are the five phases of the traditional Waterfall lifecycle model, and what is its main flaw regarding requirements?
- How does the Spiral lifecycle model differ from the Waterfall model, and what two features does it explicitly incorporate?
- What are the two key features of Rapid Application Development (RAD), and what does DSDM stand for?
- In the Star lifecycle model, what is the role of evaluation, and how are activities related to each other?
- What are the five stages of the Goal-Directed Design process, and why is it important for designers to act as researchers?
📘 Lecture 18 — Goal-Directed Design Methodologies
📖 Overview: This lecture introduces the Goal-Directed Design approach, a methodology that balances user desires, business viability, and technical feasibility to create successful interactive products. It emphasizes understanding user goals and behaviors through systematic phases, while also addressing the critical distinction between beginner, intermediate, and expert users.
🗂️ Topics Covered
The lecture covers the Goal-Directed Design model which balances business, engineering, and user concerns across five phases: Research, Modeling, Requirements Definition, Framework Definition, and Refinement. It describes how ethnographic research and user interviews inform the creation of personas and usage patterns, then explains the importance of designing primarily for perpetual intermediate users rather than beginners or experts.
📝 Lecture Summary
18.1 Goal-Directed Design Model
Underlying the goal-directed approach to design is the premise that a product must balance business and engineering concerns with user concerns. You begin by asking, “What do people desire?” then you ask, “Of the things people desire, what will sustain a business.” And finally you ask, “Of the things people desire, that will also sustain the business, what can we build?” A common trap is to focus on technology while losing sight of viability and desirability.
Understanding the importance of each dimension is only the beginning; understanding must also be acted upon. The goal-directed design process is an analog to business and engineering planning processes—it results in a solid user model and a comprehensive interaction plan. The user plan determines the probability that a customer will adopt a product, the business plan determines the probability that the business can sustain itself, and the technology plan determines the probability that the product can be made to work. Multiplying these three factors determines the overall probability that a product will be successful.
💡 Why this matters: This three-dimensional balance prevents designers from building technically impressive products that nobody wants or businesses that cannot sustain themselves.
18.2 A Process Overview
Goal-Directed Design combines techniques of ethnography, stakeholder interviews, market research, product/literature reviews, detailed user models, scenario-based design, and a core set of interaction principles and patterns. It provides solutions that meet the needs and goals of users while also addressing business/organizational and technical imperatives. The process is divided into five phases:
Research Phase: This phase employs ethnographic field study techniques (observation and contextual interviews) to provide qualitative data about potential and/or actual users of the product. It also includes competitive product audits, reviews of market research and technology white papers, and one-on-one interviews with stakeholders, developers, subject matter experts (SMEs), and technology experts. One of the principal outcomes is an emergent set of usage patterns—identifiable behaviors that help categorize modes of use of a potential or existing product. These patterns suggest goals and motivations (specific and general desired outcomes of using the product). In business and technical domains, these behavior patterns tend to map to professional roles; for consumer products, they tend to correspond to lifestyle choices.
Modeling Phase: During the modeling phase, usage and workflow patterns discovered through analysis are synthesized into domain models (information flow and workflow diagrams) and user models or personas—detailed composite user archetypes that represent distinct groupings of behavior patterns, goals, and motivations. Personas serve as the main characters in narrative scenario-based design and represent a powerful communication tool that helps developers and managers understand design rationale and prioritize features based on user needs. Specific design targets are chosen through a process of comparing goals and assigning a hierarchy of priority.
Possible user persona type designations include:
- Primary: the persona's needs are sufficiently unique to require a distinct interface form and behavior
- Secondary: primary interface serves the needs of the persona with a minor modification or addition
- Supplement: the persona's needs are fully satisfied by a primary interface
- Served: the persona is not an actual user of the product, but is indirectly affected by it and its use
- Negative: the persona is created as an explicit, rhetorical example of whom not to design for
Requirements Definition Phase: This phase employs scenario-based design methods focused on meeting the goals and needs of specific user personas. For each interface/primary persona, the process involves an analysis of persona data and functional needs, prioritized and informed by persona goals, behaviors, and interactions with other personas. The analysis is accomplished through iteratively refined context scenarios that start with a “day in the life” of the persona using the product, describing high-level product touch points, and thereafter successively defining detail at ever-deepening levels. The output is a requirements definition that balances user, business, and technical requirements.
Framework Definition Phase: Teams synthesize an interaction framework by employing general interaction design principles and a set of interaction design patterns that encode general solutions to classes of previously analyzed problems. These patterns are hierarchically organized and continuously evolve. After data and functional needs are described at a high level, they are translated into design elements according to interaction principles, then organized into design sketches and behavior descriptions. The output is an interaction framework definition—a stable design concept that provides the logical and gross formal structure for the detail to come.
Refinement Phase: The refinement phase proceeds similarly to the framework definition phase but with greater focus on task coherence, using key path and validation scenarios focused on storyboarding paths through the interface in high detail. The culmination is detailed documentation of the design—a form and behavior specification delivered in either paper or interactive media.
Goals, Not Features, Are Key to Product Success
Programmers and engineers share a strong tendency to think about products in terms of functions and features because this is how developers build software: function-by-function. The problem is that this is not how users want to use it. The deciding factor for whether a feature should be included should never be simply that we have the technical capability to do it; instead, the deciding factor should be whether that feature directly or indirectly helps to achieve the goals of the user while still meeting the needs of the business.
The successful interaction designer must be sensitive to user's goals amid the pressures and chaos of the product-development cycle. The Goal-Directed process, with its clear rationale for design decisions, makes persuading engineers easier, keeps marketing and management stakeholders in the loop, and ensures that the design isn't just guesswork or a reflection of team members' personal preferences.
18.3 Types of Users
Most users are neither beginners nor experts; instead they are intermediates. If we graph number of people against skill level, a relatively small number of beginners are on the left side, a few experts are on the right, and the majority—intermediate users—are in the center. The bell curve is a snapshot in time. Although beginners do not remain beginners for very long, and experts come and go rapidly, beginners change even more rapidly. Both beginners and experts tend over time to gravitate towards intermediacy.
Nobody remains a beginner for long because people don't like to be incompetent. Beginners become intermediates very quickly—or they drop out altogether. Most users thus remain in a perpetual state of adequacy striving for fluency, with their skills ebbing and flowing depending on how frequently they use the program. Larry Constantine first identified the importance of designing for improving intermediates, but the term perpetual intermediates is preferred because although beginners quickly improve to become intermediates, they seldom go on to become experts.
A well-balanced user interface devotes the bulk of its efforts to satisfying the perpetual intermediate. At the same time, it avoids offending either beginners or experts, recognizing that both are vital. Most users in this middle state would like to learn more about the program but usually don't have the time. Sometimes they use the product extensively and learn new things; other times they don't use the program for months and forget significant portions of what they knew.
Optimizing for Intermediates: Programmers qualify as experts in the software they code because they must explore every possible use case, so their natural tendency is to design implementation model software with every possible option given equal emphasis. Meanwhile, sales, marketing, and management—who demonstrate products to beginners—lobby for bending the interface to serve beginners. Programmers create interaction suitable only for experts, marketers demand interactions suitable only for beginners, but the largest, most stable, and most important group of users is the intermediate group.
Our goal is threefold: to rapidly and painlessly get beginners into intermediacy; to avoid putting obstacles in the way of those intermediates who want to become experts; and most of all, to keep perpetual intermediates happy as they stay firmly in the middle of the skill spectrum.
What Perpetual Intermediates Need: They need access to tools, not explanations of scope and purpose. Tooltips are the perfect perpetual intermediate idiom—they state function in the briefest of terms, consuming minimal video space. Perpetual intermediates know how to use reference materials, so online help via a comprehensive index is a perpetual intermediate tool. They will establish a working set of frequently used functions, and these tools must be placed front-and-center in the user interface. Perpetual intermediates also find it reassuring to know that advanced features exist, even if they don't need them, as it confirms they made the right choice in investing in the program.
⭐ Key Takeaways
The Goal-Directed Design process consists of five sequential phases—Research, Modeling, Requirements Definition, Framework Definition, and Refinement—that balance user, business, and technical concerns. Personas are the central design tool, with primary personas dictating distinct interface forms and other persona types (secondary, supplement, served, negative) having lesser influence. The most critical insight is that most users are perpetual intermediates, not beginners or experts, so design should prioritize making beginners rapidly become intermediates while keeping the majority happy. Programmers tend to design for experts, while marketers push for beginners, yet both approaches ignore the largest user segment. The key to product success is focusing on user goals rather than features.
🧠 Quick Revision Questions
- What are the five phases of the Goal-Directed Design process, and what is the primary output of each phase?
- How does the Goal-Directed Design model balance user desires, business viability, and technical feasibility?
- What are the five persona type designations, and how does each influence the design?
- Why are most users considered "perpetual intermediates," and what should designers do to accommodate them?
- What is the difference between designing for features versus designing for goals, and why is this distinction important?
📘 Lecture 19 — User Research Part-I
📖 Overview: This lecture introduces the foundational concepts of user research in Human Computer Interaction, focusing on the critical distinction between qualitative and quantitative research methods. It emphasizes why understanding users through qualitative techniques is essential for successful design, and provides a detailed exploration of various qualitative research methods that help designers gather rich, contextual information about users, their behaviors, and their environments.
🗂️ Topics Covered
The lecture begins by contrasting qualitative and quantitative research, explaining why human behavior is too complex for purely numerical analysis. It then details the value of qualitative research for understanding user domains, contexts, and constraints. The main body covers six types of qualitative research techniques: stakeholder interviews, subject matter expert interviews, user and customer interviews, user observation/ethnographic field studies, literature review, and product/prototype and competitive audits, each with specific guidance on when and how to apply them.
📝 Lecture Summary
Qualitative versus Quantitative Research
Research is often associated with science and objectivity, but this biases people toward thinking only quantitative data is valid. The notion that "numbers don’t lie" is prevalent, though numbers ascribed to human activities can be manipulated or reinterpreted as dramatically as words. Data from hard sciences like physics is fundamentally different from data on human activities—electrons don’t have moods that vary minute to minute, and the tight controls physicists use are impossible in social sciences. Reducing human behavior to statistics overlooks important nuances that make an enormous difference to product design. Quantitative research can only answer questions about how much or how many along a few reductive axes, while qualitative research tells you about what, how and why in rich, multivariate detail. Social scientists have long recognized that human behaviors are too complex and subject to too many variables to rely solely on quantitative data.
🔑 Definition — Quantitative Research: A type of research that yields numerical data, answering questions about "how much" or "how many" along reductive axes. 🔑 Definition — Qualitative Research: A type of research that provides rich, multivariate detail about what, how, and why regarding human behaviors and experiences. 💡 Why this matters: Understanding this distinction is crucial because designing for human users requires understanding context and meaning, not just countable metrics.
The value of qualitative research
Qualitative research helps understand the domain, context and constraints of a product in more useful ways than quantitative research. It quickly helps identify patterns of behavior among users and potential users. Specifically, qualitative research helps understand: existing products and how they are used; potential users and how they currently approach activities and problems; technical, business, and environmental contexts of the product; and vocabulary and other social aspects of the domain. It also helps design projects by providing credibility and authority to the design team, uniting the team with a common understanding, and empowering management to make more informed decisions. Qualitative methods tend to be faster, less expensive, more flexible, and more likely to provide useful answers to important design questions such as: what problems are people encountering? Into what broader contexts does the product fit? What are the basic goals and tasks?
📌 Example: Qualitative research can answer "What problems are people encountering with their current ways of doing what the product hopes to do?"—a question that quantitative metrics cannot adequately address.
19.1 Types of qualitative research
Social science and usability texts contain many methods for conducting qualitative research. The following techniques are discussed: stakeholder interviews, subject matter expert (SME) interviews, user and customer interviews, user observation/ethnographic field studies, literature review, and product/prototype and competitive audits.
Stakeholder interviews
Research for any new product should start by understanding the business and technical context in which the product will be built. Stakeholders are any key members of the organization commissioning the design work, typically including managers and key contributors from engineering, sales, product marketing, marketing communications, customer support, and usability. They may also include similar people from partner organizations and executives. Interviews with stakeholders should occur before any user research begins. It is most effective to interview each stakeholder one-on-one to promote candor and ensure individual views are not lost. Interviews need not last longer than about an hour. Important information to gather includes: the preliminary vision of the product from each stakeholder perspective; budget and schedule; technical constraints; business drivers; and stakeholders’ perceptions of the user. Understanding these issues helps designers better serve their customers and build internal consensus critical for decision making.
🔑 Definition — Stakeholders: Any key members of the organization commissioning the design work, including managers and key contributors from various departments. 💡 Why this matters: Different business departments may have slightly different and incomplete perspectives on the product, like the fable of the blind men and the elephant, and these must be harmonized with user perspectives.
Subject matter expert (SME) interviews
Some stakeholders may also be subject matter experts (SMEs) : experts on the domain within which the product will operate. Most SMEs were users of the product or its predecessors at one time and may now be trainers, managers, or consultants. They can provide valuable perspective, but designers should recognize that SMEs represent a somewhat skewed perspective. Points to consider: SMEs are expert users whose long experience may have made them accustomed to current interactions; they are not designers, so the most useful information from their suggestions is the causative problems leading to their proposed solutions; SMEs are necessary in complex or specialized domains such as medical, scientific, or financial services; and you will want access to SMEs throughout the design process for reality checks on design details.
🔑 Definition — Subject Matter Expert (SME): An expert on the domain within which the product will operate, often a former user now serving as trainer, manager, or consultant.
User and customer interviews
It is easy to confuse users with customers. For consumer products, customers are often the same as users, but in corporate or technical domains, they rarely describe the same people. Customers are those who make the decision to purchase the product. For consumer products, customers are frequently users, though for products aimed at children, customers are parents. In enterprise products, the customer is often an IT manager with distinct goals. It's important to understand customers and their goals to make a product viable, while realizing that customers seldom use the product themselves. When interviewing customers, you want to understand: their goals in purchasing, frustrations with current solutions, decision process, role in installation and management, and domain issues. Users should be the main focus of the design effort—they are the people personally trying to accomplish something with the product. A good set of user interviews includes both current and potential users. Information from users includes: problems and frustrations, context of use, domain knowledge from a user perspective, current tasks, and user goals.
🔑 Definition — Customers: People who make the decision to purchase a product, who may or may not be the actual users. 🔑 Definition — Users: People who personally try to accomplish something with the product, should be the main focus of the design effort.
User observation
Most people cannot accurately assess their own behaviors, especially outside the context of their activities. Interviews performed outside the context of situations yield less complete and less accurate data. You can talk to users about how they think they behave, or observe it first hand—the latter provides superior results. Many usability professionals use technological aids like audio or video recorders, but care must be taken not to make these too obtrusive. Perhaps the most effective technique for gathering qualitative user data combines interviews and observation, allowing the designer to ask clarifying questions about situations and behaviors observed in real-time.
Literature review
In parallel with stakeholder interviews, the design team should review any literature pertaining to the product or its domain. This can include product marketing plans, market research, technology specifications and white papers, business and technical journal articles, competitive studies, Web searches, usability study results, and customer support data. The design team should collect this literature, use it as a basis for developing questions, and later use it to supply additional domain knowledge and vocabulary.
Product and competitive audits
Also in parallel to stakeholder and SME interviews, it is helpful for the design team to examine any existing version or prototype of the product, as well as its chief competitors. Doing so gives the design team a sense of the state of the art and provides fuel for questions during interviews. The team should engage in an informal heuristic or expert review of both the current and competitive interfaces, comparing each against interaction and visual design principles. This familiarize the team with strengths and limitations of what is currently available.
🔑 Definition — Heuristic Review: An informal evaluation of a user interface against established usability principles or "heuristics."
⭐ Key Takeaways
The most critical distinction from this lecture is between qualitative research, which explores what, how, and why in rich detail, and quantitative research, which only measures how much or how many—human behavior is too complex for purely numerical analysis. Students must remember that qualitative research is essential for understanding domain context, user behaviors, and design constraints, and it tends to be faster and more flexible than quantitative approaches. The six types of qualitative research each serve a specific purpose: stakeholder interviews provide business and technical context; SME interviews offer specialized domain expertise; user and customer interviews reveal distinct perspectives from purchasers versus actual users; user observation captures authentic behavior that self-reporting cannot; literature review supplies background knowledge; and competitive audits establish the state of the art. A critical point is that customers (who buy the product) and users (who use it) are often different people, especially in enterprise contexts, and both must be understood separately. Finally, the most effective user research combines interviews with direct observation in the user's natural context, as people cannot accurately report their own behaviors outside their environment.
🧠 Quick Revision Questions
- What are the fundamental differences between qualitative and quantitative research in terms of the types of questions they can answer?
- Why is it important to conduct stakeholder interviews before any user research begins?
- What is the key distinction between customers and users, and why must designers treat them differently?
- Why does the lecture claim that user observation provides superior results compared to interviews alone?
- What types of information should a design team gather during a literature review, and how should this information be used?