Lessons from Jef Raskin

Jef Raskin, the visionary creator of the Apple Macintosh project and a pioneer in human-computer interaction, left behind a wealth of wisdom on designing technology that serves people. His work, most notably encapsulated in his book "The Humane Interface," challenges designers and engineers to prioritize human needs and cognitive abilities over machine efficiency.

On the Primacy of the Interface

"As far as the customer is concerned, the interface is the product." [1][2] This foundational principle emphasizes that a user's entire experience and perception of a product are shaped by its interface.
"An interface is humane if it is responsive to human needs and considerate of human frailties." [1][3] This definition encapsulates the core philosophy of humane design.
"Users do not care about what is inside the box, as long as the box does what they need done." [1][2] A reminder that technical specifications are secondary to user-centric functionality.
"Once the product's task is known, design the interface first; then implement to the interface design." [1][2] This advocates for an interface-first design process, ensuring the user experience dictates the technical implementation.
"Right now, computers, which are supposed to be our servant, are oppressing us." [1][4] A stark commentary on the state of user-unfriendly technology.

The Laws of Interface Design

"A computer shall not harm your work or, through inaction, allow your work to come to harm." [1][2] Raskin's First Law, inspired by Asimov's Laws of Robotics, underscores the importance of data preservation and system reliability.
"A computer shall not waste your time or require you to do more work than is strictly necessary." [1][2] Raskin's Second Law highlights the ethical imperative to respect the user's time and effort.

On Simplicity and Usability

"What users want is convenience and results." [1][2] This quote boils down the fundamental desires of any user.
"A well-designed and humane interface does not have to be split into beginner and expert subsystems." [1][2] Raskin argued against separate modes for different user levels, advocating for a single, well-designed interface for all. [5]
"Simple tasks should always be simple to perform." [5] A core tenet of humane design is that complexity should not be introduced where it is not necessary.
"The most efficient interface is not necessarily the best interface." [3] Efficiency is a quality, but not the only one to consider in interface design. [3]
"Just because we don't have systems that are easy to learn and fast to use, doesn't mean that it isn't possible." [3] A call to action for designers to strive for better, more intuitive systems.
"Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining." [1][2] This vivid analogy illustrates the absurdity of accepting user-hostile design in computing.
"The system should treat all user input as sacred." [1][2] This principle emphasizes the importance of capturing and correctly interpreting user actions.

On Cognitive Science and Design

"Design should be based on 'universal psychological facts' rather than 'industry standards'." [5] Raskin advocated for a design process grounded in the understanding of human psychology.
"The ideal interface is one that can be operated entirely by habit." [3] Interfaces should be designed to leverage the power of habituation, reducing cognitive load. [6][7]
"When you have to choose among methods, your locus of attention is drawn from the task and temporarily becomes the decision itself." [1][2] This highlights how unnecessary choices can distract users from their primary goals.
"As a grad student, I stopped asking 'How to make this algorithm more efficient?' to 'What is this supposed to do?'" [3] This reflects a pivotal shift in his thinking from a machine-centric to a user-centric perspective.
"What people think they are doing, is not what they actually are doing." [3] A reminder for designers to base their work on observation rather than assumptions about user behavior.
"Humans form habits after repetition; it is our natural tendency to learn tasks to the point where they become automatic." [5] This psychological principle is central to his advocacy for consistent and predictable interfaces.

Critiques of Prevailing Design Paradigms

"I hate mice. The mouse involves you in arm motions that slow you down. I didn't want it on the Macintosh, but Jobs insisted." [1][2] Raskin was a vocal critic of the computer mouse, believing it to be an inefficient pointing device.
"The biggest mistake I've made is the one button mouse... It never occurred to me to label the two mouse buttons [to avoid confusion between the meaning of each button]." [3] In a moment of reflection, he acknowledged the potential for confusion even in his own simplified designs.
"I am confident that we can do better than GUIs because the basic problem with them...is that they ask a human being to do things that we know experimentally humans cannot do well." [1] Raskin believed that the Graphical User Interface was not the ultimate paradigm and that more humane alternatives were possible.
"Voice interface is the biggest red herring... what I'm talking about are interface concepts that apply to all types of interfaces." [3] He was skeptical of voice as a universal solution, emphasizing the need for fundamental design principles.
"Many interfaces look pretty, but they fall down." [3] A critique of designs that prioritize aesthetics over functionality.

Learnings and Broader Philosophy

If I had not studied music, there would be no Macintosh computers today. [1][2] Raskin often cited his interdisciplinary background as crucial to his innovative thinking. [8]
You should never have a human factors person on a project -- they should always be the leader of the project. [3] This underscores his belief in the centrality of human-centered design in product development.
If our field is 'to advance', we must - without displacing creativity and aesthetics - make sure our terminology is clear. [1][2] A call for precision and clarity in the language of design.
The content of a file is its own best name. [1][2] This quote is from his proposal to eliminate traditional file names and directories in favor of content-based retrieval. [9][10]
An unlimited-length file name is a file. [1][2] A concise expression of his vision for a more intuitive file system.
The instinct [in interface design] is to use too few words. [3] He cautioned against sacrificing clarity for the sake of brevity.
If you are kind and gentle to the machine, you are hostile to the user. [3] This provocative statement argues that prioritizing machine constraints over user needs leads to poor design.
Every computer should have an undo button. [3] A fundamental feature for a forgiving and humane system.
It is technically possible to boot a computer in under 10 seconds. Why has no one done this? More importantly, why has no one studied this? [3][11] A critique of the industry's failure to address common user frustrations.
The problem was...the computer was just much more complicated to use than necessary. [11] His early realization that the fault lies with the system, not the user.
Interface design often included too late in the design cycle. [5] He argued for integrating interface design from the very beginning of a project. [5]
Users should set the pace of interaction. [5][12] A humane interface should not keep users waiting unnecessarily. [12]
An adaptive interface is a bad idea—it prevents users from habituating. [5] He was critical of interfaces that change their behavior, as this undermines the formation of habits. [5]
Elimination of warning screens – modern software applications often ask the user 'are you sure?'...Raskin argues they are unhelpful because users tend to ignore them out of habit. [9] He advocated for universal undo instead of confirmation dialogs. [9]
An end to stand-alone applications – every software package should be structured as a set of tools available to users on any document. [9] His vision for a more integrated and seamless computing experience.
He identifies a phenomenon he calls the 'Halo Effect,' which 'causes every invention to be attributed to the leader, or the most charismatic, or currently most news-worthy member of the group.' [11][13] A caution against the oversimplification of the history of innovation.
I realized that we should be designing computer systems to make them easier to use and that was more important than what I was being taught in my computer science classes. [10] A reflection on the genesis of his focus on human-computer interaction.
I'm very disappointed in the Macintosh interface. It's more complex, harder to use than it was when we started. [10] His later assessment of the evolution of the product he initiated.
A human-machine interface is modal with respect to a given gesture when (1) the current state of the interface is not the user's locus of attention and (2) the interface will execute one among several different possible responses to the gesture, depending on the system's current state. [14] His precise definition of a modal interface, which he generally argued against.
Use icons only in the few situations where research has shown them to be advantageous. Otherwise words are better. [14] A cautionary note on the overuse of icons in interface design.
There are no interface tools (of which I'm aware) that allow you to build a good interface. [3] A critique of the state of design tools during his time.
The user would never have to know about formatting. [15] An example of his philosophy of hiding unnecessary technical details from the user.
A computer is a device with a mindlessness of its own. [11] A humorous and insightful observation on the often-frustrating nature of computers.
He tried to shoot the project down. [1] A reference to Steve Jobs' initial opposition to the Macintosh project.
I was unimpressed by his thoughts on how computers should work. [8] Raskin's candid assessment of his early interactions with Steve Jobs regarding computer design.

Learn more: