Content and marketing pipeline — SCQ(H)

Superseded as the active framing by docs/content-strategy.md. Retained as planning history; edit the central document going forward.

Status: working framing for review. This is the central problem definition; workflow and tool proposals are subordinate hypotheses.

Purpose and sources

Capture Rufus's September 2026 clarification: improve the contribution of content to meaningful growth through efficient, high-quality, on-brand publication and marketing. DAM, CRM, AI, and tracking support that outcome. They are not ends in themselves.

Sources: current planning conversation; strategy/motivation.md; strategy/second-renaissance-strategy.md; ref/content-production-pipeline-and-dam.md; research preserved in docs/plans/2026-09-13-content-record-and-dam-design.md. Existing strategy supplies audience, tone, and channel hypotheses, not proof of current performance. Older brand names, audience figures, ownership, and cadences require reconciliation before operational use.

Situation

We have a substantial body of recordings, writing, ideas, and other media, plus ongoing production. Material and editing activity span tools such as Riverside, Drive, Canva, and publishing platforms. Existing comms strategy describes an audience, brand voice, long-form content, and channels that help people discover and engage with the work. Comms has production issues, a content backlog, and historical logs.

The desired outcome is meaningful growth: reaching relevant people, deepening engagement, and helping them take a useful next step. What growth means operationally—engaged subscribers, returning audience, participation, course uptake, or another outcome—and its near-term priority are not yet settled here.

Complication

  1. Publication and marketing are weak points. Rufus reports material queuing up, with getting it published and marketed properly more problematic than creating more material. Marketing is the leading constraint hypothesis; its precise location and causes need evidence from actual queued work.
  2. Backlog value remains unrealized. Useful older material is difficult to rediscover, prioritize, finish, and reuse. It may contain strong hooks for social content, but finding a promising excerpt is only the start of making an effective, truthful, on-brand publication.
  3. The connection to strategy is incomplete. A clear audience, promise, channel role, and desired next action must guide selection and packaging. Publishing volume or social reach alone cannot establish success.
  4. Limited capacity and inconsistent handoffs constrain quality and throughput. Asset hunting, unclear ownership, editorial choices, approvals, marketing production, scheduling, or follow-up may each explain delays. We have not measured their relative contribution.
  5. Tool-centered framing risks solving a secondary problem. A better DAM, CRM, or tracker could improve one step while leaving the main constraint untouched. AI could increase upstream output and enlarge the queue unless directed at the work limiting publication and effective marketing.

Question

How should we organize and improve our content-to-audience pipeline so that new and existing material becomes high-quality, on-brand published and marketed work that produces meaningful growth, with sustainable human effort and effective AI support?

Questions to resolve before choosing infrastructure

  1. Which audience, promise, and next action should the next cycle serve, and how will we recognize meaningful growth?
  2. Where does material actually wait, why, and which constraint should we address first?
  3. Which jobs and handoffs are necessary to take a selected piece from source to publication, promotion, and audience response?
  4. How should we select older material and extract hooks in service of the strategy?
  5. What quality and brand judgments are needed, who owns them, and which tasks can AI perform or assist?
  6. What minimum information, tools, and integrations are needed to support those jobs and learn from results?

Core jobs and how to serve them

Proposed delivery mechanisms below are hypotheses, not approved tool choices.

Core job storyDesired resultPossible supportEvidence of success
When choosing what to work on, I need to connect audience needs, strategic themes, and a next action so effort serves growthA prioritized editorial briefShort strategy brief and editorial selectionEach selected piece has a purpose and intended audience action
When work queues up, I need to see what is waiting and remove the actual obstacle so useful work reaches peopleFaster progress through the constraintQueue review, owner/next action, limited work in progressWaiting time and age of queued work fall without quality loss
When preparing a release, I need to find the source, current edit, and related material so I can work without huntingReliable handoffLinked working locations; catalogue only if neededLess search/reconstruction time; fewer wrong-version handoffs
When reviewing old content, I need to identify strategically useful pieces and hooks so existing work gains a new audiencePrioritized reuse candidatesBounded backlog review; AI-assisted transcript/clip suggestionsCandidates become approved, published, useful outputs—not merely tags
When packaging a piece, I need strong hooks, titles, thumbnails, descriptions, and a fitting invitation so the right people want to engageEffective, on-brand release packageBriefs, examples, templates, AI drafts, editorial reviewReview pass rate, correction effort, and audience response
When distributing, I need to adapt and release the package on chosen channels so it reaches people consistentlyCompleted publication and promotionChannel checklist, scheduling, verified publication linksPlanned promotion completed; time from approved material to release
When people respond, I need to support the relevant next step and learn what resonates so engagement can deepenAudience relationship and useful learningDestination pages, subscription/follow-up flows, analytics; CRM where relationships require itEngaged subscriptions, return visits or chosen participation outcome
When material enters or outputs are created, I need to retain context and relationships so later work can reuse themLow-friction continuityMinimal capture at handoffs, source/output links, proportionate retentionCapture is sustained and later retrieval succeeds

The earlier jobs remain covered: image selection, timestamped passage retrieval, discovery of underused work, provenance/version/usage checks, and retaining corrections. Their priority depends on which pipeline job is limiting results.

Hypotheses to test after the framing

H1 — Start at publication and marketing. A short review of queued content will identify a specific constraint worth relieving before adding intake or production capacity. Inspect 5–10 pieces across stages; distinguish waiting from active effort and record the reason. Do not assume every delay is an asset-location problem.

H2 — A strategically briefed release package improves completion. Pick one suitable queued piece and define its audience, message, destination/next action, required marketing outputs, reviewer, and completion criteria. Test the full path to publication and promotion, rather than merely completing an edit.

H3 — AI can reduce the expensive work at that constraint. Candidate uses include finding source-grounded hooks, drafting several brand-consistent packaging options, adapting approved material, and checking completeness. Compare human effort, correction burden, and final quality to the current approach. Preserve source context and timestamps; do not treat a compelling AI suggestion as a verified quote or automatically approve publication.

H4 — Backlog mining can feed the same pipeline. Select a small sample against the same strategic brief; carry at least one candidate through packaging and distribution. Avoid creating a large new queue of suggestions that nobody can finish.

H5 — Minimal coordination may be sufficient. An episode-centered record in existing tracking may help handoffs, with a derived internal directory for discovery. Compare it with simpler linked notes or a separate catalogue only against observed needs. This is a supporting hypothesis, not the organizing principle of the project.

Measures and boundaries

Agree one primary growth outcome and a small set of supporting measures. Candidate operational measures: time from selected material to published-and-promoted release; human minutes per release package; queue age; marketing completion; review/rework. Candidate outcome measures: qualified engagement, visits to intended destinations, engaged subscriptions, or participation. Establish baselines before setting numeric targets. Click-through and reach are diagnostic, not substitutes for the chosen outcome; attribution may remain partial.

Brand quality includes truthfulness to the source, a clear promise fulfilled by the content, recognizable voice and visual standards, and fit with the intended audience. More hooks or posts are not inherently better. A human editorial owner remains a proposed first-cycle requirement while AI reliability and brand consistency are evaluated.

Ownership and terminology

Comms is the home of strategy, pipeline design, job stories, experiment results, and operational coordination. DAM and CRM repositories hold supporting implementation work only when a need is established.

Earlier use of "comms tracker" was imprecise: it meant GitHub issues in comms together with a relevant project view. The content backlog is board #38 in the inspected documentation; the general Comms Board is #36. Those are different views, and neither live setup has yet been audited. No board change or definitive choice is implied here.

The proposed directory was an internal way to find published and unpublished work and its working assets. A public website episode directory is a separate audience-facing product, potentially fed by selected verified publication metadata later.

Existing issues are evidence of previous attempts and unresolved needs, not authoritative requirements for the new design. Preserve their research without inheriting their solution framing.

  1. Reconcile the existing strategy into a one-page brief: priority audience, promise, intended next action, channel roles, quality bar, and growth measure. Human choices must be explicit.
  2. Map a small sample of queued work through the actual pipeline and locate the constraint. Reuse current episode research as one example.
  3. Choose one intervention and a bounded release/backlog pilot against that brief and constraint.
  4. Derive operational and technical tasks from the pilot needs. Revisit tracker, directory, DAM, CRM, and automation choices at this point.

Keep the strategy clarification proportional: enough to direct the next cycle, while preserving deeper brand strategy as its own workstream. Do not restart all prior strategy from a blank page.