Self-Directed Learning Plan Checklist
Set up a learning path you will actually finish — a real reason, a scoped commitment, the build step that converts reading into capability, and the honest checkpoints that catch drift early.
Markdown. No sign-up, no email.
Most self-directed learning fails the same way: enthusiastic start, three topics at once, no build step, quiet abandonment around week three. Every item here targets one of those.
What I am learning: _______________ Start date: _______
1. The reason#
- [ ] There is a specific thing I want to be able to do, not a subject I want to know about
- [ ] I can name where I will use it within three months
- [ ] I would still want this if nobody knew I had learned it
In one sentence, I am learning this so I can: _______________
🔴 "I should probably learn X" has the lowest completion rate of any motivation. Learning attached to a real task sticks; learning attached to a vague sense of obligation does not survive a busy fortnight.
2. Scope#
- [ ] One topic at a time. Not three
- [ ] The path is written down, in order
- [ ] I have deliberately excluded things that are adjacent but not needed now
Explicitly not learning yet: _______________
Three topics in parallel is the most common way to finish none. Sequence them.
3. Time#
- [ ] Hours per week I will actually spend: ____
- [ ] When in the week — specific slots, not "evenings"
- [ ] What I am giving up to make that time
- [ ] Total weeks I expect this to take: ____
If nothing is being given up, the time will not appear. It has to displace something.
4. The build step — the part that matters#
- [ ] Every stage has something I build, not just read
- [ ] The first build is small enough to finish in one sitting
- [ ] I can tell whether it worked without asking anyone
- [ ] The final piece is substantial enough to show someone
| Stage | Read | Build | Done |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | |||
| 4 |
Reading three guides in a row feels productive and produces recognition — the feeling you would know it if you saw it. Recognition disappears in front of a blank editor. Only building converts it.
5. Checkpoints#
- [ ] Week 2: have I done anything beyond reading?
- [ ] Week 4: could I explain this to someone who will interrupt?
- [ ] Week 6: can I build something small without the guide open?
- [ ] End: is there something I can show?
Failing a checkpoint is information, not failure. Usually it means the scope was too wide or the build step was skipped. Both are fixable if noticed in week two rather than month three.
6. Honest self-check at the end#
- [ ] I built something that works
- [ ] I can explain a decision I made and what I rejected
- [ ] I predicted a failure correctly before running something
- [ ] I know what I still do not know
What I still cannot do: _______________
That last line is the most useful thing on the page. Knowing the boundary of your own competence is what distinguishes someone who has learned a subject from someone who has read about it.
7. Next#
- [ ] The next topic is chosen, or deliberately deferred
- [ ] Notes are somewhere I will find them again
- [ ] Anything I built is in version control
| Started | |
| Finished | |
| Actual hours vs planned | |
| Would I do this again the same way? |