2006
DOI: 10.1504/ijiscm.2006.011199
|View full text |Cite
|
Sign up to set email alerts
|

Understanding technochange in ERP implementation through two case studies

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
15
0
1

Year Published

2013
2013
2023
2023

Publication Types

Select...
6

Relationship

0
6

Authors

Journals

citations
Cited by 11 publications
(16 citation statements)
references
References 34 publications
0
15
0
1
Order By: Relevance
“…Having multiple case design adds confidence, precision, validity, stability, and trustworthiness to findings (Miles et al, 2014; Yin, 2014). In deciding the number of cases, the concepts of appropriateness, adequacy, and the purposive sampling strategy (Patton, 1990 in Shakir, 2002) were observed.…”
Section: Methodsmentioning
confidence: 99%
See 1 more Smart Citation
“…Having multiple case design adds confidence, precision, validity, stability, and trustworthiness to findings (Miles et al, 2014; Yin, 2014). In deciding the number of cases, the concepts of appropriateness, adequacy, and the purposive sampling strategy (Patton, 1990 in Shakir, 2002) were observed.…”
Section: Methodsmentioning
confidence: 99%
“…Therefore, the case study methodology would enable the researchers to simultaneously capture organizational and individual information. The approach is considered the most suitable research strategy when context is important (Meyer, 2001; Shakir, 2002). To mention, the research reported in this article was taken from doctoral research aimed to explore SL status, progress, and challenges in company-based sustainability programs.…”
Section: Methodsmentioning
confidence: 99%
“…Time is required for technology usage, new routines and social relations to dis-embed and re-embed, as well as, organisational learning to develop among employees involved. The "punctuated equilibrium" model of techno-change is useful for researching the various dimensions of IS alignment and exploring the role of external consultants and internal employees in supporting change (Davison, 2002;Shakir and Viehland, 2006). There are typically many layers of internal and external ERP/enterprise wide integration, as new modules are added and more departments, or organisational users come on board, all of which increases the complexities of techno-change alignment (Aloini et al, 2007;Jenkin and Chan, 2010).…”
Section: Processual Alignment As a Lens On Erp Techno-changementioning
confidence: 99%
“…particular, this disruption can be offset through greater user involvement, training and staff communication, in order to build stronger trust in the newly adopted ERP system. A major implication is that techno-change alignment requires some time to embed, and continual adjustment of stakeholder expectations is necessary to absorb the long-term benefits success from ERP for a truly workable solution (Markus, 2004;Shakir and Viehland, 2006;Chan and Reich, 2007). It also helps stakeholders (whether, users, providers, or senior management) to understand the nature of unintended consequences and to expect the need for re-embedding new activities and routines after each ERP rollout.…”
Section: Wider Implications Of Context and Social Relations For Techno-change Alignmentmentioning
confidence: 99%
“…Despite general IT projects, technochange projects comprise transformation in work operations, organizational business processes and units to design a solution that is likely to be used within the organization. Technochange projects can either emerge as a consequence of the IT implementation process, or be thoroughly planned and executed (Markus 2004;Shakir and Viehland 2006). However, as Markus (2004) states, both types of the change process can fail due to misfits.…”
Section: Introductionmentioning
confidence: 99%