Do you always need a blueprint

No. If your document is short, telling its structure may seem too mechanical.

Another time a blueprint may seem too mechanical is when your document has many parts. Suppose, for example, it has nine sections. Readers normally don't want to read through a list of the nine topics you're going to cover. On the other hand, a document with nine sections can get confusing, can't it?

So I suggest using an implied blueprint: "I'll cover the nine issues in the case, starting with the most important one." Your reader now knows the structure of your document. You've given the number of "stops" on the trip but not the lengthy list of their names.

And what if you can't give a blueprint of your document? That means you probably haven't organized it into clear blocks of information. Very occasionally that's okay for a document. Most times, though, busy readers will become confused and start skimming.

Was this article helpful?

0 0

Post a comment