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

A client rarely arrives with a question. They arrive with a request and a situation. Sign-ups are too low, the team has three months, and someone has already decided the answer is a redesign. The document that follows is a proposed solution dressed as a problem statement. Treating it as a specification to be met is a reliable way for capable work to end up beside the point.

This third of ten units, after the second read the setting, argues that a professional's first act is to turn the brief into a question a study or a design can actually answer. The claim is not that practitioners should be difficult with clients. The literature comes from two traditions that seldom cite each other, design cognition and professional reflection.

The problem is framed before it is solved

Schon (1983) gave the argument its canonical form. He studied how engineers, architects, managers and psychotherapists actually work. From those studies he argued that competent practitioners treat a situation as a unique case, to be framed and reframed in conversation with its materials. The practitioner sets the problem. Rival framings of one situation yield rival problems and rival acceptable answers.

Goel and Pirolli (1992) supplied empirical support from protocol studies. They compared design tasks in architecture, mechanical engineering and instructional design with non-design problem solving. They found that designers structure design problem spaces, and that those spaces share invariant features across disciplines. That presents design as a radial category of problem solving. Lawson (1990) described the habit from the practitioner's side. Designers move towards solutions early, using precedent and a solution-focused strategy. They do so as a way of understanding the problem, not as a failure to analyse it first.

Problem and solution move together

If the problem is constructed, the construction does not happen first. Dorst and Cross (2001) analysed design activity and found the problem space and the solution space co-evolve. Understanding the problem and proposing solutions advance together. Lloyd and Scott (1994) analysed protocols from experienced engineering designers. They found that designers with specific experience of the problem type approached the task through solution conjectures rather than problem analysis, framing the problem in terms of relevant solutions. The problem the designer works on is the structure imposed on the brief, not the brief as written.

Visser (2006) generalised the finding, arguing from cognitively oriented studies of real design work. Designers construct increasingly specific representations of both problem and solution, opportunistically and in a moving order. That runs against models that assume a fixed decomposition. Restrepo and Christiaans (2004) add the information side. Information needs are triggered by the emerging structure of the problem, so the frame settles what to read, ask and measure as it develops. Scoping cannot be fixed in advance without cutting off the work that comes next.

Reframing is a practice, not a failure to listen

The obvious objection is that reframing is a euphemism for ignoring the client. Paton and Dorst (2011) studied how practising designers handle a brief. They described briefing and reframing as a situated practice, in which the designer works the tension between the client's stated need and the designer's own framing. A brief should be answered with an open proposal to reframe, not a silent substitution of the designer's problem for the client's.

Paton and Dorst's interviews show the moves. Fifteen experienced visual communications designers were asked how briefing worked on a project they judged typical and on one they judged innovative. The innovative projects turned on whether the brief could be reframed during briefing at all. The designers described three ways of loosening a client's frame. They argued from an analogy, engaged with the context the client worked in, and put a conjecture to the client to read the reaction. The designer then reflected the new frame back and checked that it was shared. The sample is fifteen self-reporting professionals, so the paper records what they say they do. The three moves are a repertoire rather than a validated method.

Buxton (2007) supplies the reason to argue early. His account of sketching distinguishes the sketch from the prototype. He argues the profession's greatest risk is working on the wrong design well. Getting the right design precedes getting the design right. A brief accepted without question commits the project to the client's framing at the point where the framing is cheapest to change.

The method carries a client the client never met

Reframing is constrained by the methods a practitioner brings. Goguen and Linde (1993) surveyed and evaluated requirements elicitation techniques, from introspection and interviews to discourse analysis. They argued elicitation is a social process, in which each technique foregrounds a different aspect of the setting and hides others. The choice of technique is therefore already a partial framing.

Potts (1995) made the sharper version for off-the-shelf software. Requirements engineering had been shaped by funding for bespoke, contract-built systems. Assumptions inherited from that work break down when a product is sold to unknown users. The methods can encode the wrong kind of client, inventing requirements and imagining customers who are not the real users: typically able-bodied, of working age and reading in English.

My aim is to provoke and stimulate thought, not to propose a developed solution.

Potts wrote that of his own paper, and it describes the position well. A practitioner who applies an inherited method without asking whom it was built to serve repeats the brief's assumptions rather than testing them.

The brief is now an object to contest, and the frame an object to measure

Recent work treats the brief itself as an object worth contesting. Paez and Auger (2026) draw on a speculative-design teaching project. They argue that the conventional brief reproduces existing norms and a solutionist mindset, arriving already narrowed to what the commissioning organisation expects. They propose reframing it as an infrastructure for holding several framings open.

The newest contribution tries to make reframing computationally explicit. Casakin, Goldstein and Gero (2026) build a model of framing and reframing from constructive and situated memory theories. The model represents frames as activations that rise and decay. They apply it to architecture students' design sessions. They report that framing peaks during exploration and declines as solutions stabilise. Semantic diversity expands, then narrows. Reframing is thus a memory-driven and measurable process. Measurability is what would make it teachable rather than a matter of talent.

That connects to method as well as to cognition. Blandford, Furniss and Makri (2016) set out how qualitative methods are used in HCI. They argue rigour lies in matching method to question and in making the analytic process visible. If the frame produces the question, the professional's discipline is to hold the frame still long enough to answer it. It is also to show how the frame was chosen.

Contested question: should the brief be accepted, reframed or resisted?

The literature agrees the problem is not simply given and disagrees about what to do with that fact. One position reframes within the commission. Schon (1983) frames a situation the client still owns. Paton and Dorst (2011) treat reframing as a situated negotiation rather than a takeover. Dorst and Cross (2001) describe co-evolution, in which the client's problem and the designer's solution develop together.

A second position holds that the brief should be resisted. Paez and Auger (2026) argue the conventional brief perpetuates norms and solutionism and should be replaced by one holding several framings open. The risk, which their own account names, is that a resistant reframing substitutes the practitioner's agenda for the client's and the users'.

A third position denies that the choice is free. Goel and Pirolli (1992) find invariant features in design problem spaces. That suggests the construction is bounded by the task environment rather than freely chosen. Visser (2006) argues against models that assume a fixed decomposition at all. Lawson (1990) adds that early solution moves are a habit that can close the frame before it is understood.

What would settle the disagreement is comparative evidence the literature does not contain. The existing work is case-based, resting on single projects or small sets of sessions, as in Lloyd and Scott (1994) and Casakin et al. (2026). A study would separate the positions, if it took comparable briefs, had one team accept and one reframe, and measured both against the client's stated goal and the users' needs. Until then, reframing is legitimate and its justification is owed to the client rather than asserted.

The evidence is thin on all three sides. The reframe-within-the-commission and resist positions rest on single cases and teaching projects, as in Paton and Dorst and Paez and Auger; the bounded position rests on protocol studies such as Goel and Pirolli. None compares outcomes against a client's own goal. While the dispute is open, a designer should put a reframing to the client as a proposal and record why the frame was chosen. The strongest objection is that reframing serves the designer: recasting the brief can substitute an interesting problem for the client's real one and call it professionalism.

Where the argument is heading

The direction of travel is towards making framing an explicit and inspectable object. Casakin et al. (2026) model it. Blandford et al. (2016) tie method choice to it. Paez and Auger (2026) turn disagreement about the brief into a design method. Visser (2006) frames design as the construction of representations. The defence of a reframing will rest less on experience and more on a recorded trail of how the frame was chosen.

The sources this unit rests on

• Blandford, A., Furniss, D. and Makri, S. (2016). Qualitative HCI Research. Synthesis Lectures on Human-Centred Informatics. doi:10.1007/978-3-031-02217-3 Sets out how qualitative methods are used in HCI, covering study design, data collection, analysis and reporting. Argues rigour lies in matching method to question.
• Buxton, B. (2007). Sketching User Experiences: Getting the Design Right and the Right Design. San Francisco: Morgan Kaufmann. https://archive.org/details/sketchinguserexp0000buxt Distinguishes the sketch from the prototype and argues the profession's greatest risk is working on the wrong design well. Places sketch and evaluation as instruments for getting the right design before getting the design right.
• Casakin, H., Goldstein, A. and Gero, J. S. (2026). Framing and reframing in design: the use of an NLP-based memory model. Proceedings of the Design Society. doi:10.1017/pds.2026.10456 Builds a memory-based model of framing and reframing and applies it to architecture students' design sessions. Finds framing peaks during exploration and declines as solutions stabilise.
• 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 Ran protocol studies with nine experienced industrial designers whose designs were rated for quality and creativity. The observations refined a co-evolution model in which problem and solution spaces develop together.
• Goel, V. and Pirolli, P. (1992). The structure of Design Problem Spaces. Cognitive Science. doi:10.1207/s15516709cog1603_3 Reports protocol studies of design tasks in three professions compared with non-design problem solving. Finds design problem spaces structured by the designer and sharing invariant features across disciplines, so the problem is constituted by the designer's work on an ill-defined task.
• Goguen, J. A. and Linde, C. (1993). Techniques for requirements elicitation. Proceedings of the IEEE International Symposium on Requirements Engineering (RE 1993). doi:10.1109/isre.1993.324822 Surveys and evaluates requirements elicitation techniques, including introspection, interviews and discourse analysis, with attention to social issues. Argues elicitation is a social process each technique foregrounds differently.
• Lawson, B. (1990). How Designers Think: The Design Process Demystified. Oxford: Architectural Press. https://archive.org/details/howdesignersthin0000laws Examines how designers think, contrasting design problems with puzzles and describing solution-focused strategies and the use of precedent. Argues designers move to solutions as a way of understanding the problem, a professional strategy rather than a shortcut.
• Lloyd, P. and Scott, P. (1994). Discovering the design problem. Design Studies. doi:10.1016/0142-694x(94)90020-5 Applied a discipline-independent cognitive framework to protocol studies of engineering designers. Found that designers with specific experience of the problem type approached the task through solution conjectures rather than problem analysis, framing the problem in terms of relevant solutions.
• Paez, R. and Auger, J. (2026). Against the Given: Reframing the Brief for Transformative Design Practices. Proceedings of DRS. doi:10.21606/drs.2026.1837 Uses a speculative-design teaching project to argue the conventional brief perpetuates existing norms and a solutionist mindset. Proposes reframing the brief as a device for holding several framings open.
• Paton, B. and Dorst, K. (2011). Briefing and reframing: A situated practice. Design Studies. doi:10.1016/j.destud.2011.07.002 Interviewed fifteen experienced visual communications designers about briefing for typical and innovative projects. Found that designers elicit the client's frame, reframe it to be more workable and reflect it back, making reframing during briefing a negotiated practice.
• Potts, C. (1995). Invented requirements and imagined customers: requirements engineering for off-the-shelf software. Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95). doi:10.1109/isre.1995.512553 Argues requirements engineering was shaped by bespoke-contract funding and therefore serves off-the-shelf product developers poorly, inventing requirements and imagining customers who are not the real users.
• Restrepo, J. and Christiaans, H. (2004). Problem Structuring and Information Access in Design. Journal of Design Research. doi:10.1504/jdr.2004.009842 Studied what triggers designers' information seeking, proposing a model of problem structuring and information access. Argues information needs arise from the emerging structure of the problem, so framing includes deciding what to read and ask.
• Schon, D. A. (1983). The Reflective Practitioner: How Professionals Think in Action. New York: Basic Books. https://archive.org/details/reflectivepracti00scho Argues that competent professionals work by reflection in action, treating a situation as a unique case to be framed and reframed through dialogue with it rather than by applying rules to a well-formed problem.
• Visser, W. (1990). More or less following a plan during design: opportunistic deviations in specification. International Journal of Man-Machine Studies. doi:10.1016/s0020-7373(05)80119-1 Observed one engineer defining functional specifications for an automated machine tool and found the activity organised opportunistically, the plan followed only while cognitively economical. The primary study behind the review claim that design reasoning is opportunistic.
• Visser, W. (2006). Designing as Construction of Representations: A Dynamic Viewpoint in Cognitive Design Research. Human-Computer Interaction. doi:10.1207/s15327051hci2101_4 Reviews cognitively oriented studies of real design work and argues designers construct increasingly specific representations of both the problem and the solution, opportunistically and dynamically, against models that assume a fixed decomposition.