lecture 4: Technochange Flashcards
Techno change project
A project that changes an organization based on new uses of IT.
IT projects
A purely technical IT project ( such as upgrading web-server)
problems of seperation
the problems that comes with separating IT developments from organizational development.
A complete desing
A design that not only consist of the design in IT but also the design of the changes to the organization.
implementable design
a design without misfits toward key organizational characteristics such as culture, business process and incentives.
Technochange prototyping
an interaktive approach that not only focused the development of IT but the organizational changes and benefits as well.
benefits realization
The process of managing and organizing, such that the potential benefits arising from the use of IT are actually realized.
benefits realization: benefits planning
the ability to effectively indetify and describe the planned outcome of an IS development project and explicitly specify the requirements and how they will be achieved.
benefits realization: benefits delivery
the ability to design and execute the program of organizational change necessary to realize all of the benefits specified in the benefits realization plan.
benefits realization: benefits review
the organizations ability to effectively assess the success of a project in terms of the potential benefits, the delivered benefits and the identification of the ways and means by which the further benefits might be realized.
benefits realization: benefits exploitation
The adoption of the portfolio of practices required to realize the potential benefits from information, applications and IT services, over their operational life.
complementary changes
the changes that is not IT related - but helps benefit from IT changes
- changes in business processes and workflow, new job designs, new skills training, restructuring departments or business units, new places, new performance evaluations and incentives etc.
different between technochange and IT project
IT projects: Can do a big different in the short-run, the payoff from these proejcts can be signifikant but they often dont make an appreciate different in how organizations work.
Technochange projects: Using IT in a way that it is possible to trigger major organizational changes, creating high-risk BUT potntially high-reward situations.
Technochange is technology-driven organizational change. Today these project would be labelled as “transformational” or “disruptive”.
ressistance to change
Resistance to change is the act of opposing or struggling with modifications or transformations of the organization.
challenges with technochanges
the major challenges for technochange projects is to much seperation between system development and implementation // between IT and the organization
seperation between IT and organization
The lack of IT understanding in business –> They are not always fully aware of what the IT can and can not do, and what possiblities exist for changing business processes.
Lack of business understanding in IT –> Intentionally or unintentionally, IT design decisions are often made on the basis of technical criteria
Bad strategy for collsborative innovation –> People involved in participatory design processes often produce incremental solutions, even when more radical change is needed.
technochange lifecycle problem: time and distance
3 problems:
- they are to drift away from their initial business objectives.
- it is that the initial business needs and organizational processes will have changed, resulting in misaligned IT solutions.
- they are to lose management attention and be terminated.
technochange life cycle problem: exported problems to later phase
Exported problems are problems that arise during one phase of the life cycle but either are not recognized as problems or fixed at that time. Instead, they show up in later phases, when it may be too late or too expensive to fix them.
Classic example is when a IT problem actually are a technochange problem
technochange life cycle problem: creating unintended consequence
long technochange efforts continue with exported problems, the more difficult and expensive it is to correct them. Even completed and apparently successful technochange initiatives can have unintended consequences, that were not expected or intended by executives or project personnel.
technochange prototyping
Technochange prototyping is iterative / agile development + organizational changes integrated into one, and the same, process.
–> The essential characteristic of the Technochange prototyping approach is that each phase (iteration) involves both new IT functionality and related organizational changes, such as redesigned business processes, new performance metrics, and training.
what is a good technochange solution?
A complete solution,
An implementable solution,
A solution where benefits actually are exploit
what can go wrong in a good technochange solution?
A solution may be technically adequate but still not fit the ways people work in particular settings:
- Cultural misfits
Incentive misfits/political misfits
it is important to take potential misfits carefully into account when designing technochange solutions and when dealing with apparent cases of resistance to technochange.
benefit realization as another way of dealing with seperation problems
By combining benefits realization with the ideas from technochange organizations might be in a better positions to successfully manage IS development and implementation projects.
