Strategic Reading

Read a source through the lens of a specific problem. Produces an applied playbook, not a summary.

Read a book, article, paper, transcript, or case study through the lens of a specific strategic problem. Produces an applied playbook that maps the source's insights onto the problem and gives actionable recommendations.

This is not summarization. This is reading with a mission.

Contract

• Requires TWO inputs: source text AND a specific strategic problem or question
• Output is an applied analysis, not a general summary
• Every recommendation maps back to a specific passage in the source
• Never runs on a source without a clear "what problem does this help with?"

When to use

• You have a strategic problem and a source that might inform it
• An academic paper or book needs to be read for actionable takeaways
• A career, research, or project decision could be informed by external knowledge
• Learning with intent: "I need to understand this SO I can DO that"

When NOT to use

• Casual reading or general interest — that's a book note, not strategic reading
• Pure fact-finding — use a research skill instead
• First-pass source familiarization — read the source first, then apply

Phases

1. Identify the strategic problem. What specific situation or decision is the user working on? Get this explicit before reading the source.
2. Read the source. Extract key frameworks, tactics, observations, and historical patterns.
3. Map to the problem. For each major section: relevance to the user's problem (HIGH / MEDIUM / LOW), one applicable quote, specific mapping.
4. Build the playbook. What can the user do? Organize as short-term (now), medium-term (this month), long-term (this quarter) recommendations.
5. Write to knowledge base. Save under the relevant project or reading directory.

Output Structure

text

---
title: "{Source Title} — Applied to {Problem}"
type: applied-reading
date: YYYY-MM-DD
source: "{citation}"
problem: "{the strategic question}"
---

# {Source Title} — Applied to {Problem}

> Executive summary: how the source maps to the situation, the key insight, the bottom line.

## The Core Parallel
How the source's central dynamic maps onto the user's situation.

## Section Triage
For each major section of the source:
- 2-3 sentence summary of what it says
- Relevance to the problem: HIGH / MEDIUM / LOW
- One directly applicable quote

## The Playbook
Organized by the source's framework, mapped to the user's context:
- Tactics to apply directly
- Anti-patterns to avoid
- Timing and sequencing

## Short/Medium/Long-Term Actions
- **Now:** immediately applicable moves
- **This month:** medium-term implementation
- **This quarter:** long-term strategic shifts

## Connections
Related notes, projects, and concepts this analysis touches.

Anti-Patterns

• Producing a generic book summary instead of applied analysis
• Reading without a clear strategic question — get the problem first
• Forgetting to map recommendations back to the source passages
• Writing analysis disconnected from the user's actual situation
• Over-recommending: 2-3 high-impact moves beat 10 low-impact suggestions