The note-making tool I use to discover ideas from anywhere (Heptabase Tutorial)

TL;DR

Start with a single strong curiosity, then capture it immediately in Heptabase’s Journal so the idea has a clear origin date.

Briefing Cornell Notes

Briefing

A movie about submarine rescue sparks a practical “idea sonar” workflow: capture a single curiosity, mine it with synonyms and definitions, and turn the results into connected building blocks inside Heptabase—without breaking deep-thinking momentum to switch apps. The payoff is not just more notes, but a traceable origin for each idea, plus a network of links that clarifies how one insight can guide future thinking.

The process begins with a specific trigger. While watching *Hunter Killer*, the viewer fixates on a sonar technician’s ability to distinguish torpedo and ship sounds. That curiosity becomes a journal entry in Heptabase’s Journal meta app, along with a Navy article URL describing sonar technician duties. The key detail is traceability: once the idea is fleshed out, the system lets the user return to the exact date the card was created and see the related ideas written that day—along with where the card sits in the workflow (weekly review and a “workbench” whiteboard where connections are built).

From there, the workflow shifts into a “stay in the app” research mode. In the Heptabase workbench whiteboard, a dedicated section—“become a sonar technician of ideas”—holds a card that already contains the pasted Navy URL. Instead of leaving Heptabase, the user opens a sidebar, copies the URL, and triggers an in-app Google lookup. Passages from the article are highlighted and pasted into the section, then key words are emphasized with orange highlights and bolding.

Those highlighted terms become the engine for progressive summarization through language. Words like “quietly track,” “still,” “surveillance,” “identify,” “track,” “collect,” and “navigation” are treated as prompts. The user looks up synonyms and definitions directly inside Heptabase using embedded Google searches, keeping multiple lookups open as needed. “Quietly track” leads to the idea of “be still,” tying the concept of stillness to the ability to follow a trail of meaning. The user then converts that into a building-block phrase—“awareness follows Stillness”—and extends it into a navigation metaphor: in stillness, people follow the trail; following the trail reveals ideas that help steer life.

A second path comes from “surveillance.” In context, surveillance is reframed as close observation, which the user links to steering one’s life through careful attention. That connection is reinforced with a Socrates quote about the value of an examined life, positioning observation as a prerequisite for wise direction.

Finally, the Navy job description supplies a structural template. The sonar technician’s tasks—identify, track, and collect scientific undersea data for defense and navigation—become a direct analogy for knowledge work: identify, track, and collect ideas so they can navigate life. The result is a clearer “sonar technician of ideas” identity built from cross-industry cues, plus visible connections between concepts that might otherwise remain buried.

The central message is that deep thinking can be engineered: start with one strong curiosity, mine it through synonyms and definitions, and convert the findings into linked, reusable knowledge blocks—while keeping research and synthesis inside the same app to preserve focus.

Cornell Notes

A single curiosity from a film—how sonar technicians detect meaningful sounds—turns into a repeatable Heptabase workflow. The method captures the initial idea in the Journal, attaches a relevant source (a Navy job description), then moves to a workbench whiteboard where highlighted phrases become prompts for synonym and definition lookups. Those lookups happen inside Heptabase via embedded Google searches, so research and synthesis stay in one place. Key terms like “quietly track,” “still,” “surveillance,” and “identify/track/collect” are translated into building blocks such as “awareness follows Stillness,” linking stillness to knowing and observation to steering life. The approach matters because it produces traceable, connected ideas that can guide future thinking rather than isolated notes.

How does the workflow turn one movie moment into a structured knowledge system?

It starts with a specific trigger—sonar technicians distinguishing torpedo and ship sounds—then immediately records it in Heptabase’s Journal. The user adds a Navy article URL about sonar technician duties to the same idea trail. Later, the idea is moved into a dedicated workbench whiteboard section (“become a sonar technician of ideas”), where the original card can be traced back to the Journal date and related ideas from that day. This creates both a birthplace for the idea and a place to expand it.

Why are synonyms and definitions treated as part of the “idea sonar” process rather than separate research?

Highlighted words from pasted passages become prompts for in-app Google lookups. For example, “quietly track” leads to synonyms for “quiet” (silent, still, noiseless) and then to the concept “be still.” Those lookups remain accessible as accordion-style searches inside Heptabase, so the user can keep multiple definitions open while continuing to connect ideas rather than switching tools.

What does “quietly track” become after the synonym/definition mining?

The user connects “quietly track” to “be still,” using the Bible phrase “be still and know that I am God” as a conceptual anchor. From that, the user formulates a building-block idea: “awareness follows Stillness.” The metaphor is explicit: stillness makes way for knowing, and in stillness people follow the trail—discovering ideas that help navigate life.

How does “surveillance” get reframed into a life-steering principle?

In context, surveillance is treated as essential to navigation. The user interprets surveillance as close observation—observing carefully—and then links that to steering one’s life. To reinforce the principle, the user recalls Socrates’ line that “the unexamined life is not worth living,” positioning close observation and examination as prerequisites for wise direction.

How does the Navy job description structure the final analogy for knowledge work?

The job description lists tasks: identify, track, and collect scientific undersea data for boat defense and navigation. The user turns this into a direct knowledge-work template: identify, track, and collect ideas so they can navigate through life. The purpose of the verbs—defense and navigation—becomes the purpose of the knowledge process: turning scattered inputs into guidance.

What role does staying inside Heptabase play in the workflow’s effectiveness?

Staying in the app preserves deep-thinking flow. The user copies/pastes source passages into the workbench, then performs Google searches inside Heptabase’s sidebar without leaving the environment. Searches can be closed or removed later, but they remain available during synthesis. That reduces context switching while building connections from highlighted terms.

Review Questions

If you had to replicate this workflow, what would you record first in the Journal, and what would you attach to it to enable later expansion?
Which highlighted term in the process most directly leads to a building-block phrase (e.g., “awareness follows Stillness”), and what intermediate synonym/definition step bridges them?
How do “identify, track, collect” map onto knowledge work in this system, and what “purpose” does the analogy assign to the process?

Key Points

1
Start with a single strong curiosity, then capture it immediately in Heptabase’s Journal so the idea has a clear origin date.
2
Attach a relevant source (like a job-description article) to the idea early, so later expansion has grounded material to mine.
3
Move from Journal to a dedicated workbench whiteboard section where ideas can be expanded into connected cards and text elements.
4
Highlight key words in pasted passages and treat those terms as prompts for synonym and definition lookups.
5
Use Heptabase’s in-app Google search capability to keep research and synthesis in the same environment, reducing context switching.
6
Convert mined language into reusable building blocks (e.g., “awareness follows Stillness”) that connect concept to action.
7
Translate domain-specific tasks (identify/track/collect for navigation) into a personal knowledge workflow that guides future thinking.

Highlights

A film-triggered curiosity becomes a traceable idea card: it can be traced back to the exact Journal date and expanded on the workbench whiteboard.

Embedded Google searches inside Heptabase let synonym/definition mining happen without leaving the app, keeping deep thinking intact.

“Quietly track” is transformed into a stillness principle—“awareness follows Stillness”—linking attention to knowing.

“Surveillance” is reframed as close observation, tied to steering life through examination (Socrates).

The sonar technician job description provides a direct knowledge-work template: identify, track, and collect ideas for navigation through life.

Topics

Heptabase Tutorial
Idea Mining
Progressive Summarization
Knowledge Maps
PKM Workflow

Mentioned

Heptabase
Heptabase Journal
Heptabase Workbench
Google
Greg Wheeler
Socrates