Lection 11 - Trust continued, Implementation for value Flashcards
What are the four phases in the ERP lifecycle? (Markun and Tanis, 2002) (taken from slides)
- Chartering: decisions defining the business case and solution constraints.
- Project: getting system and end users up running
- Shakedown: stabilizing, eliminating “bugs”, getting to normal operations.
- Onward and upward: maintaining system, supporting users, getting results, upgrading, system extensions. (slides)
What are the key differences between the “for profit sector” and the public sector related to normative goal, principal source revenue, measure of performance, key calculations of improvements? (Svejvig, Schlichter, Andersen, 2012)
“For profit sector” = PS, Publib Sector = PB
Normative goal: PS (to maximize shareholders wealth), PB (to achieve social mission)
Principal source revenue: PS (Sales og service and products), PB (Tax appropriations).
Measure of performance: PS (Financial buttom line), PB (Efficiency and effectiveness in achieving the mission)
Key calculations of improvements: PS (Find and exploit distinctive competence of
firm by positioning it in product/service
markets.), PB (Find better way to achieve
mission).
What are the four chosen quality dimesions used to measure quality in the article by (Svejvig, Schlichter, Andersen, 2012)?
- Professional quality (Early dianostics, numbers of people who assessed a physiotherapist, and Proportion of patients who die within 30 days of admission for acute stroke)
- Organizational quality (lenght of hospital stay)
- Patient percieved quality (degree of happiness with the hospital stay).
- Employee percieved quality (The experience of the whole treatment process as well-organised and
coordinated and I always felt to be in a position where I
could give the patient good information about the treatment”)
Can you explain what this article is overall about: FROM BUSINESS IT VALUE TO PUBLIC IT VALUE
– AN ACTION RESEARCH STUDY OF HEALTHCARE
IN THE FAROE ISLANDS? (Svejvig, Schlichter, Andersen, 2012)
Obtaining business value from IT is a recurring theme that has diffused into healthcare information
systems (HIS) where stakeholders often question the value of IT investments. Having finished the
implementation of an integrated HIS, the Faroese Health Service (FHS) has started discussions about
getting value from their IT investment, and how to reap those benefits is the subject of this paper. In
order to fulfil this objective an action research project was started in the autumn of 2010 consisting of
three cycles: (1) setting the stage for benefit realisation, (2) benefit realisation in a pilot area, and (3)
diffusion of benefit realisation to other areas. This paper reports on the first two action cycles.
Consideration of the first cycle reveals that it is not possible to distinguish between working processes
and HIS, and the benefit realisation in health care (a public organisation) has a much broader
perspective than just financial value. Considering the second action cycle, specific key performance
indicators (KPIs) were identified, and a baseline established for a stroke process (pilot area). The
outcome is that public value in this case can be measured by the KPIs, classified as: (1) professional
quality, (2) organisational quality, (3) patient perceived quality, and finally (4) employee perceived
quality. None of the KPIs is a financial value.
What are the critical success factors mentioned by Nah et Delgado, 2006?
- Business plan and vision
- Change management
- Communication
- ERP team composition, skills and compensaiton.
- Project management
- Top management support and championship.
- System analysis, selection and technical implication.
What two groups can business value of a IT in a business context be devided into? (Slide)
Direct benefits: that immediately affect the organization Indirect benefits (transformational) that provides the organization with a capacity to establish direct benefits in the future. The organizational changes are by nature, both a precondition for benefit realisation from, and a result of the IT implementation projects. (slide)
What are the five value categories? (Slide)
- Strategic value: to change the nature of how a company competes.
- Informational value: To provide information for decision making in the company.
- Transactional value: To enable cost savings and support operational management.
- Transformational value: To change the organizational structure of a company as a result of the implemented IT systems that provide a greater capacity for further future benefit realization. This is typically a longer term effect (lag effect).
- Unplanned/emergent value: A result of a transformation or change process.
How can resistance be defined? (Markus, 1983, Power and Politics)
Resistance is defined as behavior to prevent a certain change. Resistance is a relative behavior - it only exists in contradiction to someone else’s perceived intended behavior. Resistance is not always bad, because it depends on which view you apply and may sometimes even be good in organizational contexts because it can prevent the organization from moving away from its objectives.
What are the three theoretical perspectives that can be applied when analyzing a resistance-case, and how can resistanse be avoided according to these perspectives? (Markus, 1983, Power and Politics)
- The people-determined view: Resistance is a product of a person or group’s unique cognitive styles. The same people will therefore show resistance to any system because of their personalities/group mentalities. Resistance can be avoided by educating users, persuade users, obtain commitment through user participation and place people different places in the organization.
- The system-determined view: Resistance occurs because of a system design that fails to deliver the needed functionality and usability. A system that meets resistance in one setting will therefore meet resistance in any setting/by any person or group. Resistance is avoided by educating designers, modifying the system to organizational procedures and through user participation.
- The interaction view, where the interaction view consist of a power and politics dimension that determines if resistance will occur and how to avoid it.
Within the interaction theory Resistance is a product of the certain interaction between the system, the users, and the setting and is therefore different in each situation. Resistance is avoided by changing/fixing organizational problems before introducing the system, restructure incentives for users, and restructure the relationships between users and designers – this implies that user participation is not always appropriate.
What is meant by the power and politics dimensions? (Markus, 1983, Power and Politics)
The power and politics dimension proposes that the group of people who are to gain power due to an implementation are likely to behave positively towards the system, while people who are to loose power will resist to the system. (Markus, 1998)
How can resistance be avoided according to the power and politic dimension? (Markus, 1983, Power and Politics)
In order to avoid resistance, according to the power/politic dimension in the interaction theory, one must fix organizational problems before introducing the system, restructure incentives for users, and restructure the relationships between users and designers – this implies that user participation is not always appropriate.
What is the purpose of the artikle by Markus 1983: Power, politics, and Management Information System implementation?
The purpose of this paper is to examine which theoretical view can best be used to describe, analyze and prevent resistance towards an implementation of a MIS. MIS = Management information system.
By applying the three theoretical perspectives on a case, the authors conclude that the interaction view is most appropriate when trying to understand or avoid resistance towards a MIS implementation. They suggest a thorough analysis of the organizational and personal context a system is supposed to be implemented in, and use this analysis to prevent power-related resistance.
Why - according to the interaction theory - does some people or groups of people resist to use a system when others do not? (Markus, 1983, Power and Politics)
Who resists to the implementation of a system depends on who is perceived to gain or lose power as a result of the system. Power may be relocated due to new data structures or ownership of data, due to the system’s impact on organisational structures/procedures, or due to the right/authorization structures of the system. If the person who is to gain power is located in a higher position, resistance is much less likely than if he/she is in a subordinate position.
Why do the authors conclude that the interaction theory is the most appropriate way to understand and avoid situations of resistance in a MIS implementation? (Markus, 1983, Power and Politics)
The interaction theory is most appropriate because it acknowledges that an implementation is affected by both internal and external factors - both users, system, and designers - whereas the two other theories focus only on either the persons or the system as the source of resistance. The interaction theory implies larger organisational implications as the source of resistance, and entails more complex power structures to be important factors when implementing a MIS. This can be seen as a disadvantage of the theory, because it is not universal since every organisational context differs. Nevertheless, by applying this theory one will avoid simplification of a resistance issue, and may avoid resistance fully by analyzing and reacting to the organisational challenges before implementing a system - by doing so, any resistance will be towards the organisational change rather than towards the system itself.
How can the decision behind outsourcing be explained from a rational and institutional perspective? (Svejvig, 2011, Institutional Theory)
It is theorized that the decision to outsource stems from both rational and institutional explanations. Rational explanations contain straightforward objective justifications while institutional ones encompass subjective arguments.
These two classes exist because a decision (outsourcing, or other) is usually taken based on elements from both. Rational explanations present clear, readily-available justifications for outsourcing (e.g. cost-saving). Institutional explanations require organizational analysis (qualitative) which yields primarily subjective justifications for outsourcing (e.g. norms). One method of interpreting justifications within the two classes is by applying the Transaction Cost Theory (TCT) (for the rational class) and the Institutional Theory (INT) (for the institutional class).