PowerUp Coaching — Living Knowledge Base

Stop Saving What You Know and Start Saving How You Think

4 min read

Topic

The distinction between storing information (what you know) and storing intelligence (how you think) — and why the second creates a cognitive twin while the first just creates a database.

Target Reader

Coaches, consultants, and knowledge entrepreneurs who are building personal AI systems or knowledge bases but find their outputs still feel generic. AI maturity: intermediate — they’ve done prompt engineering and maybe built a few skills, but their AI doesn’t yet “think like them.”

The Fear / Frustration / Want / Aspiration

“AI can produce my content faster than I can, but it doesn’t think like me. The outputs are competent but lack my judgment, my perspective, my way of approaching problems. How do I transfer THAT?”

Before State

Building knowledge bases that store facts, procedures, and conclusions. AI outputs are competent but interchangeable with what any other expert in the field might produce. The missing ingredient is the expert’s reasoning process.

After State

Capturing both operational knowledge (what was done) AND cognitive knowledge (why it was done, what frameworks informed the decision, what patterns the expert exhibits). AI outputs reflect the expert’s actual reasoning, not just their domain knowledge.

Narrative Arc

Open with the frustration: your AI assistant knows everything you’ve taught it, but its outputs still don’t sound like you thought them. The turn: the missing layer isn’t information — it’s the thinking behind the information. Show Don Back’s example where AI surfaced coaching patterns he didn’t know he was exhibiting. The resolution: a capture protocol that extracts reasoning alongside results.

Core Argument

Information is replicable; intelligence is not. The knowledge entrepreneurs who build genuine cognitive twins aren’t just feeding AI their conclusions — they’re feeding it their reasoning process, their frameworks, their judgment patterns, and their blind spots. “Don’t transfer information, transfer intelligence” is the design directive that separates a database from a digital twin.

Key Evidence / Examples

  • Lou’s prime directive: “Don’t transfer information — transfer intelligence”
  • Don Back’s discovery: Opus analyzed his coaching interviews and surfaced moments of unconscious expertise — “I didn’t even realize that I did it”
  • Don’s observation: human memory reconstructs through belief filters, but externalized capture preserves what actually happened
  • The dual capture model: operational knowledge (what) + cognitive knowledge (why, frameworks, patterns)
  • Lou’s prompt: “pay specific attention to the feedback I gave to try to get a sense of my perspectives, my frameworks, my thought patterns”

Proposed Structure (5-7 beats)

  1. The database trap: your AI knows everything you know, but nothing about how you think
  2. Information vs. intelligence: the distinction that changes everything
  3. What cognitive capture looks like in practice (the dual capture model)
  4. Don Back’s revelation: when AI sees your expertise better than you do
  5. The reconstruction bias problem: why human memory is unreliable for self-analysis
  6. The capture protocol: what to add to your end-of-conversation prompt
  7. From database to twin: the compounding effect of accumulated cognitive profiles

Editorial Notes

Tone: philosophical but grounded. This is the most abstract of the three briefs from this session — anchor it with Don’s concrete example of AI surfacing unconscious coaching patterns. The “capture protocol” section needs to be specific enough to implement. Risk: this could drift into AI consciousness territory — stay firmly in the practical lane of “how to make your AI think more like you.”

Next Step

  • Approved for drafting
  • Needs revision
  • Deprioritised

Graph View