MétaCan
Menu
Back to cohort
Record W2041985223 · doi:10.1057/jit.2008.21

Top Management Support of Enterprise Systems Implementations

2009· article· en· W2041985223 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueJournal of Information Technology · 2009
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicInformation Technology Governance and Strategy
Canadian institutionsWestern UniversityToronto Metropolitan University
Fundersnot available
KeywordsImplementationKnowledge managementProcess (computing)Process managementInformation systemComputer scienceEnterprise resource planningEnterprise systemSoft systems methodologyManagement information systemsKey (lock)Resource (disambiguation)BusinessEngineering

Abstract

fetched live from OpenAlex

Despite the general consensus regarding the critical role of top management in the information systems (ISs) implementation process, the literature has not yet provided a clear and compelling understanding of the top management support (TMS) concept. Applying metastructuring (Orlikowski et al., 1995) as a guiding framework for understanding TMS behaviors, this paper attempts to address the gap by focusing on two key questions: (1) What supportive actions do top managers engage in during IS implementations? (2) How do these actions affect IS implementation outcomes? Analyses of in-depth case studies at two Canadian universities that had implemented a large-scale enterprise system revealed three distinct types of TMS actions: TMS - resource provision (TMSR - actions related to supplying key resources such as funds, technologies, staff, and user training programs); TMS - change management (TMSC - actions related to fostering organizational receptivity of a new IS); and TMS - vision sharing (TMSV - actions related to ensuring that lower-level managers develop a common understanding of the core objectives and ideals for the new system). Results suggest that different support behaviors exercise different influences on implementation outcomes, and that top managers need to adjust their support actions to achieve the desired outcomes. In particular, TMSR affected project completion, TMSC impacted formation of user skills and attitudes, and TMSV influenced middle manager buy-in. Theoretical and practical implications of these findings are discussed.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.848
Threshold uncertainty score0.373

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.001
Science and technology studies0.0000.000
Scholarly communication0.0000.004
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.005
GPT teacher head0.227
Teacher spread0.222 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it