Gemini Notebook mind map: check three source branches

A Gemini Notebook mind map gives you a branching view of source topics, not a verified workflow. After this exercise, you can generate one map, inspect three branches against a small source and save both the view and a review record. The useful result is a retrievable map with explicit checks, rather than an attractive diagram you cannot explain.

A mind map places related ideas around a central subject. A branch groups a topic; a node is an individual idea you can select. AI means artificial intelligence. Here it proposes a structure for supplied information, but it does not approve a policy or prove that one action must precede another.

Content checked: 15 October 2026. Google's product page now calls NotebookLM Gemini Notebook. Older guides may retain the previous name. This walkthrough assumes a working account with access in a desktop browser. The fictional example and acceptance criteria are teaching material, not an observed account trial, participant test or measured time saving.

What should your first map help you understand?

Imagine a small workshop preparing an exhibition display. Its notes mention materials, review and an unresolved space requirement. You want to see how those subjects are grouped, then inspect whether the grouping preserves what the notes actually say. You are not asking the assistant to invent a production schedule or decide which display is approved.

Keep the first attempt to one source and three branch checks. A source map, a project plan and a decision record answer different questions. Choose the source map for this exercise and resist adding every useful planning feature to it.

The artificial intelligence guide offers wider context. This task is deliberately smaller: turn a short document into a visual entry point that you can check and find again.

Which source should you add for the exercise?

Copy the following author-created sample, including its title, version and E labels. Those labels are ordinary references for your review, not special product commands. No customer names, unpublished designs or private employee information are needed. When replacing this example with a real document, first establish that you are permitted to upload it.

FICTIONAL SOURCE: Exhibition display notes, version 01. E1: Preparation includes choosing a sample print and a reusable display stand. E2: The sample should show the print at full view and include a close view of its texture. E3: The display coordinator approves the sample selection. E4: An unapproved selection must not be presented as final. E5: The available display width is not specified here and must be confirmed with the venue contact. E6: A changed stand requires another stability review. This is teaching material, not an operational instruction.

Open notebook.google.com on your computer, sign in with an appropriate account and create a notebook. In Add sources, choose the copied-text route. Paste the block and name the source Display practice 01. Once it is imported, open it and confirm that both E1 and E6 are present. Your output from this stage is one readable source, not yet a map.

Google's source guide documents pasting text and naming the new source. You do not need web research, additional documents or an upload of your organisation's real procedures for this exercise. If an existing notebook contains unrelated material, make a separate practice notebook rather than deleting the existing sources or assuming the generated view ignores them.

The source maintenance guide addresses a different job: replacing outdated information and checking a new answer. Here the source stays fixed while you inspect a visual output. If you edit the source during review, record another version instead of presenting the old map as the result of the new wording.

How do you generate and explore the map?

Find the Mind Map chip in the notebook's chat area and start generation. Google's current instructions place that control in chat and the generated map as a new note in Studio. Open the result and confirm that its central topic concerns the display exercise. A map of unrelated material is not a completed attempt simply because it rendered successfully.

Expand and collapse branches to inspect the available topics. Zoom if necessary. Locate ideas covering preparation, approval and the unknown display width. Their names may differ from yours, and two ideas may share a broader branch. Record that grouping rather than pretending the product promises one node for every E label.

There is no requirement to obtain exactly three branches. Three is the size of your review sample, not a claimed generation setting. If the approval condition is hard to find, inspect the wider relevant branch and note what is missing or ambiguous. Do not invent a control for rearranging exact nodes or assume a chat request permanently edits the map.

Google's current mind-map help says the mobile app does not support the feature. Use a desktop browser for this walkthrough. If the control is unavailable in your account, preserve the source and record the access blocker. Do not buy a plan merely to resolve an unexplained missing button. This article promises neither a particular entitlement nor a fixed generation time.

Which three meanings deserve a source check?

Selecting a node lets you ask about that topic in chat. Use the prompt below to investigate its support, not to create a more persuasive explanation for a doubtful branch. Where a citation appears, open it and read the surrounding condition. A reference marker alone does not establish that the displayed idea preserves the source's meaning.

Use only Display practice 01. State what the selected branch appears to mean in one sentence. Identify the supporting E label and provide a source citation where available. Add no new approval, dimension or work sequence. If the branch loses a condition or the source does not answer, say so explicitly. This is a source-review exercise, not permission to operate the display.

These criteria apply only to this fictional source. For a different document, choose one ordinary fact, one conditional rule and one unresolved issue from that document before testing. Write what would count as acceptable support for each. Do not rewrite your original source simply to make it pass this example's checks.

Google notes that a very short source may be referenced as a whole rather than cited sentence by sentence. If that happens, open the original source, find the E label manually and record that you performed a manual comparison. If the relevant paragraph still does not support the claim, mark it unsupported. Lack of a precise citation is not a reason to fabricate one.

Be especially careful about sequence. Two ideas placed under the same topic are not necessarily successive steps. A branch connecting a stand and a sample does not prove when a stability review occurs beyond the condition stated in E6. The procedure-writing guide concerns explicit operating instructions; this visual exploration is not a substitute for an approved procedure.

How do you save a view and an honest review record?

Use Download within the map window. Save the offered file in Documents under a recognisable base name such as display-map-01, keeping the extension supplied by the product. Open the downloaded file and check whether the labels are readable. A saved view does not establish that the file preserves interactive nodes or the chat citations used during review.

Open Notepad and add headings for notebook name, source version, map filename, reviewed branch, E label, decision and unresolved question. Paste the three branch names, observed responses and supporting source sentences. For each, choose acceptable, needs correction or untested. Press Ctrl+S, choose Documents and save as display-map-review-01.txt. Close the file, reopen it from that folder and confirm the final entry is present.

Return to Studio and find the map again. Retrieving the notebook artifact and opening a downloaded file are separate checks. Sharing is outside this exercise. Google documents notebook sharing as another route, but wanting to show a diagram is not itself a reason to grant access to its complete source collection.

If a branch is wrong, preserve that observation in the review record. This walkthrough does not instruct you to delete an existing note or conceal the first result. The training quiz guide checks a different artifact: questions and answer keys.

What counts as a useful fifteen-minute outcome?

1. First four minutes: add and open the source. Output: E1 through E6 are visible.
2. Next three minutes: generate the map and locate three review targets. Output: a bounded inspection scope.
3. Next five minutes: compare meanings with the source. Output: three decisions and explicit gaps.
4. Final three minutes: save and reopen the view and record. Output: two retrievable files.

This is a planning allowance, not a measured completion guarantee. If generation takes longer, record source ready, map pending. In my earlier essay about effectiveness and perfection, I described projects delayed by pursuing every detail. Applied here, that principle means checking three meaningful relationships before polishing the entire diagram. It is not a claim that I ran this account workflow or measured a gain.

The freelancer prompt guide offers other bounded tasks for later practice. For today, finish with two questions: can you retrieve the map, and can you identify the source support for the three claims you checked? If either answer is missing, leave that stage open. Do not describe three reviewed branches as a certification of every node.