MétaCan
Menu
Back to cohort
Record W3004823301 · doi:10.24251/hicss.2020.528

Orchestrating the Digital Transformation Process through a ‘Strategy-as-Practice’ Lens: A Revelatory Case Study

2020· article· en· W3004823301 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.

Bibliographic record

VenueProceedings of the ... Annual Hawaii International Conference on System Sciences/Proceedings of the Annual Hawaii International Conference on System Sciences · 2020
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicInformation Technology Governance and Strategy
Canadian institutionsUniversité du Québec à Trois-Rivières
Fundersnot available
KeywordsOrchestrationProcess (computing)Context (archaeology)Digital transformationProcess managementAsset (computer security)Knowledge managementComputer scienceService (business)Lens (geology)BusinessPerspective (graphical)EngineeringMarketingWorld Wide WebArtificial intelligence

Abstract

fetched live from OpenAlex

Implementing a digital transformation (DT) strategy constitutes an important challenge for most firms. Small and medium-sized enterprises (SMEs) in particular must be helped in enacting and managing their DT process. To do so, we aim to answer two research questions: What are the dimensions that define a DT strategy in a SME context? And how do these dimensions contribute to the enactment of a DT process in this context? Using an information systems (IS) strategy-as-practice theoretical lens, combined with an information technology (IT) asset orchestration perspective, we opt for an interpretive case study of an industrial service SME whose characteristics are conducive to a renewed vision of IS strategy in a DT context. From this study emerges a process model that allows us to describe and better understand, in a concrete manner, how a DT occurs and how it is managed through a coherent DT strategy.

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.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies, Scholarly communication, Open science
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.984
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.002
Science and technology studies0.0020.002
Scholarly communication0.0020.014
Open science0.0070.001
Research integrity0.0000.001
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.072
GPT teacher head0.309
Teacher spread0.237 · 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