PowerUp Coaching — Living Knowledge Base

Your Back Catalog Is Not a Course — And Your Members Know It

7 min read

Topic

Why members drown in a valuable archive, why search and curation both miss the point, and the third option: stop organizing the catalog and build a layer that composes a personal learning path on demand.

Target Reader

A knowledge entrepreneur with two-plus years of accumulated material — session recordings, newsletters, podcast episodes, a member library. The archive is genuinely valuable and they know it. They also know members aren’t using it, and the guilt shows up as a stalled plan to “finally organize everything into courses” that has been stalled for a year.

The Fear / Frustration / Want / Aspiration

“There are two years of gold in there. My members pay for it and barely touch it. New members take one look and give up. I keep meaning to turn it into proper courses, but every week I add another session, and the gap between what exists and what’s navigable gets wider. I’m sitting on my best asset and it’s decaying.”

Before State

The reader believes their problem is organization, so their plan is a big one-time reorganization project — pick themes, sequence material, produce curricula. It never happens, because it’s months of work, it’s obsolete the week after it ships, and some part of them knows it’s a guess about what members need. Meanwhile the archive is organized by when it was produced — the producer’s convenience, exposed to the consumer as a wall.

After State

The reader can distinguish the two questions they’d been conflating: “where is the thing about X?” (a search problem, mostly solved) and “what should I learn about X, in what order?” (a sequencing problem, which no amount of search touches). They understand why building courses is the expensive wrong answer and why a composition layer inverts the economics — build once, and every member gets the path only they needed. And they know the diagnostic to run before building anything.

Narrative Arc

Open on Mazie: “I’m so far behind in all of the learning here.” Every knowledge entrepreneur has a Mazie and has misread her — assuming she needs better search or a friendlier index. The tension: the instinctive fixes both assume the problem is finding, and it isn’t. The turn comes in her reaction to the composer — “that would be like a lifesaver” — which is not how anyone has ever described a search feature. She didn’t need to find content. She needed a path. Resolution: chronology is the defect. And you don’t fix it by reorganizing — you fix it by composing on demand, which makes a growing archive an asset instead of a liability that compounds.

Core Argument

Your members aren’t failing to find your content — they’re failing to sequence it, and a curriculum built on demand from the whole archive beats a curriculum you guessed at in advance and can’t keep current.

Key Evidence / Examples

  • Lou naming his own version of the problem, which is the reader’s version too: “I don’t know where to find the stuff that I want to find, and I don’t just want to browse articles for an hour. I know it’s in there. I know we talked about it. And by the way, I don’t just want a quick response — I want to learn. I want to turn that into a teaching path.”
  • Mazie Zdanowicz’s exchange — the emotional core of the piece. The ask (“possibly I can use composer to help me develop some tutorials as to how to go through all the past information”), the confirmation, and the response: “That would be like a lifesaver.”
  • Lou’s diagnosis, one sentence: “Right now those things aren’t organized by course or by learning path. They’re just weekly calls.”
  • The scale of the general problem: “We are faced with these enormous sets of resources… we don’t want to go through the entire back catalog to figure out which stuff I needed and which one I didn’t.”
  • The mechanism, concretely: a single question composed from nine sources, returned as a cited article rather than a chat answer; threads accumulating into a workspace; the workspace collapsible into a tutorial, a newsletter, or a learning sequence.
  • The honest status, which belongs in the piece: “I don’t know if it’s overkill, or if it’s just kind of useful.” Shipped as a dev-link experiment, gated on member usage.

Proposed Structure (6 beats)

  1. Meet Mazie. The member who’s behind, feels it, and has stopped trying. Every reader has one.
  2. The two fixes that don’t work. Search assumes she’s looking for something. Curation assumes you know what she needs. Both are wrong about the same thing.
  3. What she actually asked for. The reaction that gives it away — nobody calls a search box a lifesaver. She wanted a path, not a file.
  4. Chronology is the defect. “They’re just weekly calls.” Your organizing principle is the date you made it, which is about you. Name this clearly; it’s the insight the reader will repeat.
  5. Compose, don’t organize. Curriculum as a query result, not an artifact. The inversion: growth makes the archive better instead of worse, because there’s more to compose from.
  6. Run the diagnostic first. Ask three behind members what they’re trying to learn, not find. Try to answer one by hand and time yourself. If it takes you — the person who made it — more than ten minutes, they gave up long ago.

Editorial Notes

Tone: Empathetic toward the member, direct with the reader. Mazie’s line is the emotional engine — use it, attribute it, don’t over-explain it. The reader should feel recognized, not scolded; the stalled course project is a rational response to an impossible task, not laziness.

Angle to avoid: Do not write a Composer feature announcement. It’s an unproven experiment on a dev link that errored during its own demo — the piece must survive the feature being abandoned. The insight is the diagnosis (chronology is the defect; sequencing ≠ finding), which is true regardless of what anyone builds.

Weakest score is actionable (3), and that’s the drafting risk. The reader can’t install a composer. Mitigate by making the diagnostic genuinely useful on its own — the three-member interview and the ten-minute hand-composition test deliver value even if they build nothing. If the draft leaves the reader with only “you should build a composition layer,” it has failed; the diagnostic is the deliverable.

Note the two-audience framing Lou surfaced live: for a member, the composer builds a personal learning path; for a coach, it’s a content engine over their own material. Worth one line — the reader is both. Do not build a section on it.

Don’t overstate demand. One member’s enthusiastic reaction is a signal, not validation. Lou himself conditioned further development on whether anyone actually uses it. Keep that honesty in the piece — it’s more persuasive than a claim we can’t support.

Next Step

  • Approved for drafting
  • Needs revision
  • Deprioritised

Graph View