Hansen, K L and Vanegas, J A (2003) Improving design quality through briefing automation. Building Research & Information, 31(5), pp. 379-386. ISSN 0961-3218
Abstract
Briefing and the strategic support of decision-making through the life of a building project is an important factor for successful project outcomes. The automation of design briefs might allow enhanced linking of client/user requirements to design, construction, operation and post-occupancy review. It has the potential for improved collection of requirements, project integration, as well as feedback and feedforward for clients and designers. Current US research on briefing practices is reviewed in relation to improving design quality by using design performance measures. A Web-based tool under development is described. This tool is one example of how automation of the briefing process can assist design firms to analyse and assess a client's needs, shorten the product delivery cycle and provide an end product with greater customer satisfaction.
| Item Type: | Article |
|---|---|
| Uncontrolled Keywords: | architectural programming; briefing; client requirements; customer focus; design quality |
| Index terms: | design brief, programming, client requirements, customer satisfaction, decision-making, integration, briefing, product delivery, automation, design firm, design quality, user requirement, designer, project outcome, feedforward, performance measure |
| Subjects: | programming, practitioner, control systems, scope management, profession, project completion, user-centered design, professional practice, product delivery, technical documentation, service delivery, automation and robotics, professional development, performance measurement, organizational analysis, decision analysis |
| Topics: | Organizational Design, Design Practice, Digital Applications, Quality Management, Supply Chain Management, Risk Management, Roles and Professions, Stakeholder Management, Project Management, Engineering Principles, Information 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