A Service Design Principle for better productivity

I'm slowly building a new habit when it comes to work documents. At the top of documents that I share, I usually have a section that starts with: "What's this document about?". There I try to summarise in a few words the goal of the document and how shitty or final it is. 

When it's a document that I know I'll come back to, I also add a section to help me know what I'd like to do next in this document when I re-open it. 

I find that these two little sections which take maybe 30 seconds to a minute to write, help me get much quicker in the work and I believe it helps my teammates do the same. 

For example, a colleague might think:
"Okay, this is just a first draft, and he's already planning on adding this information, so I don't need to add feedback about that piece of information being missing". when he opens a document.

And this allows him to give more useful feedback.

Action question

How can you help yourself, your team members or your users to quickly understand what is the goal, progress and next steps of the document they just opened? 

Footnote

(1) In the book Building a Second Brain Tiago Forte shares the idea of using what he calls a "Hemingway Bridge" that is pretty similar to this idea. Matt Stine wrote a 2-minute summary called "How You Can Use Hemingway’s Bridge to Ship Today’s Momentum to Tomorrow" that might interest you.

Daniele's note

This is a first draft of a principle that might end up in a book of the "Service Design Principles" series.