Historical milestone · 1989
Technology Acceptance Model
Reviewed through September 18, 2026
1989 · Historical milestone
Technology Acceptance Model
- Era
- 1980s
- Theme
- Human–AI interaction & adoption
- Evidence form
- Survey-based model linked perceived usefulness and perceived ease of use to adoption intentions and system use
- School / paradigm
- Information systems adoption
- Institution / context
- MIT Sloan / University of Michigan
- Researchers
- Fred Davis
Researcher index
Fred Davis
Technology adoption · MIT / University of Michigan
Technology Acceptance Model
Why it still matters. Operationalized usefulness and ease of use as adoption drivers.
Representative source for this researcher — not necessarily the source of this milestone: https://doi.org/10.2307/249008 (opens in a new tab)
Understand
Plain-language record, transferred from the reviewed source module.
Theory or experimental setup. Established that user beliefs and workflow fit are major determinants of technology uptake.
Result / historical claim. Self-report and intention measures may not predict sustained use, organizational value, or coercive adoption.
Apply
Professional implication, only where the reviewed record states one.
The checked-in record does not state a separate professional application for this entry. The topic page places it in the wider research lineage: Human–AI interaction and adoption.
Verify
Evidence status, stated limitations, and the external sources this record actually carries.
Evidence form. Survey-based model linked perceived usefulness and perceived ease of use to adoption intentions and system use
Limitation / debate. Enterprise AI adoption, trust, usefulness, friction, and change-management measurement.
Source status. The source link below is the verified link our reviewed topic research already carries for this milestone.
Reproduce
A reproduction tutorial is linked only when one exists for this exact record.
A reproduction tutorial is not yet available for this entry. The closest reviewed material is Human–AI interaction and adoption.
Cite or share
APA-like: This historical record carries a year only, and no author or publisher of record in the checked-in data. An APA reference would have to invent that metadata.
BibTeX: BibTeX requires an author and publication venue. Historical lineage entries store a narrative record and its source link, not structured authorship, so the field would be fabricated.