From briefing to client requirements processing

Kamara, J M; Anumba, C J and Hobbs, B (1999) From briefing to client requirements processing. In: Hughes, W (ed.) Proceedings of 15th Annual ARCOM Conference, 15-17 September 1999, Liverpool, UK.

Abstract

The briefing process in construction, which is used to communicate client objectives for a project, is an evolutionary process where design is used to clarify client requirements. This approach implies that a solution is formulated from a hazy understanding of client requirements, and therefore has the potential of shifting focus from the client to the preferences of the designer(s). However, to ensure that construction is more client-oriented, there should be rigorous processing of client requirements before the start of conceptual design. This should be done through a structured framework which provides for the definition, analysis and translation of client requirements into design specifications that are solution neutral. This paper describes how this can be done through a Client Requirements Processing Model which is based on Quality Function Deployment, a technique used in manufacturing to translate customer requirements into appropriate product features. Client requirements processing enables a better understanding of client requirements, facilitates design innovation, and enhances the success of integrated procurement strategies (e.g. design and build) which require clear and unambiguous briefs as a very early stage. It also provides a necessary first step for ultimate client satisfaction through the effective encapsulation of client requirements in the design and construction process.

Item Type: Conference Paper (Paper)
Uncontrolled Keywords: briefing; client; construction; processing; requirements
Index terms: design specification, client requirements, design and construction, client satisfaction, preference, quality function deployment, conceptual design, design and build, briefing, designer, procurement strategy
Subjects: contractual arrangements, profession, client relations, scope management, quality assurance, design practice, decision-making and reasoning, professional development
Topics: Stakeholder Management, Roles and Professions, Procurement, Information Management, Research Practice, Project Management, Design Practice, Quality Management
Descriptive scope: 2 PC

N.B. Descriptive scope is a count of how many of the five facets of empirical research are indicated by the words used in title, abstract and keywords. It is not intended as a judgement on the research; merely a count of the kind of word we would expect to indicate Phenomenon, Concepts, Theoretical framing, Empirical techniques, Analytical techniques. If all five are present, then a code of “5 PCTEA” will indicate this. If you feel the coding for this record is questionable, we welcome discussion around the terms we matched or the way we categorized them. The facet you would expect may not be coded, or a facet may be coded inappropriately. This can also bear on a larger question, of which facets should be treated as defining in construction management research. Please get in touch, and we will look at it. More details here