Dear Klaus,
Well put! I agree its important to distinguish between proposal and specification, and perhaps plan (though that is more subtle). There is a categorical distinction between proposal and specification as you've outlined. This suggests there are different situations where each is appropriate. I've focused on specification because of its key roles in contract and handover. Specification does have a looser form similar to how you describe proposal that doesn't necessarily tie down everything. It also aligns well, as does proposal, with the main dictionary definitions of the term 'design' (noun). For me, the disadvantage of proposal is that it also includes the political issues involving enticement to accept the proposal .I'd prefer on epistemological grounds to keep them separate. I can see though that including political factors is of advantage in the areas you work. This proposal-specification-plan issue is an area that probably need some added attention to carefully bridge across the different perspectives whilst maintaining the differences in theory detail.
Best wishes,
Terry
From: Klaus Krippendorff
... it must be manifest in the delivery of
something, which i think is best described by a proposal. i say proposal,
not plan, because plans are worthless if they do not entice people with
means, know-how, and interest to accept the proposal for what it suggests.
also, i say proposal, not specifications, as many design activities outline
an approach and leave certain details open to be determined by others, even
by users who may have ideas that differ from designer's intentions.
engineers, for example, might take a design as the contours within which
they can work out their contributions. the notion of specifications does
not imply the freedom for others to interpret a design
klaus
|