Alan, I agree. The primary purpose of specs does not seem to be to communicate to the users. I think we are struggling for 2 reasons: Claim avoidance, and production efficiency.
Much of what we include seems to be there to respond to the contractor’s complaint/claim: “you did not tell me that.” We write to the lowest level of trade contractor, telling her/him many things that are means and methods, and burying the information s/he wants to know in pages of mind-numbing minutiae. We make it difficult for those who care, and can read, to determine what we want; and the others aren’t going to read it anyway.
The most important consideration when writing anything is: who is the reader? But in writing masters, we must assume that the users can’t tie their shoes without us. Thanks to production methods, there’s little penalty if the section is 3 or 4 [or more] pages longer than it needs to be.
How many of us, upon opening a new appliance, read, or even scan, the useless warnings that are placed at the beginning of the manual? At least there, most of the BS is placed at the beginning and is easily skipped. Imagine that stuff sprinkled throughout the manual. That is what many current spec sections are like.
“Concise” has been replaced with “comprehensive” and in the process we lost “communication,” [which wasn’t one of the 4 C’s to begin with].
There are certainly many sections that are inherently complex, but do we really put forth an effort to make them easier to use? If users found specs easy and quick to comprehend, useful tools to execute the work and increase profitability, don’t you think they might use them willingly?
Unfortunately, I don’t have a solution to how we might transform the project manual from a fearsome implement of torture and retribution to a user-friendly tool. Probably a pipe dream.
Write it like you say it!!!