How Do You Choose Which Skill to Learn Next?
TL;DR: Choose the next skill by starting with the real result you need in the next two weeks, then favor the option that is most urgent, high leverage, compact, and easy to practice with fast feedback. Build a short spaced plan, self-test as you go, and skip skills that are too broad or would wreck your sleep.
Start with the outcome you actually need
Start by picking the real result you need in the next two weeks, then work backward from there. If that result looks like "send a cleaner client update," "fix the spreadsheet that keeps lying to me," or "make the deck not look like it was assembled in a parking lot," pick the skill that gets you there directly.
This beats chasing the most interesting skill. That path usually lands you with a fancy technique you cannot use yet. It is useful, sure, just not immediately useful. Which makes it a very expensive hobby.
Separate “high leverage” skills from “nice to have” skills
High leverage skills unlock other work, remove bottlenecks, or make your current job noticeably easier. Nice to have skills are fine, but they can wait unless they are tied to a near-term result.
A practical test: will this skill help you finish work faster, reduce back-and-forth, or improve something people will actually see soon? If yes, it is probably worth the sprint. If it mostly makes you more well-rounded in a vague, inspirational-poster way, park it for later.
Check whether the skill is compact enough for a two-week sprint
Not every skill fits into two weeks. Some are huge, messy, and sneaky about it. A good sprint skill has a small enough scope that you can practice it, try it in real work, and repeat.
In short windows, specific beats broad. “Write clearer follow-up emails” is manageable. “Become a better communicator” is a fog bank wearing a name tag.
Pick the skill with the clearest practice loop
Favor skills where you can do deliberate practice, get feedback, and fix mistakes. The Frontiers in Psychology review defines deliberate practice as activities specially designed to improve current performance, and it is the kind of setup that makes short learning periods more productive when you can actually see what went wrong (Frontiers in Psychology).
Good practice loops usually look like this:
- Do a small attempt.
- Compare it to a standard, example, or checklist.
- Fix one thing.
- Repeat.
If a skill gives you no feedback, it is hard to improve quickly. You can stare at it heroically, but the skill will not care.
Use a simple decision filter
When you have a few candidates, compare them on four things:
- Urgency, does it solve a problem you need to handle soon?
- Usefulness, will it help with several tasks, not just one?
- Learnability, can you get a decent first version in two weeks?
- Access to practice material, can you find examples, cases, or real work to practice on right away?
Choose the skill with the best overall fit, not the one that wins one category by a mile and loses the others by a crater.
Worked example: choosing between three possible next skills
Suppose your options are spreadsheet formulas, basic presentation design, and email writing.
- Spreadsheet formulas: high leverage if you are stuck cleaning up data or making recurring reports. Good feedback loop, because formulas either work or they do not. But if you only need to communicate one project this week, it may not be the fastest win.
- Basic presentation design: useful if you need to present soon. You can improve layout, hierarchy, and readability quickly, and the feedback is visible. Still, it may be less urgent if the immediate pain is slow admin work.
- Email writing: often the fastest win if your current bottleneck is follow-up, coordination, or getting answers from other humans, which is usually where time goes to nap and never return.
If the most immediate problem is that your inbox is causing real-world delays, email writing is probably the best next skill. It solves the current problem, has fast feedback, and you can practice it immediately on real messages.
Turn the choice into a two-week learning plan
Once you choose the skill, break it into small sessions. Mix practice with self-testing, and spread the sessions over time instead of cramming them all into one dramatic weekend.
That approach matches the IES practice guide, which recommends spacing learning over time and using quizzing to promote learning (IES Practice Guide). The APS review also highlights practice tests and distributed practice as high-utility techniques (APS review).
A simple two-week structure:
- Days 1 to 3: learn the basics and make one small attempt.
- Days 4 to 7: practice with real examples and review what broke.
- Days 8 to 10: try again with slightly harder material.
- Days 11 to 14: self-test, revise, and use the skill on a live task.
Keep the sessions short enough that you can actually pay attention. Attention is annoyingly important.
Protect the learning plan from forgetting
Do not wait until the end of the two weeks to review. Memory fades with time, and repeated retrieval helps you keep what you learned. That is consistent with the PLOS ONE replication of the forgetting curve, which found that relearning after delays matters (PLOS ONE).
So review after a delay, then again later. Try recalling the steps or solving a fresh example from memory before checking your notes. Retrieval is a little uncomfortable, which is usually a sign it is doing something useful.
Make sleep part of the decision
Choose a skill you can practice without wrecking your sleep. The NHLBI says sleep is vital for learning, focus, and memory, and that sleep deficiency can interfere with learning and thinking (NHLBI).
That means a skill you can work on consistently for 20 or 30 minutes is often better than one that pushes you into late-night grinding. A tired brain is a dramatic little liar. It will feel busy and still retain less.
When to skip a skill for now
Put a skill aside if it is too broad, too passive, or too hard to practice in a short window.
Examples of "not now" include:
- broad subjects with no clear target,
- skills that require long reading before any practice,
- topics where you cannot get feedback quickly,
- abilities that would push you to sacrifice sleep or other responsibilities.
You are not rejecting the skill forever. You are just saying, "Not this sprint, buddy." Revisit it later when you have more time or a clearer use case.
Optional FAQ
How do I choose if two skills seem equally useful?
Pick the one with the better practice loop and the smaller scope. If both matter, choose the one you can test fastest in real work.
What if the best skill is still too big for two weeks?
Shrink it until it fits. Focus on one subskill, one use case, and one measurable outcome. For example, not "learn presentations," but "make one slide cleaner and easier to scan."