| name | learning-something-new |
| description | Use when picking up a new topic, tool, or skill - structured plan that gets you to first useful output fast |
| kind | workflow |
| audience | anyone |
| ai-tools | any |
| complexity | guided |
| time | 30 min planning + execution time |
| version | 1.0.0 |
| source | bundled |
Learning Something New
What this does
Turns "I want to learn X" into a structured plan: a concrete first project, a small number of high-signal sources, and a checkpoint to detect when you've stalled.
When to use
- Picking up a new tool, language, framework, or domain
- Onboarding to a new role or team
- Catching up on a topic for an upcoming conversation
- Hobby learning (instrument, sport, craft)
What you bring (Inputs)
- The thing you want to learn
- Why you want to learn it (the use case — concrete, not "to be smarter")
- Time available per week
- Your existing knowledge level (none / some / experienced in adjacent)
What you get (Output)
A learning plan: first useful project, source list (max 5), checkpoints with a rescue plan if stalled.
How it works (Steps)
This is a workflow.
Stages
Stage 1: Define the first useful output
What's the smallest thing you could make / do / decide that would prove you've learned the basics? This is your first project.
Examples: "Deploy a hello-world service in this framework," "Hold a 5-minute conversation in this language," "Diagnose a basic bug in this codebase," "Bake a loaf of sourdough."
Stage 2: Pick 2-3 starter sources
Not 12. Two to three high-quality sources for the basics, picked from a known canonical reference (official docs, top-recommended book, top course). Resist the urge to bookmark 20 things.
Stage 3: Schedule the first sprint
When are you doing this in the next 7 days? Block calendar time. Without a block, the plan is wishful thinking.
Stage 4: Set checkpoints
After 1 week, you should have completed the first useful output. After 4 weeks, you should be able to do a slightly harder version.
If you've not hit checkpoint 1, run the rescue plan.
Stage 5: Rescue plan (when stalled)
Common causes of stall (with fixes):
- Too many sources: cut to 1
- Too big a first project: shrink it (hello-world, then a step up)
- No application: the gap from "learning" to "doing" is widening; force a doing-mode session
Stage 6: Define when "learned enough"
For what use case did you start this? When you can do that use case unaided, you're done with the learning project. Move from "learning X" to "using X."
Checkpoints
- After Stage 1: first useful output is concrete and small
- After Stage 2: 2-3 sources picked, no more
- After Stage 3: time blocked on calendar
- After Stage 4: explicit checkpoints (1 week, 4 weeks)
- After Stage 5: a written rescue plan exists
- After Stage 6: end criterion is named
Loop-back conditions
Return to Stage 1 when the first useful output turns out to be too big or too small.
Quality bar
- First useful output is sized for one focused session
- 2-3 sources max (more = procrastination)
- Time is on the calendar, not "when I have time"
- End criterion is concrete (a use case, not "feel comfortable")
Variations
- Crash mode: 2-week sprint, daily blocks, checkpoint at day 7
- Slow burn: 1 hour/week, checkpoint at 4 weeks
- Onboarding to a team: first useful output = ship one small thing alone
Example
Input: Want to learn enough Spanish to have a coffee-shop conversation in Mexico City in 6 months.
- Stage 1: First useful output: order coffee + ask one follow-up question without falling back to English.
- Stage 2: Pinsleur + 1 SRS app + tutor 1x/week.
- Stage 3: 30 min/day, 9 PM block.
- Stage 4: Checkpoint at week 2 (300 words active vocab), week 8 (first tutor convo entirely in Spanish).
- Stage 5: Rescue: cut SRS app, double down on tutor.
- Stage 6: Done = had the coffee-shop convo successfully on the trip.