The best design brief, ever!
The practice of architecture has traditionally based design solutions on what we call the “program.” At its least accomplishment, it’s a statement of the client’s functional requirements to be satisfied in the design. Better practice includes more complete examinations and analysis of what the client wants to achieve and why and with what resources, etc. There is a craft in writing them (I’m a fan of Problem Seeking), and for many building projects, the program becomes a large and complex document.
Recently, the term “design brief,” borrowed from other design disciplines, has crept into the architect’s vocabulary. We’ve periodically searched around for examples of best practice to inform how we can improve our problem statements.
Since we are also now also beginning to hear the term from clients, we’ve become a bit more attentive. So when this showed up today, referenced in the Planner Reads blog and originating from @hellomuller, we immediately raised it to the top of the list of aspirational achievements. Enjoy!
