Thur 28 Sept 2012 (13) Literature - Thur 11 Oct 2012

Listed Questions to answer from reading papers.
Started Literature Reading

The whole point of this paper is to create and start to end solution/list of recommendations/model/guide that will achieve user acceptance. Based on articles read... it is unclear how to achieve this in a clearly defined way.

What does the List paper argue about in the papers about the models?
What are my views on the short comings of each of the models?
What is lacking in the models?
What works well in the model?
What was actually noticed in companies regarding what the model says?
What info I need from the companies to get this?
How does the plan below work/combine/contrast from the user acceptance models already in existence?
Compare and contrast what works well and what does not and how the model below makes up for this.
How does this plan below cater for the different types of companies being investigated?
Will it always work for Technology company? Insurance, School?
How do I continue to monitor and measure that the projects are maintaining the UA standards?


Technology Acceptance Model (TAM)
perceived ease of use +  perceived usefulness = > behavioral intention to use it -> use. However if after the hype dies down and the system does not solve my needs in a user friendly way. I will resort to my old methods. My initial thoughts will change to a negative feeling towards it. Hence a proper development solution is also needed.

If no access to resources ( lit paper) so I don't get the support I need, I will abandon the idea to use it. I might have been willing to use it but not now.

Unified Theory of Acceptance and Use of Technology (UTAUT).

Theory of Reasoned behaviour

I agree - access to resources does affect user acceptance. ( help, continued , support, manuals, training)
Social Influence does affect whether some1 is willing to try something new. If however it fails to convince them, they will go back to their old practices.

Even before UA starts, sometimes users need a push to try it, and a plan needs to be in place to bump up the excitement and use levels before the negative notions and preconceptions start. Whether it is from top down management roll out, peer influence.

MY User Acceptance PLAN:
1
Understand target users(tech vs non tech, ages, culture, personal, office)
Every project has diff needs, diff users, diff skillet of people.
OBJ: understand target users in order to create solution for them that works, as well as to design PR campaign that works for diff users.
|
| 
2                                                   3                                                              4
Design plan  ===>                   System changes (Dev solution)         ====> Continued support to users to
Mass Users on board
Positive Hype(PR)                  that actually solve the user problems              dispel fears, concerns, deal
Get as many users                  Hence proper user requirement gatherings,    with queries, enhancements
 on board with hyper              Iterative development to ensure user              (OBJ: foster trust, confidence in
OBJ: get initial buy in,              needs are adequately being dealt with             IS/IT team, solution)
  Positive thoughts                  UA testing
 (peer influence TRA)             Efficient User Requirement,
    TAM                                  development, user testing, strategy
                                              OBJ: solid solution that caters more than adequately for
                                              user needs
                                              ( initial trust/buy in, will not give you UA alone,
                                              they will just go back to their old procedures)
5
Celebrate with all and reward
employees who were key
to the success of the project
to project a culture of
ownership and change adoption
OBJ: create a culture of
ownership and create confidence in
users to help build a better system
Each 1 has a part to play

Company A has adopted this type of UA plan and it has worked for their recent WebStar project of a new interface for daily processing of work. UA can also be seen such that users are not coming forward to log recommendations and suggestions on how to make the system more tailored to their needs. users are no longer sitting idly by as they use to. They are taking more ownership.


Issues not addressed by the models the importance of
-Trust and confidence in the system - absence can lead to lack of use and lack of acceptance
-Start to end implementation in the IS/IT system change and UA journey - how to achieve UA in terms of    the Actual live environment with a system. Models too general
-Solutions that deals with the user needs

Wed 26 Sept 2012 (4 hours)

Review my paper
clear up aim, objectives    **DONE**
narrow search - lit review

Redo/Tweak Proposal      **DONE**
Submitted Proposal to Bobby and Ravi to read.   **DONE**

Meeting with Supervisor wed 26 sept 2012

Meeting with Supervisor Bobby Sookram

Outcome
Figure out what the aim is
Then narrow the literature review based on this
Then use the compare/contrast method for internal and external projects in company
Start writing


T - 2 months

Plan ( 2)

Structuring Direction of the paper and identifying further areas of research to drill down into.

What am I trying to achieve? (objectives and slant)
How user acceptance varies across different industries/companies?

How am I going to accomplish this?
What data I need from the companies?
Evaluate and critique the information from companies. Not just 2 dimensional

What kind of data from the 3 companies do I need?
How do you measure/monitor user acceptance. Meaning that you have achieved what you set out to do.
Is there a benchmark?
Does it vary across projects or same orojec
What happens when you do not meet the standard/benchmark?


What is the end result?
  What does the lit say?
  What is actually being done? Across companies? What worked in which companies? Will it work in all           companies?
  What are I think should be done?

Reading (10 hours)

THinking process of new slant. Brain storming session. Reading papers.