Design Research

Design research is the systematic study of how designed things are made, used, and understood—and the deliberate use of research methods inside the act of designing.

10 frameworks, from 1962 to today · Design · Arts & Architecture

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

Overview

Design research is the systematic study of how designed things are made, used, and understood—and the deliberate use of research methods inside the act of designing1. It matters because design decisions are made before anyone encounters the result: a chair, an app, a hospital wayfinding system, a public service. Design research asks how those decisions can be made on evidence rather than habit, how the people affected by a design can have a say in it, and how designing itself can produce knowledge that others can use. The field is unusual in that its practitioners are often designers who research, rather than researchers who study designers, and its history is a long argument about whether design is a science, a craft, a form of inquiry, or all three.

Design as science: the methods movement of the 1960s

The first self-conscious design research grew out of the Second World War, when operations research, ergonomics, and systems analysis showed that complex problems could be tackled with explicit procedures. In the early 1960s a group of architects and engineers—among them Horst Rittel in Germany and later California, Christopher Alexander in England and the United States, and Bruce Archer in Britain—argued that design should become a rigorous, teachable discipline rather than a matter of individual inspiration.

The landmark event was the Conference on Design Methods held in London in 1962, organised by John Christopher Jones and others, which brought together engineers, architects, and industrial designers to compare formal procedures. The movement that followed, often called the Design Methods Movement, produced a wave of techniques: systematic checklists, morphological charts that break a problem into parameters and combine options, and explicit stages of analysis, synthesis, and evaluation. The claim was that if the design process were made visible and rule-governed, it could be taught, compared, and improved.

The most influential single work was Christopher Alexander's Notes on the Synthesis of Form (1964), which tried to decompose design problems into sets of requirements and their interactions, so that a building or product could be assembled from resolved sub-problems. Alexander later repudiated much of this approach, and the movement's confidence was shaken when practitioners found that real design problems refused to decompose neatly. Horst Rittel and Melvin Webber named the difficulty in 1973: design problems are "wicked problems," meaning they have no definitive formulation, no stopping rule, and no single correct solution, because every attempt to solve them changes the problem. That diagnosis redirected the field from prescribing methods to studying how designers actually work.

The reflective practitioner and the turn to practice

The next turning point came from Donald Schön, whose The Reflective Practitioner (1983) studied architects, engineers, and other professionals at work. Schön argued that competent practice is not the application of rules but a "conversation with the situation": the designer acts, the material or drawing "talks back," and the designer reframes the problem in response. His notion of reflection-in-action—thinking while doing, adjusting as the situation responds—gave a name to what experienced designers had always done and made it a subject of research.

Schön's account was convincing because it explained what the methods movement could not: why skilled designers often ignore formal procedures and still succeed, and why design problems get redefined mid-project. It also opened a research programme. If design knowledge lives in practice, then studying practice—through observation, interviews, and protocol analysis of designers thinking aloud—becomes the way to understand it. This shift from prescribing methods to describing practice is the hinge on which much later design research turns.

Users enter the process

Alongside these debates, a parallel strand grew from ergonomics and human-factors engineering. User-Centered Design, articulated influentially by Donald Norman in the 1980s and codified in standards work in the following decade, held that the needs, capabilities, and limitations of the people who use a product should drive its design, and that usability should be tested with real users rather than assumed. Norman's The Design of Everyday Things (1988, originally The Psychology of Everyday Things) popularised the idea that confusing objects are design failures, not user failures, and introduced widely used concepts such as affordances and feedback.

The methods that grew around this approach—usability testing, task analysis, iterative prototyping with users—made the user an empirical presence in design research. But they also drew criticism: testing tends to ask whether people can use what has already been proposed, not whether the proposal is the right one. That gap pushed the field toward methods that bring users in earlier and more deeply.

Designing with people: participatory and ethnographic approaches

Participatory Design emerged in Scandinavia in the 1970s and 1980s, rooted in trade-union politics and workplace democracy. Researchers such as Kristen Nygaard and the projects around the Norwegian Iron and Metal Workers Union argued that workers affected by computer systems should help design them. The approach produced concrete techniques—future workshops, mock-ups, and cooperative prototyping—in which users and designers build and test proposals together. Its central claim, that people have a right to shape the systems that shape their work, spread from Scandinavia to international research communities and later into public-sector and community design.

A related development was the import of ethnography into design. Beginning in the 1980s and 1990s, researchers at Xerox PARC and elsewhere—Lucy Suchman's Plans and Situated Actions (1987) is a landmark—showed that people's actual behaviour diverges sharply from the plans and procedures designers assume. Ethnographically informed design research uses observation and interviews to understand what people really do, then feeds that understanding into design. The method's contribution is to treat use as a situated, social activity rather than a set of tasks, and it became a standard part of commercial and academic design research.

Research through design

By the 1990s a further question pressed: can designing itself produce knowledge? Research through Design is the answer that took shape in the 2000s, especially in the interaction-design and human–computer-interaction communities. Its argument is that making a prototype, artefact, or system is a form of inquiry: the designer constructs a possible future, tests it in a situation, and learns something that could not have been learned by description alone. The designed thing becomes an instrument of research, and the knowledge produced is often embodied in the artefact and its documented process rather than stated as a general law.

This position gave academic legitimacy to practice-based design research and doctoral work by making, and it remains one of the field's most active debates—how such knowledge is evaluated, generalised, and shared. It also connects design research to the older craft tradition of learning through making, while insisting that the making be framed as a contribution to knowledge.

Values, critique, and speculation

From the 1990s onward, design research increasingly asked not only how to design well but what designs should do and whom they serve. Value-Sensitive Design, developed by Batya Friedman and colleagues from the late 1990s, proposed that human values—privacy, autonomy, trust, fairness—be treated as explicit design requirements, identified and weighed during the process rather than left to chance. Its methods include value scenarios and stakeholder analysis, and it has been applied to privacy in information systems and to the design of emerging technologies.

A more provocative strand came from Critical Design, associated with Anthony Dunne and Fiona Raby, whose work from the late 1990s used designed objects and scenarios to question assumptions rather than to solve problems23. Their Design Noir (2001) and later Speculative Everything (2013) argued that design could function as a form of social and cultural critique, proposing alternative presents and futures to make people think. This critical and speculative turn widened what counted as design research and fed directly into the neighbouring field of speculative design.

Design thinking and the present

The most visible export of design research has been Design Thinking—the packaging of designerly approaches (empathy with users, problem framing, rapid prototyping, iteration) as a method for non-designers. Its academic roots run through the methods movement and Schön's reflective practice; its popular form was shaped by the design firm IDEO and by business-school teaching from the 1990s onward, and it spread widely into management, public services, and education in the 2000s and 2010s. Design thinking has been both influential and contested: critics argue that its workshop-friendly version can flatten the political and technical difficulty that serious design research addresses, while its defenders point to its role in bringing user-centred, iterative practice to organisations that had none.

Today the field holds several approaches in productive tension. Practice-based and research-through-design work continues to grow, especially in interaction design and doctoral programmes. Ethnographic and participatory methods are standard in commercial and public-sector research. Value-sensitive and critical approaches have pushed questions of ethics and consequence into the centre of the field. The open questions are substantial: how to generalise knowledge that is produced through making; how to make participatory processes genuinely share power rather than consult; how to evaluate speculative and critical work; and how design research can address large-scale problems—climate, care, inequality—that exceed any single product or user. The history above is the record of a field learning, repeatedly, that its hardest problems are not technical but human, and that the methods for studying them must keep changing with the problems they meet.

References

  1. Design research, Wikipedia
  2. Speculative design, Wikipedia
  3. Critical design, Wikipedia

The frameworks of Design Research

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

  1. 1962-1975

    Design Methods Movement

    Can design be made a rigorous, teachable procedure?

    About Design Methods Movement
    The Design Methods Movement is best understood as a sustained attempt to make the act of designing more systematic, explicit, and open to scrutiny. Its organizing idea is that design is not a mysterious flash of intuition but a rational process that can be broken down into discrete, repeatable steps. By externalizing the designer’s private thinking—through diagrams, matrices, checklists, and decision trees—the movement aimed to replace guesswork with method. The problem it addressed was the growing complexity of mid-twentieth-century design challenges, from urban planning to industrial products, which seemed to overwhelm the traditional reliance on individual talent and accumulated craft knowledge. In the face of large-scale social and technical problems, the movement’s proponents argued that design needed a rigorous, almost scientific, foundation.
    This ambition distinguished the movement from earlier design traditions and from some of its successors. Unlike the Beaux-Arts emphasis on aesthetic precedent or the Bauhaus focus on artistic expression, the Design Methods Movement treated design as a form of applied logic. It also differed from later participatory or user-centered approaches by initially placing the designer as the central rational agent, even when the methods were meant to serve broader social goals. The movement’s early phase, roughly from the late 1950s through the mid-1960s, was optimistic about the power of systematic analysis. Its later phase, in the late 1960s and early 1970s, became more critical and self-aware, as key figures began to question whether any method could fully tame the messy, value-laden nature of real-world problems.
    To grasp the movement’s core concepts, it helps to follow a logical progression. First, consider the idea of problem structuring: the belief that a design problem must be explicitly defined, decomposed into sub-problems, and analyzed before any solution is sought. This leads to the second concept, systematic generation of alternatives, where methods such as morphological charts or brainstorming are used to produce a wide range of possible solutions rather than settling on the first idea. Third is evaluation and selection, which involves using criteria, matrices, or even early computer-based tools to compare alternatives in a transparent way. Fourth, and increasingly important as the movement matured, is the recognition of wicked problems—problems that resist clear definition, have no definitive solution, and where every attempt to solve one aspect changes the problem itself. Finally, the movement introduced the idea of methodological reflection, meaning that designers should not just use methods but also critically examine which methods are appropriate for which situations, and why.
    The intellectual history of the movement is anchored in a few well-documented figures and events. The 1962 Conference on Systematic and Intuitive Methods in Engineering, Industrial Design, Architecture, and Communications, held in London, is widely regarded as the movement’s founding moment. J. Christopher Jones, an engineer and ergonomist, was a central figure; his 1970 book Design Methods became a canonical text, offering a catalog of techniques from user research to creativity exercises. L. Bruce Archer, a mechanical engineer and design researcher, contributed a rigorous, almost scientific model of the design process, arguing that design could be a third area of education alongside the sciences and the humanities. Horst Rittel, a mathematician and design theorist, initially embraced systematic methods but later introduced the concept of “wicked problems” in the late 1960s, fundamentally challenging the movement’s early optimism. Herbert A. Simon’s The Sciences of the Artificial (1969) provided a broader intellectual justification, framing design as a science of the artificial—a field concerned with how things ought to be, rather than how they are. The movement also had roots in Germany, particularly at the Ulm School of Design, where cybernetics, systems theory, and semiotics were integrated into the curriculum, and where the link between design and industry was deliberately strengthened.
    The movement’s significance today is both foundational and cautionary. It established design as a legitimate subject of academic study and research, creating the intellectual space for what would later become design research, design science, and human-centered design. Its emphasis on explicit process influenced fields far beyond its original scope, including software engineering, service design, and policy-making. At the same time, its internal critiques—especially Rittel’s—remain essential lessons. The recognition that many design problems are wicked, and that no method can eliminate the need for judgment, values, and stakeholder engagement, directly shaped later approaches such as participatory design and reflective practice. The movement did not fail because it was wrong; it failed because it was incomplete. Its legacy is the ongoing tension between systematic rigor and creative flexibility, a tension that still defines design practice and research.
    For a reader approaching this topic, no specialist background is required. A basic familiarity with design practice—whether in architecture, engineering, or product design—will help, but the movement’s core ideas are accessible to anyone interested in how decisions are made under uncertainty. The most useful prerequisite is a willingness to think about design not as an art form but as a decision-making process, and to consider how that process can be made more transparent, more democratic, and more responsive to the complexity of real-world problems.
    The 9 concepts its tower teaches
    • Systematic Design
    • Problem Structuring
    • Systematic Generation of Alternatives
    • Evaluation and Selection
    • Wicked Problems
    • Methodological Reflection
    • Design as an Academic Discipline
    • Design as a Science of the Artificial
    • Participatory and User-Centered Design

    Fly to its tower in Nousfarer

  2. 1973-Present

    Wicked problem

    Why do design problems resist definitive solution?

    Fly to its tower in Nousfarer

  3. 1975-Present

    Participatory Design

    Should the people affected help design the system?

    About Participatory Design
    Participatory Design is a framework for making things that insists on a fundamental shift: the people who will use a system, tool, or service should have an equal say in how it is designed. It answered the rationalist impulse of the Design Methods Movement—which tried to turn design into a science—by arguing that design is first and foremost a political act. Where Human-Centered Design later would focus on understanding users' needs from a designer's expert perspective, Participatory Design demands that users become co-designers with genuine decision-making authority. The core question is not simply "what do people need?" but "who decides what is a good design, and how do we share that power fairly?"
    Core curriculum (in logical learning order)
    1. Scandinavian Labor Movement Roots & Workplace Democracy: Participatory Design was forged in the 1970s as part of a broader labor struggle in Scandinavia. Workers and unions demanded a voice in how new computing systems would reshape their jobs. The framework's deepest commitment is to democratizing the workplace, ensuring that technological change serves workers rather than automating their control.
    2. Collective Resource Approach: This early argument held that the collective knowledge and interests of workers were a resource to be respected, not just a problem to be solved. It shifted the frame from individual user satisfaction to shared, democratic control over the means of production.
    3. Mutual Learning: Designers and users teach each other. Designers learn the tacit skills and real conditions of work; users learn about technical possibilities and trade-offs. This two-way exchange replaces the expert-to-layperson model.
    4. User as Co-Designer: This is the core identity shift. Users are not informants, test subjects, or passive recipients. They are full partners in the design team, with genuine authority over decisions.
    5. Participatory Design Methods: A toolbox of techniques specifically created to make co-design possible. These include cooperative prototyping, future workshops, and organizational games.
    6. Cooperative Prototyping: A hands-on technique where users and designers build rough, working versions of a system together. Users can immediately test and reshape the prototype in real time, revealing tacit knowledge and preventing misunderstandings.
    7. Future Workshops: A structured, three-phase session (critique, fantasy, implementation) that helps users envision ideal futures free from current constraints. It is explicitly political: it starts by naming problems with power and then moves to creative solutions.
    8. Organizational Games: Simple, role-playing games that map out how work actually gets done, who controls information, and how decisions are made. They expose the social and political dynamics that a technical system must account for.
    9. Stakeholder Engagement & Power Redistribution: Participatory Design is not just about including people; it is about rearranging authority. The process deliberately seeks out less powerful stakeholders—the workers, the marginalized users—and gives them tools to negotiate on equal footing with managers and experts.
    10. Participatory Design Process & Design by Doing: The process is iterative, hands-on, and pragmatic. Ideas are tested through action—building mock-ups, acting out scenarios—rather than through abstract specifications. This "design by doing" keeps the focus on concrete, lived experience.
    Intellectual history Participatory Design emerged in Scandinavia in the late 1960s and early 1970s, a direct outgrowth of the labor movement. This is not a matter of influence: it is the framework's origin. In Norway and Sweden, unions and their research allies—notably the Norwegian Computing Centre and the Swedish Center for Working Life—launched projects that gave workers control over the design of new computer systems. The most famous early project was the 1971–1973 Norwegian Iron and Metal Workers' Union project (often called the "Iron Project" or "NJMF project"), where workers and researchers together designed a system for wage calculation and job scheduling.
    Key figures from this founding period include Kristen Nygaard (1917–2002), the Norwegian computer scientist and union activist who co-developed the Simula programming language and argued that system design was inherently political. Nygaard's work on the Norwegian Iron and Metal Workers' Union project was foundational. Pelle Ehn (born 1948) and Morten Kyng (born 1955) are the two scholars most associated with codifying the framework's methods. In their seminal 1987 collection Design at Work: Cooperative Design of Computer Systems, they articulated the core concepts of cooperative prototyping, future workshops, and mutual learning, drawing directly from their union collaborations in Sweden and Denmark.
    Another important co-founder is Finn Kensing (born 1945), whose 1983 article "Skill, Ethics, and a Method for Design" consolidated the ethical argument for user participation. The seminal text for the workplace democracy dimension is Claus Otto Scharmer's (later codified in the 2000s) but earlier work by Bjørg Aanestad and others argued for the "collective resource approach," a label that became standard.
    The framework was initially a direct competitor to the rationalist Design Methods Movement. It shared the Second-Generation Design Methods' critique that problems were "wicked" (Horst Rittel's term), but went further by embedding design within a clear political commitment to workplace democracy. It is distinct from Human-Centered Design, which began to emerge in the 1980s. HCD absorbed some Participatory Design techniques—like prototyping with users—but stripped away the political dimension. HCD treats users as sources of information; Participatory Design treats them as decision-making partners.
    Participatory Design remains active today. It influenced later decolonial and critical design frameworks, which also question who holds power in the design process. However, its core political commitment—to democratize the workplace—has sometimes been softened in later, managerial versions that call for "stakeholder engagement" without actually redistributing power.
    Caution: Do not conflate Participatory Design with Human-Centered Design or design thinking. They share some methods (e.g., prototyping, iteration) but differ fundamentally in their purpose: Participatory Design aims to redistribute power, while HCD and design thinking focus on innovation and user satisfaction within existing power structures.
    The 10 concepts its tower teaches
    • Collective Resource Approach
    • Cooperative Prototyping
    • Future Workshops
    • Mutual Learning
    • Organizational Games
    • Participatory Design Methods
    • Power Redistribution
    • Scandinavian Labor Movement Roots
    • User as Co-Designer
    • Workplace Democracy

    Fly to its tower in Nousfarer

  4. 1983-Present

    Reflective Practice

    How do skilled practitioners actually think while working?

    About Reflective Practice
    Reflective practice entered design research as a direct challenge to the idea that design could be made fully rational, explicit, and scientific. In the 1960s, the design methods movement had tried to break design into repeatable, logical steps, treating it as a problem-solving activity that could be formalized and even automated. By the 1970s, that program had largely stalled, and practitioners increasingly recognized that real design problems were not the neat, well-defined puzzles that the methods assumed. Reflective practice, articulated most influentially by Donald Schön in his 1983 book The Reflective Practitioner, offered a different account: design is not the application of pre-existing knowledge but a form of intelligent action in which the practitioner thinks while doing.
    The framework’s distinctive organizing idea is that professional competence, especially in design, is not primarily a matter of applying theory to practice. Instead, skilled practitioners engage in a kind of knowing-in-action, a tacit, embodied sense of how to proceed that is difficult to put into words. When a situation does not fit familiar patterns, the practitioner does not stop and consult a manual; they engage in reflection-in-action, a process of thinking on their feet, experimenting, and adjusting their approach in real time. After the work is done, reflection-on-action allows them to look back, analyze what happened, and extract lessons that will shape future practice. The central problem this framework addresses is the gap between the formal, abstract knowledge taught in schools and the messy, uncertain, value-laden reality of professional work. Schön called this the "swampy lowlands" of practice, where problems are ill-defined and solutions cannot be derived from theory alone.
    To understand reflective practice, it helps to learn its concepts in a specific order. First, grasp the idea of knowing-in-action: the spontaneous, often unarticulated expertise that professionals display in their everyday work. Second, understand reflection-in-action, the moment of surprise or difficulty that prompts a practitioner to think about what they are doing while they are doing it, often by framing and reframing the problem. Third, learn reflection-on-action, the retrospective analysis that turns experience into learning. Fourth, consider the reflective conversation with the situation, Schön’s metaphor for how a designer shapes a design and then lets the design "talk back," revealing new constraints and possibilities that reshape the designer's understanding. Finally, recognize the role of framing: the way a practitioner names and frames a problem determines what solutions are possible, and reflection often involves reframing the problem itself.
    The intellectual history of reflective practice in design research begins with the collapse of the design methods movement. Schön, a philosopher and urban planner, drew on earlier thinkers such as John Dewey, who had emphasized the role of experience and reflection in learning, and on the tradition of pragmatism. His 1983 book was not aimed at designers alone; it examined architects, psychotherapists, engineers, and managers, but the architectural studio became a central example. Schön’s account of the design studio, where students learn by doing and by receiving critiques, became a touchstone for design educators. His work gave design research a language for describing what designers actually do, rather than what a rationalist model said they should do. It also provided a justification for studio-based education and for the idea that design knowledge is partly personal and tacit, not fully transferable as explicit rules.
    Reflective practice differs from nearby approaches in a clear way. The design methods movement and the later science of design sought to make design knowledge explicit, generalizable, and testable. Reflective practice, by contrast, treats the practitioner’s own experience as the primary source of knowledge. Participatory design, which was emerging around the same time, focuses on involving users in the design process; reflective practice focuses on the designer’s own thinking and learning. Human-centered design, which became dominant later, emphasizes empathy with users and iterative testing, but it often treats the design process as a structured sequence of stages. Reflective practice is less concerned with the sequence of stages than with the quality of attention the designer brings to their own actions and assumptions. It is not a method for producing a better artifact directly, but a discipline for becoming a better practitioner over time.
    The continuing significance of reflective practice lies in its insistence that design is a learning activity. In a field where problems are often unique, ambiguous, and value-laden, no textbook can provide the right answer in advance. The designer must learn from each situation, and reflective practice provides a way to make that learning deliberate. It has been widely adopted in design education, where the studio critique and the reflective journal are direct descendants of Schön’s ideas. It also remains relevant to professional practice, where designers are asked to explain and justify their decisions, and to design research, where the researcher’s own position and assumptions are recognized as part of the inquiry. While later frameworks such as research through design have built on the idea that designing can generate knowledge, reflective practice remains the foundational account of how the designer learns from their own work.
    No specialist background is required to begin studying reflective practice. The framework is accessible to anyone who has ever done a skilled activity and noticed that they learned something from doing it. A basic familiarity with the history of design methods in the 1960s is helpful for understanding why reflective practice emerged as a response, but it is not a prerequisite. The primary prerequisite is a willingness to examine one’s own assumptions and actions critically, and to treat experience, not just theory, as a legitimate source of knowledge.
    The 5 concepts its tower teaches
    • Knowing-in-action
    • Reflection-in-action
    • Reflective conversation with the situation
    • Reflection-on-action
    • Framing

    Fly to its tower in Nousfarer

  5. 1986-Present

    User-Centered Design

    How should products fit the people who use them?

    Fly to its tower in Nousfarer

  6. 1987-Present

    Ethnography in Design

    What do people actually do, as opposed to what is planned?

    Fly to its tower in Nousfarer

  7. 1991-Present

    Design Thinking

    Can designerly methods be taught to non-designers?

    Fly to its tower in Nousfarer

  8. 1993-Present

    Research through Design

    Can making an artefact produce knowledge?

    About Research through Design
    Research through Design (RtD) is a research approach within the broader field of design research that treats the act of designing itself as a primary mode of inquiry. Rather than studying design from the outside—as a historian or sociologist might—or using design merely as a tool to apply pre-existing theories, RtD generates new knowledge through the iterative process of conceiving, building, and testing artifacts. The central claim is that the designed object is not just an outcome; it is a vehicle for exploring complex, ill-defined problems and for producing insights that could not be reached through words or numbers alone.
    To understand RtD, it helps to place it within the three-part distinction that organizes design research: research for design, research into design, and research through design. Research for design gathers information to support a specific project—user interviews, market analysis, or usability tests. Research into design treats design as an object of study, asking historical, sociological, or philosophical questions about it. Research through design, by contrast, uses the design process as the method of investigation. The researcher does not simply observe or describe; they intervene by creating prototypes, systems, or experiences, and then reflect on what those creations reveal. The knowledge produced is often tacit, situated, and embodied—embedded in the artifacts themselves and in the decisions made during their development.
    The intellectual roots of RtD lie in the failure of the earlier design methods movement of the 1960s. That movement, driven by engineers and architects, sought to make design more rigorous by applying scientific and computational methods—breaking problems into linear steps, using optimization algorithms, and treating design as a rational problem-solving activity. By the 1970s, this approach had largely collapsed under its own weight. Design problems, it turned out, are rarely well-defined; they are "wicked" or "ill-structured," meaning that the problem and the solution co-evolve. You cannot fully specify the problem before you start designing, because the act of proposing a solution changes your understanding of the problem. This realization opened the door for a different kind of rigor—one based not on prediction and control, but on reflection, iteration, and the disciplined use of judgment.
    The formal articulation of RtD is most closely associated with the work of Christopher Frayling in 1993, who popularized the term in his essay "Research in Art and Design." Frayling distinguished between research into art and design (historical or theoretical study), research for art and design (gathering materials and references), and research through art and design (where the practice itself is the research). However, the deeper intellectual foundation was laid by Donald Schön, whose 1983 book The Reflective Practitioner argued that professionals in fields like architecture and design do not simply apply theory; they engage in "reflection-in-action," thinking on their feet and reshaping their understanding as they work. Schön's work, which emerged from the reflective practice tradition, provided the epistemological justification for RtD: if skilled practitioners generate knowledge through doing, then that doing can be a legitimate form of academic inquiry.
    RtD gained significant traction in the 1990s and 2000s, particularly within human-computer interaction (HCI) and interaction design. Researchers such as Bill Gaver and his colleagues at the Royal College of Art used RtD to explore speculative and critical design, creating "probotypes" and "cultural probes" that provoked new questions rather than solving existing ones. Gaver's 2012 manifesto, "What Should We Expect From Research Through Design?," argued that RtD produces three types of knowledge: theory (new conceptual frameworks), prototypes (artifacts that embody and communicate ideas), and annotated portfolios (collections of work with accompanying commentary that makes the underlying reasoning visible). This period also saw the rise of constructive design research, a Scandinavian term that overlaps heavily with RtD, emphasizing the construction of artifacts as the core research activity.
    A key distinction between RtD and its close relative, participatory design, lies in the role of the user. Participatory design, which emerged in the 1970s in Scandinavia, involves users as co-designers in the research process, often with a political commitment to workplace democracy. RtD, while it may involve users, does not require their direct participation. The designer-researcher is the primary agent, and the focus is on the knowledge generated through the design process itself. Similarly, RtD differs from human-centered design (HCD), which dominated the 1980s and 1990s. HCD is a problem-solving methodology that places user needs at the center of the design process, often using iterative testing to refine a solution. RtD, by contrast, is not necessarily about solving a problem; it may be about exploring a question, challenging assumptions, or opening up new possibilities. The goal is not a better product but a better understanding.
    The relationship between RtD and design for social justice, which began to emerge around 2000, is also instructive. Social justice design uses design methods to address systemic inequalities, often working directly with marginalized communities. While RtD can be used for social ends, its primary commitment is to knowledge production, not social change. A social justice designer might use RtD as a tool, but they would measure success by the impact on the community, not by the novelty of the insights. RtD, in its purest form, is agnostic about the application of its findings; it is a mode of inquiry, not a mode of intervention.
    For a newcomer to RtD, the most important thing to understand is that it requires a tolerance for ambiguity. Unlike traditional scientific research, which begins with a hypothesis and tests it, RtD often begins with a hunch, a question, or even just a material fascination. The researcher does not know in advance what they will find. The rigor comes from the systematic documentation of the process—sketches, prototypes, failures, revisions—and from the reflective analysis that turns that messy process into communicable knowledge. The results are often presented not as definitive conclusions but as "intermediate-level knowledge": design patterns, annotated portfolios, or strong concepts that other designers can pick up and use in their own work.
    In practice, RtD is most valuable when the problem is too complex or too novel for existing theories to handle. It is ideal for exploring emerging technologies, new forms of interaction, or social practices that do not yet have established vocabularies. It is less useful for well-understood problems where a standard methodology would be more efficient. The knowledge produced by RtD is often provisional and contextual, but it is precisely this situatedness that gives it power. A prototype that fails in a surprising way can teach more than a successful product that confirms what we already knew.
    To engage with RtD, you do not need a background in philosophy or social science, but you do need a willingness to treat your own design practice as an object of study. You must be willing to document your decisions, to articulate your reasoning, and to expose your work to critique. The prerequisites are not technical but attitudinal: curiosity, humility, and a commitment to reflection. If you can design, you can do research through design—provided you are willing to ask not just "Does this work?" but "What does this work reveal?"
    The 14 concepts its tower teaches
    • Research through Design
    • Modes of Design Research
    • Ill-Structured Problems
    • Reflective Practice
    • Designer-Researcher Role
    • Iterative Design Inquiry
    • Prototypes as Research Instruments
    • Systematic Documentation
    • Knowledge Types in RtD
    • Provisional and Contextual Knowledge
    • Surprising Outcomes as Insights
    • Intermediate-Level Knowledge
    • Evaluation Criteria for RtD
    • Comparison with Related Approaches

    Fly to its tower in Nousfarer

  9. 1996-Present

    Value-Sensitive Design

    How can human values be built into design?

    Fly to its tower in Nousfarer

  10. 1999-Present

    Critical and Speculative Design

    Can designed objects question assumptions and propose alternatives?

    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.

Design Methods MovementWicked problemParticipatory DesignReflective PracticeUser-Centered DesignEthnography in DesignDesign ThinkingResearch through DesignValue-Sensitive DesignCritical and Speculative Design

Beyond the field

Where Design Research's ideas came from in other fields, and what they led to there: the strongest 12 of 50 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 Research is a planet in Nousfarer

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

Land on Design Research

Related fields

Fields its ideas are linked to

More in Design

See where Design Research sits on the Map of Human Knowledge