---
title: "How to Think About Things We Don't Understand"
description: "Give the mystery a shape before you try to solve it: name it as a placeholder, map what it touches, and define what an answer would even look like."
url: https://buildfirstbrain.com/journal/mapping-the-unknown/
canonical: https://buildfirstbrain.com/journal/mapping-the-unknown/
author: "Lawrence Arya"
authorUrl: https://www.linkedin.com/in/vibecoding/
published: 2026-06-04
updated: 2026-06-04
category: "Networked Thought"
tags: ["epistemics", "knowledge graph", "uncertainty", "first brain", "metacognition"]
lang: en
---

# How to Think About Things We Don't Understand

> **TL;DR** You think about things you don't understand by mapping them before solving them: create a placeholder node for the mystery, name it, then trace its edges, what it touches, what constrains it, and what an answer would have to look like. Most minds either force premature certainty or look away entirely; both lose. Classify the unknown, draw the honest boundary of your competence, and hold the question open without grabbing the first answer, the capacity Keats called negative capability. A well-shaped hole in your knowledge graph is half-solved, and it quietly recruits everything you learn afterward.

You think about things you don't understand by giving them a shape before you try to solve them. The Build First Brain move is the placeholder node: name the mystery explicitly, then trace its edges, what it touches, what facts already constrain it, and what an answer would have to look like. It works because a mind cannot reason about a void but can reason about a well-traced hole, because a named open question recruits every relevant thing you learn afterward, and because the alternative responses, forcing premature certainty or looking away, both lose information. This is for questions that matter and resist answers. Trivial gaps deserve a quick lookup, and irrelevant ones deserve nothing at all.

## Why does the mind hate an open question?

Because closure feels like safety. An unanswered question registers as a threat, so the mind grabs the first available answer and stops looking, which works fine for where are my keys and fails completely for what is making this system behave strangely. The deeper danger sits one layer down: the gaps you have not even noticed. The famous formulation distinguishes [known unknowns, the gaps you can see, from unknown unknowns, the things you do not know you do not know](https://en.wikipedia.org/wiki/There_are_unknown_unknowns), and it is the second category that produces the genuine disasters, in intelligence analysis and in ordinary projects alike.

**Premature certainty is how unknowns stay unknown.** The verdict ends the search at exactly the spot where the search was about to matter.

| Response to the unknown | Best for | Why it works | Main limit | Verdict |
| --- | --- | --- | --- | --- |
| Map it as a placeholder node | Hard questions that matter | Gives the mystery a workable shape | Requires tolerating open loops | Best overall |
| Force an immediate answer | Trivial, low-stakes gaps | Closes the loop fast | Reliably wrong on hard problems | Good for trivia |
| Ignore it entirely | Unknowns outside your concerns | Saves scarce attention | Blind spots compound where it matters | Good for the irrelevant |

## What is a placeholder node?

A named hole in your knowledge graph. Instead of leaving the mystery as a vague unease, you make it a first-class citizen of your thinking: a node called the thing that makes this customer leave, or whatever dark matter is, sitting in the graph with explicit edges to everything known around it. Physics does exactly this, dark matter is a placeholder node with decades of carefully mapped edges and no confirmed interior, and the practice is why the field can make progress on something it cannot yet see.

The shape is the progress. Once the hole has edges, you can see which experiments would shrink it, which incoming facts are relevant to it, and crucially, when a proposed answer fails to match the hole's known outline, the same discipline that catches a too-convenient explanation in [how to overcome confirmation bias](/journal/cognitive-biases-as-graph-errors/).

## How do you map the edges of a mystery?

Four passes, all in writing.

**Write what you do know around it.** The constraints, the observations, the boundary conditions: everything solid that touches the hole. Most mysteries shrink during this pass alone.

**Define the answer's silhouette.** What would a real answer have to explain, predict, or rule out? An answer-shaped description filters out ninety percent of candidate explanations on contact.

**Mark the boundary honestly.** Note where your competence ends and someone else's begins; [knowing the perimeter of your circle of competence is what keeps everything inside it trustworthy](https://fs.blog/circle-of-competence/), and pretending the circle is bigger than it is corrupts the map. The mistake I see most often is the opposite of ignorance: people not knowing where their knowledge stops.

**Schedule the revisit.** A placeholder node is a living entry, not a tombstone. Reopen it monthly, attach what arrived, and watch which edges have firmed up. Mysteries crack between visits, not during them.

## How do you stay comfortable not knowing?

By treating the tolerance itself as a skill. Keats named it [negative capability: being capable of remaining in uncertainties, mysteries, and doubts without any irritable reaching after fact and reason](https://en.wikipedia.org/wiki/Negative_capability), and it is the working temperament of everyone who solves genuinely hard problems, since they must live with the open question longer than anyone else. Two supports help. One is calibration: [the antilibrary, Eco's shelf of deliberately kept unread books, is a standing map of what you do not know](https://fs.blog/the-antilibrary/), a daily vaccine against the feeling of having learned enough. The other is reframing: a mapped unknown is not a debt, it is the most fertile region of your graph, the place where [epistemic humility](/journal/epistemic-humility-across-ages/) and plain wonder do their compounding work, the territory explored in [the epistemology of awe](/journal/the-epistemology-of-awe/).

## When should you leave the unknown alone?

When it is outside your circle and your stakes. You cannot maintain placeholder nodes for everything, and trying turns mapping into a hobby that crowds out solving; an unknown that touches none of your decisions deserves no node. The other failure mode is mapping as procrastination: some decisions must be made before the mystery resolves, with weighted confidence rather than certainty, the move described in [how to know what is true anymore](/journal/navigating-the-post-truth-quantum-reality/). Map what matters, act under uncertainty where you must, and let the rest stay dark without guilt.

## Key takeaways: thinking about what you don't understand

The unknown becomes workable the moment it has a shape: name the mystery as a placeholder node, trace what constrains it, define what an answer would have to look like, and revisit on a schedule. Convert unknown unknowns to known ones by probing your map's edges, keep the boundary of your competence honest, and train the Keatsian tolerance that lets a question stay open until a real answer fits the hole. Reserve the practice for unknowns that touch your actual decisions. A graph with well-shaped holes is the mark of a serious mind, and building one is the project of [Building Your First Brain](/), free for the first 1,000 readers.

## Frequently asked questions

### How do you think about things you don't understand?

Map them before solving them. The Build First Brain method I recommend creates a placeholder node: name the mystery explicitly, then trace its edges, what it connects to, what facts constrain it, and what an answer would have to look like. That gives the unknown a shape your mind can actually work on, instead of forcing a premature answer or looking away. A well-shaped open question then recruits everything you learn afterward, because new information has a node to attach to.

### What are known unknowns and unknown unknowns?

A classification of ignorance. Known unknowns are gaps you can see: questions you know you cannot answer yet. Unknown unknowns are gaps you cannot see: things you are not even aware of not knowing, which is where the worst surprises live. The practical use is conversion: deliberately probing the edges of your map, asking what would surprise me here, turns unknown unknowns into known ones, which can then be worked.

### What is negative capability?

The poet John Keats's term for the capacity to remain in uncertainties, mysteries, and doubts without any irritable reaching after fact and reason. In modern terms: tolerating an open question without grabbing the first closure available. It is a working skill, not a poetic luxury, because premature certainty ends the search exactly where hard problems begin, and the people who solve them are the ones who could stand not knowing the longest.

### Isn't admitting you don't understand something a weakness?

The opposite, and measurably so. A named gap can be worked: it directs reading, sharpens questions, and recruits new information as it arrives. An unadmitted gap stays invisible and compounds into bad decisions. The strongest thinkers keep explicit maps of their own ignorance, the boundary of their circle of competence, precisely because knowing where your knowledge ends is what keeps the knowledge inside it trustworthy.

### What is an antilibrary?

Umberto Eco's term, popularized by Nassim Taleb, for the unread books you deliberately keep: a standing, visible map of what you do not yet know. Its value is psychological calibration. A shelf of unread books works against the illusion that you have read enough, the way a placeholder node works against the illusion that you understand enough. Both keep the boundary of your ignorance in view, which is where all genuine learning starts.

## Dive deeper in

- [How to Overcome Confirmation Bias: Build Counter-Edges](/journal/cognitive-biases-as-graph-errors/)
- [How to Learn From Someone Younger: Epistemic Humility](/journal/epistemic-humility-across-ages/)
- [The Epistemology of Awe](/journal/the-epistemology-of-awe/)
- [How to Know What Is True Anymore: Think in Probabilities](/journal/navigating-the-post-truth-quantum-reality/)

---

Source: https://buildfirstbrain.com/journal/mapping-the-unknown/
Author: Lawrence Arya — https://www.linkedin.com/in/vibecoding/