There are lessons and videos online for almost any skill, yet many people start learning on their own and give up within a week or two. The reason is usually not a lack of willpower but the lack of a plan: it is unclear what to learn, in what order and until when. In this article we walk through a complete system for planning a new skill without a teacher: the end result, a skill tree, choosing resources, the “learn, practise, build” cycle, a weekly and daily structure, feedback, measuring progress and replanning, motivation and a learning journal. Then we look at the plan of Lola, who takes Excel to dashboard level in 12 weeks, go through common mistakes, and finish with a fill-in template and a checklist.
We have written about daily study habits in effective learning for adults and about not forgetting what you learn in memory techniques. Here the focus is on planning the whole journey.
Describe the end result
A plan starts at the end. “I want to learn Excel” or “I want to know programming” is a direction, not a destination. Write the destination as one sentence:
“In 3 months I will be able to …”
Fill the gap with an action, not knowledge: not “I know formulas” but “I build our department’s monthly report with formulas myself”. An action is visible and can be checked, whereas knowledge always feels “not quite enough yet”.
A good result statement has three features:
- A concrete task. It describes real work from your own life: a report at work, a page for a family business, explaining a lesson to your child.
- A deadline. 8–12 weeks is often convenient: long enough for a visible result, short enough not to lose motivation.
- A way to check. Who or what will confirm it: your manager accepts the report, the project file is finished, the test is passed.
We covered how to write specific, measurable goals in setting SMART goals. For self-study, add one more question: “Why does this matter to me?” Write the answer as the first line of your plan; when motivation drops, that is the line you will come back to.
Break the skill down: a skill tree
A big skill is not learnt in one go. Picture it as a tree: the trunk is the core concepts, the branches are the major areas and the leaves are specific small abilities. This approach is called a skill tree.
How to draw the tree:
- Write the end result at the top. For example, “Monthly sales dashboard”.
- List the 4–6 major areas it requires. For a dashboard: clean data, formulas, looking up and combining data, pivot tables, charts, design.
- Split each area into leaves. A leaf is an ability you can learn and check in 1–3 sessions: “conditional totals with SUMIFS”, “create a column chart and label the axes”.
- Mark the dependencies. Which leaf cannot be learnt without another? A pivot table needs a clean table first; a dashboard needs charts.
- Set aside optional branches. Move topics that are interesting but not needed for the result (macros, advanced programming) to a “later” list.
You can keep the tree on paper or in a spreadsheet; what matters is that every leaf is specific and checkable. “Formulas” is far too big; “a status column using IF with two conditions” is a good leaf.
The tree also becomes your progress map: you tick off the leaves you have mastered. It is handy, too, to turn the leaves into cards and move them across a Kanban board with the columns “Queued — Learning — Mastered”.
Choose resources: one main source
The most common trap for self-learners is too many resources: ten open tabs, saved videos, three courses started. Every new source looks better than the last, and you keep going back over the basics without moving forward. Collecting materials feels like learning, but it is not learning.
The rule is simple: one main source plus 1–2 extras.
- Main source: a structured online course or book, where topics come in order and with exercises. The skeleton of your plan is built on it.
- Extra source: a different explanation of a topic that remained unclear: a short video, an official help page, an article.
- Reference: for quickly looking up a function or term: the program’s official documentation or a cheat sheet.
When choosing the main source, check:
- Does it fit your tree? Compare the table of contents with your skill tree. Most of the topics should match.
- Is there practice? Explanations and videos alone are not enough. There should be tasks, files and tests.
- Is it the right level? Look at the first lesson: too easy and you will get bored; too hard and you will give up.
For choosing a course, see getting the most out of an online course; for learning from books, see the book-reading habit.
Add a new source in only two cases: the main one does not cover the topic at all, or you have read the explanation twice and still do not understand it. “This one looks better” is not a reason.
The “learn, practise, build” cycle
Watching videos and reading books do not give you a skill; they only give you the material for one. Every leaf should go through three stages:
- Learn. Read or watch the new topic in your main source. Make a short note: “why it is needed” and “how it is used”.
- Practise. Drill the ability straight away: first the task from the course, then a similar one you invent yourself. Practice should take more time than learning.
- Build. Combine several leaves into a piece of work close to the real result. One small project every 2–3 weeks is enough: for example, a report sheet where three formulas work together.
Building is the most important stage: a real task is messier than a textbook exercise, and the skill sets precisely when you solve its problems. Later your projects become a portfolio and show an employer more than a certificate does; we wrote about this in certificates and real skills.
A test question: “What did I actually do this week?” If the only answers are “watched” and “read”, add more practice.
A weekly and daily structure
Until a plan is in your calendar, it is only an intention. First, honestly estimate how much time a week you can set aside, taking work, family and travel into account. A little time, regularly, is more useful than a lot of time in scraps.
Then spread the time across the week. Below is an example for a working person with about 5 hours a week (illustrative; adapt it to your own schedule):
| Day | Time | What to do |
|---|---|---|
| Monday | 40 minutes | New topic: learning from the main source |
| Tuesday | 40 minutes | Practice: tasks from the course |
| Wednesday | 20 minutes | Review and self-testing |
| Thursday | 40 minutes | New topic or continuation |
| Friday | 20 minutes | Practice, adding to the list of questions |
| Saturday | 2 hours | Working on the project |
| Sunday | 15 minutes | Weekly review and next week’s plan |
Each daily session should have a structure too:
- Start (2–3 minutes). Read yesterday’s journal entry and write down one specific task for today.
- Main work. Learning or practice, as planned.
- Wrap-up (3–5 minutes). Close the book, write in 2–3 sentences of your own what you learnt today, and note the first step for tomorrow.
It helps to tie the session to a fixed time: for example, after a cup of tea when you get home from work, or once the children are asleep.
Sources of feedback
The weak spot of learning without a teacher is: who points out your mistakes? Without feedback you can practise the wrong technique for months, so build feedback sources into the plan in advance:
- Self-tests. At the end of each section, do the source’s tests or your own questions without looking at the material. Wherever you cannot recall the answer is where you need to review.
- Comparing with a model answer. Many courses include a worked solution. Do the task yourself first, then compare and note the differences in your journal.
- Community. Ask questions on a topic forum, in a Telegram group or in the course chat. Be precise: what you wanted to do, what you did, what happened. Attach a screenshot.
- Work or code review. Show your finished project to someone more experienced: a colleague, a specialist you know, a group member. In programming this is called code review, but it works in any field: reports, design, writing.
- A mentor. Even one or two short conversations a month with a specialist go a long way. Come with prepared questions and your work, and respect their time.
Treat criticism not as a personal attack but as data for your plan; we wrote about this in feedback.
Progress, replanning and motivation
Measuring progress
If you do not measure progress, either it feels as though nothing is changing, or you notice too late that the plan has gone off track. You do not need a complicated system:
- Ticks on the skill tree. How many leaves are mastered and how many are left.
- Number of sessions. How many of the week’s planned sessions actually happened.
- Projects. How many small projects are finished.
- Things you could not do before. Redo a task that was hard at the start of the month and compare the time and difficulty.
A retrospective every 2 weeks
Every two weeks, spend 20–30 minutes writing answers to four questions:
- What got done? Which leaves and projects.
- What worked? Which time, source or technique was most useful.
- What got in the way? Not enough time, a hard topic, an unsuitable source.
- What will I change in the next two weeks? One or two specific changes.
A retrospective is not for blaming yourself but for correcting the plan. If you fall behind two weeks in a row, the plan is too dense: cut some leaves, extend the deadline or drop optional branches. Changing the plan is not failure; it is a normal part of the process.
The plateau
Almost every learner hits a period of “nothing is changing”: at first progress is quick to see, then the topics get harder and growth stops being obvious. This is called a plateau, and often it is exactly when the skill is consolidating underneath. On a plateau it helps to:
- reread your journal entries from the first weeks and remember what was hard then;
- spend a week on a project instead of a new topic;
- make the task slightly harder or choose a different kind of exercise.
The minimum day
For days when you are tired or very busy, decide on a “minimum day” in advance: the smallest possible action of 5–10 minutes, such as reviewing flashcards or rewriting one formula. It keeps the chain unbroken: the next day you start from where you left off rather than from zero. Just make sure the minimum day stays an exception.
An accountability partner
An accountability partner is someone who knows your plan and asks once a week, “How is it going?” It might be a friend, a colleague or an acquaintance learning the same thing. A short message is enough: “What I did this week, what I will do next week.” A plan promised to another person is not so easily abandoned.
A learning journal
A journal can be an ordinary notebook, document or spreadsheet. After each session, write a few lines:
Date: …
What I did today: …
What was hard: …
My questions: …
First step for tomorrow: …
The journal helps you start the next session quickly, run your retrospectives and see how far you have come during a plateau. The habit of lifelong learning rests on exactly these small, repeated steps.
Example: Lola’s 12-week plan
The example below is illustrative. Lola, 28, is an office manager at a trading company in Tashkent. She can make a simple table in Excel but knows few formulas. Her manager asks for a clear sales report every month, and Lola wants to prepare it herself. She can set aside about 5 hours a week.
End result: “In 12 weeks I will build a filterable dashboard from our department’s monthly sales data and present it to my manager.”
Why it matters: growth at work and a possible move into data analysis later.
Main source: one structured free online Excel course. Extras: Microsoft’s official help pages and one guide to dashboards. Feedback: the course forum, Dilshod, an experienced colleague in accounts, and finally her manager.
| Weeks | Skill tree branch | Project or result |
|---|---|---|
| 1–2 | Clean table: data entry rules, formatting, sorting, filtering | Turn last month’s sales data into a clean table |
| 3–4 | Formulas: SUM, AVERAGE, IF, absolute references, SUMIFS, COUNTIFS | A sheet of sales totals by sales rep |
| 5–6 | Lookup and cleaning: VLOOKUP or XLOOKUP, removing duplicates, splitting text | Connect the product list to the sales table |
| 7–8 | Pivot tables and charts | A pivot table by month and region, plus 3 charts |
| 9–10 | Dashboard: summary cards, slicers, design rules | A draft dashboard and Dilshod’s feedback |
| 11–12 | Final project, revisions, presentation | A dashboard presented to the manager |
Weekly structure: Monday, Tuesday and Thursday evenings, 40 minutes each for the course and exercises; Wednesday and Friday, 20 minutes each for review; Saturday morning, 2 hours on the project; Sunday, 15 minutes for the journal and plan. Minimum day: rewrite one formula.
Retrospectives: at the end of week 4, Lola saw she was behind on SUMIFS and gave part of week 5 to that topic. In week 8 a plateau set in: instead of a new topic, she spent a week practising pivot tables on her own work data only. In week 10, Dilshod said the dashboard had too many charts, and Lola kept three.
Lola’s weeks 9–10 rely on the steps in building a dashboard for reports.
Common mistakes, exercise and checklist
Common mistakes
- Starting without a result. Starting to “learn” with no idea when to stop. Write your result sentence first.
- Collecting resources. Ten courses saved, none finished. Pick one main source.
- Only watching. Counting video time as learning. Give more time to practice and projects.
- An overly dense plan. Scheduling two hours a day in the first week and burning out on day three. Start from the time you really have.
- Going without feedback. Nobody sees the mistake, and it becomes a habit. Build checking sources into the plan.
- Never adjusting the plan. Falling behind and abandoning everything instead of fixing the plan. That is exactly what retrospectives are for.
Practice exercise: your own plan template
Copy the template into a notebook or document and fill it in:
- End result: “In … weeks I will be able to …” \
- Why this matters to me: … \
- Skill tree: major areas (4–6) and the leaves in each: … \
- Optional branches (the “later” list): … \
- Main source: … Extra sources (1–2): … \
- Real time per week: … hours. Session days and times: … \
- Projects (one every 2–3 weeks): … \
- Feedback sources: … \
- Minimum day: … \
- Accountability partner: … \
- Retrospective dates: …
Once the template is complete, write a specific task for each day of the first week and put tomorrow’s first session in your calendar.
Checklist
- The end result is one sentence, written as an action, with a deadline.
- Every leaf on the skill tree is specific and checkable.
- One main source is chosen, with no more than 1–2 extras.
- There is practice every week and a project every 2–3 weeks.
- The weekly schedule is based on real time and is in your calendar.
- At least two feedback sources are identified.
- Retrospective dates, a minimum day and an accountability partner are set.
- The learning journal is started.
Self-study can do without a teacher, but not without a plan: a good plan answers the question “what am I doing today?” every single day.
If you would like to learn a new profession or skill systematically with experienced teachers, take a look at our association’s free training programmes. When you are ready, submit an application and our specialists will get in touch.