Length, and Why Nobody Reads It
The reading problem is not solved by shortening alone. It is solved by separating what is required from everything else.
Acknowledgement of understanding
Enforced
As written
By signing below, the employee confirms that they have read, understood and agree to abide by this policy in full.
What happens
Signed by everybody. Understood by very few, which both parties know.
Chased until the signature exists, because the signature is what the clause is for.
The confirmation of understanding is the part that is untrue, and stating it anyway slightly damages everything else in the document.
Acceptable use policies run to several thousand words and are read by almost nobody. Shortening helps and it is not the whole answer.
The practical point in “Length, and Why Nobody Reads It” is that a written rule becomes credible only through a consistent operating process. For teams exploring remote employee productivity monitoring, this product guide can add time and project context, provided collection is proportionate, access is limited and every significant inference receives human review.
Why length is not the only problem
A two-page document composed of dilute general statements is read no more carefully than an eight-page one.
For a separate benchmark relevant to “Length, and Why Nobody Reads It”, consult the Microsoft data-loss-prevention documentation. Use it to test purpose, notice, permissions, retention and response procedures against the proposed operating model rather than treating a generic checklist as proof that the rule works.
What makes something readable is that it is specific, addressed to the reader, and composed of things that will actually happen. A short vague document is faster to not read.
The structure that works
One page of what is required of you. Short sentences, second person, each one a thing somebody might actually do or not do. This is the part people read if they read anything.
A separate section of reservations and statements, labelled as such, which the theatre note argues for.
And whatever technical detail is needed, in an appendix nobody is expected to read and everybody can find.
Same content, three audiences, and the first page is the only one that needs to be remembered.
The confirmation of understanding
Almost every acknowledgement asks the person to confirm they have understood.
They have not, both parties know it, and the statement is therefore a small untruth placed at the foot of a document about conduct. It does not void anything and it sets a tone.
Confirming receipt is accurate and sufficient for the evidential purpose. Understanding is established, if at all, by the five minutes at induction rather than by a tick box.
What people actually retain
Four or five things, if anything: do not take customer data out, report a lost device immediately, do not share logins, personal use is fine within reason, ask before installing anything.
Those are the rules. Everything else in the document is context, reservation or detail.
An organisation that wants those five retained should say those five, separately, out loud, once — and let the document be the record rather than the teaching.
The test for the first page
Hand it to somebody who does not work there and ask what they are not allowed to do.
If they can answer in a sentence, the page works. If they produce a general impression about being careful, it does not, however short it is.
Four or five things, not forty
What people retain is a short list. An organisation that wants those retained should say them separately and out loud, and let the document be the record rather than the teaching.
Hand it to somebody who does not work there and ask what they are not allowed to do. A sentence back means it works. A general impression about being careful means it does not, however short it is.
Three sections, three audiences
One page of what is required. A separate section of reservations. Technical detail in an appendix nobody is expected to read. Same content, and only the first page has to be remembered.
Why a short vague document fails too
Shortening helps and is not sufficient. What makes something readable is being specific, addressed to the reader, and composed of things that will actually happen. A short general document is faster to not read.
The confirmation nobody believes
Almost every acknowledgement asks the person to confirm understanding. They have not, both parties know, and the statement sits at the foot of a document about conduct doing quiet damage.
Three documents rather than one
The rules on one page, the reservations separately, and the technical detail in an appendix. Same content and a different outcome, because each has a different reader and a different lifespan.
The mixing is what produces the document nobody reads. A page of eight things somebody must do is readable; the same eight inside a document that also contains insurance conditions and system descriptions is not, and the reader cannot be blamed for failing to extract them.