Design And Artifacts

Design and artifacts is the part of the philosophy of technology that takes made things seriously as objects of thought: not just machines in the abstract, but the chair you sit on, the bridge you cross, the app that tells you when to stand up.

11 frameworks, from 1954 to today · Philosophy Of Technology · Philosophy

still a working view ended · each leads to its entry below

Overview

Design and artifacts is the part of the philosophy of technology that takes made things seriously as objects of thought: not just machines in the abstract, but the chair you sit on, the bridge you cross, the app that tells you when to stand up. Its practitioners ask what kind of thing an artifact is, how design decisions embed values, and whether the people who make things can be held responsible for what those things do to the people who use them1. The stakes are practical as well as philosophical. If a technology is a neutral tool, then the only questions that matter are about how people choose to use it1. If, instead, artifacts shape behavior, perception, and social relations, then the design of a thing is already a moral and political act—and the field's history is a long argument about exactly how far that claim can be pushed1.

Classical Foundations: Technology as a Force in Human Life

Philosophy of technology as a self-conscious discipline emerged in the twentieth century, and its first major figures were concerned with technology at the scale of civilization rather than the scale of individual objects1. The German philosopher Martin Heidegger, in his 1954 essay "The Question Concerning Technology," argued that modern technology is not merely a collection of instruments but a way of revealing the world—one that treats everything, including human beings, as a "standing reserve" of resources to be optimized and drawn upon. The French philosopher Jacques Ellul, in The Technological Society (1954), described technique as an autonomous system that reorganizes society according to the criterion of efficiency, regardless of human intentions. The American philosopher Langdon Winner, in Autonomous Technology (1977), asked whether technology had escaped human control altogether.

This "classical" philosophy of technology was grand in scope and often pessimistic. Its central problem was that it treated technology as a monolithic force, and its central weakness was that it had little to say about particular artifacts. A bridge and a bomb were both instances of "technology," and the analysis rarely descended to the level of how a specific design choice affected a specific group of people. That gap is what the next generation of scholars set out to close.

The Empirical Turn: Studying Artifacts Up Close

Beginning in the 1980s, a group of scholars—many of them working in science and technology studies rather than philosophy departments—began to argue that the big questions about technology could only be answered by looking at how particular technologies were actually made. This shift is often called the "empirical turn." Its practitioners studied laboratories, engineering firms, and design studios, and they came back with a picture of technology as something shaped by human negotiation rather than something that imposed itself from outside.

The most influential of these approaches was the Social Construction of Technology, or SCOT, developed by Trevor Pinch and Wiebe Bijker in a 1984 paper on the history of the bicycle. SCOT argued that a technology's development is not determined by what works best but by what a relevant social group agrees counts as working2. The early bicycle took several forms—the high-wheeled "penny-farthing," the low-wheeled "safety" bicycle—and each was championed by different groups with different needs. The high wheel was fast and elegant but dangerous; the safety bicycle was slower but accessible to women and older riders. Which design "won" was not a matter of engineering necessity but of social negotiation. SCOT introduced the useful concept of "interpretive flexibility": the same artifact can mean different things to different groups, and closure—the point at which a design stabilizes—is a social achievement, not a technical inevitability.

A parallel approach, Actor-Network Theory (ANT), was developed by Bruno Latour, Michel Callon, and John Law in the same period3. ANT's radical move was to treat human beings and non-human things as equivalent "actors" in a network3. In Latour's famous example of the door closer, a hydraulic mechanism can be analyzed as an actor that enforces a rule—"close the door"—that would otherwise require a human doorman. The door closer does not merely assist human action; it replaces a human actor and thereby changes the social arrangement. ANT's vocabulary of "actants" and "networks" was controversial, but it gave scholars a way to describe how artifacts participate in social life without reducing them to either neutral tools or mysterious forces.

Design Methods and the Problem of Wicked Problems

While sociologists of technology were studying existing artifacts, a separate tradition was growing among designers and engineers who wanted to make design itself more rigorous. The Design Methods Movement of the 1960s and 1970s—associated with figures such as Horst Rittel in Germany and the United States, and with conferences and journals that brought together architects, engineers, and planners—sought to systematize the design process. The hope was that design could be made scientific: that systematic procedures could replace intuition and produce better buildings, products, and systems.

That hope ran into a problem that Rittel himself named. In a 1973 paper with Melvin Webber, he distinguished "tame" problems, which can be solved by applying established techniques, from "wicked" problems, which have no definitive formulation, no stopping rule, and no objective test of a correct solution. Designing a public building is a wicked problem: every solution changes the problem, and different stakeholders disagree about what counts as success. The Design Methods Movement's ambition to make design fully systematic was thus checked by the recognition that design is inherently a matter of judgment under conditions of uncertainty.

A related strand came from Donald Schön, whose 1983 book The Reflective Practitioner studied how professionals—architects, engineers, psychiatrists—actually work. Schön argued that competent practitioners do not simply apply rules; they engage in a "reflective conversation with the situation," testing moves, noticing unexpected results, and adjusting. His concept of "reflection-in-action" gave philosophical weight to the tacit, situated knowledge that design methods had tried to formalize away4. Together, Rittel and Schön shifted the question from "How can we make design scientific?" to "What kind of knowledge is design, and how should it be taught and practiced?"

Values in Design: From Neutral Tools to Moral Artifacts

The 1990s brought a new question: if artifacts shape behavior, can they be designed to shape it well? The Dutch scholar Peter-Paul Verbeek and others developed the idea of "technological mediation"—the claim that technologies actively co-shape human perception and action rather than merely facilitating it. A speed bump does not just slow cars; it changes what drivers perceive as a reasonable speed. A thermometer does not just measure temperature; it changes what counts as a fever. Mediation theory, drawing on the postphenomenology of Don Ihde, gave philosophers a vocabulary for describing these effects without falling back into either technological determinism or the assumption of neutrality.

The most direct attempt to turn this insight into a design practice was Value-Sensitive Design, or VSD, developed by Batya Friedman and colleagues at the University of Washington beginning in the 1990s5. VSD proposed that designers should identify the values implicated in a technology—privacy, autonomy, fairness, trust—and treat them as design requirements alongside functional ones5. The approach was influential in human-computer interaction and in the design of information systems, and it spawned a family of related methods, including "design for values" in the Netherlands and "responsible innovation" frameworks in Europe. Its critics pointed out that values conflict, that designers cannot always know which values matter to which users, and that the method can become a checklist rather than a genuine engagement with moral complexity.

A more political strand of the same insight is the "politics of artifacts," a phrase associated with Langdon Winner's 1980 essay "Do Artifacts Have Politics?" Winner argued that some technologies are political not because of how they are used but because of what they are. His example was Robert Moses's low bridges on the Long Island parkways, which—according to Winner's account—were built low enough to exclude buses and thus, in practice, to exclude the poor and Black residents who relied on public transit from the beaches. The empirical accuracy of the Moses example has been disputed by later historians, but the philosophical point survived: artifacts can embody and enforce social arrangements, and analyzing those arrangements is part of understanding what a technology is.

Engineering Philosophy and the Turn to Practice

A parallel development came from engineers and philosophers of engineering who thought the field had been too preoccupied with the social reception of technology and not enough with its making6. The "engineering philosophy of technology," a term associated with the Dutch philosopher of engineering Peter Kroes and others, argued that artifacts have a distinctive ontological structure: they are objects designed to fulfill a function, and their function is not reducible to their physical properties. A screwdriver is not just a piece of metal and plastic; it is a thing whose identity includes what it is for. This "dual nature" of artifacts—their physical constitution and their functional role—became a central topic. The approach also brought philosophical attention to engineering design as a form of reasoning, with its own logic of trade-offs, specifications, and failure analysis1.

This tradition connected to a broader movement in the philosophy of technology toward studying practices rather than abstractions. Instead of asking "What is technology?" in general, scholars asked how specific engineering disciplines justify their choices, how standards are negotiated, and how safety and reliability are reasoned about. The result was a philosophy of technology that looked more like the philosophy of science—attentive to actual cases, methods, and controversies—than like the grand critiques of the mid-twentieth century.

Postphenomenology and the Present Landscape

The most active contemporary framework for thinking about design and artifacts is postphenomenology, developed by Don Ihde and extended by Verbeek and others. Postphenomenology begins with the phenomenological insight that experience is always experience of something, and it adds the claim that technologies mediate that relation. Ihde's taxonomy of human-technology relations—embodiment relations (glasses), hermeneutic relations (a thermometer reading), alterity relations (interacting with a machine as if it were other), and background relations (infrastructure)—gave scholars a precise way to describe how artifacts shape experience. Verbeek's "moralizing" of this framework argued that designers have a responsibility to anticipate how their artifacts will mediate human action and to design for desirable mediations.

Today the field is plural. Empirical studies of design practice continue alongside philosophical analysis of artifact ontology. Value-sensitive design and its descendants are taught in engineering and computer science programs. The politics of artifacts is a standard reference point in debates about algorithmic systems and infrastructure. Postphenomenology remains a major theoretical resource, especially in Europe. What unites these approaches is the rejection of the classical view that technology is a monolithic force and the insistence that the details of design—who makes what, for whom, and with what assumptions—are where the philosophical action is. The open questions are the ones the field has carried from the beginning: how to weigh the values embedded in artifacts against the values of the people who use them, and whether philosophy can say anything useful to the people who actually build things before those things are built.

References

  1. Philosophy of technology (introduction, 20th century to present), Wikipedia
  2. Social construction of technology, Wikipedia
  3. Actor–network theory (introduction, Background and context), Wikipedia
  4. Reflective practice (History and background), Wikipedia
  5. Value sensitive design, Wikipedia
  6. Philosophy of engineering, Wikipedia

The frameworks of Design And Artifacts

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1954-1985

    Classical Philosophy of Technology

    What is the fundamental nature of modern technology?

    Fly to its tower in Nousfarer

  2. 1960-1980

    Design methods

    How can the design process be made systematic?

    Fly to its tower in Nousfarer

  3. 1973-Present

    Wicked problem

    How should we approach problems without clear solutions?

    Fly to its tower in Nousfarer

  4. 1980-Present

    Politics of Artifacts

    Do physical objects carry inherent political weight?

    Fly to its tower in Nousfarer

  5. 1983-Present

    Reflective Practice

    How do skilled professionals actually make decisions in practice?

    Fly to its tower in Nousfarer

  6. 1984-Present

    Actor-Network Theory

    How do human and non-human elements interact in action?

    Fly to its tower in Nousfarer

  7. 1984-Present

    Social Construction of Technology

    How is the development of a technology shaped by social groups?

    Fly to its tower in Nousfarer

  8. 1990-Present

    Engineering Philosophy of Technology

    What is the ethical responsibility of the engineer?

    Fly to its tower in Nousfarer

  9. 1990-Present

    Postphenomenology

    How does an artifact change our experience of reality?

    Fly to its tower in Nousfarer

  10. 1990-Present

    Value-Sensitive Design

    How can we design technology that upholds human values?

    Fly to its tower in Nousfarer

  11. 2000-Present

    Technological Mediation

    How does a technology mediate our perception and action?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

Classical Philosophy of TechnologyDesign methodsWicked problemPolitics of ArtifactsReflective PracticeActor-Network TheorySocial Construction of TechnologyEngineering Philosophy of TechnologyPostphenomenologyValue-Sensitive DesignTechnological Mediation

Beyond the field

Where Design And Artifacts's ideas came from in other fields, and what they led to there: the strongest 12 of 51 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Design And Artifacts is a planet in Nousfarer

Its city has a tower for each of these 11 frameworks. Land, walk in, and climb one concept at a time.

Land on Design And Artifacts

Related fields

Fields its ideas are linked to

More in Philosophy Of Technology

See where Design And Artifacts sits on the Map of Human Knowledge