Holt, D. T., Armenakis, A. A., Feild, H. S., & Harris, S. G. (2007). Toward a
Comprehensive Definition of Readiness for Change: A Review of Research
and Instrumentation. In W. A. Pasmore & R. W. Woodman (Eds.), Research
in Organizational Change and Development (Vol. 16, pp. 289-336). Oxford,
UK: Elsevier.
Weiner, B. J., Amick, H., & Lee, S. Y. (2008). Conceptualization and measurement of organizational readiness for change: a review of the literature in health
services research and other fields. Medical Care Research and Review, 65(4),
379-436. doi: 10.1177/1077558708317802
I hope these references would be helpful for you to conceptualize change readiness measures.....
Holt, D. T., Armenakis, A. A., Feild, H. S., & Harris, S. G. (2007). Toward a
Comprehensive Definition of Readiness for Change: A Review of Research
and Instrumentation. In W. A. Pasmore & R. W. Woodman (Eds.), Research
in Organizational Change and Development (Vol. 16, pp. 289-336). Oxford,
UK: Elsevier.
Weiner, B. J., Amick, H., & Lee, S. Y. (2008). Conceptualization and measurement of organizational readiness for change: a review of the literature in health
services research and other fields. Medical Care Research and Review, 65(4),
379-436. doi: 10.1177/1077558708317802
I hope these references would be helpful for you to conceptualize change readiness measures.....
measuring readiness to change and finding thresold has been considered a challenging tassk before management. Organizational readiness for change is a multi-level, multi-faceted construct. organisational readiness for change refers to organizational members' shared resolve to implement a change (change commitment) and shared belief in their collective capability to do so (change efficacy). the following link may be usefull in developing concept for the subject.
My research is looking at how organisations can reduce disruption when implementing a change. My case study is the activation of a software module within an existing software product, for use by a group of highly intelligent Engineering analysts. The Analysts feel today that the software module is cumbersome to use, thus there is no pull from many of them to adopt the software. My aim is to use existing Technostress measures as a checklist to determine if the software transition project can be improved through its various stages to improve adoption rates and hence project success. Thus far, I am developing a metric that for this type of change determines if any specific element of the proposed change needs further review to reduce risk.
This is different to Technology Acceptance, as it looks at some wider Change Management measures, such as pre-change, technical & social aspects and post-change elements. The original question was to ascertain if someone had come across any similar metrics for either Change readiness in general or specifically focussed on implementing a software change.
I do appreciate your feedback and apologies for any ambiguity in the originally posted question, Kevin
I am not sure whether the attached document will be of any interest or help to you regarding your project largely because I am not sure the degree to which you can enter variables into your analysis and/or collect data associated with those variables.
Nevertheless, the article connects the "psychological climate" among those making changes and the stages of the "project plan" that may be lacking.
Anyway, the article is short so you will not waste much time either way ... :-).