Logos52

Shoot

6 min read

Shoot

Part of Deep Processing

Sources become useful when they answer the questions created during Aim and start forming a working map. Shoot is the second step of Bear Hunter System.

The practical goal: satisfy curiosity, clarify relationships, add detail, and keep constructing the map while learning.

How To Use Shoot

1. Put Aim Questions Beside The Source

Start with the questions from Aim visible.

Do not read with a blank mind. Read to answer.

2. Answer Questions In Your Own Structure

As the source gives information:

  • answer the relevant Aim question;
  • place the answer under the chunk it belongs to;
  • add a relationship if it changes the map;
  • mark uncertainty if the answer is incomplete.

Do not copy source order unless the source order is genuinely the best structure.

3. Keep Updating The Map

Shoot is a working map built while the source is still open.

While shooting:

  • move concepts;
  • rename chunks;
  • split overloaded areas;
  • merge weak areas;
  • add missing relationships;
  • delete details that do not matter.

The map should change as understanding improves.

4. Do Not Fear Missing Details

Details missed during Shoot will surface in later stages — retrieval, Skin, or the next encoding pass. A complete learning system has multiple layers, and each layer catches what the previous one missed. The risk of encoding details too early is greater than the risk of missing them: detail learned before the surrounding structure exists is isolated, harder to retain, and likely to require memorization instead of inference.

Details encode better when the concept layer they belong to already exists. What felt impossible to retain in isolation often becomes obvious once the logic and concept layers are in place.

The exception: details that directly clarify a relationship or prevent a misunderstanding about a chunk should be captured immediately.

5. Add Detail Only When It Serves The Structure

Details are useful when they:

  • explain a relationship;
  • support a chunk;
  • clarify an example;
  • prepare for assessment;
  • prevent likely forgetting;
  • expose a gap.

Details are not useful when they are copied because they appeared in the source.

5. Leave Unanswered Questions

Not every Aim question needs a perfect answer.

Sometimes the learning happens because the question makes you look for relationships. If the question remains too advanced, mark it and move on.

Shoot During A Lecture Or Video

Use the source as a live answer stream.

Practical method:

  • write short notes, not sentences;
  • map as you go;
  • attach details to existing chunks;
  • use question marks for unresolved points;
  • avoid transcript mode;
  • after the event, spend 5-10 minutes cleaning the rough map.

If the event is too fast, capture only the backbone and unresolved questions. Finish Shoot afterward.

Shoot During Reading

Reading gives more control.

Practical method:

  • pause after each section;
  • ask which Aim question the section answers;
  • add the answer to the map;
  • check whether the section suggests a new chunk;
  • avoid highlighting without processing.

If you highlight, each highlight should either answer a question or support a chunk.

Delaying Note-Taking

Most formal education trains students to read and write continuously. Constant note-taking feels productive but removes the brain’s incentive to process what it has just consumed. When writing begins before thinking has happened, the notes capture the source rather than the learner’s understanding of it.

The principle underneath Shoot: spend more time making sense of what has been consumed before writing anything. Writing should capture conclusions, not transcription. This is uncomfortable — sitting with information and trying to figure out where it belongs creates genuine cognitive friction. That friction is the processing.

Research on linear versus non-linear note-taking consistently shows that verbatim and linear notes produce lower retention and lower performance on average. Non-linear notes prioritize relationships over sequence, which forces the learner to decide where each piece belongs — a decision that is itself part of encoding. Non-linear note-taking is a technically demanding skill; learners who try it without guidance and find it ineffective are usually running a flawed version, not a fundamentally weak method.

The practical application in Shoot: pause after each section, make sense of what it means for the map, then write. Delay writing until there is something to say about where the information goes and why.

What Shoot Should Feel Like

Good signs:

  • Shoot feels easier because Aim gave direction;
  • you are answering questions, not collecting text;
  • source details have places to go;
  • your map changes as you learn;
  • you notice when chunks are weak.

Warning signs:

  • the map follows the textbook exactly;
  • you are copying full sentences;
  • you are afraid to move chunks;
  • every detail feels equally important;
  • your notes are linear blocks with arrows added later;
  • Shoot feels scattered because Aim was weak.

Practical Quality Checklist

After a Shoot session:

  • Did I answer the main Aim questions?
  • Did I add only useful details?
  • Did the map change from my first guess?
  • Can I explain the main relationships out loud?
  • Did I mark unresolved questions?
  • Did I avoid copying source order?

Common Fixes

ProblemFix
Shoot becomes copyingStop and answer one Aim question from memory.
Too much detailAsk what chunk the detail supports. If none, remove or park it.
Map is chaoticIdentify the 3-5 largest chunks and rebuild around them.
Relationships are unclearAsk “how is this related to ___?” between nearby concepts.
Aim questions are weakPause Shoot and re-Aim with better why/how questions.

Output

Shoot should produce:

  • a working map;
  • answered Aim questions;
  • clarified relationships;
  • details attached to chunks;
  • unresolved questions;
  • material ready for Skin.

How It Should Feel

Shoot should feel like using the source to satisfy directed curiosity. You are not transcribing the material. You are testing, answering, and revising the questions and chunks created during Aim.

Good signs:

  • source details land under meaningful questions;
  • the map changes as understanding improves;
  • you notice when a chunk label is weak;
  • and confusion becomes more specific instead of more global.

Warning sign: Shoot has become passive when your notes follow the source order without changing the structure.

Open Questions

  • What signs tell the user that Shoot has become passive copying?

Graph View

Backlinks