Geyto Research · Mariano D'Angelo · Evidence review · · 2 min read
Acceptance is not adoption. What TAM and UTAUT explain and what they leave out
Acceptance models explain individual intention to use a system and its use. Adoption in an organization also means looking at the work and its context.
In brief: technology acceptance models such as TAM and UTAUT are widely used to explain why people use a system or not. They explain individual intention well. But adopting a technology in an organization is more than wanting to use it: it means the work changes and the change holds. For that, you also have to look at practice, at the task and at the conditions of the place where the work happens.
What acceptance models say
In 1989, Fred Davis proposed the Technology Acceptance Model (TAM). Its central idea is simple and powerful: the intention to use a technology depends on how useful and how easy to use people perceive it to be. The model became a reference point because it predicts intention to use with few variables.
In 2003, Viswanath Venkatesh and his colleagues brought eight earlier models together in the Unified Theory of Acceptance and Use of Technology (UTAUT). They proposed four determinants: performance expectancy (how much it helps), effort expectancy (how much it costs), social influence (what others expect) and facilitating conditions (what resources and support are available).
These models explain something real. If a system is seen as useless or difficult, it is unlikely to be used well.
What they leave out
Acceptance is individual; adoption is organizational. A person can accept a system and still be unable to use it as intended, because they depend on other areas, on data that does not arrive or on decisions that are not theirs to make.
Intention is not practice. The models explain intention to use and use. They are not designed to look at whether the way the work is done has changed, or whether that change holds months later.
The system is not a fixed thing. Wanda Orlikowski proposed looking at technology through practice: the same tool is used in different ways depending on the group, the task and the moment. What gets adopted is not the software as it was delivered, but the way each team builds it into its work.
Facilitating conditions are the center, not one factor among others. UTAUT includes them, but in a real implementation they are decisive: time to learn, support on the job, clarity about who decides what. In UTAUT they are measured as the user's perception; in the organization they depend on how the change was designed and supported.
A question in two parts
Acceptance models answer one question: do people want to use this? Adoption calls for answering two at once:
- What does this change actually ask of people, teams and routines?
- What capacity is there, in the specific place where the work happens, to meet it and sustain it?
When the two do not match, both sides can be adjusted: the organization, and the initiative too.
What to do with this
- Use acceptance surveys as a signal, not as the measure of adoption.
- Complement them with observation of the work: what changed, what is the same, and why.
- Treat facilitating conditions as part of the initiative's design, not as an assumption.
More on this view in our approach and in the glossary.
Geyto Research publishes essays, evidence reviews and market notes on what happens after go-live.
Frequently asked questions
What is the TAM model?
The Technology Acceptance Model, proposed by Fred Davis in 1989, explains the intention to use a technology through two perceptions: its usefulness and its ease of use.
What does UTAUT add?
The Unified Theory of Acceptance and Use of Technology (Venkatesh et al., 2003) brought eight earlier models together into four determinants: performance expectancy, effort expectancy, social influence and facilitating conditions.
Why is acceptance not enough to explain adoption?
Because acceptance models focus on individual intention and use. Adoption in an organization also depends on how routines, handoffs and the conditions where the work happens change.
Sources
- Davis, F. D. (1989). Perceived usefulness, perceived ease of use, and user acceptance of information technology. MIS Quarterly, 13(3), 319–340.
- Venkatesh, V., Morris, M. G., Davis, G. B. and Davis, F. D. (2003). User acceptance of information technology: Toward a unified view. MIS Quarterly, 27(3), 425–478.
- Orlikowski, W. J. (2000). Using technology and constituting structures: A practice lens for studying technology in organizations. Organization Science, 11(4), 404–428.
- Rogers, E. M. (2003). Diffusion of Innovations (5th ed.). Free Press.
Share