Infrastructure Studies
Also known as: Infrastructural inversion, Ecology of infrastructure, Study of boundary objects
The infrastructure studies method, developed by Susan Leigh Star, Geoffrey Bowker, and Karen Ruhleder, studies the normally invisible relational systems—standards, classifications, pipes, protocols, and installed bases—on which modern life silently depends. Its signature move is 'infrastructural inversion': deliberately foregrounding the background, treating the taken-for-granted substrate as the object of analysis, and reading its standards, classifications, and breakdowns to understand how it shapes work, knowledge, and lives.
Key highlights
- Makes visible the powerful but normally invisible substrate—standards, classifications, installed bases—that other methods overlook entirely.
- Reveals the politics and morality of apparently neutral technical categories, showing whom they privilege and whom they erase.
- Provides durable concepts—boundary objects, installed base, infrastructural inversion, invisible work—that travel across domains.
- Uses breakdown and friction as a disciplined empirical entry point into systems that are otherwise transparent in use.
Intuition
This section is available to Pro members. Upgrade to Pro
How it works
This section is available to Pro members. Upgrade to Pro
When to use it
Use the infrastructure studies method when the object of interest is a large, embedded, relational system—an information standard, a classification scheme, a network, a platform—whose workings are normally invisible and taken for granted. It suits research on how categories and standards organise work and knowledge, on whose labour and whose existence a system renders visible or invisible, and on the politics buried in apparently neutral technical arrangements. It assumes that infrastructure is relational and best studied through breakdown, ethnography, and historical tracing. It is less appropriate when you need a controlled comparison, a quantified outcome, or when the system in question is novel enough to lack an installed base or settled standards.
Strengths & limitations
- Makes visible the powerful but normally invisible substrate—standards, classifications, installed bases—that other methods overlook entirely.
- Reveals the politics and morality of apparently neutral technical categories, showing whom they privilege and whom they erase.
- Provides durable concepts—boundary objects, installed base, infrastructural inversion, invisible work—that travel across domains.
- Uses breakdown and friction as a disciplined empirical entry point into systems that are otherwise transparent in use.
- The interpretive, ethnographic approach resists generalisation and quantified comparison across many infrastructures.
- Studying invisible systems demands deep, time-consuming access to sites, archives, and practitioners that is hard to obtain.
- Identifying what counts as 'the' infrastructure is itself a relational judgement, leaving the unit of analysis open to dispute.
- Rich description of one infrastructure can be difficult to translate into actionable design or policy recommendations.
Common pitfalls
This section is available to Pro members. Upgrade to Pro
Applications
This section is available to Pro members. Upgrade to Pro
Frequently asked
What exactly is 'infrastructural inversion'?
Infrastructural inversion, a term Bowker drew on and developed with Star, is the analytic move of foregrounding the background—treating the normally invisible substrate of standards, classifications, and technical arrangements as the central object of study rather than as inert support for human action. It reverses the usual figure-ground relation, so that the boring, taken-for-granted infrastructure becomes the thing you most want to explain. It is the method's defining gesture.
Why study infrastructure through breakdown?
Because infrastructure is, by definition, transparent in use: it works best when you do not notice it. That very invisibility makes it hard to study directly. Breakdowns, friction, and the struggles of newcomers learning the system make the hidden assumptions and the sustaining labour suddenly visible. Star treated breakdown not as a nuisance but as the analyst's privileged window onto a substrate that otherwise refuses to appear.
What is a boundary object and how does it fit in?
A boundary object is an entity—a form, a specimen, a classification—plastic enough to adapt to the local needs of different communities yet robust enough to maintain a common identity across them, letting groups cooperate without full consensus. Star introduced the concept to explain coordination across social worlds, and it is central to infrastructure studies because standards and classifications often function as boundary objects, holding diverse practices together while meaning different things to each.
Sources
- 1.Star, S. L., & Ruhleder, K. (1996). Steps toward an ecology of infrastructure: design and access for large information spaces. Information Systems Research, 7(1), 111-134.
- 2.Bowker, G. C., & Star, S. L. (1999). Sorting Things Out: Classification and Its Consequences. MIT Press.ISBN 9780262522953
You have read it. What now?
Cite this page
ScholarGate. (2026, June 22). Infrastructure Studies. ScholarGate. https://scholargate.app/science-technology-studies/infrastructure-studies-method