|
Abstract
In organizational adoption, the word ‘adoption’
itself contains meaning and purpose of this concept.
Here adoption means making decisions on change and for
same reason analyzing the system or process to avoid
potential roadblocks in making that decision. The organizational
adoption concept is based on the root ideas in dealing
with large organizational change and its impact. Organizational
adoption also helps to remove the clouds of uncertainty
- the questions like what will happen next - from the
minds of end-users. For example, how will we deal with
this change? Who will assist me if I need help in post
implementation situation? So many more questions like
this are possible to answer by driving organizational
adoption. Utilization of organizational adoption concepts
depend upon the volume of impact measured in case of
extensive business process deviation. For example, if
project initiatives has pure information technology
outputs and don’t force any business process changes
or with untouched system changes, then this concept
may not be needed to consider very aggressively at organization
level but still an assessment can be done to make appropriate
decision. Also organization adoption can address the
dip in productivity issue, which normally hits user
community post solution implementation. Organizational
Adoption helps organization to increase the implementation
and sustainability of the new solution.
This white paper mainly aims to record
project learning and provides the brief conceptual idea
behind the requirement of adding the organizational
adoption function in large IT projects. Also, this paper
touches different aspects of organizational adoption
(OA) and explains why it can be one of the safe choices
for project executers and stakeholders.
Author
Prasad S Deshpande
To know more about Wipro in enterprise application
services, go to www.wipro.com/eas
|
