Image Source: stockunlimited.com
Predicting User Acceptance
I‘ve been asked to help a friend with the design of a portal.
Not just any type of portal, but one that will provide an alternative to using the standard “thick client”.
So, I started thinking about what I can do to really “sell” the portal to the users. What will make them WANT to use it, instead of the client that they are already familiar with?
While doing some research, I read about TAM.
The TAM is short for “Technology Acceptance Model“.
It is a model that proposes that application usage and adoption can be predicted based upon two factors.
Here is what the basic TAM looks like:
A Closer Look at TAM
Perceived Usefulness can be defined as “the degree of which a person believes that using a particular system would enhance his or her job performance“.
Perceived Ease of Use
Perceived Ease of Use as “the degree by which a person believes that using a particular system would be free of effort“.
Attitude and Behavioral Intentions
If a person thinks that a technology will be useful and they find that it’s easy to use, then this influences their attitude of a user towards the technology.
Which, in turn, determines behavioral intentions and leads to actual system use.
So – what did I think of this when I first saw it? I thought “Duh!! That’s obvious.”
But then,as I thought about it more, I realized that it IS obvious – if a user thinks something is going to make their job easier, AND they think that it will be effortless (not having to learn a new system, etc), then, of course, they are more willing to use it.
It gives something measurable
Now, the title of this post is “Predicting User Acceptance“. But how?
Because this is a model, lots of different values can be matched to each of the parts of the model, so that the outcome gives a mathematical value for the user acceptance. And that means that you can get a measured idea of the degree something will be accepted.
There are, in fact, a couple of documented examples where the TAM has been used to predict intranet/portal usage. I want to go into these in a future post.
Till then, the simplicity of the TAM has helped crystallize, for me, the real essence of user acceptance:
- “Will this make my job/life easier?”
- “Does it require effort to use?”
Read my following related posts:
- Applying (loosely) the Technology Adoption Model to a Real-Life situation
- The “Model Office” and improving user acceptance
- The Use of Collaborative Software in Virtual Teams
Want to learn more?
Below is a selection of resources that I personally feel are relevant to this blog post, and will allow you to get more in-depth knowledge. I do earn a commission if you purchase any of these, and for that I am grateful. Thank you. (Important Disclosure)