Public Websites Need Better Download Names for Official Documents

Official documents are often downloaded with vague file names such as document.pdf or form1.pdf, making them difficult to identify later.

Organizations sometimes respond to recurring confusion by writing longer instructions.

Agencies should use descriptive file names that include the document type and, where useful, a revision year or version number.

Length is not always the answer. A short checklist, example, status label, or clearly named contact can be more useful than another page of policy language.

The goal should be usable information, not simply more information.

Good file names are a small form of information design that continues helping users after they leave the website.

Feedback from occasional users is especially useful because they cannot rely on familiarity. Their experience often reveals assumptions that regular users no longer notice.

Information should stay consistent across websites, signs, emails, apps, and staff instructions. Conflicting messages can undermine even a sensible policy.

Small improvements can produce substantial cumulative benefits when they affect a routine task that many people repeat throughout the year.

After implementation, organizations should compare repeated questions, delays, and common mistakes with the earlier process. If the same confusion remains, the design should continue to evolve.

Feedback from occasional users is especially useful because they cannot rely on familiarity. Their experience often reveals assumptions that regular users no longer notice.

Information should stay consistent across websites, signs, emails, apps, and staff instructions. Conflicting messages can undermine even a sensible policy.

Small improvements can produce substantial cumulative benefits when they affect a routine task that many people repeat throughout the year.

After implementation, organizations should compare repeated questions, delays, and common mistakes with the earlier process. If the same confusion remains, the design should continue to evolve.

Feedback from occasional users is especially useful because they cannot rely on familiarity. Their experience often reveals assumptions that regular users no longer notice.


K. Chen