Building a Knowledge Map

See how many blocks there are and which depends on which, then decide what to learn

I want to learn [field/skill], with the goal of [specific use]. Give me a knowledge map first, without explaining anything yet: 1) break it into 4–7 modules, one sentence each on the problem it solves; 2) use a table to show dependencies between modules (you need A before B); 3) mark which 20% drives 80% of the result, and what can be added later; 4) give the shortest path for my goal, and say what that path gives up.

How to use

Don't let it explain during the mapping stage — the moment it does, it becomes a textbook and the structure disappears.

Good for

You have just decided to self-study a field and have no idea what the blocks are or where you currently stand
You have started and quit repeatedly (three courses bought, none finished) and need a structure that shows progress

Not for

You already have a concrete next task (add caching to this endpoint this week), so drawing the map is procrastination
The field moves fast (internals of a frontend framework), so the map is stale in three months and nothing will warn you

Example

Input

Field: distributed systems. Goal: be able to review a sharding-and-partitioning proposal inside my company.

What you get

Five or six modules at most (replication, partitioning, consistency models, consensus, failure detection, observability), with a dependency table that states hard orders such as you must understand replicated logs before consensus. The 20% should sit on real CAP trade-offs, the visibility of replication lag, and partition-key choice. The shortest path must say what it gives up (no Paxos proofs, no Raft implementation) and which review questions you then will not be able to answer.

Common mistakes

Collecting five knowledge maps and finishing none: the certainty the map provides replaces the learning itself
After getting the map, asking it to also explain every module, which yields a 300-word fake textbook full of illusory depth

Try tweaking it like this

Add 'five hours a week for eight weeks', so the same map becomes a time-scaled route and you can see what must be cut
Ask for an interview path and a doing-the-work path side by side with the fork marked, which suits the stage where the goal is still unsettled