Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 585

The DOI matches its Crossref record.

Technochange Management: Using IT to Drive Organizational Change

Markus, M Lynne·2004·Journal of Information Technology

Abstract

Using IT in ways that can trigger major organizational changes creates high-risk, potentially high-reward, situations that I call technochange (for technology-driven organizational change). Technochange differs from typical IT projects and from typical organizational change programs and therefore requires a different approach. One major risk in technochange—that people will not use information technology and related work practices—is not thoroughly addressed by the discipline of IT project management, which focuses on project cost, project schedule, and solution functionality. Organizational change management approaches are also generally not effective on their own, because they take as a given the IT “solutions” developed by a technical team. Consequently, the potential for the IT “solution” to be misaligned with important organizational characteristics, such as culture or incentives, is great. Merely combining IT project management and organizational change management approaches does not produce the best results, for two reasons. First, the additive approach does not effectively address the many failure-threatening problems that can arise over the lengthy sequential process of the typical technochange lifecycle. Second, the additive approach is not structured to produce the characteristics of a good technochange solution: a complete intervention consisting of IT and complementary organizational changes, an implementable solution with minimal misfits with the existing organization, and an organization primed to appropriate the potential benefits of the technochange solution. With hard work and care, the combined IT project management plus organizational change approach can be made to work. However, an iterative, incremental approach to implementing technochange can be a better strategy in many situations. The essential characteristic of the technochange prototyping approach is that each phase involves both new IT functionality and related organizational changes, such as redesigned business processes, new performance metrics, and training.

Overview

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1057/palgrave.jit.2000002

Cites

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cited by

Metadata

Authors
Markus, M. L.
Venue
Journal of Information Technology
Published
2004-03
Volume
19
Issue
1
Pages
4-20
ISSN
  • 0268-3962 (ISSN-L)
  • 1466-4437
OpenAlex
W2087291729
Cited by
585
References
0
FWCI
43.43
Type
journal article
Language
en
Open access
closed
Licence
journals.sagepub.com/page/policies/text-and-data-mining-license (tdm)

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.