Sat 11th Feb 2012 (4) Meeting with Supervisor & internalization

Sat 1:00 - 3:00pm (2 hours) - meeting with  supervisor
(2 hours) internalization of the outcome of the meeting & documentation

Feedback

Question:

************ 
************
During the monitor training session this week with company A, felt like there was no real reaction besides silence during session. Not enough info gathered. Did not feel fruitful.
What are my options in terms of getting real data from them?

1) Maybe the monitor sessions that were done this week can be followed up with interviews and questionnaires , since the group of users during the training session in Company A were silent during the training session.
2) possibly also investigate company culture in this regard, also top down management pushing to no choice in the matter


************ 
************
I am afraid the solution will be generic. For e.g. Have a flat company culture/structure in companies.,
1) a better solution would be have a solution for each type of culture in the different types of organisations
   e.g. flat company might have more communication but top down management style might not hold weight to            force implementation of process.
      - bigger organisation - not flat but have stronger top down influence. find a solution tailored to each type   of culture organisation
customized solution for the type of org culture - tailored metrics






************ 
************


The models I mention deal with people and behavior and applying it to user acceptance.
Comment: this can be quite useful and possibly a hybrid approach could be used to devise a User Acceptance Model for the research paper. To devise the metrics for the user acceptance checklist

See if the questionnaire can be used to bring out the models in actions the percieved usefulness of the system, perceived ease of use etc

use the metrics to analyse the data



************ 
************
I do not see statistics for strictly user acceptance. There are stuff on Successful and failed projects and the causes
Comment: see how well the root causes of the success and failure of projects are linked to end users.
Look at past projects ie post implementation reviews about how well users fit into the  project.( lit review)


************ 
************


Information gathering for user acceptance
Some parts of a system might be successful but others not successful. 3 out of 5 units might actually be used. What happens to the other 2 modules of the system. why don't users use it?

When the dusts settles and at the end of user acceptance curve, how many models pf system actually used? This tells how much of it was accepted.

Comment:
-Monitor by using audit logs of screens pages used
-How many people use 5250 and how many used genie? whats did the #s show?
-what about the RI part of it - user was running a bunch of reports to do something when one would have done the job. why the round about process to get the job done?



************ 
************