Communication Framework

What It Is

An abstract thinker can begin with a conclusion that took many intermediate steps to reach. The listener has none of those steps. The ladder problem describes that gap: the speaker starts at rung 10 with a general theorem while the listener starts at rung 1 with concrete experience.

Build the explanation from an experience both people recognize. Show the same pattern in other cases, then work toward the general insight together. The listener should not have to request an example except to clarify something further. If “Can you give me an example?” is needed to begin understanding, the opening has already failed.

This applies pedagogical magnification to conversation. Begin at the scale of observable experience and introduce the underlying machinery when curiosity creates a reason for it. Observation → pattern → theorem preserves the intellectual depth while changing the order in which the listener encounters it.

Asking what the examples have in common lets the listener help derive the conclusion. That shared construction makes the insight something they remember, own, and can use.

Each step should give the next one a reason to exist; an example is part of the explanation, not an optional rescue.

Read this diagram

Shared observation → Another concrete case → A pattern → The general idea.

The Ladder Problem

The following sample starts with the conclusion and leaves the listener without a route to it:

You: "Overthinking is underthinking at wrong resolution with insufficient compute"
     [Started at rung 10]

Them: [At rung 1, has no ladder]
     "...what?"

You: [Scrambles for example]
     [Too late—already lost them]

The second starts with choosing a laptop. It introduces excessive magnification only after establishing the familiar difficulty of getting lost in specifications:

You: "You know when deciding on laptop, you start researching CPU specs?"
     [Rung 1—concrete shared experience]

Them: "Yeah, I get lost in details"
     [Confirms they're with you]

You: "It's like you zoomed microscope to 1000x—see detail, lose whole picture"
     [Rung 3—introduce metaphor]

Them: "Oh, so you spread your thinking too thin?"
     [Climbing with you]

You: "Exactly! Overthinking is underthinking at wrong resolution"
     [Rung 10—arrived together]

The example gives the abstraction something the listener can already picture.

The Bottom-Up Algorithm

Start with the observation that produced the insight. Name a specific situation or action: “Have you noticed [specific situation]?”, “Yesterday I was [specific action] and saw [specific thing],” or “You know when you [relatable experience]?”

Add 2-3 examples with the same structure. “Same thing happens when [example 2]” or “It's like how [example 3]” lets the listener compare cases. A further example can show the pattern elsewhere: “Actually this is everywhere: [example 4].”

Ask the listener to identify what they share. Use “What do you think is going on here?”, “Do you see what these have in common?”, or “There's a pattern, right?” The listener participates in making the connection.

State the general claim once the pattern is established. “I think what's happening is [universal truth],” “So basically [abstraction],” or “This is what I mean by [your term]” attaches a name to the relation already observed.

Offer deeper detail when wanted. Once the listener is curious, ask “Want to go deeper on why this works?” Other invitations include “The really weird part is...” or “If you zoom in you see...” The machinery now answers a question the listener has a reason to ask.

Example Generation Algorithm

To find an example during a conversation, first identify the structure of the insight:

Identify its type and 3-5 core properties. Then ask what else has that structure. Search among physical objects such as tools and materials; everyday processes such as cooking, driving, and shopping; feelings and discoveries; bodies, organizations, and ecosystems; and interactions between people.

An accessible example is something the listener can picture immediately and has encountered, while still revealing a surprising relation. It must preserve the insight. Reject examples that require specialized knowledge or are themselves too abstract.

Check the correspondence explicitly. Match the first property of the insight to the first property of the example, then the second, and finally the surprising result. If those connections fail, search again.

This trace develops an example for pedagogical magnification:

Insight: "Start teaching macroscopic, introduce machinery later"

Deep structure: Process with proper sequencing
- Property 1: There's complex machinery underneath
- Property 2: There's accessible high-level interface
- Property 3: Learning interface before machinery works better
- Surprise: Details-first seems more rigorous but fails pedagogically

Search isomorphic:
- Driving: Learn to drive (macro) before engine mechanics (micro) ✓
- Cooking: Follow recipes before food chemistry ✓
- Music: Play songs before music theory ✓
- Software: Use apps before understanding code ✓

Filter: All accessible, all experienced

Test mapping (driving):
- Machinery = engine internals
- Interface = steering wheel, pedals, dashboard
- Sequence = drive first, mechanics later (if ever)
- Surprise = You can master driving without knowing combustion

Example: "You learned to drive before understanding how engines work, right? That's pedagogical magnification—start with what the thing does (macro), dive into how it works (micro) only when needed."

Driving works because the wheel, pedals, and dashboard provide a usable interface before engine mechanics are understood. The same sequence appears in recipes before food chemistry, songs before music theory, and app use before code. The surprise is that knowing the machinery first feels more rigorous but teaches less effectively.

Bridging Phrases

Signal a change in abstraction level so the listener can follow it.

• From a case to a pattern: “Here's what I mean...”, “Think about it this way...”, “The pattern is...”
• From a pattern to a general claim: “So basically...”, “What's happening is...”, “The universal thing here is...”
• Back to a concrete case: “For example...”, “Like when you...”, “It's kind of like...”
• To check understanding during the explanation: “Does that make sense?”, “See the similarity?”, “Have you noticed that too?”
• To repair an explanation: “Wait, let me try that again...”, “Let me give you a different example...”, “Actually, forget that—simpler version:”

Red Flags: Going Too Abstract

These terms require an immediate example: “mathematical structures,” “formal systems,” “symbolic representation,” “isomorphic mappings,” “emergent properties,” “computational substrate,” “meta-cognitive,” and “epistemic.” They signal that intermediate steps have been skipped.

When you hear yourself use one, stop mid-sentence and say, “Wait, let me show you what I mean...” Point to or describe something physical. Then connect its action to the result: “See this [object]? When you [action], it [result]. That's what I'm talking about.”

The Mutually Constructed Theorem

A listener can accept a finished claim without having derived or taken ownership of it:

You: "Prevention architecture beats willpower by orders of magnitude"
Them: "Okay..." [accepts but doesn't own it]

The donut example instead asks the listener to compare resisting an available temptation with removing it:

You: "You know how donuts on your desk are hard to resist?"
Them: "Yeah, I cave every time"
You: "What if desk had no donuts?"
Them: "Oh, then I wouldn't think about it"
You: "Right! And how much effort does that cost you?"
Them: "None, I guess?"
You: "So resisting costs willpower, but preventing costs zero?"
Them: "Whoa. Prevention is way better than willpower"
     [They discovered it—now they own it]

The key moment is the listener stating the insight in their own words before the speaker supplies it. The observation and comparison let them participate in arriving at the conclusion.

Integration with Teaching

To teach an abstraction in mathematics, physics, or philosophy, begin with an everyday phenomenon the learner knows. Show the pattern in several contexts and let them predict the theorem. Confirm or refine the prediction, then introduce the formal machinery. This is pedagogical magnification in conversation.

To teach a system or framework, start with a problem the learner recognizes and show how the framework solves that case. Add 2-3 applications. Let the shared structure become visible before naming and formalizing it.

Related Concepts

• Pedagogical Magnification - Beginning with observations before the underlying explanation
• Golden Orb - Keeping communication authentic rather than performing a technique
• Neural Positivism - Positive instructions working where negative framing fails
• Question Theory - Using questions to construct understanding together
• Working Memory - Concrete examples fitting capacity while abstractions overflow it
• AI as Accelerator - The texture that reality contact adds beyond simulation

Key Principle

Use 3 examples before stating a theorem. Start from shared experience at rung 1, establish the pattern through rungs 2-4, and reach the general claim at rung 10 together. Check understanding along the way, invite the listener to predict the relation, and return to something physical when the intermediate steps are missing.