Who this is for
You have decided to learn something — a craft, a technical skill, an instrument, a discipline — and you have been at it long enough to notice the pattern: you consume material steadily and produce almost nothing, so you cannot tell whether you are improving.
This template is organised around that specific failure. Its central assumption is that self-directed learning fails at the production step, not the input step. Courses are plentiful and easy to start. Making something with the skill is uncomfortable and optional, so it gets deferred indefinitely, and without it there is no feedback and no evidence.
The branches
What "able" concretely means. Before anything else: what would you be doing, that you cannot do now, if this worked? "Know Python" is unfalsifiable. "Take a messy spreadsheet and produce a chart without asking anyone" is checkable. This branch is short and it governs the rest — a vague destination is why most learning maps cannot tell you when to stop.
The gap between consuming and producing. Explicitly its own branch, because it is the failure mode. What have you actually made? What is the smallest thing you could make this week that uses the skill badly? The word "badly" is load-bearing.
Fundamentals I keep working around. Every self-taught person has a hole they route around — the theory they skipped, the technique they avoid, the concept they half-understand. It compounds quietly and eventually caps you. This branch is for naming it, which is most of the work.
Contact with something real. A person, a deadline, an audience, a problem that is not from an exercise set. Skills mature under conditions where being wrong has consequences, and exercises are designed to remove exactly that.
Feedback I can actually get. Who will tell you what is wrong? A community, a teacher, a friend who does this, or a mechanical check — tests passing, the piece sounding right, the dish tasting correct. Learning without a correction signal produces confident bad habits.
Evidence in six months. What will exist? A portfolio, a recording, a shipped thing, a passed assessment. Decide now, because it determines what you should be making all along.
How to use it
Import it and mark the production branch as Focus, not the fundamentals branch. This is counterintuitive and deliberate: attempting to make something reveals which fundamentals actually matter, whereas studying fundamentals first tends to continue indefinitely because there is always more.
Then let the fundamentals branch fill up with the specific gaps that surfaced while you were failing to make something. That list is far better than a syllabus, because it is yours.
Do not add dates to most of this. Skill acquisition does not respond to deadlines you invented, and missing them teaches you to distrust your own dates.
What to add once it is yours
Replace the branches with your actual skill's specifics — the real technique, the real tool, the real thing you are trying to make. Delete anything that does not apply; five branches is plenty.
Attach Proof as you go. The first thing you made, however bad. The recording from month one. A branch cannot be marked Proven without evidence, and in learning that constraint pays off unusually well, because progress is invisible day to day and obvious across six months of artifacts.
Signs it is working
- You have made something, however small, in the last two weeks
- The fundamentals branch is filling with specific gaps rather than general topics
- Someone or something has told you what was wrong, and you changed
- You can point at an artifact from a month ago and see the difference
Signs it is not
- The map is mostly resources — courses, books, channels
- Nothing has been produced, but a lot has been consumed
- The "what able means" branch is still vague after several weeks
- You keep restarting with a better resource rather than continuing with a worse one