Since the early 1960s, a small but influential community of designers and researchers has asked a deceptively simple question: can design be turned into a systematic, teachable, or even scientific activity? The answers have been anything but simple. Design methods, as a subfield of design inquiry, is the history of competing frameworks that prescribe how design should be done and who should be involved. At its core lies a persistent tension between rational procedure, democratic participation, user focus, critical provocation, and systemic thinking. Each framework emerged to address a specific problem left unresolved by its predecessors, and many remain in active use today, creating a landscape of pluralism rather than a single settled paradigm.
The first serious attempt to formalize design practice was First-Generation Systematic Design Methods, launched at the 1962 Conference on Design Methods in London. Its proponents—engineers, architects, and operations researchers—argued that design could be made more reliable by breaking it into logical stages: analysis, synthesis, evaluation, and implementation. They borrowed from systems engineering and computer science, treating design as a problem of optimizing a solution within given constraints. The method prescribed checklists, flowcharts, and decision matrices. But by the late 1960s, practitioners found that the approach worked well for well-defined technical problems but collapsed when faced with open-ended social or political ones.
Second-Generation Design Methods (1967–1985) emerged directly from this failure. Led by Horst Rittel and others, the second generation argued that most important design problems are "wicked problems"—ill-defined, value-laden, and resistant to linear decomposition. Instead of prescribing a fixed sequence, second-generation methods treated design as an argumentative process in which stakeholders debate alternative framings. The designer became a facilitator of deliberation rather than a solver of equations. This shift from rational optimization to argumentation was a genuine rupture: it preserved the first generation's interest in method but replaced its epistemology with a social, communicative one. The wicked-problem framing would later feed directly into Participatory Design, Systemic Design, and Transition Design.
While the second generation was rethinking method as argumentation, three other frameworks offered distinct alternatives to rationalism, each with a different emphasis.
Participatory Design (1970–Present) grew out of the Scandinavian labor movement and the Norwegian Iron and Metal Workers' Union's push for workplace democracy. Its core claim was that users should not merely be consulted but should have genuine decision-making power over the systems they use. Participatory Design developed concrete techniques—cooperative prototyping, future workshops, and organizational games—that gave workers a seat at the design table. Unlike the second generation's abstract argumentation, Participatory Design was explicitly political: it redistributed authority. It remains active today, especially in community informatics and public-sector innovation, and it stands in sharp contrast to later user-focused frameworks that treat users as data sources rather than co-deciders.
Pattern Language (1977–Present), introduced by Christopher Alexander and his colleagues, took a different path. Instead of prescribing a process, it offered a library of reusable solutions—patterns—each describing a recurring problem and its core solution in a specific context. The method was architectural, but the idea of a pattern language migrated widely, most famously into software engineering (the "Gang of Four" design patterns). Pattern Language did not reject systematic methods outright; rather, it shifted the unit of analysis from the design procedure to the design outcome, arguing that good design emerges from the cumulative application of proven solutions rather than from a single rational plan.
Reflective Practice (1983–Present), articulated by Donald Schön in The Reflective Practitioner, attacked the very foundation of technical rationality—the idea that professional practice is simply the application of scientific theory to practical problems. Schön argued that designers think in action: they frame problems, experiment, and reflect on their own moves in a continuous loop. Reflective Practice did not produce a prescriptive method; instead, it offered an epistemology of practice that explained why formal methods often fail in the messy, uncertain conditions of real design. Its influence has been profound in design education, where studio pedagogy emphasizes learning-by-doing and critique, but it coexists uneasily with frameworks that still seek systematic procedures.
The 1980s and 1990s saw a consolidation of user-focused approaches, but with very different assumptions about who the user is and what role they play.
User-Centered Design (1986–Present), formalized in Donald Norman and Stephen Draper's User Centered System Design, grounded design in cognitive science. It prescribed iterative cycles of user research, prototyping, and usability testing, treating the user as an empirical subject whose needs, goals, and limitations could be studied and accommodated. User-Centered Design narrowed the scope of design to the interaction between a person and a product, and it succeeded because it offered a clear, testable methodology. But it also reduced the user to a data source: the designer still held authority over the final decision. This put it in tension with Participatory Design, which insisted on shared power rather than mere empathy.
Design Thinking (1987–Present) emerged from the Stanford design school and IDEO as a popularized, simplified version of human-centered methods. It packaged iterative prototyping, multidisciplinary collaboration, and user empathy into a five-stage process (empathize, define, ideate, prototype, test) that could be taught to non-designers. Design Thinking's great achievement was to spread design methods into business, education, and public policy. But its critics argue that it oversimplified the User-Centered Design tradition, stripping away the rigorous empirical testing and replacing it with a generic innovation recipe. Today, Design Thinking remains dominant in practice, while academic design research often distances itself from what it sees as a diluted version of earlier methods.
Computational and Parametric Design (1990–Present) took a different direction entirely. Instead of focusing on users, it focused on form and performance. Using algorithms, scripts, and parametric models, designers could generate and evaluate thousands of design variations automatically. This framework revived the first generation's interest in systematic procedures, but with a crucial difference: the computer, not the designer, executed the procedure. The designer's role shifted to defining rules and constraints, then selecting among generated options. Computational and Parametric Design coexists with human-centered frameworks by operating at a different scale—it excels at optimizing complex geometries and structural systems, but it does not address the social or political dimensions of design.
Beginning in the late 1990s, a set of frameworks challenged the problem-solving orthodoxy that had dominated design methods since the 1960s. These frameworks asked: what if design's purpose is not to solve problems but to provoke, question, or imagine alternatives?
Critical Design (1999–Present), introduced by Anthony Dunne in Hertzian Tales, used design artifacts as a medium for social critique. Instead of producing usable products, Critical Design produced "design fictions"—objects that embodied ethical, political, or technological questions. Its method was speculative making: designers created provocative prototypes and exhibited them in galleries or academic settings. Critical Design deliberately rejected the user-centered imperative to satisfy needs; it aimed to unsettle rather than serve. Its limitation was its audience: it remained largely within art and academic circles, with little influence on mainstream practice.
Speculative Design (2013–Present), developed by Dunne and Fiona Raby in Speculative Everything, extended Critical Design's provocation into the construction of alternative futures. Where Critical Design critiqued the present, Speculative Design built worlds—complete with artifacts, systems, and narratives—that asked "what if?" questions about technology, society, and values. The two frameworks overlap heavily, but Speculative Design is more explicitly about worldbuilding and less about negative critique. Both remain active in design research and education, but they have not displaced problem-solving frameworks in professional practice.
Systemic Design (2012–Present) returned to the wicked-problem tradition of the second generation, but with new tools from complexity science, systems thinking, and service design. It treats design problems as embedded in interconnected social, ecological, and technical systems. Its methods include stakeholder mapping, causal loop diagrams, and multi-level perspective analysis. Systemic Design absorbs the second generation's argumentative approach while adding formal modeling techniques. It is particularly influential in public policy, healthcare, and sustainability transitions.
Transition Design (2015–Present), proposed by Terry Irwin and others, goes further. It argues that contemporary problems—climate change, inequality, biodiversity loss—require not just systemic redesign but a fundamental transition to new societal structures. Transition Design draws on the second generation's wicked-problem framing, Participatory Design's democratic values, and Systemic Design's complexity tools, but adds a long-term temporal perspective: design for transitions that may take decades. It remains the youngest framework, still developing its methods, but it represents the most ambitious attempt to synthesize earlier traditions.
Today, no single framework dominates design methods. Instead, the field is characterized by a division of labor. Design Thinking and User-Centered Design are the most widely practiced in industry, especially in technology and business. Participatory Design remains strong in community development, public services, and research contexts where democratic legitimacy matters. Computational and Parametric Design is the default in architecture and engineering. Critical Design and Speculative Design thrive in academic and artistic settings. Systemic Design and Transition Design are growing in policy and sustainability circles. Pattern Language continues to influence software architecture and urban planning. Reflective Practice underpins design pedagogy but does not prescribe a method.
What the leading frameworks agree on is that design is not a purely technical, value-neutral activity. All reject the first generation's faith in rational optimization. They agree that context, stakeholders, and values matter. Where they disagree is on who should hold authority—the designer, the user, the community, or the system—and on whether design's primary purpose is to solve problems, empower people, provoke thought, or transform society. This pluralism is not a sign of failure; it reflects the richness of the questions design methods set out to answer.