The Heavy Document

A document arrived, and before anyone understood what was inside it, its size had already made an impression.

This happened often enough to become funny. A thick report looked serious. A long book looked like value. A Word file so large that it opened slowly could almost become proof that somebody had worked very hard.

The document might even fail at being convenient and still succeed at looking important.

That contradiction bothered me.

Engineering is supposed to reward making difficult things clearer. Yet professional life often rewards visible debris: pages, tables, slides, attachments, meetings, revisions, and files large enough to suggest suffering.

A short answer can look suspiciously easy.

A long answer arrives carrying evidence of labor.

This creates an unfortunate incentive. Once people notice that quantity is mistaken for seriousness, they produce quantity. The report grows not because the reader needs more information, but because the authors need the reader to see how much work happened.

The best work often has the opposite problem.

Someone struggles through false starts, removes unnecessary sections, simplifies the explanation, and leaves behind ten clear pages. The reader sees the clean room, not the cleaning.

That is the strange punishment of clarity.

The old joke was that perhaps a customer should reward the author of an enormous document simply for surviving the effort.

I would now give the reward to the person who made the document easy to use.

The heavier file is not always the heavier thinking.