Where does computer anxiety collide?

The degree of an individual's apprehension, or even fear, when confronted with the possibility of using a computer. Heinssen, Glass, and Knight built the Computer Anxiety Rating Scale in 1987, a nineteen-item measure of the worry, self-doubt, and unease people report as they face a computing task, validated against computer experience and performance. Their work treats the referent as an emotional state of apprehension toward the machine itself, separable from general trait anxiety, and it became the reference instrument the acceptance literature later borrowed. This is the measurement origin: a scale of felt apprehension toward computing, timed to the moment of use.[1]

Unit

A person's felt apprehension toward using a computer

Recovery means

Reported anxiety tends to fall with training and repeated successful use

Measured by

Nineteen Likert items on worry and unease before and during computer use

Computer anxiety as an affective reaction within the social cognitive theory of computer use. Compeau, Higgins, and Huff followed users over a year in 1999 and placed anxiety among the affective and behavioural reactions tied to computer self-efficacy: the more capable people judged themselves, the less anxiety they reported, and the two together shaped affect and use. Here the construct is not a standalone trait but one node in Bandura's reciprocal model, an emotional reaction inversely related to self-efficacy and bearing on whether people use the technology. What differs from the scale literature is the theory: anxiety is bound to a capability judgement, not a primitive measured for its own sake.[2]

Unit

A user's emotional reaction to computing, tied to self-efficacy

Recovery means

Not applicable

Measured by

Anxiety items alongside computer self-efficacy, affect, and usage over time

Computer anxiety as an anchor determinant of perceived ease of use in TAM3. Venkatesh's 2000 study of ease-of-use determinants cast anxiety as one of the general anchors people lean on when they judge a new system before they have used it, and Venkatesh and Bala folded it into TAM3 in 2008 as an emotion that adjusts downward with hands-on experience. In this role the construct is neither the primary outcome nor a trait valued for its own sake: it is an individual difference that biases the ease-of-use judgement early and fades as the object anchor of direct experience takes over. What differs again is the job the same feeling is asked to do.[3][4]

Unit

A user's pre-use apprehension that anchors an ease-of-use judgement

Recovery means

The anchoring effect weakens as direct experience with the system accumulates

Measured by

Anxiety items modelled as a determinant of perceived ease of use