Construct · 3 names · 4 citations

Where does output quality collide?

Different names. Different fields. One construct. One map.

● jangle · how well it does the job, one antecedent Nearest construct by meaningjob relevancecompare the meanings
How to read this

Every construct on the map is compared with every other by the meaning of its definitions, and the closest one is surfaced here. The nearest construct to output quality is job relevance.

Hold this as a prompt, not a verdict. Two constructs sitting close in meaning is a reason to read them side by side and decide for yourself whether they are one idea under two names. It is not proof that they are. Compare the meanings in the Collider.

RETAINED UNCHANGED (2008)outputquality3 NAMESTAM2VENKATESH DAVIS 2000TAM3VENKATESH BALA · TAM3IS success modelDELONE McLEAN · SUCCESS

Spokes are the names and the models that coined them; dashed arcs are borrowings. Tap a field for its definition, unit, and measures.

2026

Drag to watch the word get claimed. Each name appears at the publication date of the earliest source cited for it. Tap a year to see which.

TAM2

an individual's perception of how well a system performs the tasks it is used for, a determinant of perceived usefulness.

An individual's perception of how well the system performs the tasks it is used for, one of the cognitive-instrumental determinants of perceived usefulness in Venkatesh and Davis's 2000 extension of TAM. Alongside job relevance, result demonstrability, and perceived ease of use, output quality feeds usefulness, but it answers a different question: given that the system can do the tasks that matter to the job, how well does it do them. Venkatesh and Davis modelled it as interacting with job relevance, so that a system judged high on both is rated most useful, and reported output quality as a significant determinant of usefulness across four longitudinal field studies. The referent is a job-holder's belief about performance quality, feeding perceived usefulness, not a property scored on the system itself.[1]

Unit
A user's belief about how well the system does its tasks
Recovery means
Not applicable
Measured by
A few seven-point Likert items on the quality of the system's output; perceived usefulness as the criterion it feeds

TAM3

a cognitive-instrumental determinant of perceived usefulness, carried unchanged from TAM2 into TAM3's integrated model of IT adoption.

The same construct, carried forward without change into Venkatesh and Bala's 2008 TAM3, which merged TAM2's determinants of perceived usefulness with the determinants of perceived ease of use into one integrated model of individual IT adoption and use. Output quality stays a cognitive-instrumental determinant of usefulness, keeping its anchoring against job relevance and result demonstrability and its interaction with job relevance. TAM3 adds interventions and moderators around the network but leaves the definition and role of output quality intact, so a study citing TAM3 for output quality is measuring the same belief as one citing TAM2. The label changes model but not referent.[2]

Unit
A user's belief about how well the system does its tasks
Recovery means
Not applicable
Measured by
The TAM2 output-quality items, unchanged, inside the integrated TAM3 nomological network

IS success model

two IS success dimensions: system quality, covering properties like reliability, and information quality, covering output accuracy and timeliness.

The kin that shares the words but sits in a different model. DeLone and McLean's IS success framework, set out in 1992 and updated in 2003, lists system quality and information quality as two of its dimensions of success: system quality names properties of the artifact such as reliability and response time, and information quality names properties of the output such as accuracy, timeliness, and completeness. Both are scored on the system and its output, and in the model they predict use and user satisfaction, which in turn feed net benefits. Output quality in TAM points at the same thing, how well the system does its work, but it is a user's perception acting as an antecedent of usefulness, not a dimension of success measured as an outcome. One belief predicts adoption; the two quality dimensions describe a system's success.[3][4]

Unit
A dimension of the system or its output, scored as a success outcome
Recovery means
Not applicable
Measured by
System-quality and information-quality scales, positioned as predictors of use and user satisfaction, not as antecedents of perceived usefulness

Next

Run it through the Collider, or take the citations with you.

See how output quality sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in ColliderExport BibTeXReport this collision

Nearby collisions

IS success4 names · 5 citationsjangle · the dependent variable, six namesjob relevance3 names · 3 citationsjangle · does it fit my job, one antecedentquality6 fields · 13 citationsjingle · one name, six constructs

References

  1. Venkatesh, V., & Davis, F. D. (2000). A theoretical extension of the technology acceptance model: Four longitudinal field studies. Management Science, 46(2), 186–204. https://doi.org/10.1287/mnsc.46.2.186.11926
  2. Venkatesh, V., & Bala, H. (2008). Technology acceptance model 3 and a research agenda on interventions. Decision Sciences, 39(2), 273–315. https://doi.org/10.1111/j.1540-5915.2008.00192.x
  3. DeLone, W. H., & McLean, E. R. (1992). Information systems success: The quest for the dependent variable. Information Systems Research, 3(1), 60–95. https://doi.org/10.1287/isre.3.1.60
  4. DeLone, W. H., & McLean, E. R. (2003). The DeLone and McLean model of information systems success: A ten-year update. Journal of Management Information Systems, 19(4), 9–30. https://doi.org/10.1080/07421222.2003.11045748

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct