a proposal (specification) may or may not respond to a problem or. it could
be something unanticipated and new and relate only marginally to what a
client thought to get,
what a designer typically delivers is something that others can and desire
to realize. so, what designers produce exists in a relationship between
people, not in the abstract, not any one's idea of "it." intentions may
matter to a designer, but they themselves are of no consequence.
klaus
-----Original Message-----
From: PhD-Design - This list is for discussion of PhD studies and
related research in Design [mailto:[log in to unmask]]On Behalf
Of Lubomir S. Popov
Sent: Monday, January 10, 2005 4:13 PM
To: [log in to unmask]
Subject: Re: specification Re: Design and intention
Hello,
It was said at least a couple of times that
>design is a specification, and not a product or an artefact.
I would strongly disagree with this vision. The specifications constitute
the brief, the design program, the design problem (and what ever you call
it in different design fields) but not the design. The design is a response
to the specifications/design program. This distinction is very important
for the appropriate education and professionalization of designers and
specification developers/programmers.
Best,
Lubomir
|