Start with the question your future self will ask
Finishing a project often brings a rush to tidy the workspace and move on. Before you do, set aside a short session to document it. You do not need to preserve every note or reconstruct every hour. The aim is to give your future self enough context to understand what you made, why you made it that way and which parts are worth using again.
Imagine opening the record months later. You might ask, “What was I trying to do?”, “Where is the final version?” or “Why did I choose this approach?” Let those questions guide what you save. A useful record is easy to scan and points to the relevant files; it is not a complete diary of the project.
Make a one-page project record
Create one note that serves as the entry point to the project. Give it a clear name and include the goal, intended audience or use, final outcome and location of the finished work. Add a brief description of the starting conditions: the time, tools, materials or knowledge you had available. Those details help you judge later whether an approach still fits a new situation.
Then write a few sentences under three prompts: “What worked?”, “What was difficult?” and “What would I do differently?” Be specific enough to act on. “Planning helped” is less useful than “Drafting the outline before gathering examples kept the scope manageable.” If the outcome differed from your original goal, describe the change without treating it as a failure. A changed goal can be one of the most important things to remember.
Capture decisions, not just the final product
A finished item rarely shows the choices behind it. Record two or three decisions that shaped the result. For each one, note the options you considered, the reason you chose one and any trade-off you noticed. For example, you might have shortened a guide to make it easier to use, while leaving some background explanation out. That note will help if you later adapt the guide for readers who need more detail.
Keep observations separate from guesses. “Two test readers could not find the instructions” describes something you observed; “the layout caused confusion” is a possible explanation. Both can be worth saving, but labeling them clearly prevents a tentative idea from becoming a rule you follow without question. You can also note unresolved questions rather than forcing a conclusion.
Save materials in a form you can actually reuse
Look through your working files for items that could shorten a future project: a checklist, outline, prompt, template, sample, set of questions or small process you developed. Give each item a descriptive name and add one sentence explaining when it is useful. Remove project-specific details from a copy if you want a general template, but keep the original when its context matters.
Organize the folder so someone unfamiliar with it could find the final version. You might keep the project record at the top level, place reusable materials in their own folder and move rough drafts into an archive folder. If files depend on a particular tool or format, note that in the record. A small amount of labeling now is often more helpful than an elaborate filing system you will not maintain.
Turn the record into a starting point
End with a short “next time” list. Include one practice to repeat, one change to try and one question to investigate. Make each item concrete: “Ask a reader to test the instructions before polishing the design” gives you a clearer starting action than “Get feedback earlier.” If the project taught you a skill you want to strengthen, name a small exercise that would let you practice it.
Finally, check whether the record works. Close the other files and read only your project note. Can you locate the finished work, understand the main choices and identify something you could reuse? Add what is missing, then stop. Documentation is most valuable when it is light enough to finish and clear enough to help you begin the next project.
