Construct · 1 fields · 1 citations

strategic necessity hypothesis: a standalone construct

One name. One construct. A landmark on the map.

● anchor · a standalone construct Nearest construct by meaning·not indexed

A single standalone construct; nearby constructs are located against it in the Collider. Tap a field for its definition, unit, and measures.

Information systems

the proposition that IT applications rivals can easily copy become necessary to stay in business but give no lasting advantage on their own.

In information systems, strategic necessity hypothesis refers to the proposition that IT applications rivals can easily copy become necessary to stay in business but give no lasting advantage on their own. This meaning comes from Clemons (1991) in MIS Quarterly.[1]

Unit
Recovery means
Measured by

Run it through the Collider, or take the citations with you.

See how strategic necessity hypothesis sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in Collider Export BibTeX Report this entry

Nearby constructs

business1 fields · 1 citationsanchor · a standalone construct hypothesis2 fields · 2 citationsjingle · one word, two constructs information4 fields · 5 citationsjingle · one word, four constructs

References

Clemons, E. K., & Row, M. C. (1991). Sustaining IT Advantage: The Role of Structural Differences. MIS Quarterly, 15(3), 275-292. https://doi.org/10.2307/249639

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct