Cognitive Engineering

Norman, Donald A. "Cognitive Engineering." (1986) http://brainimaging.waisman.wisc.edu/~perlman/papers/ HumanFactors/2%20norman%20cognitive%20engineering %20user%20centered%20system%201986.pdf-2up--1-perSig.pdf

Notes
Section:

1. An Analysis of Task Complexity
2. Toward a Theory of Action
3. Conceptual Models and the System Image
4. On the Quality of Human-Computer Interaction
5. Design Issues

Summary

Notes

1986: Ronald Reagan, Tax Reform Act

"...neither Cognitive Psychology, nor Cognitive Science, nor Human Factors."

Goals:

1. "To understand..."
   • principles
     • human action
     • performance
   • relevant for
     • "...engineering principles of design."
2. "To devise..."
   • pleasant systems
     • goal is neither
       • efficiency
       • ease
       • power
     • "to produce what Laurel calls 'pleasurable engagement'"

The work is broken into five sections.

1. An Analysis of Task Complexity

Single variable to object mappings leave out control complecities.

"The correct conceptual model can transform confusing, difficult tasks into simple, straightforward ones."

• Mapping Problems
• Ease of Control
• Evaluation

2. Toward a Theory of Action

Theory of Action: How people do things.

"There isn’t any realistic hope of getting the theory of action, at least for a long time, but we should be able to develop approximate theories."

"...a person interacts with a system..."
psychological vs physical
"...design, analysis, and use of systems."

Each Gulf is unidirectional.

Gulf of Execution: "...from Goals to Physical System."

Gulf of Evaluation: "...from Physical System to Goals."

Stages of User Activity:

• "Establishing the Goal"
• "Forming the Intention"
• "Specifying the Action Sequence"
• "Executing the Action"
• "Perceiving the System State"
• "Interpreting the State"
• "Evaluating the System State with respect to the Goals and Intentions"

3. Conceptual Models and the System Image

Conceptual Model: scaffolding to cross gaps (bridge aforementioned Gulfs)

• Design Model
• User's Model

System Image: result of physical structure built

4. On the Quality of Human-Computer Interaction

5. Design Issues

"know both the approximate model and its limits."

Different needs and requirements have different design technique tradeoffs.
Use-modes and customizations (but causes increased programming complexity).

"Prescriptions": (What he is suggestion be done.)

• "Create a science of user-centered design."
• "Take interface design seriously as an independent and important problem."
• "Separate the design of the interface from the design of the system."
• "Do user-centered system design: Start with the needs of the user."

Summary

"Pay attention to the "theory of action" he proposes." -Professor Fast

This paper explains the approximations involved in creating a pleasant interactions. Like Direct Manipulation Interfaces, Norman also focuses on "gulfs" or gaps between systems and their users. Norman talks about intentions vs interpretation, however in this shorter paper, he did not talk about the classifications and details of measuring those distances.

Highly recommends the value of designing for the user.