π Lecture 1 β Introduction to Human Computer Interaction β Part I
π Overview: This lecture introduces the field of Human Computer Interaction (HCI) by examining how technology has evolved from the 1950s to the present day. It uses compelling real-world examples to demonstrate why HCI is critically important for designing systems that serve human needs rather than frustrate them.
ποΈ Topics Covered
The lecture covers the historical evolution of computers from expensive, specialist-only machines to ubiquitous everyday devices, the consequences of poor interface design illustrated through multiple case studies (airline crash, digital cameras, alarm clocks, cars, and warships), and concludes with a formal definition of HCI and its role in bridging the gap between human understanding and machine interfaces.
π Lecture Summary
Introduction to Human Computer Interaction β Part I
The lecture opens by describing how computers have invaded every aspect of modern life. Devices like ATMs, cell phones, VCRs, remote controls, ticketing machines, digital personal organizers, calculators, watches, photocopiers, toasters, banks, air conditioners, microwaves, and medical equipment all contain computers. Unlike the 1950s when only highly skilled technical specialists used computers, today users come from every walk of life β commerce, farming, education, retailing, defense, manufacturing, and entertainment.
In the 1950s, computers were extremely difficult to use for several reasons: they were very large and expensive machines (making human labor cheap by comparison), used only by technical specialists familiar with punch cards, and little was known about how to make them easier to use. None of these conditions hold today β computers have become much less expensive, users are diverse, and we understand much more about fitting machines to people's needs.
The silicon chip enabled dramatic decreases in computing costs, allowing miniaturization and packing large numbers of circuits onto tiny chips. In less than thirty years, computers changed from huge machines in air-conditioned rooms to small portable devices. The development of the first personal computers in the 1970s was a major landmark, providing interactive computing power for individual users at low cost.
π‘ Why this matters: Computers now perform more and more tasks, making life without them as unimaginable as life without electricity. However, this invasion has both bright and dark sides.
Bright side results: Computers are enabling new discoveries, leading to efficiencies, and making our life easy and convenient.
Not so bright side results: Computers are annoying us, infuriating us, and even killing a few of us. We are irreversibly dependent on these "hopeful monsters," so we must fundamentally rethink how human and machines interact.
1.1 Riddles for the Information Age
This section presents four case studies demonstrating what happens when computers are integrated into everyday objects.
Riddle 1: Computer with an Airplane In December 1995, American Airlines Flight 965 departed from Miami to Cali, Columbia. On landing approach, the pilot of the 757 needed to select the navigation fix "ROZO". He entered "R" into his navigation computer, which returned a list of nearby fixes starting with "R". The pilot selected the first option β "ROMEO", 132 miles northeast instead of "ROZO". The jet descended into a north-south valley, followed the flight computer indications, began an easterly turn, and slammed into a granite peak at 10,000 feet. 152 passengers and all 8 crewmembers perished; only 4 survived with serious injuries.
Riddle 2: Computer with a Camera The evolution of cameras demonstrates increasing complexity:
- Thirty years ago: A 35mm Pentax Model H had a small battery for the light meter, simple to maintain
- Fifteen years ago: A 35mm Canon T70 used two AA batteries with a simple On/Off switch
- Five years ago: A first-generation digital camera had automatic shutdown after one minute of inactivity
- One year ago: A Panasonic PalmCam had an Off/Rec/Play switch with modes
- Newest: A Nikon CoolPix 900 (third-generation) displays a Windows-like hourglass while booting up, with four switch settings: Off/ARec/MRec/Play
π Definition β ARec: "automatic record" mode on the digital camera π Definition β MRec: "manual record" mode on the digital camera
The Nikon's power management program causes problems: when zooming, charging flash, and energizing display simultaneously drains power, it suspends picture-taking ability. When the user presses the shutter button, it shuts down the LCD display to shed load. When the user drops the camera, it senses more power available and takes a picture β of the user's kneecap.
Riddle 3: Computer with an Alarm Clock A JVC FS-2000 clock-radio has sophisticated computer features including fading up volume at 6 AM. However, it's very hard to tell when the alarm is armed, so it occasionally fails to wake the user on Monday and wakes them early on Saturday. The alarm indicator is a small symbol in the upper left corner of an alphanumeric liquid crystal display (LCD) β barely visible in a dim bedroom. The backlight only comes on when CD or radio is explicitly turned on, but the alarm won't sound while the CD is left on regardless of alarm settings.
To disarm the alarm: press "Alarm" button once. To arm it: press exactly five times (showing alarm time, sound-off time, radio/CD selection, preset volume, then normal view with alarm armed). One additional press disarms it.
By contrast, an old non-computerized alarm clock had a single red light when armed, dark when not armed β simple and clear.
Riddle 4: Computer with a Car Porsche's Boxster has seven computers, including one dedicated to engine management. In early models, if fuel level got very low (about one gallon remaining), centrifugal force from a sharp turn could cause fuel to collect at the tank side, letting air enter fuel lines. The computer interpreted this as catastrophic injection system failure and shut down the ignition completely, preventing restart until the car was towed and serviced. The only solution Porsche offered was disconnecting the battery for five minutes to reset the computer.
Riddle 5: Computer with a Warship In September 1997, the USS Yorktown (an Aegis guided-missile cruiser) stopped dead in the water during fleet maneuvers. A Navy technician entered a zero while calibrating an on-board fuel valve into a Pentium Pro running Windows NT. The program attempted to divide another number by zero (an undefined mathematical operation), causing a complete crash of the entire shipboard control system. The engine halted, and the ship sat for 2 hours and 55 minutes until towed to port.
1.2 Role of HCI
Humans designed the frustrating interfaces we hate. Humans continue to use dysfunctional machines even as awkward interfaces strain their eyes, ache their backs, and ruin their wrist tendons. HCI plays a role to bridge the gap between machine interfaces and human understanding.
π Definition β Human-Computer Interaction (HCI): "A discipline concerned with the design, evaluation and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them" β ACM/IEEE
β Key Takeaways
HCI is fundamentally about designing systems that fit human needs rather than forcing humans to adapt to machine logic. The lecture demonstrates through real-world tragedies (plane crash killing 160 people) and everyday frustrations (cameras, alarm clocks, cars) that poor interface design has serious consequences β from inconvenience to loss of life. The definition of HCI encompasses design, evaluation, implementation, and study of interactive systems. Computers will continue to infiltrate every product because it's economically cheaper than mechanical methods, making HCI knowledge essential. The fault for bad design lies with humans, not machines, and we must fundamentally rethink human-machine relationships.
π§ Quick Revision Questions
- What four factors made 1950s computers extremely difficult to use?
- What specific interface failure caused the crash of American Airlines Flight 965?
- How does the Nikon CoolPix 900's power management program fail its user?
- What happened to the USS Yorktown and why?
- According to the ACM/IEEE definition, what four components comprise the discipline of Human-Computer Interaction?
π Lecture 2 β Introduction to Human-Computer Interaction β Part II
π Overview: This lecture examines the adverse impacts of poor human-computer interaction through real-world examples like airplane crashes and confusing car interfaces. It introduces the formal definition of HCI, contrasts human and computer capabilities, and explains the concept of "software apartheid" β how poorly designed software creates social and economic divisions. The lecture also differentiates the user-centered focus of HCI from the system-centered focus of Software Engineering.
ποΈ Topics Covered
The lecture covers the formal ACM/IEEE definition of HCI, analyzes the fatal American Airlines Flight 965 crash as a case study of poor computer communication, and examines other problematic interfaces like BMW's iDrive system and ATMs. It then contrasts the nature of humans versus computers, introduces the concept of software apartheid, and concludes by differentiating the approaches of Software Engineering (system-centered) and HCI (user-centered).
π Lecture Summary
2.1 Definition of HCI
The formal definition of Human-Computer Interaction is provided by the ACM/IEEE: βHuman-Computer Interaction is a discipline concerned with the design, evaluation and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them.β This establishes HCI as a discipline that goes beyond just building systems to understanding the entire context of human use.
π Definition β HCI (Human-Computer Interaction): A discipline concerned with the design, evaluation, and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them.
2.2 Reasons of non-bright Aspects
This section examines real-world examples where computer systems failed their human users, often with tragic consequences. The core argument is that computers "may tell us facts but they don't inform us."
Airplane + Computer Case Study: The lecture analyzes the fatal crash of American Airlines Flight 965 in Cali, Colombia. The National Transportation Safety Board (NTSB) declared the cause "human error" β the pilot selected the wrong navigation fix (ROMEO instead of the correct fix for landing). However, the lecture argues this was not truly the pilot's fault. The flight computer's front panel showed the selected fix and a course deviation indicator (needle), but the needle looked the same whether the plane was on course to land or on course to crash. The computer gave no indication that ROMEO was an inappropriate fix for the landing approach.
π‘ Why this matters: The computer was "utterly unconcerned with the actual flight and its passengers" β it only cared about its own internal computations, not the real-world consequences of its output.
The Computer Industry Joke: A pilot lost in clouds asks "Where am I?" and gets the reply: "You are in an airplane about 100 feet above the ground." The pilot immediately knows the course because the answer was "completely correct and factual, yet it was no help whatsoever" β revealing the responder was a Microsoft software engineer. This joke highlights a "fundamental truth about computers: They may tell us facts but they don't inform us. They may guide us with precision but they don't guide us where we want to go."
I-Drive Car Device: BMW's iDrive system uses a single large, multifunction knob in the console between the front seats. Users rotate the knob to scroll through menus, push it axially to select, and move it forward/back or side-to-side to change functions (communications, climate control, navigation, entertainment). Several hundred functions are controlled with this one device.
The fundamental problems include:
- Users must look at an LCD screen to see what they're selecting, taking their eyes off the road
- Force feedback indicates the menu level but not the actual content in the menus
- It "takes 15 minutes to change a Radio Channel"
- Results in constant calls to help desk
Feature Shock: "Every digital device has more features than its manual counterpart, but manual devices are easier to use." Hi-tech companies add more features thinking it improves the product, but the product becomes complicated. The key insight: "Bad process can't improve product."
Computer + Bank (ATM Case Study): The ATM exhibits "sullen and difficult behavior." If the user makes the slightest mistake (like selecting "savings" when they only have checking), it rejects the entire transaction and forces them to start over. The ATM knows the user doesn't have a savings account, yet still offers it as a choice β then punishes the user for selecting it. "The only difference between me selecting 'saving' and the pilot of Flight 965 selecting 'ROMEO' is the magnitude of the penalty."
The lecture notes that this behavior "is not intrinsic to computers... nothing is intrinsic to computers: they merely act on behalf of their software, the program." Programs are "as malleable as human speech" β they can be polite or rude. "All it takes is for someone to describe how. Unfortunately, programmers arenβt very good at teaching that to computers."
π‘ Why this matters: This problematic behavior across all these examples is what drives the need for the emerging field of Human-Computer Interaction.
2.3 Human verses Computer
Human species: Human beings are the "most interesting and fascinating specie on planet." They are complex, diverse, intelligent, and free in nature. Humans "think on a problem dynamically" and can find solutions that "may not exist before." They can invent. They are both rational and emotional. "And fortunately or unfortunately they make mistakes."
Computer species: Computers are an invention of human beings. They are "complex but also pretty dumb." They "can think but can't think on its own will" β they think only as directed. Their speed is "marvelous." They "do not tire. It is emotionless. It has no feelings, no desires." And "they do not make mistakes."
Before vs. Now: Before computer penetration in daily life, humans performed tasks with personal responsibility and interaction. A salesperson could judge a client's mood through tone, attitude, and body language, providing relevant answers. Now, "in this age of information technology we are expecting computers to mimic human behavior" β e.g., eCommerce websites acting as salespersons. "That is now; a dumb, unintelligent and inanimate object will perform the complex task which was performed by some human being."
2.4 Software Apartheid
Apartheid definition: "Racial segregation; specifically: a policy of segregation and political and economic discrimination against non-European groups in the Republic of South Africa."
π Definition β Software Apartheid: Institutionalizing obnoxious behavior and obscure interactions of software-based products.
The lecture argues that programmers "work in high-tech environments, surrounded by their technical peers" (like Silicon Valley), with limited contact with frustrated users. The term "computer literacy" is used as a requirement β assuming users must acquire fundamental training to use computers. However, "having a computer literate customer base makes the development process much easier... but it hampers the growth and success of the industry and of society."
The Car Analogy Refuted: Apologists counter that "you must have training and a license to drive a car," but they overlook that "a mistake with software generally does not [cause death]. If cars were not so deadly, people would train themselves to derive the same way they learn excel."
Social Division: The requirement for computer literacy creates "a demarcation line between the haves and have-nots in society." If you must master a computer to succeed in the job market, the difficulty of using interactive systems "forces many people into menial jobs rather than allowing them to matriculate into more productive, respected and better-paying jobs."
Key Arguments:
- "Users should not have to acquire computer literacy to use computer for common, rudimentary task in everyday life"
- An accountant "trained in the general principles of accounting, should not have to become computer literate to use a computer in her accounting practice. Her domain knowledge should be enough to see her through"
- The term "computer literacy" becomes "a euphemism for social and economic apartheid"
- "Software-based products not INHERENTLY hard to use β Wrong process is used to develop them"
π Definition β Computer Literacy (as critiqued): A key phrase that brutally bifurcates our society, creating an artificial barrier between those who can use technology and those who cannot, based on technical knowledge that should be inconsequential.
Software Engineering and HCI
"There is a basic fundamental difference between the approaches taken by software engineers and human-computer interaction specialists. Human-computer interface specialists are user-centered and software engineers are system-centered."
Software Engineering Approach:
- Good at modeling certain aspects of the problem domain
- Formal methods developed to represent data, architectural, and procedural aspects
- Deals with managerial and financial issues well
- Useful for specifying and building functional aspects of a software system
HCI Approach:
- Emphasizes developing a deep understanding of user characteristics
- Clear awareness of the tasks a user must perform
- Tests design ideas on real users
- Uses formal evaluation techniques to replace intuition in guiding design
- "This constant reality check improves the final product"
β Key Takeaways
The most critical lesson is that computers can provide precise, factually correct information while being tragically unhelpful or dangerous β they may tell us facts but don't inform us. Poor interface design has real-world consequences ranging from fatal accidents (Flight 965) to everyday frustration (ATMs, car controls). The concept of software apartheid reveals that requiring "computer literacy" for basic tasks creates artificial social and economic divisions, forcing people to master irrelevant technical distinctions (like RAM vs. Hard Disk) to participate in the modern economy. The fundamental difference between SE and HCI is that SE is system-centered (focused on data, architecture, and procedures) while HCI is user-centered (focused on understanding user characteristics, tasks, and testing with real users). Poor software interfaces are not inevitable β they result from using the wrong development process.
π§ Quick Revision Questions
- What is the ACM/IEEE definition of Human-Computer Interaction?
- Why does the lecture argue that the crash of Flight 965 was not truly "human error" by the pilot?
- What is "software apartheid" and how does the concept of "computer literacy" contribute to it?
- Compare and contrast the nature of human beings versus computers as described in this lecture.
- How does the approach of Software Engineering differ from the approach of HCI specialists in developing interactive systems?
π Lecture 3 β Introduction to Human-Computer Interaction β Part III
π Overview: This lecture explores the real-world consequences of poor design in high-tech tools, using vivid examples from the airline industry and studies on "techno-rage." It explains why the high-tech industry is in denial about usability problems, and defines what it takes to succeed in the new economy by mastering the intersection of business and technology.
ποΈ Topics Covered
The lecture begins by examining the negative effects of bad tools, using case studies of in-flight entertainment systems. It then discusses the high-tech industry's denial of usability failures and the phenomenon of "techno-rage," supported by survey data on user frustration and attacks on computers. Finally, it presents success criteria for the new economy, emphasizing the need for business-savvy technologists and technology-savvy businesspeople, and concludes with a legal case about web accessibility.
π Lecture Summary
Effect of Bad Tools
The lecture uses the example of in-flight entertainment (IFE) systems to illustrate the catastrophic consequences of bad design. One airlineβs IFE was so frustrating for flight attendants that they preferred shorter, less glamorous routes to avoid using it. This caused a serious morale problem, costing the airline money, customer loyalty, and staff loyalty.
Another airlineβs IFE was even worse because it linked movie delivery with cash collection. This forced flight attendants to walk to a console, enter a password, and complete a cash-register transaction before a passenger could watch a movie. Out of sheer frustration, flight attendants would trip the circuit breaker on the system at the start of each flight and announce it was broken. The airline had spent millions on a system so obnoxious that its users deliberately turned it off to avoid interacting with it, causing a catastrophic financial loss.
π‘ Why this matters: The software inside the IFEs worked with flawless precision but was a resounding failure because it misbehaved with its human keepers. This highlights that technical perfection is worthless without good user experience.
3.1 An Industry in Denial
The high-tech industry is in denial about the fact that its products are difficult to use. Technologists and software engineers believe they have done their best and that only new technology (like voice recognition or AI) can improve the user experience. However, the real problem is not technology, but a deficiency in culture, training, and attitude in the development process.
The industry has inadvertently put programmers and engineers in charge, whose hard-to-use engineering culture dominates. The lecture states, "We have let the inmates run the asylum." When creators examine their products, they see rich features, but ignore how difficult they are to use, how long they take to learn, and how they degrade the people who must use them.
3.2 Techno-Rage
A widespread undercurrent of techno-rage is rising. An article in the Wall Street Journal described a popular video clip of a man violently attacking his computer, which tapped into a powerful feeling of frustration. A joke about "Computer Touretteβs" describes otherwise-normal people swearing repeatedly at their monitors due to frustrating interactions.
The Novatech survey of 4,200 replies revealed a dark story: one in every four computers has been physically attacked by its owner. Technical support people worldwide have stories of computers brought in for repair that were deliberately smacked, kicked, or otherwise injured.
Another study by Symantec and Britainβs National Opinion Poll found that over 40% of British users have sworn at, kicked, or abused their computers. A separate survey by Concord Communications found that 83% of U.S. respondents had witnessed such attacks. Stress from computer rage has resulted in a loss of productivity and is described as being "much more prolific than road rage." The most frustrating incident is when people lose their work after a computer crash.
Key statistics from the studies:
- 70% swear at PCs
- 67% experienced frustration, exasperation, and anger
- Nearly half of all computer users had become angry at some time.
3.3 Success Criteria in the New Economy
The successful professional of the 21st century is either a business-savvy technologist or a technology-savvy businessperson.
- A technology-savvy businessperson knows their success depends on the quality of information and how they use it.
- A business-savvy technologist is an engineer with a keen business sense.
All businesspeople can be divided into two categories: those who master high technology, and those who will soon go out of business. Business is now information processing, and digital information is the beating heart of the workday. Bad information processes can cause a company to lose everything. The lecture shares several facts and figures highlighting the cost of bad user experience:
- Users can only find information 42% of the time (Jared Spool).
- 62% of web shoppers give up looking for an item (Zona Research).
- 50% of potential sales from a site are lost because people can't find items (Forrester Research).
- 80% of software lifecycle costs occur after release, and 80% of that is due to unmet user requirements (IEEE Software).
- 63% of software projects exceed cost estimates due to user changes, overlooked tasks, and poor communication (Communications of the ACM).
- BOO.com, a $204m startup, failed (BBC News).
- Poor web sites will kill 80% of Fortune 500 companies within a decade (Jakob Nielsen).
The product with bad user experience deserves to die. The lecture illustrates this with a table comparing two scenarios of an e-commerce site with a $100 million revenue potential. In Scenario A (good user experience), 0% sales are lost, and actual revenue is $100 million. In Scenario B (bad user experience), 50% of sales are lost, and actual revenue is only $50 million, resulting in a $50 million loss.
3.4 Computer + Information
The lecture asks, "What do you get when you cross a computer with information?" and answers by describing a lawsuit. Before the 2000 Sydney Olympics, a blind man, Bruce Lindsay Maguire, filed a lawsuit against the Sydney Organizing Committee for the Olympic Games (SOCOG) for unlawful discrimination. He complained that the website was not accessible to him.
According to the law in many countries, organizations must ensure their websites are accessible to disabled persons. The SOCOG website was not. The result was that the complainant won the case and was awarded damages. This was very embarrassing for SOCOG and the company that developed the website.
β Key Takeaways
Bad tools can cause catastrophic financial and morale damage, as shown by the IFE examples where users deliberately turned off expensive systems. The high-tech industry is in denial, blaming a lack of new technology instead of a flawed development culture that prioritizes features over user-friendliness. This has led to widespread "techno-rage," with a significant percentage of users verbally and physically attacking their computers, costing productivity and increasing stress. To succeed in the new economy, professionals must be both business-savvy and tech-savvy, as poor user experience leads to massive revenue losses, project failures, and even legal consequences for accessibility violations.
π§ Quick Revision Questions
- What were the two specific design flaws in the in-flight entertainment systems that led flight attendants to sabotage them?
- According to the lecture, what is the true cause of the difficulty in using high-tech products, and who is blamed instead?
- What was the result of the Novatech survey regarding physical attacks on computers, and what did the Symantec study find about the prevalence of "techno-rage"?
- Name three statistics that prove the significant financial cost of a bad user experience on e-commerce websites.
- What was the legal outcome of the Bruce Lindsay Maguire vs. SOCOG case, and what core accessibility issue did it address?
π Lecture 4 β Goals & Evolution of Human Computer Interaction
π Overview: This lecture defines the core goals of Human-Computer Interaction, distinguishing between usability goals (effectiveness, efficiency, safety, utility, learnability, memorability) and user experience goals (satisfaction, enjoyment, fun). It also traces the historical evolution of HCI through landmark systems like the Dynabook, Xerox Star, and Apple Lisa, highlighting key design principles that shaped modern interfaces.
ποΈ Topics Covered
The lecture begins with a formal definition of HCI from ACM/IEEE, then delves into the two major categories of HCI goals: usability goals and user experience goals. Each usability goal is explained in detail with real-world examples. The second half covers the evolution of HCI, focusing on three pioneering systemsβDynabook, Star, and Lisaβand their contributions such as direct manipulation, WYSIWYG, and consistency. The section concludes with transatlantic research differences and the emergence of the user interface concept.
π Lecture Summary
4.1 Goals of HCI
The term Human Computer Interaction (HCI) was adopted in the mid-1980s to describe a field broader than just interface design, encompassing all aspects of interaction between users and computers. The goals of HCI are to produce usable, safe, and functional systems. These goals can be summarized as "to develop or improve the safety, utility, effectiveness, efficiency and usability of systems that include computers." The term 'system' refers not just to hardware and software but to the entire environmentβincluding people at work, home, or leisure. Utility refers to the functionality of a system. Usability is a key concept concerned with making systems easy to learn and easy to use.
Part of understanding user needs involves clarifying the primary objective: designing an efficient system for high productivity, a challenging system for learning, or something else. These are called usability goals and user experience goals. Usability goals meet specific criteria (e.g., efficiency), while user experience goals concern the quality of the user experience (e.g., being aesthetically pleasing).
π Definition β HCI: "Human-Computer Interaction is a discipline concerned with the design, evaluation and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them" (ACM/IEEE).
Usability goals
Usability involves optimizing interactions to enable users to carry out activities at work, school, and in everyday life. It is broken down into six specific goals.
Effectiveness It is a very general goal and refers to how good a system is at doing what it is supposed to do.
π Definition β Effectiveness: How good a system is at doing what it is supposed to do.
Efficiency It refers to the way a system supports users in carrying out their tasks.
π Definition β Efficiency: The way a system supports users in carrying out their tasks.
Safety It involves protecting users from dangerous conditions and undesirable situations. This includes two aspects: first, external working conditions (e.g., controlling X-ray machines remotely); second, helping users avoid accidental unwanted actions. Safety mechanisms include: preventing serious errors by not placing quit/delete commands next to save commands, and providing means of recovery should errors occur. Undo facilities and confirmatory dialog boxes (e.g., "Are you sure you want to delete all these messages?") are common safety features.
π Definition β Safety: Protecting users from dangerous conditions and undesirable situations, including preventing errors and providing recovery mechanisms.
Utility It refers to the extent to which the system provides the right kind of functionality so users can do what they need or want to do. An example of high utility is an accounting software package providing powerful computational tools. An example of low utility is a drawing tool that forces users to use only polygon shapes and does not allow freehand drawing.
π Definition β Utility: The extent to which a system provides the right kind of functionality for users' needs.
Learnability It refers to how easy a system is to learn to use. People want to get started straight away without spending too much time learning. This is especially important for everyday products (e.g., interactive TV, email) and infrequently used systems. For complex systems (e.g., web authoring tools), people are prepared to spend longer learning. A key concern is determining how much time users are willing to spend learning.
π Definition β Learnability: How easy a system is to learn to use.
Memorability It refers to how easy a system is to remember how to use, once learned. This is especially important for infrequently used systems. Users should be able to remember or be rapidly reminded how to use a system without having to relearn tasks. Design supports memorability through meaningful icons, command names, menu options, and structuring options into relevant categories.
π Definition β Memorability: How easy a system is to remember how to use, once learned.
"Don't Make me THINK, is the key to a usable product"
User experience goals
The emergence of new technologies (virtual reality, web, mobile computing) in diverse application areas (entertainment, education, home) has brought about wider concerns. Beyond improving efficiency and productivity, interaction design increasingly concerns itself with creating systems that are:
- Satisfying
- Enjoyable
- Fun
- Entertaining
- Helpful
- Motivating
- Aesthetically pleasing
- Supportive of creativity
- Rewarding
- Emotionally fulfilling
These goals are concerned primarily with the user experienceβwhat the interaction with the system feels like to the users. User experience goals differ from objective usability goals because they are concerned with how users experience a product from their perspective, rather than assessing how useful or productive a system is. Recognizing trade-offs between usability and user experience goals is important, as some combinations may be incompatible (e.g., designing a process control system that is both safe and fun).
π‘ Why this matters: Understanding the difference between usability and user experience goals helps designers make conscious trade-offs based on user needs. A banking app prioritizes safety and efficiency, while a game prioritizes fun and enjoyment.
4.2 Evolution of HCI
HCI takes place within a social and organizational context. Knowledge of human psychological and physiological abilities and limitations is important, including human information processing, language, communication, interaction, and ergonomics. Equally essential is knowledge of computer hardware and software possibilities, including input techniques, dialogue technique, dialogue genre/style, computer graphics, and dialogue architecture. This knowledge is brought together in the design and development of systems. Evolution plays an important role by enabling designers to check that their ideas match user needs.
Three landmark systems along this evolutionary path are the Dynabook, the Star, and the Apple Lisa. A unifying theme is that they provided effective, easy interaction for both novices and experts, with visual-spatial interfaces where objects could be directly manipulated with immediate feedback.
Dynabook Alan Kay designed the first object-oriented programming language, Smalltalk, in the 1970s, which became the basis for windows technology. Kay envisioned the Dynabookβa notebook-sized computer with a keyboard on the bottom and a high-resolution screen at the top.
Star The Xerox Star drew on PARC's ideas to create an integrated system for office environments, designed for users with no previous computer experience. The Star pioneered icons, moveable scrollable windows, and intermixed text and graphic images. The graphic user interfaces (GUIs) of today are variants of this original design.
Key design principles of the Star included:
Direct manipulation The core concept used a bitmapped screen to present direct visual representations of objects. Using a desktop metaphor, documents, printers, folders, and other office objects were depicted on screen. To print a document, the user could point to the document icon and printer icon while using a key to indicate a Copy operation.
WYSIWYG (what you see is what you get) Unlike previous programs where users created a programming-like representation and compiled it, the user works directly with the desired form through direct manipulation. The Star user could intermix text, tables, graphs, drawings, and mathematical formulas.
Consistency of commands Because a single development group developed all Star applications, a coherent and consistent design language was possible. The Star keyboard embodied generic commands used consistently across all applications: Move, Copy, Delete, Open, Show Properties, and Same. Evoking a command produced the same behavior regardless of the object type. Through property sheets, users could manipulate element-specific aspects.
Other unique features included attention to the communicative aspects of graphic design, integration of an end-user scripting language (CUSP), and mechanisms for internationalization.
Lisa by Apple The Apple Lisa introduced the GUI that started it allβwith a mouse and pull-down menus. The first Lisa had dual 5.25 inch floppy drives and an external hard drive. The Lisa 2/10 moved the hard drive inside, lost one floppy drive, and shared the new 3.5-inch floppy with the Macintosh. Lisa was later marketed as the Macintosh XL, lacking the ROM toolbox built into every Macintosh, so it used MacWorks to emulate a Macintosh.
Earlier groundwork included Licklider (1960), who visualized a symbiotic relationship between humans and computers, and Sutherland (1963), who developed the Sketchpad system at MIT, introducing the ability to display, manipulate, and copy pictures on screen and the use of the light pen.
Alongside graphic interfaces, interactive text processing systems evolved. The underlying philosophy of WYSIWYG ("what you see is what you get") displayed documents on screen exactly as they would look in printed form, contrasting with earlier editors where commands were embedded in text.
Interesting transatlantic differences emerged: USA pioneers were concerned with how computers could enrich lives and facilitate creativity. European researchers (1980s) focused on constructing theories of HCI and developing design methods ensuring user needs were considered. One major European contribution was formalizing the concept of usability (Shackel, 1981).
During the 1970s, the notion of user interface (also called Man-Machine Interface or MMI) became a general concern. Moran defined this as "those aspects of the system that the user comes in contact with," meaning "an input language for the user, an output language for the machine, and a protocol for interaction."
Academic researchers focused on the capabilities and limitations of human usersβunderstanding the 'people side' of interaction. As the field developed, it became clear that other aspectsβmanagement, organizational issues, health hazardsβall contribute to the success or failure of computer systems.
β Key Takeaways
The six usability goals (effectiveness, efficiency, safety, utility, learnability, memorability) are objective criteria for evaluating how well a system supports user tasks, while user experience goals (enjoyment, fun, aesthetic appeal, etc.) capture subjective feelings about interaction. Designers must recognize trade-offs between these two categories, as some goals may be incompatible for certain systems. The evolution of HCI is marked by landmark systemsβDynabook (vision of portable computing), Star (pioneering direct manipulation, WYSIWYG, and consistency), and Lisa (popularizing the GUI)βwhich established foundational design principles still used today. Understanding both human capabilities/limitations and technological possibilities is essential for creating effective interactive systems.
π§ Quick Revision Questions
- What are the six specific usability goals, and how does each differ in focus?
- How do user experience goals differ from usability goals in terms of what they measure?
- What were the three key design principles of the Xerox Star, and how did each improve user interaction?
- Who developed the Dynabook concept, and what was its significance for personal computing?
- What was the difference between US and European research approaches to HCI during its early evolution?