The brief as a problem to be constructed, not a specification to be met

A brief arrives looking like an instruction. It names a client, a setting and an outcome, and invites the designer to supply what the words describe. Reading it that way is the mistake this unit argues against: a brief is an ill-structured problem whose goal, constraints and embedded solutions must be separated and reframed. Problem and solution co-evolve, so a better requirements exercise alone cannot fix them.

Requirements work is not useless. Elicitation narrows a brief without deciding it, because the designer chooses the goal they finally serve during designing. A brief is a structure of tensions to resolve, not a checklist to meet. This is the second of ten units; it hands unit three the brief it leaves standing, to model the work it implies.

The brief is not a specification

Rittel and Webber (1973) supply the originating claim. Problems of social policy, they argue, are wicked: they cannot be definitively described, have no stopping rule, have no objectively correct solution, and every attempt to solve one changes it. Their characteristic example is the freeway, which one cannot build to see how it works and then correct, so there is no cheap trial and no turning back. They contrast these with the tame problems the sciences were built to handle.

Simon (1973) supplies the counterweight. He argues that the boundary between well-structured and ill-structured problems is vague and fluid. An ill-structured problem becomes tractable when a designer represents it as a well-structured one, and then gathers information about that representation. Design is his central example.

Buchanan (1992) carries the argument into design: designers address wicked problems by placement, putting a problem in a particular subject matter so that it can be argued about rather than listed.

Designers move the problem while they solve it

Dorst and Cross (2001) are the direct support for the thesis. Nine experienced industrial designers each worked alone for two and a half hours on the same written brief, a litter disposal system for a new Dutch Railways train, and their problems still moved under their hands though the brief was explicit and shared beforehand. One thread runs through almost every protocol, from newspaper litter to keeping newspapers separate to why they should go into a bin at all, and none could resist it, so the study shows convergence rather than novelty: each understanding of the problem came from an attempt at a solution.

Goel and Pirolli (1992) explain why a brief behaves so differently from a well-defined task. They compared protocol data from architecture, mechanical engineering and instructional design with non-design problem solving and claim a dozen invariant features in the design problem space. Two are extensive structuring before any solving, and evaluation by better or worse rather than right or wrong.

Dorst (2011) names the mechanism. Designers, he argues, reason abductively. They propose a working principle and a value at once, so the frame and the thing arrive together. The distinctiveness of design thinking therefore lies in framing rather than in problem solving. Reframing a brief is not a preliminary to the work. It is the form the work takes.

Elicitation narrows a brief but cannot decide it

The requirements literature is the reply the thesis has to survive. Goguen and Linde (1993) surveyed elicitation techniques, from interviews and questionnaires to the conversation, interaction and discourse analyses that grew out of ethnomethodology and sociolinguistics, and argued the discourse-based methods are more precise because they elicit tacit knowledge by observing what people actually do at work.

Beyer and Holtzblatt (1998) turn observation into a method: in contextual design the designer studies the work in its setting, models it at several levels and designs from the models, so the object of design is the customer's work rather than their stated requirements. Maiden and Rugg (1996) make the choice explicit through ACRE, which generates questions from facets describing each acquisition method's strengths and weaknesses.

Pacheco, Garcia and Reyes (2018) tested which choices work. They reported which techniques are mature and effective, and concluded that the answer depends on the product, the stakeholders and the type of information sought.

Elicitation also assumes a respondent with something to say: Newell and Gregor (2000) argue that designing from a notional average user leaves older and disabled people unserved.

Where the reply stops matters as much as what it achieves. Pohl (1994) separates requirements engineering into three orthogonal dimensions, specification, representation and agreement, measuring completeness, formality and shared understanding, and argues the field's difficulties come from treating a problem in one dimension as though it were in another. Nuseibeh and Easterbrook (2000) list bridging the gap between contextual-enquiry elicitation and formal specification as an open problem.

A good brief resolves misfit in a structure

Alexander (1964) supplies the constructive formulation. A design problem, he argues, should be decomposed into a hierarchy of misfit between form and context, since a good design resolves requirements in a structure rather than a list, and his object of analysis is the requirements and their interrelations. The method is worked through once in full, on a village: the appendix analyses a plan for Bavra, an agricultural village of six hundred people in Gujarat, lists its needs as potential misfit variables and decomposes the network into four groups, cattle and fuel, water and crops, communal life, and private life and shelter.

Contested question: can reframing be specified, or is it a situated practice?

The literature divides on the status of the reframing this unit treats as the first design act. Dorst (2011) and Buchanan (1992) hold that framing is the core of design thinking, can be named and analysed, and so can be taught and transferred. Kimbell (2011) holds the opposite, distinguishing three accounts of design thinking, a cognitive style, a general theory of design and a resource for organisations, and arguing each is undermined by a dualism between thinking and acting, by the diversity of situated practices, and by treating the designer as the only agent in designing.

The requirements tradition sits between the two. Goguen and Linde (1993), Maiden and Rugg (1996) and Pacheco, Garcia and Reyes (2018) hold that a designer can specify a method and choose it deliberately, which sides with Dorst and Buchanan. But Pacheco and colleagues find effectiveness depends on the product, the stakeholders and the information sought, which is Kimbell's point in another vocabulary: what works is what fits. A narrower dispute sits inside the first position. For Simon (1973) the productive move is to represent an ill-structured problem as well-structured. For Rittel and Webber (1973) the representation is where the contested question is quietly settled.

A matched experiment would settle the first disagreement: hold a brief constant, train one group in an explicit framing method and not another, and judge the resulting work blind against needs established independently of both. Kimbell's position predicts the trained frame will not transfer; Dorst's predicts it will. Shin, Polyanskaya, Lucero and Oulasvirta (2025) ran a version of that test, and with 280 designers and blind judging, three LLM reframing approaches produced frames no more novel or useful than working alone, and widened the gap between the more and the less competent. The Simon and Rittel disagreement needs an account of which solutions a given representation admits, collected before the solutions are chosen.

The two sides rest on evidence of different kinds. Dorst argues from protocol cases and Buchanan from a theory of design as argument, so neither measures whether a frame transfers, while Kimbell reviews how a management idea travelled rather than testing teaching. Pacheco, Garcia and Reyes review 140 studies and find the best method depends on the situation. The strongest objection is that the unit cannot tell reframing from guessing: if problem and solution co-evolve, no reading of a brief tells a designer whether a frame is good until the work is built. While the dispute is open, a designer writes the frame down with the value it serves, and tests it on the next attempt at a solution.

Where the argument is heading

Nuseibeh and Easterbrook's (2000) roadmap and Kimbell's (2011) critique point the same way from opposite sides: the roadmap wants a bridge between contextual enquiry and formal specification, and Kimbell argues it was built from the wrong materials, because a general method ignores the situations it serves. Pacheco, Garcia and Reyes (2018) supply the terms on which the argument will be decided, and Shin and colleagues (2025) show a generative tool does not supply that judgement either. What the unit lacks is an account of reframing that says when a brief should be made well-structured, when that would beg the question, and how anyone could tell.

The sources this unit rests on

• Alexander, C. (1964). Notes on the Synthesis of Form. Harvard University Press. https://archive.org/details/notesonsynthesis0000unse Alexander decomposes a design problem into a hierarchy of misfit between form and context, arguing that a good design resolves requirements in a structure rather than a list, and makes their interrelations the object of analysis. That is this unit's formulation for a brief as a structure of tensions.
• Beyer, H. and Holtzblatt, K. (1998). Contextual Design. Morgan Kaufmann. https://archive.org/details/contextualdesign00beye Beyer and Holtzblatt set out contextual design, in which the designer studies the work in its setting, models it at several levels and designs from the models, treating the customer's work rather than their stated requirements as the object of design. It shows what a brief becomes when observed rather than obeyed.
• Buchanan, R. (1992). Wicked problems in design thinking. Design Issues. doi:10.2307/1511637 Buchanan imports the wicked-problem argument into design and argues that design thinking addresses such problems by placement, putting a problem in the context of a particular subject matter, and that design is a liberal art of argument. Placement is the unit's first form of reframing.
• Dorst, K. (2011). The core of design thinking and its application. Design Studies. doi:10.1016/j.destud.2011.07.006 Dorst argues that designers reason by abduction, proposing a working principle and a value at once, and locates the distinctiveness of design thinking in framing rather than in problem solving. His account explains what reframing is.
• Dorst, K. and Cross, N. (2001). Creativity in the design process: co-evolution of problem-solution. Design Studies. doi:10.1016/S0142-694X(01)00009-6 Dorst and Cross ran protocol studies of nine experienced industrial designers working to a written brief. They found that problem and solution co-evolve, each new understanding of the problem emerging from an attempt at a solution, the unit's direct evidence for co-evolution.
• Goel, V. and Pirolli, P. (1992). The structure of design problem spaces. Cognitive Science. doi:10.1207/s15516709cog1603_3 Goel and Pirolli compared protocol data from design tasks in architecture, mechanical engineering and instructional design with non-design problem solving, and claimed invariant features constitutive of a design problem space, including extensive structuring before solving.
• Goguen, J. A. and Linde, C. (1993). Techniques for requirements elicitation. Proceedings of the IEEE International Symposium on Requirements Engineering. doi:10.1109/ISRE.1993.324822 Goguen and Linde surveyed elicitation techniques, from interviews and questionnaires to conversation, interaction and discourse analyses, and argued the discourse-based methods are more precise because they elicit tacit knowledge by observing actual interactions at work. Observing beats asking.
• Kimbell, L. (2011). Rethinking design thinking: part I. Design and Culture. doi:10.2752/175470811X13071166525216 Kimbell reviews how design thinking spread from design research into management and distinguishes three accounts of it: as a cognitive style, as a general theory of design and as a resource for organisations. She argues these accounts ignore situated practices and privilege the designer.
• Maiden, N. A. M. and Rugg, G. (1996). ACRE: selecting methods for requirements acquisition. Software Engineering Journal. doi:10.1049/sej.1996.0024 Maiden and Rugg present ACRE, a framework that generates questions from facets describing the strengths and weaknesses of each requirements acquisition method. They argue no single technique collects everything and a combination must be chosen deliberately.
• Newell, A. F. and Gregor, P. (2000). User sensitive inclusive design: in search of a new paradigm. Proceedings on the 2000 Conference on Universal Usability (CUU). doi:10.1145/355460.355470 They argue that designing from a notional average user leaves older and disabled people unserved.
• Nuseibeh, B. and Easterbrook, S. (2000). Requirements engineering: a roadmap. Proceedings of the Conference on the Future of Software Engineering. doi:10.1145/336512.336523 Nuseibeh and Easterbrook survey requirements engineering and list its open research problems, among them better modelling of problem domains and bridging the gap between contextual-enquiry elicitation and formal specification. The second is stated as open, so the field says the bridge is not yet built.
• Pacheco, C., Garcia, I. and Reyes, M. (2018). Requirements elicitation techniques: a systematic literature review based on the maturity of the techniques. IET Software. doi:10.1049/iet-sen.2017.0144 Pacheco, Garcia and Reyes reviewed 140 studies of requirements elicitation published between 1993 and 2015 and reported which techniques are mature and effective. They found the best choice depends on the product, the stakeholders and the type of information sought.
• Pohl, K. (1994). The three dimensions of requirements engineering: a framework and its applications. Information Systems. doi:10.1016/0306-4379(94)90044-2 Pohl argues that requirements engineering runs along three orthogonal dimensions, the specification, the representation and the agreement, and that the field's difficulties come from treating a problem in one dimension as though it were in another. Gathering requirements is not one task but three.
• Rittel, H. W. J. and Webber, M. M. (1973). Dilemmas in a general theory of planning. Policy Sciences. doi:10.1007/BF01405730 Rittel and Webber argue that social policy problems are wicked: they cannot be definitively described, they have no stopping rule, they have no objectively correct solution, and every attempt to solve one changes it. This is the unit's originating claim that a brief is contested.
• Shin, J., Polyanskaya, A., Lucero, A. and Oulasvirta, A. (2025). No Evidence for LLMs Being Useful in Problem Reframing. Proceedings of the 2025 CHI Conference on Human Factors in Computing Systems. doi:10.1145/3706598.3713273 With 280 designers and blind expert evaluation, three ways of reframing with LLMs produced frames no more novel or useful than a manual baseline, and widened the competence gap.
• Simon, H. A. (1973). The structure of ill structured problems. Artificial Intelligence. doi:10.1016/0004-3702(73)90011-8 Simon argues that the boundary between well-structured and ill-structured problems is vague and fluid, and that an ill-structured problem becomes tractable when represented as a well-structured one, with information then gathered about the representation; design is his example. He is the base of the strongest objection to the thesis.