Construct · 4 names · 5 citations
Different names. Different fields. One construct. One map.
● jangle · one label, moving referent Nearest construct by meaningresourcecompare the meaningsEvery construct on the map is compared with every other by the meaning of its definitions, and the closest one is surfaced here. The nearest construct to IT capability is resource.
Hold this as a prompt, not a verdict. Two constructs sitting close in meaning is a reason to read them side by side and decide for yourself whether they are one idea under two names. It is not proof that they are. Compare the meanings in the Collider.
Spokes are the names and the models that coined them; dashed arcs are borrowings. Tap a field for its definition, unit, and measures.
Drag to watch the word get claimed. Each name appears at the publication date of the earliest source cited for it. Tap a year to see which.
The firm's ability to mobilize and deploy IT-based resources together with other resources, so that the combination creates an advantage a rival cannot easily copy. Bharadwaj's 2000 study framed IT capability as an application of the resource-based view of the firm, built from three parts: a flexible IT infrastructure, human IT skills, and IT-enabled intangibles such as customer orientation and knowledge assets. She compared firms named as IT leaders with a matched control group and found the leaders showed higher profit ratios and lower cost ratios. The referent here is a firm-level ability, not the technology itself and not the money spent on it. This is the meaning the rest of the map is measured against.[1]
In the productivity-paradox debate, researchers asked why heavy IT investment often failed to show up in firm performance, and part of the answer was that spending is an input while capability is an ability, and the two are not the same. Santhanam and Hartono revisited Bharadwaj's claim in 2003, checked whether IT-capable firms really did outperform once prior performance and industry effects were controlled, and largely confirmed that they did. Their methodological point was that IT capability has to be measured as a firm attribute, not read off the size of the IT budget. Here the moving referent is sharpest: the same words, IT capability, are sometimes attached to what a firm can do and sometimes to what it buys. A study that proxies capability with spending is measuring a different thing.[2]
IT business value research asks when and how information technology improves organizational performance, and treats IT as one resource among many rather than a lever that works on its own. Melville, Kraemer, and Gurbaxani's 2004 review pulled this literature into a single model in which technological and human IT resources raise performance only in combination with complementary organizational resources, and only within a competitive and macro environment that shapes the payoff. In their reading the label covers both the IT resources a firm holds and the business processes those resources are applied to. This is close kin to Bharadwaj's IT capability, but the unit of analysis slides between the resource, the process, and the whole firm. Naming which level you mean is the work the shared label leaves undone.[3]
As the technology changed, the same idea was renamed for a faster world. Sambamurthy, Bharadwaj, and Grover argued in 2003 that IT should be seen not as a fixed asset but as a set of digital options that let a firm sense and act on change, so IT capability becomes a source of agility. Warner and Wager later cast the same move as building dynamic capabilities for digital transformation, an ongoing process of sensing, seizing, and reconfiguring. The referent has shifted from a stock of IT resources toward a capacity to keep changing, which overlaps with the separate literatures on dynamic capabilities and agility. Whether this is the old IT capability under new names or a genuinely new construct is exactly the question the shared vocabulary hides.[4][5]
Next
See how IT capability sits against neighbouring constructs in the Collider, or export every reference on this page in one click.
Open in ColliderExport BibTeXReport this collisionCited on this page?
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