Weekly close
Record one strong piece of evidence, one recurring error, one support need and one next task.
Learning Journal
A method for recording not merely how long I studied, but the question I asked, what I produced, where it failed and what changed in the second version.
WHY A JOURNAL?
Making thinking visible rather than documenting private life
This is not a diary sharing everyday personal detail. It is a working tool that shows why decisions were made, what evidence changed a conclusion and whether the same error returned in a lesson, project or investigation.
Writing only “I studied Python today” does not explain progress. A useful record contains a question, initial expectation, artefact, test, error, feedback, change and next step. The same structure can be used for coding, electronics, research, sport data or school subjects.
EIGHT FIELDS
A basic template for every entry
| Field | Question | Short example |
|---|---|---|
| 1. Date and topic | What did I work on? | Sensor threshold |
| 2. Question | What uncertainty am I trying to resolve? | Why does the count rise with no movement? |
| 3. Initial expectation | What did I think would happen? | The threshold may be too low |
| 4. Artefact | What did I build or write? | A ten-reading test script |
| 5. Evidence | What did I observe or measure? | Three false counts while still |
| 6. Error | Which assumption failed? | One threshold did not fit every condition |
| 7. Change | What changed after feedback? | Added a time window and a second check |
| 8. Next step | What is the next small test? | Try different movement speeds |
SAMPLE ENTRY
Sensor threshold example — not a personal project claim
The following scenario demonstrates the journal format; it is not a completed personal project record. Imagine a movement sensor that counts whenever its value crosses a threshold. In the first test, a low threshold creates counts even while the device rests on a table.
The second version checks two conditions across a short time window. False counts fall, but some slow movements may be missed. Instead of writing only “fixed”, the journal records both false positives and missed movements. The decision then rests on measurable change rather than one successful demonstration.
ERROR LOG
An error is a learning artefact in its own right
If an error log is cleaned up to look perfect, the strongest learning evidence disappears. The aim is not to create failure, but to reproduce it safely and explain its cause.
- Record the condition in which the error appears.
- Separate expected and actual results.
- Check whether the error can be reproduced.
- Keep several possible explanations open before deciding.
- Record an unsuccessful fix as well as a successful one.
- State what improved and what became worse in the next version.
A STEADY ROUTINE
Weekly and monthly return
Monthly comparison
Look across four weeks for repeated questions and error types.
Term archive
Select two meaningful artefacts together with their first and final versions.
New goal
Choose it from an evidence gap rather than a vague result target.
PRIVACY
Not everything written in a journal should be public
Private emotions, health information, detailed school records, names of teachers or classmates, location, regular routes, account details and contact information are not placed in a public learning journal. A private record can remain offline with appropriate family or trusted-adult support.
A public entry should explain the educational or technical method without identifying a person unnecessarily. Screenshots, code, photographs and datasets need personal-data and licence checks before publication.
RETURN AND REVIEW
How can the quality of an entry be checked?
A useful journal entry does not need to be long; it needs to make the decision traceable. If another person can understand why the first expectation changed and which question the second test addressed, the record is doing its job.
Collecting numerical data alone is insufficient. The limits of the measuring tool, number of observations, conditions and method of observation should be stated. Otherwise a detailed-looking table can create false certainty.
Entries are not given a performance score at month end. Instead, recurring errors, frequently used sources, points where help was needed and the number of second versions are reviewed. The journal then improves learning method rather than creating pressure to appear productive.
- Make the decision traceable
- Record measurement conditions
- Avoid false certainty
- Review the method monthly