A Collection Stores Material; a System Produces Feedback
The test is whether one activity changes the next activity.
Use Five Linked Layers
Each layer has a different job.
| Layer | Purpose | Typical record |
|---|---|---|
| Concepts | Preserve definitions, conditions, representations, and connections. | A concept note with an example, non-example, and open question. |
| Problems | Test whether concepts work under constraints. | Attempts, solutions, method choices, and an error log. |
| Sources | Bring in lectures, books, papers, official documents, and data. | A source note that records what was used and why. |
| Outputs | Turn knowledge into something inspectable. | A proof, report, explanation, presentation, code file, or project section. |
| Review | Decide what to strengthen, schedule, simplify, or remove. | A weekly list of next actions and unresolved questions. |
Organise Around Questions and Concepts, Not File Types Alone
The same idea should be reachable from its definition, problems, evidence, and output.
Local checklist
Minimum record for one important concept
Progress is stored only in this browser.
Problems Should Update Notes
An error log is useful only when it changes later study.
| Error type | Example | Repair |
|---|---|---|
| Concept | A theorem is applied outside its hypotheses. | Rewrite the conditions and add a counterexample. |
| Recognition | The correct concept is known but not noticed in the problem. | Practise mixed problems and identify the concept before solving. |
| Strategy | The first method creates unnecessary work. | Compare two methods and record when each is efficient. |
| Notation | A symbol is misread or used inconsistently. | Create a notation key and rewrite the affected step. |
| Calculation | The plan is sound but arithmetic or algebra fails. | Add a verification step and practise the specific operation. |
| Reading | A condition in the question is ignored. | Underline givens and rewrite the goal before calculation. |
Use a Weekly Cycle, Not Constant Reorganisation
The system grows through a short review, not a dramatic redesign.
A realistic weekly cycle
Capture
Record only what deserves a later action
Definitions, decisions, mistakes, sources, and questions matter more than complete transcription.
Connect
Attach each item to a concept or project
A note without a relationship becomes difficult to retrieve and easy to forget.
Test
Use retrieval and problems
Close the source, reconstruct the idea, and solve a problem that requires choosing the concept.
Produce
Create a small output
Write a proof, explanation, code example, diagram, paragraph, or presentation slide.
Review
Choose the next actions
Keep the system small by archiving duplicates and scheduling only the most useful work.
A Worked Example: Eigenvalues
One topic can connect all five layers.
| Layer | Eigenvalue example |
|---|---|
| Concepts | Definition, characteristic equation, geometric interpretation, assumptions, and a non-example. |
| Problems | Direct computation, conceptual questions, diagonalisation decisions, and an error such as treating every non-zero vector as an eigenvector. |
| Sources | Lecture notes, a textbook section, and one advanced source showing an application. |
| Outputs | A one-page explanation, a plotted transformation, a short code experiment, or a seminar example. |
| Review | Retrieve the definition, solve one varied problem, and revisit the recorded error after a delay. |
Choose Tools After You Choose the Workflow
A notebook, folder, spreadsheet, or app can all work.
Tool-centred and learning-centred organisation
| Topic | Tool-centred | Learning-centred |
|---|---|---|
| Starting question | Which app has the best features? | Which academic actions must the system make easier? |
| Success measure | The dashboard looks complete. | Concepts are easier to retrieve, test, and use. |
| Maintenance | Frequent redesign and migration. | A short weekly review and minimal structure. |
| Failure signal | Another tool seems more attractive. | The next academic action remains unclear. |
Decision framework
What should enter the system?
Choose the item you are deciding how to handle.
The tool helps with academic organisation. It does not prescribe a particular application or guarantee improved grades.
Prevent the System From Becoming Another Form of Procrastination
Organisation should reduce friction, not become the main academic activity.
Keep the system honest
- Do not copy material merely to make the system look complete.
- Keep one trusted location for each type of record.
- Use links or indexes instead of duplicating the same content.
- Record unresolved questions and errors, not only polished notes.
- Schedule retrieval and problem solving, not only reading.
- Archive structures that are no longer used.
- Judge the system by the quality of academic output it supports.
Questions about student knowledge systems
Do I need a specialised note-taking app?
No. A notebook, folders, documents, or spreadsheets can work. The important feature is the connection among concepts, problems, sources, outputs, and review.
How much time should weekly maintenance take?
Start with twenty to forty minutes for one subject. If maintenance regularly takes longer than the studying it supports, simplify the system.
Should every note become permanent?
No. Temporary working notes are normal. Keep material that supports understanding, evidence, correction, retrieval, or a future output, and archive the rest.