Mind Mapping a Talk
Meera knows her message for the Pune meetup: "Your app can react to the weather with ten lines of Python." Now she needs the contents. If she starts typing slide 1, she will lock in an order before she has even seen all her ideas. A mind map lets her see everything first.
The rule
Spread every idea out first; choose and order later.
A mind map is a diagram with one idea in the centre and everything related branching out from it. The main branches are big themes; smaller branches hang off them with examples, stories, demos and data.
Why not just write a list? A list is already an order, and deciding the order too early makes you judge ideas before you have compared them. A map shows clusters (lots of ideas about demos), gaps (nothing about what can go wrong) and outliers (that one idea connected to nothing).
For a talk, put the one message in the centre. Good starter branches are the questions an audience brings: Why should I care? How does it work? What can go wrong? What do I do next? Add branches for stories and demos. Paper, a whiteboard or any drawing app works; the tool matters far less than the habit.
Here is part of Meera's map, written out as a list:
- Centre: React to rain with ten lines of Python
- Why care: soaked delivery riders, rained-off cricket matches, wasted irrigation
- How it works: one API call, the JSON fields,
rain_chancefrom 0 to 1 - Demo: a delivery-alert script, a live rain map
- What can go wrong: forecasts are probabilities, daily limits, no network
- Stories: a rider caught in a downpour, Meera's own first failed demo
- Next step: the sample repo, the free tier
The shortcut
Make two timed passes, and never mix them.
- Pass 1, generate (10 minutes): write down every idea that comes to mind. No judging, no ordering, no deleting.
- Pass 2, choose: circle the branches that serve the centre, cross out the rest, and then number the circled branches in the order the audience needs them.
Pass 1
In ten minutes she writes 23 ideas, including "our latest funding round" and "how weather radar works".
The trap is judging during the first pass. The best idea often shows up at minute eight, after the obvious ones are out of the way, and it will not show up if you are busy crossing things out. The opposite trap is keeping everything simply because it made it onto the map.
Drills
Answer fast — trust the rule.
What goes in the centre of a mind map for a talk?
During the first pass, Meera writes "radar physics" and immediately feels it is too deep. What should she do?
Why map ideas before writing an outline?
In the second pass, "our latest funding round" is on the map. It serves Rainkit, not the audience's goal. What happens to it?
Remember
- Spread every idea out first; choose and order later.
- Shortcut: two timed passes. Generate without judging, then circle, cross out and number.
- Trap: judging during the first pass, or keeping everything because it made the map.