- Atlas
- Arts & Architecture
- Design Methods
Design Methods
Design methods are the deliberate procedures designers use to move from an unclear need to a workable proposal: how to frame a problem, gather information, generate alternatives, test them, and decide.
10 frameworks, from 1671 to today · Design · Arts & Architecture
- Beaux-Arts Composition 1671-1920
- Systematic Design Methods 1962-1980
- Participatory Design 1970-Present
- Wicked problem 1973-Present
- Pattern Language 1977-Present
- Reflective Practice 1983-Present
- User-Centered Design 1986-Present
- Design Thinking 1991-Present
- Research through Design 1993-Present
- Transition Design 2014-Present
Overview
Design methods are the deliberate procedures designers use to move from an unclear need to a workable proposal: how to frame a problem, gather information, generate alternatives, test them, and decide. The field matters because most design failures are not failures of craft but of method—solving the wrong problem beautifully, or never asking the people who will live with the result. Its history is a long argument about how much of designing can be made explicit, systematic, and shareable, and how much must remain tacit, situated, and reflective.
Beaux-Arts Composition: Method Before "Methods"
The earliest codified design method in the modern West was architectural. From the seventeenth century, the French Académie royale d'architecture and later the École des Beaux-Arts taught composition through a fixed sequence: the analyse of a given program, the parti (a single governing idea or diagram), and the esquisse—a sketch produced under time pressure that locked in the scheme before detailed development. Students learned by copying classical precedents and by competing in the concours.
This was a method in the strong sense: a repeatable procedure with explicit stages, taught through studio criticism rather than textbooks. Its limitation was that it treated the program as given and judged results by compositional convention, not by whether the building served its users. When modern architecture and industry demanded responsiveness to function, materials, and production, that limitation became the opening for everything that followed.
Systematic Design Methods: The 1960s Turn to Procedure
The decisive break came in the 1960s, when engineers, architects, and designers tried to make design as rigorous as science. The immediate context was postwar complexity: large technological systems, mass housing, and the sense that intuitive studio judgment could not cope with problems of that scale.
The founding event is usually dated to the Conference on Design Methods held in London in 1962, organized by J. Christopher Jones and D. G. Thornley, which brought together architects, engineers, and psychologists. Around it clustered a wave of books: Jones's Design Methods (1970), L. Bruce Archer's work at the Royal College of Art on "systematic method," Christopher Alexander's Notes on the Synthesis of Form (1964), and in Germany the Ulm School of Design's curriculum, which under Horst Rittel and others replaced the Bauhaus's craft apprenticeship with operations research, ergonomics, and mathematical planning.
The core idea was decomposition: break a design problem into sub-problems, specify requirements, generate and evaluate alternatives against explicit criteria, and iterate. Alexander's early work tried to compute which requirements conflicted and to cluster them into semi-independent subsystems—a formal procedure for turning a messy brief into a structured one. The Ulm model, influential through its 1950s–60s teaching, insisted that design decisions be justifiable in public, scientific terms.
The movement's own crisis came quickly. In a much-cited 1972 article, "The Design Methods Movement: The First Fifteen Years," Jones himself announced its failure, arguing that systematic procedures had become rigid and had lost the intuitive, participatory qualities of designing. The critique was not that method was wrong but that it had been oversold as a substitute for judgment.
Wicked Problems and the Limits of Systematization
The sharpest statement of the limits came from Horst Rittel, who had moved from Ulm to Berkeley1. With Melvin Webber he published "Dilemmas in a General Theory of Planning" in 1973, introducing the term wicked problem: a problem with no definitive formulation, no stopping rule, no true-or-false test of a solution, and where every attempt to solve it changes the problem. Planning problems, they argued, are wicked by nature, so the search for an optimal solution is misconceived; what is needed is argumentation among stakeholders.
This reframing changed what a design method could claim to do. It shifted attention from optimizing to deliberating—from the designer as solver to the designer as participant in a contested process. It also set the agenda for the participatory and user-centered work that followed.
Pattern Language: Making Tacit Knowledge Explicit
A parallel response to the failure of grand systematization was Christopher Alexander's A Pattern Language (1977, with Sara Ishikawa and Murray Silverstein). Rather than a top-down procedure, Alexander offered a library of 253 named patterns—recurring solutions to recurring problems in buildings and towns, each stated as a context, a problem, and a solution, and linked to larger and smaller patterns.
The pattern "Light on Two Sides of Every Room," for instance, encodes an empirical observation about how people experience rooms, in a form a designer can apply. The method's appeal was that it made design knowledge portable and cumulative without pretending to be a science of optimization. Its influence spread far beyond architecture, into software engineering (where "design patterns" became a standard idiom) and later into interaction design1.
User-Centered Design and the Turn to People
From the 1970s, a different strand grew out of ergonomics, human factors, and computer science. The term user-centered design was popularized by Donald Norman in his 1988 book The Design of Everyday Things (originally The Psychology of Everyday Things), which argued that design should start from how people actually perceive and act—affordances, mapping, feedback, constraints—rather than from how the artifact is built.
The method that made this operational was contextual inquiry and its relatives, developed at Xerox PARC and elsewhere in the late 1980s: designers observed users in their own settings and modeled their work before proposing systems. This was a real methodological shift—from asking people what they want to watching what they do. It fed directly into the iterative, prototype-and-test cycles that became standard in software and product design, and into the ISO 9241-210 standard for human-centred design, first issued in 1999.
Participatory Design: The Scandinavian Challenge
A distinct and politically sharper tradition emerged in Scandinavia in the 1970s and 1980s. The "collective resource approach" of Kristen Nygaard and others in Norway, and the DEMOS project in Sweden (late 1970s), insisted that workers whose jobs would be reshaped by computer systems should help design those systems. The method was not consultation but co-design: workers and designers as equal partners, often using mock-ups and prototypes as boundary objects for negotiation.
The tradition's landmark statement is the 1990 collection Participatory Design: Principles and Practices, edited by Douglas Schuler and Aki Namioka, and the biennial Participatory Design Conference, held since 1990. Its claim—that design is a political act and that those affected have a right to shape it—remains the main alternative to expert-led user-centered design, and it has since spread into public-sector and community design worldwide.
Reflective Practice: The Practitioner's Counterargument
In 1983 Donald Schön published The Reflective Practitioner, a study of how professionals in architecture, engineering, and psychotherapy actually work. His central concept was reflection-in-action: the practitioner conducts a "conversation with the situation," framing and reframing the problem as the work proceeds, rather than applying a pre-set procedure.
Schön's target was precisely the technical-rational model that the systematic methods movement had embodied. His account gave academic legitimacy to studio teaching and to the tacit knowledge that methods had tried to formalize. It became foundational for design education and for the later argument that design knowledge is best produced through making.
Research through Design: Knowing by Making
The 1990s and 2000s turned Schön's insight into a research program. Research through design holds that designing—building prototypes, artifacts, and interventions—is itself a mode of inquiry that produces knowledge, not merely an application of knowledge produced elsewhere. The term gained currency through the work of Christopher Frayling, whose 1993 essay "Research in Art and Design" distinguished research into, through, and for art and design, and through the Design Research Society and the journal Design Issues.
A concrete case is the annotated portfolio, developed by Bill Gaver and John Bowers in the early 2010s: a collection of designed artifacts presented together with documentation of the judgments and decisions behind them, so that the knowledge embodied in the making can be shared and contested. The approach remains contested—critics ask how such knowledge is validated—but it has become a standard route for practice-based doctorates and for design research in universities.
Design Thinking: Method for Non-Designers
The most widely circulated descendant of the methods movement is design thinking. The phrase was used earlier, but its popular form came from IDEO and the Stanford d.school in the 1990s and 2000s, codified in Tim Brown's Change by Design (2009) and in the five-stage model—empathize, define, ideate, prototype, test—taught in workshops worldwide.
Its claim was that the designer's approach could be transferred to managers, educators, and public servants facing ill-defined problems. It drew directly on the user-centered and iterative strands above, and on the wicked-problems literature, while stripping away the political edge of participatory design. It has been enormously influential and heavily criticized: for reducing method to a checklist, for promising innovation without evidence, and for treating empathy as a stage rather than a relationship. Both the adoption and the critique are part of its history.
Transition Design and the Present
The most recent strand, transition design, was articulated by Terry Irwin, Cameron Tonkinwise, and Gideon Kossoff at Carnegie Mellon from around 2014. It argues that design methods must operate at the scale of long-term societal transitions—climate, resource depletion, inequality—and therefore must combine systems thinking, stakeholder co-design, and a temporal horizon of decades. It explicitly inherits from both the wicked-problems tradition and participatory design, and it treats the designer as a facilitator of change in complex social systems rather than as a solver of discrete problems.
Today the field is plural. Systematic, requirement-driven methods persist in engineering and regulated industries; user-centered and iterative prototyping is the default in software and product design; participatory and co-design methods are standard in public services and community work; research through design anchors academic practice; and design thinking remains the dominant bridge to management and education. The open questions are the ones the history keeps returning to: how to validate knowledge made through making, how to make methods genuinely participatory rather than consultative, and whether any procedure can be adequate to problems that are, in Rittel's sense, wicked.
References
- Design methods (Background, Influence on all professional design practice), Wikipedia
The frameworks of Design Methods
Each framework is a way of working the field has used: when it held, and the question it answers.
- 1671-1920
- 1962-1980
- 1970-Present
Participatory Design
About Participatory Design
Participatory design (PD) emerged in the 1970s as a direct response to the limitations of expert-driven design methods. While second-generation design methods had already recognized that design problems are "wicked" and require argumentation among stakeholders, PD went further by insisting that those stakeholders—especially end users—must be active co-designers, not merely consulted. This shift was both political and methodological: it aimed to empower workers and citizens by giving them genuine influence over the technologies and environments that shape their lives. In design methods, PD stands apart from user-centered design (which studies users but keeps design authority with professionals) and from earlier systematic methods (which treated design as a rational optimization process). Instead, PD treats design as a collaborative, situated, and democratic practice.The core curriculum for participatory design in design methods begins with the foundational principle of democratic participation: all affected parties have a right to shape the design outcome. This leads to stakeholder involvement as a non-negotiable requirement, not an optional extra. The collective resource approach, developed in Scandinavian trade union projects, provides a concrete strategy: workers collectively decide on design goals and methods, supported by researchers and designers. Mutual learning is the key process—designers learn about users' work practices and contexts, while users learn about technical possibilities and design trade-offs. Co-design (or cooperative design) refers to the joint creative activity where users and designers generate ideas, sketch solutions, and build prototypes together. Design by doing emphasizes hands-on experimentation with low-fidelity prototypes in the actual work setting, rather than abstract specifications. Prototyping in context means testing designs in real use situations, often through mock-ups or early versions, to uncover tacit knowledge and unforeseen issues. Action research provides the methodological framework: PD projects are iterative cycles of planning, action, observation, and reflection, with researchers acting as facilitators. Socio-technical design reminds us that technical systems and social systems must be designed jointly, not separately. User empowerment is both a goal and a criterion: successful PD increases users' control over their tools and work environment. Finally, situated design acknowledges that design solutions are always embedded in specific local practices and cannot be transferred wholesale.These concepts are not taught as a rigid sequence but as an integrated set of commitments and techniques. A typical first course might start with the political and ethical rationale, then introduce the collective resource approach through historical case studies (e.g., the Norwegian Iron and Metal Workers Union project), then practice co-design workshops and prototyping exercises, and finally reflect on the challenges of scaling participation and maintaining genuine influence.Intellectual history: Participatory design's roots lie in the social movements of the 1960s and 1970s, particularly in Scandinavia where strong trade unions and a social democratic tradition created fertile ground. The Norwegian Iron and Metal Workers Union (NJMF) project, begun in 1971, was a landmark: researchers Kristen Nygaard and Olav Terje Bergo worked directly with union members to develop computer systems that supported workers' interests, not just management's. This project pioneered the collective resource approach, where the union itself controlled the research agenda. In Sweden, the UTOPIA project (1981-1985) extended these ideas to graphic workers, developing a text and image processing system through intensive co-design. Key figures include Pelle Ehn, who codified PD's principles in his 1988 book "Work-Oriented Design of Computer Artifacts"; Morten Kyng, who emphasized cooperative prototyping; and Susanne Bødker, who developed the concept of "design in use." The 1990s saw PD spread beyond Scandinavia to software engineering, architecture, and product design, with the 1993 anthology "Participatory Design: Principles and Practices" (edited by Schuler and Namioka) serving as a key codifier. PD coexisted with and influenced later frameworks: Pattern Language (Christopher Alexander) shared the goal of user participation but offered a different tool (pattern languages); User-Centered Design absorbed some PD techniques but often without the political commitment; and more recently, Co-Design has become a broader term encompassing many participatory practices. PD's legacy in design methods is the enduring insistence that design is not a solitary expert activity but a democratic, collaborative process that must include those who will live with the results.The 11 concepts its tower teaches
- Action Research
- Co-Design
- Collective Resource Approach
- Democratic Participation
- Design by Doing
- Mutual Learning
- Prototyping in Context
- Situated Design
- Socio-Technical Design
- Stakeholder Involvement
- User Empowerment
- 1973-Present
- 1977-Present
- 1983-Present
Reflective Practice
About Reflective Practice
In the early 1980s, design methods were dominated by two competing visions: the rational, step-by-step procedures of first-generation systematic methods and the argumentative, stakeholder-driven processes of second-generation methods. Both treated design as a problem-solving activity, but neither fully captured the intuitive, improvisational skill that experienced designers actually displayed. Reflective Practice, introduced by Donald Schön in his 1983 book The Reflective Practitioner, offered a third path. It argued that professional practice—especially in design—is not the application of pre-existing knowledge to well-defined problems, but a continuous, reflective conversation with a unique and uncertain situation. The designer does not simply solve problems; they frame them, reframe them, and learn through action. This framework shifted the focus from method as a prescribed sequence to method as a mode of inquiry grounded in reflection.At the heart of Reflective Practice lies a set of interconnected concepts that form the core curriculum for understanding design as a reflective process. These concepts are best taught as clusters that build on each other:- Knowing-in-action and Tacit Knowledge: the spontaneous, skillful performance that professionals exhibit without conscious deliberation—the know-how that is embedded in action itself.
- Reflection-in-action and Reflection-on-action: the process of thinking about what we are doing while we are doing it (reflection-in-action), and the retrospective analysis after the event (reflection-on-action). These are the mechanisms by which practitioners learn from experience.
- Problem Setting and Framing: the act of defining what the problem is, rather than accepting a given problem statement. Designers frame the situation by selecting what to attend to and what to ignore, and this framing shapes the entire design process.
- Reflective Conversation with the Situation: the back-and-forth dialogue between the practitioner and the materials of the situation. For example, an architect sketches a line, sees how it changes the composition, and responds with another line—a conversation that reveals new possibilities.
- Artistry of Practice: the creative, intuitive dimension of professional work that cannot be reduced to rules or formulas. It is the hallmark of expert practitioners.
- Design as a Reflective Process: the overarching view that design is fundamentally a reflective activity, not merely a technical or rational one.
- Theory in Practice and Learning from Experience: the idea that practitioners develop and refine their own theories through reflection on their actions, and that this learning is essential for professional growth.
- Schön's Critique of Technical Rationality: the rejection of the dominant view that professional practice is simply the application of scientific theory to practical problems. Technical rationality, Schön argued, fails to account for the messy, uncertain, and value-laden nature of real-world practice.
These concepts together provide a vocabulary for understanding how designers think and learn in action. They emphasize that reflection is not a separate step after design, but an integral part of the design process itself.The intellectual history of Reflective Practice in design methods is anchored by Donald Schön (1930–1997), a philosopher and urban planner who drew on earlier work in experiential learning and organizational behavior. Precursors include John Dewey's emphasis on experience and reflection, Kurt Lewin's action research cycle, and Jean Piaget's cognitive development theory. Immanuel Kant's notion of reflective judgment also provides a philosophical backdrop. However, Schön's 1983 book The Reflective Practitioner is the seminal work that brought these ideas into design methods. He followed it with Educating the Reflective Practitioner (1987), which applied the framework to professional education. Schön's work emerged in the wake of second-generation design methods' focus on wicked problems and argumentation, but it offered a different emphasis: instead of prescribing how to deliberate among stakeholders, it described how individual practitioners actually think and improvise. The framework coexisted with and influenced later approaches such as User-Centered Design and Design Thinking, which adopted its emphasis on iteration and learning from experience. In design education, Reflective Practice became a cornerstone for studio-based learning, where students learn by doing and reflecting on their work. Its legacy is a lasting recognition that design expertise is not just technical skill but a form of artistry cultivated through reflection.The 13 concepts its tower teaches
- Artistry of Practice
- Design as a Reflective Process
- Framing
- Knowing-in-action
- Learning from Experience
- Problem Setting
- Reflection-in-action
- Reflection-on-action
- Reflective Conversation with the Situation
- Reflective Practitioner
- Schön's Critique of Technical Rationality
- Tacit Knowledge
- Theory in Practice
- 1986-Present
- 1991-Present
Design Thinking
About Design Thinking
Design thinking emerged in the 1980s as a distinctive approach to understanding and teaching how designers reason when they engage with open-ended, ill-defined problems. Unlike earlier design methods that prescribed step-by-step procedures or focused on user participation, design thinking treats the designer's cognitive style—their characteristic ways of framing problems, generating solutions, and iterating between the two—as a transferable skill that can be studied, practiced, and applied beyond traditional design disciplines. At its core, design thinking asks: what is the nature of design reasoning, and how can it be cultivated as a disciplined, creative practice?Core CurriculumA first course in design thinking typically introduces the following concepts in a logical progression:- Designerly ways of knowing – The idea that designers possess a distinct form of knowledge and reasoning, different from scientific or artistic modes, characterized by working with incomplete information and pursuing multiple possible solutions.
- Problem framing and reframing – The process of defining and redefining the design problem itself, recognizing that how a problem is framed determines what solutions are possible.
- Abductive reasoning – A mode of logical inference that moves from observed facts to plausible explanations or design proposals, central to generating novel solutions.
- Iteration and prototyping – The cyclical process of making ideas tangible through sketches, models, or simulations, testing them, and refining them based on feedback.
- Divergent and convergent thinking – Alternating between expanding the range of possibilities (divergence) and narrowing down to the most promising options (convergence).
- Empathy and user perspective – Understanding the needs, experiences, and contexts of the people for whom one is designing, often through ethnographic methods.
- Visual thinking and sketching – Using drawings, diagrams, and other visual representations as tools for thinking and communicating design ideas.
- Reflection-in-action – The capacity to think about what one is doing while doing it, adjusting strategies in real time based on emerging insights.
- Tolerance for ambiguity – The ability to work productively in situations where goals, constraints, or criteria are unclear or shifting.
- Solution-focused problem-solving – A tendency to generate and test potential solutions early, rather than exhaustively analyzing the problem first.
- Integrative thinking – The ability to hold multiple, sometimes conflicting, perspectives or constraints in mind and synthesize them into a coherent design.
- Design judgment – The cultivated ability to make qualitative decisions about what is appropriate, elegant, or effective in a given design situation.
Intellectual HistoryDesign thinking as a named concept crystallized in the 1980s, drawing on earlier work in design methods and creativity research. The term itself appears in L. Bruce Archer's 1963–64 article series "Systematic Method for Designers," where he called for incorporating knowledge from ergonomics, cybernetics, and management science into "design thinking." However, the framework's local dominance in design methods began with the publication of two key works: Peter Rowe's Design Thinking (1987), which analyzed how architects and urban designers actually reason, and Donald Schön's The Reflective Practitioner (1983), which introduced the concept of reflection-in-action as the core of professional design expertise.Key figures include Donald Schön (1930–1997), whose work on reflective practice provided a philosophical foundation for design thinking as a form of knowing-in-action; Peter Rowe (born 1947), who systematically described design thinking as a cognitive style; and Nigel Cross (born 1942), who synthesized research on designerly ways of knowing and argued for design as a third culture alongside science and the humanities. Cross's Designerly Ways of Knowing (1982) and later Design Thinking (2011) became canonical textbooks.Seminal works include Schön's The Reflective Practitioner (1983), Rowe's Design Thinking (1987), and Cross's Designerly Ways of Knowing (1982, expanded 2006). These texts established the core curriculum: they shifted attention from prescriptive methods to descriptive accounts of design cognition, and they argued that design thinking is a fundamental human capability that can be systematically developed.Relations to other frameworks: Design thinking coexisted with and partly absorbed User-Centered Design (1986 onward), sharing its emphasis on empathy and user research. It contrasted with the rationalist procedures of First- and Second-Generation Design Methods, which focused on logical decomposition and argumentation rather than cognitive style. Later, Computational and Parametric Design (1990 onward) would challenge design thinking's human-centered emphasis by foregrounding algorithmic generation and data-driven optimization. Design thinking also influenced and was influenced by Reflective Practice, which provided its epistemological grounding.Legacy: Design thinking became widely popularized in business and innovation contexts from the 1990s onward, particularly through the work of the design consultancy IDEO and the Stanford d.school. This popularization has been criticized for oversimplifying design skills, depoliticizing managerial practice, and overstating the transferability of design thinking to complex social problems. Within design methods, however, design thinking remains a vital framework for understanding how designers think and for teaching design reasoning as a disciplined, creative practice.The 12 concepts its tower teaches
- Abductive reasoning
- Design judgment
- Designerly ways of knowing
- Divergent and convergent thinking
- Empathy and user perspective
- Integrative thinking
- Iteration and prototyping
- Problem framing and reframing
- Reflection-in-action
- Solution-focused problem-solving
- Tolerance for ambiguity
- Visual thinking and sketching
- 1993-Present
- 2014-Present
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.
Wicked problem reacted against Systematic Design Methods
The rigid, optimization-focused procedures of systematic design were directly challenged by the concept of wicked problems, which argued that many real-world issues defy such systematic solutions.
Carried by Rittel; Webber.
Research through Design grew out of Reflective Practice
The philosophical premise that professional practice involves ongoing, situated inquiry, as articulated by Schön, was formalized into the research methodology of designing as inquiry.
Carried by Christopher Frayling.
Design Thinking influenced by User-Centered Design
User-Centered Design's focus on understanding user needs and iterating based on human interaction provided a critical empirical foundation for the broader Design Thinking methodology.
Carried by Donald Norman.
Reflective Practice reacted against Systematic Design Methods
Reflective Practice arose as a critique of the overly prescriptive, mechanistic nature of the systematic design methods that sought to replace professional judgment with procedure.
Carried by Donald Schön.
Beyond the field
Where Design Methods's ideas came from in other fields, and what they led to there: the strongest 12 of 58 links.
Systematic Design Methods provoked Reflective Practice in Design And Artifacts
Schön's reflective practice was formulated as a critique of the systematic design methods of the 1960s, arguing that professional practice rests on tacit artistry rather than technical rationality.
Carried by Donald Schön; The Reflective Practitioner (1983).
Systematic Design Methods provoked Reflective Practice in Design Research
Schön explicitly criticized systematic design methods and the attempt to reduce design to rule-following procedures, defining reflective practice against that programme.
Carried by Donald Schön.
Wicked problem reacted against Rational planning model in Planning Governance And Participation
The wicked problem concept was framed as a rejection of the rational planning model in planning theory and governance, arguing its assumptions fail for open social problems.
Carried by Horst Rittel; Melvin Webber.
Wicked problem reacted against Rational planning model in Planning Theory
Rittel and Webber formulated the idea of wicked problems explicitly as an attack on the rational planning model and its assumption that planning problems are well-defined and solvable by systematic analysis.
Carried by Horst Rittel; Melvin Webber.
Pattern Language influenced Pattern Languages of Programs in Design Patterns
The Pattern Languages of Programs conferences were founded explicitly on Christopher Alexander's pattern language concept, adopting his format of context, problem and forces for software design patterns. The PLoP series and its proceedings carried Alexander's idea into programming.
Carried by Christopher Alexander; PLoP.
Pattern Language influenced Pattern Language in Design Patterns
The software design patterns movement, launched by the Gang of Four and earlier by Kent Beck and Ward Cunningham, explicitly took Christopher Alexander's pattern language format of context-problem-solution as its model.
Carried by Christopher Alexander; Erich Gamma; Design Patterns (1994).
Pattern Language influenced Gang of Four Object-Oriented Design Patterns in Design Patterns
The Gang of Four explicitly credited Christopher Alexander's pattern language as the model for their catalogue of object-oriented design patterns, adopting the form of named context-problem-solution entries. Their book's introduction cites Alexander directly as the source of the pattern idea.
Carried by Erich Gamma; Richard Helm; Design Patterns (1994).
Pattern Language influenced Idioms and Framework-Absorbed Patterns in Design Patterns
Software idioms and absorbed patterns inherit the Alexandrian pattern-language idea that recurring solutions can be named, described by forces, and composed. The pattern form used in software pattern catalogues descends directly from Alexander's pattern language.
Carried by Christopher Alexander; A Pattern Language (1977).
Pattern Language influenced Enterprise Application Architecture Patterns in Design Patterns
Fowler's enterprise patterns book follows the Alexandrian pattern-language form: named problem, context, forces, solution, popularised for software by the GoF and the Portland pattern community. The catalogue format and the idea of composing patterns into a language came from Alexander's pattern language.
Carried by Christopher Alexander; A Pattern Language (1977); Martin Fowler.
Reflective Practice influenced Reflective Design in Critical Hci
The reflective design framework draws directly on Schön's reflective practice as developed in design methods, using reflection-in-action as its core concept.
Carried by Donald Schön.
Reflective Practice reacted against Design methods in Design And Artifacts
Reflective practice was developed as a direct attack on the systematic design methods tradition, which Schön criticized for separating technical rationality from the artistry of practice.
Carried by Donald Schön.
Reflective Practice reacted against Design Methods Movement in Design Research
Schön's reflective practice was framed as a critique of the design methods movement's technical-rational model, arguing that competent practitioners work through reflection-in-action rather than applying explicit procedures.
Carried by Donald Schön; The Reflective Practitioner (1983).

Design Methods 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 MethodsRelated fields
Fields its ideas are linked to
- Design Research 11 links
- Design Patterns 7 links
- Product Design Theory 4 links
- Design And Artifacts 4 links
- Interaction Design 3 links
- Digital Design Theory 2 links
- Environmental Design 2 links
- Design 2 links
- Industrial Design 2 links
- Interaction Design Theory 2 links
- Critical Hci 2 links
- Human Computer Interaction 2 links