Assume that an information is not needed to be written down unless proven otherwise.

Always implement things when you actually need them, never when you just foresee that you need them.

Ron Jeffries. You Aren't Gonna Need It

YAGNI - You Aren't Gonna Need It: The cost of creating a document may be magnitudes smaller than the cost of maintaining that document. A document providing information that is out-of-date typically inflicts more harm than a document that does not exist.

Therefore documents are liabilities that should be created with due diligence. This starts by finding and naming at least one stakeholder who demands the information in written form. Write documents just-in-time when there is actual demand to have the information in written form.

Related Practices

The following practices are related to this principle.

Agile Documentation
A document is considered to follow the agile principle if it is valuable, essential, and created or updated just-in-time. A documentation is created and maintained in an agile way, if all its documents follow this practice.
Keep a Journal
In order to take personal notes on one's own work and to reflect upon what has to be done or has been done, keep a journal. The information in the journal should be shareable at least with all team members.
Know your Mission
Use charters to define the purpose and benefit of each document. State the expectation of the stakeholders involved.
Last responsible Moment
Defer a decision to the last responsible moment is also a risk-reducing technique for writing documentation.
No Noise
Do not render text to the reader that has no information value.

Related Principles

The following principles are related to this principle.

DRY Principle
Redundant information is hard to maintain, keeping it in-sync. Therefore strive for reducing redundancy by defining one authoritative location for each piece of information.
KISS Principle
Keep your documentation simple. Assume that authors have relevant information for the project in their mind, but not necessarily the skills and resources to communicate it. Therefore make it very simply and joyful for them to share their expertise.
Law of Demeter
Documents should not reference details in other documents that may change without notice.
Open Closed Principle
Be open for extension, closed for modification.
Principle of least Astonishment
Documentation should appear to the reader as being written by one single person. Uniformity reduces the chance of astonishment. The principles applies to all areas of documentation, including style and organization.
Self Documentation Principle
There should either be no need for additional documentation for an artifact or that documentation should be as close as possible to the artifact. This make it more probable that the documentation changes with the artifact and therefore keeps up-to-date.
Separation of Concerns
Reduce the amount of documents with overlapping information. Also divide the concerns regarding the formatting and - as far as possible - the structure from the content. Whenever there are different aspects, consider if handling them independently would make things easier.
Single Responsibility Principle
A document should focus to answer one question. This way documents can be more easily reused and combined.
Stable Dependencies Principle
A document should only reference documents that are not less stable than itself.

References

More information on this principle.

You Arent Gonna Need It
The principle described as a pattern on wiki.c2.com.
You aren't gonna need it
The principle described on Wikipedia.
Yagni
Article about YAGNI by Martin Fowler on martinfowler.com.