Goal-Directed Design: Design Serves Human Goals, Not Tasks

Users' real purpose in using software is not to 'complete a task' but to achieve a deeper life goal. Cooper distinguishes three goal levels: life goals (who the user wants to be), end goals (what the user wants to accomplish in this session), and experience goals (how the user wants to feel during use). Good interaction design must understand and serve all three goal levels, not merely optimize task completion efficiency.

Source: About Face: The Essentials of Interaction Design, 4th ed., by Alan Cooper et al., Wiley, 2014 / The Inmates Are Running the Asylum by Alan Cooper, Sams Publishing, 1999, Chapter 3

Persona: Design for a Specific Person, Not Statistics

When you design for 'all users,' you are effectively designing for no specific person. Persona creates a fictional specific character based on real user research, giving the design team a genuine 'reference point.' Designing for '32-year-old marketing manager Margaret who uses Excel daily to manage client data but doesn't understand macros' is much more concrete than designing for 'intermediate office users,' and design decisions become correspondingly clearer.

Source: The Inmates Are Running the Asylum by Alan Cooper, Sams Publishing, 1999 / About Face 3.0: The Essentials of Interaction Design by Alan Cooper, Robert Reimann, and David Cronin, Wiley, 2007

Software Industry's Core Problem: Programmers Designing for Themselves

Cooper's core criticism is that the software industry is 'an asylum run by inmates' — technologists are product decision-makers who build software according to their own mental models rather than users' mental models. This leads to pervasive 'feature creep,' complex interfaces, and interaction patterns that make users feel stupid. The solution is not to train users but to fundamentally change the software development process so interaction designers define product behavior before technologists.

Source: The Inmates Are Running the Asylum by Alan Cooper, Sams Publishing, 1999, Chapter 1

Mental Model: User Expectations Are the True Standard for Interface

Users come to products with expectations about 'how this software should work.' When the software's actual behavior (implementation model) diverges from users' expectations (mental model), cognitive friction arises. The goal of good interaction design is to make software behavior align as closely as possible with users' mental models rather than forcing users to learn engineering logic.

Source: About Face: The Essentials of Interaction Design, 4th ed., by Alan Cooper et al., Wiley, 2014, Chapter 2

Persona Creation Framework

Distill from user research data a fictional character with a name, story, and concrete goals, giving design conversations a real subject.

When designing a medical records software, Cooper interviewed 20 nurses and synthesized the data into 3 Personas: 'Kathy' — senior ER nurse, speed-first; 'Diana' — surgical ward nurse, accuracy-first; 'Elaine' — administrative nurse, reporting-first. The design team asked 'How would Kathy use this feature?' at every decision rather than 'What would users think,' significantly improving design quality.

Implementation Model vs. Mental Model Alignment

Never expose software's implementation logic in the interface; expose the behavioral logic users expect to see.

The 'Deleted Items' folder in email clients: from an engineering perspective, deleting an email only requires marking it deleted and periodically purging. But users' mental model is 'delete = put in trash, recoverable.' Early Outlook made permanent deletion too easily accessible because it fit engineering efficiency logic but conflicted with users' mental model, causing widespread complaints about accidental data loss. Cooper used this case to illustrate the harm of misalignment between implementation and mental models.

Polite Software Principle

Good software is like a polite person: discerning, non-interrupting, remembering preferences, and asking for help only when necessary.

Microsoft Word's 'Clippy' paperclip is the perfect negative example: whenever a user started writing a letter, it would pop up and ask 'I see you're writing a letter. Do you need help?' This behavior of interrupting users' workflow and assuming user ignorance violates every principle of polite software. Cooper used Clippy in About Face as the most representative example of 'design failure culture in the software industry.'

Programmer and Early Entrepreneurship Phase

1975-1992

Developed programming tools, sold interface-generation language to Microsoft (becoming the core of Visual Basic), accumulating deep awareness of the gap between programmer thinking and user needs

Cooper accumulated extensive programming experience as a programmer and software entrepreneur in the 1970s-80s. His Ruby visual programming environment and its underlying language logic were purchased by Microsoft in 1988 and became the core foundation of Visual Basic. As a programmer, he directly experienced the design culture 'centered on technical logic rather than user needs,' which became the fundamental driver of his later transformation.

Interaction Design Pioneer Phase

1992-2005

Founded Cooper design consultancy, invented the Persona methodology, published About Face and The Inmates Are Running the Asylum, systematically establishing the theoretical and practical framework of interaction design as an independent discipline

In 1992 Cooper founded Cooper design consultancy, focused on providing user-centered interaction design services for technology companies. About Face was published in 1995, The Inmates Are Running the Asylum in 1999, systematically criticizing the software industry's design failure culture and proposing the Goal-Directed Design methodology centered on Persona.

Influence Expansion and Legacy Building Phase

2005-present

Continued updating About Face, stepped back from Cooper's daily management, continued influencing interaction design and UX through speaking and writing

Cooper continued updating and revising About Face (now in its 4th edition), which became the standard textbook for UX programs at universities worldwide. Through speaking, blogging, and social media he continued criticizing and guiding the design culture of the tech industry, exploring new challenges for interaction design in an era of technological acceleration.