Mind Maps

A mind map is a planning document made before production, and its main job is to help you come up with new ideas around one theme. It is a pre-production document, so it is used while you are still thinking and deciding, not once the final product is being made.

A mind map records ideas for the whole project, which supports the creative process from the start. It gives you somewhere to put rough thoughts before judging them, so you can make connections and keep ideas flowing. For example, if your class is planning a school podcast series, a mind map around that theme could collect who might listen, what topics to cover and ideas for the opening jingle. Seeing them together helps you spot which ideas belong together and which are worth taking further.

Once initial ideas are recorded, you can explore them, break a broad idea down and develop the strongest parts. In the podcast example, topic ideas could be split into interviews, reviews and quizzes, and the interview idea could then be developed into an interview plan with a list of good points and drawbacks. A mind map is not for presenting final designs or finished decisions; it is a working document for thinking, so it can stay rough and change as your ideas grow.

A mind map is a diagram built around one central theme — also called the central node, hub or title — placed in the middle. Everything else grows outwards from that single starting point, so a mind map never has two centres.

The nodes are the key parts of the theme. They sit around the central theme, and each one covers a different component. Sub-nodes then add detail or further ideas about a node, so each sub-node must clearly belong to its parent. Branches are the lines that join the central theme to its nodes and each node to its sub-nodes. A node or sub-node left without a branch is not connected to the map, so every one should be linked.

This linking creates a hierarchy: central theme first, then nodes, then sub-nodes. The hierarchy makes the level of each idea clear — broad ideas sit close to the centre, while narrower details sit further out. Nodes are often drawn as circles, which makes them easy to spot, and branches show how different parts and processes of a project connect.

For example, a school robotics club preparing for a rescue-robot challenge might put “Rescue-robot challenge” at the centre. Nodes could be “Robot”, “Course”, “Team roles” and “Scoring”. Under “Robot”, sub-nodes might be “colour sensor” and “gripper”; under “Course”, “ramp” and “bridge”. Each sub-node is joined by a branch to the node it belongs to, and each node is joined to the centre.

A mind map is built outwards from one central theme. Put that theme in the centre, then add the main parts of the project as nodes around it. For each node, add smaller sub-nodes that break that part into useful details. Keep everything joined by branches so the structure is clear.

For example, a mind map for a community garden wildlife area could have Wildlife area in the centre. Its nodes might be Plants, Animal homes, Signs and Volunteers. Under Animal homes, sub-nodes could be bug hotel, bird box and log pile. Each sub-node belongs under that parent, so the map shows at a glance how the ideas fit together.

Presenting the map

A good mind map is well laid out and easy to read. Leave space between branches, keep text large enough to scan and group related ideas under the same node so the reader can follow your thinking without needing you to explain it. Keep one central theme; extra themes should become nodes, not rival centres.

Hand drawn or digital

You can draw a mind map by hand or make it digitally. A hand-drawn map should use neat, legible writing so other people can read every label. It can start as a quick sketch in a notebook, then be redrawn neatly once the branches are decided. Hand-drawn maps can also be made collaboratively: a group can gather round one large sheet and each person adds nodes or sub-nodes, so several people’s ideas on a theme are captured on a single document. Digital maps are made on a device and can be rearranged as the plan grows.

A mind map is a creative tool that anyone involved in a media project can use to explore and develop ideas. It is not just for designers: a client, graphic designer, web designer, illustrator, photographer or production manager may all use one at some point.

Who uses one and why

Different users come to a mind map with different needs. A client might use one to help explain what they want from a product. A graphic designer, web designer or illustrator can use one to explore options and see how visual choices connect. A photographer might use one to plan the practical side of a shoot. A production manager may use a mind map to set out the parts of a project that must be organised, for example who owns each task and what needs to happen first.

When it is appropriate

A mind map works well when you need to come up with ideas about the components of a theme, and to set out the ideas that sit under each component. It also suits breaking down one single aspect of a product into smaller pieces. You can make different mind maps at different stages of the same project.

Early in a project, use one to explore the purpose of a product, its audience and the intended response. When you are planning the practical side of production, use one to consider all the practical aspects of a shoot before work begins. You can also use one to generate ideas for creative content and to break down how a scene or production will be filmed, such as by listing its shots, set-ups and jobs.

For example, a community garden group making a short film for its open day could use an early mind map to explore why the film is needed and who should feel welcome. Later, the production manager could use a new mind map to organise the practical jobs, while the person editing the film could use one to plan the order of the clips.

An effective mind map gets two things right: its structure and its content. A good structure has one central theme, logically grouped ideas, sub-nodes that clearly belong to their parent node, a suitable number of nodes and sub-nodes, and branches linking every node. Good content matches the scenario in the brief and the client’s needs, leaves out anything that does not fit, covers enough of the project in useful detail, and helps the person who will use it.

Reviewing and improving

When you review a mind map, identify its strengths and weaknesses, suggest specific changes and explain how each change helps its user. Improvements can include removing irrelevant nodes, adding missing relevant nodes or sub-nodes, connecting unlinked nodes, expanding vague nodes with detail, and adding annotation. Annotation is extra written explanation attached to a point, not an extra idea in the hierarchy; it can explain a point in more detail, or explain how a change better meets the requirements.

Worked example

Imagine you are planning a 30-second radio advert for a school charity book swap, and the client wants students to know when to bring books, where to bring them and how to take part. Your mind map has a clear central theme, but one node says “My favourite games”, a vague node says “Music”, and “Recording date” is not joined to the rest.

You could annotate “Audience” with “Years 7 to 9; friendly, clear voices”, giving the producer more detail. An annotation on a new “Book donation point” node might say “the client wants listeners to know exactly where to drop off books”, showing how the change meets the brief.