Content Production and Marketing Pipeline — 2026

Parent initiative: Content publishing — strategy and delivery.

Beads project tracker: lip-93f.2. Associated work: bd list --label project:2602-content-delivery-pipeline. Existing SCQ and issue-tree tasks lip-kv8.5 and lip-1ie.3 remain authoritative and are linked from this tracker; the former comms design queue has been consolidated here.

Execution handoff: pipeline work briefing. The bounded plan is in Beads under handoff:content-pipeline, with who:ai, who:collab, and who:rufus execution labels. Default model recommendation is Sol; Astra is optional for difficult synthesis. The Beads descriptions and dependencies supersede the earlier generic planning sequence.

Objective

Establish a sustainable way to turn editorial direction and existing material into high-quality, published and effectively promoted content, with clear responsibilities and appropriate supporting systems.

Draft SCQ

Situation: We create and collect recordings, writing, and other material. Sometimes its intended use is clear before production; sometimes we discover what to do with it only after it exists. Turning that material into published work involves deciding what it should become, editing it accordingly, choosing where it lives, and producing the supporting material and promotion it needs.

Complication: Material does not reliably move through those decisions and into a completed, well-promoted release. Choices about what to make from it, where to publish it, and what ancillary material to create can remain unresolved even before post-production. Other work remains unpublished, or is published with less follow-through than we want. We need a reliable way to make those choices and complete the resulting work, with clear responsibilities and proportionate quality standards. Which decisions or production steps currently constrain delivery most remains to be established.

Question: How do we reliably turn new and existing material into worthwhile, published and well-promoted content—from deciding what to make of it through to follow-up—at a quality and pace we can sustain?

This draft was refined against the original diagram on 2026-09-23. Its constraint and quality-control annotations are evidence of Rufus's earlier diagnosis, not yet findings from a review of current work. Asset discovery and missing context remain possible contributing problems from the DAM discussion, rather than an assumed central cause.

Reported examples — 2026-09-23

These are Rufus's examples from the planning conversation, sufficient to sharpen the problem but not a verified inventory or diagnosis. Release status, analytics, owners, and remaining work have not been independently checked.

These examples distinguish selection, deciding how to release, and carrying out publication and follow-up promotion. The April course clarification shows that “awaiting an editorial decision” is too coarse: much of the unresolved choice concerns the release package, not simply whether the material is worth publishing. The strategy supplies criteria about audience, purpose, channels, and desired engagement; the pipeline needs to translate those criteria into a proportionate set of deliverables and complete them. A landing page or dedicated collection can help people find and use the material over time, so supporting work includes more than promotional assets.

Working hypothesis: decide what the material should become, then deliver it

An explicit editorial and release brief may bridge strategy and execution: what to make from the material, for whom and why, where it will live, which main and supporting outputs are needed, and who will produce and approve them. It can begin before recording when the intended use is known, or be formed after reviewing raw material. Confirm enough direction before substantial post-production to guide the edit and avoid unnecessary work; allow the brief to evolve as the material reveals its possibilities.

The brief should distinguish requirements for initial publication from worthwhile follow-up, so optional supporting work does not become an accidental release gate. Selecting an excerpt, publishing a whole interview, assembling a series, reusing material elsewhere, or deferring it are possible outcomes; recording something need not commit us to releasing it.

This is a candidate approach to test against the April course and Emergent Dialog cases, not a decision to add a formal approval meeting or create a landing page for every release. Whether reusable defaults for courses, interviews, or event recordings would save repeated decisions remains open.

Proposed refinement to the diagram

The original drawing remains source material. This working refinement makes the editorial decision visible before post-production, while accommodating both planned and emergent material:

flowchart TD
    S["Content strategy: audience, purpose, priorities"] --> B["Initial brief, when the use is known"]
    B --> P["Produce or record"]
    P --> D["Review material; decide or refine its use and release brief"]
    R["Existing or emergent raw material"] --> D
    S --> D
    D --> M["Edit and review the main output"]
    D --> A["Create and review supporting outputs"]
    D --> H["Defer or retain for another use"]
    M --> L["Publish and announce"]
    A --> L
    L --> F["Follow up, promote further, and learn"]
    F --> S

Main and supporting outputs can progress in parallel where their inputs are available; clips may depend on an edit, while a page or announcement can begin earlier. Only supporting outputs designated necessary for the initial release gate publication. Review standards can differ by output and destination. This model is a proposal to validate against actual work, not a claim about the current process.

Candidate outputs

• Content-team organisational chart and approval pathway.
• Organised task and production flow.
• A way to decide and deliver proportionate release packages, including where content lives, announcements, supporting material, and follow-up.
• Clearly designed and structured content pipeline, with appropriate automation.
• Decisions and operating procedures for supporting systems where the delivery needs justify them. DAM, CRM, automation, course distribution, and event ticketing are candidates, not a required implementation package.

Scope note

This is about ongoing publishing, independently of the rebranding launch. The content strategy project determines what we publish, for whom, and to what end. This project determines how we deliver it, including marketing as real production work and reuse of existing material. It can examine actual delivery while the strategic brief is being refined.

Sequencing: improve the operation now

Agreed direction from Rufus, 2026-09-23: pursue both strategy and pipeline improvement, with substantial pipeline work able to proceed independently. The pipeline is more concretely defined and is the immediate operational focus; completion of the 6–12 month strategy is not a prerequisite.

We can inspect current queues, clarify decision ownership, improve handoffs and edit notes, define output-specific review standards, locate current assets, and test completion and follow-up on already-intended releases using a provisional brief for each case. For example, the Elizabeth Debold series notes in #190 identify reconstructing edit notes for four recorded episodes as concrete work; 2RCon #215 already identifies release preparation and supporting-material choices. These issue descriptions are evidence to inspect, not proof that their old dates or state are current.

Choices that depend on strategy—programme identity, long-term channel architecture, major new content commitments, or investment in a new public destination—remain explicit local decisions or are deferred as appropriate. Their uncertainty need not block unrelated workflow improvements. Operational evidence feeds back into strategy as a better account of capacity and effort.

What the pipeline diagram contributes

The original Excalidraw drawing and PNG export are now available here. The filename dates the drawing to 2026-06-24; it was added to this repository and inspected on 2026-09-23. It shows:

Ideas → Pre-production → Production → Post-production → Marketing content → Distribution.

The September 13 interpretation captured this sequence accurately. Direct inspection adds emphasis to these distinctions:

The newsletter twice-monthly and YouTube daily annotations are historical planning inputs, not agreed current targets. Named guests and examples on the calendar do not establish a current release schedule. The linked external video and Substack examples have not been independently assessed in this pass.

Current hypotheses and open choices

• Publication and marketing may be the main constraint; the specific limiting step needs evidence from current pieces and handoffs.
• Unresolved release/prioritisation decisions and limited follow-through after publication may be separate constraints. The reported examples support investigating both; they do not yet establish whether the underlying cause is direction, ownership, capacity, or production friction.
• Repeated decisions about release destinations and ancillary material may need explicit ownership and reusable defaults. A release brief is a candidate bridge between strategic intent and production work, not yet an approved process.
• Better asset discovery and continuity may reduce friction, but DAM has not been established as the highest-value intervention.
• AI-assisted hooks and marketing packages may help if they reduce total effort and rework while preserving quality and source fidelity.
• An episode record linking sources, edits, marketing outputs, and publications is a preserved candidate design; neither a new catalogue nor a tracker has been selected.

Sources

• Rufus's reported backlog and promotion examples in the planning conversation, 2026-09-23; captured above with unresolved identification and status questions.
• Original pipeline drawing and PNG export.
• September 13 content strategy and pipeline framing, including grouped job stories.
• Pipeline diagram interpretation.
• DAM research checkpoint.
• Earlier episode-record exploration — candidate design, not approved implementation.
• [MASTER] SoR 2026 Objectives and Key Results — PROJECT: 2026 Rebrand Run-up Phases

Compact issue tree

This groups the earlier exploratory questions into three branches for review. Current-work evidence remains outstanding; the broader strategic brief is useful input rather than a hard prerequisite for refining or improving the pipeline.

• What brief must the pipeline deliver against?
  • Where do decisions about audience, purpose, editorial offer, and channel priorities belong? ✅ In the linked content strategy project; this project turns that direction into a workable delivery process.
  • Is this primarily a rebranding-launch pipeline? ✅ No — it concerns ongoing publishing; launch communications remain a distinct project.
  • Must pipeline improvement wait for the full content strategy? ✅ No — substantial operational work can proceed using current releases and provisional case briefs, while strategy develops in parallel.
  • Which brands, streams, and channels should the first improvement cover, and what strategic brief is sufficient to guide it?
  • When and by whom should the intended use of material be decided or revisited, including material whose value emerges after recording?
  • What must the brief establish about the main output, its destination, supporting material, and initial release versus follow-up?
• What currently prevents finished, well-promoted releases?
  • Where do real pieces wait: deciding their use, editing, producing ancillary material, review, or distribution—and why?
  • For the April course, is the unresolved question only whether to release? ✅ No — Rufus reports that the larger question is how, including an announcement, landing page, and other ancillary material; whether to release also remains open.
  • What prevents further promotion when a published piece shows promising audience response?
  • How do capacity, ownership, unclear quality standards, and missing material or context contribute to waiting and rework?
• What changes would improve delivery within our capacity?
  • What minimum workflow, responsibilities, handoffs, and reusable defaults would take a piece from selection through follow-up?
  • What quality standards and release criteria protect the audience experience without making every possible improvement a prerequisite?
  • Which evidenced constraints need changes in decisions, people, or process, and which justify DAM, AI assistance, or integration?
  • What bounded trial would demonstrate better completed releases and follow-through, at sustainable effort and quality?

Evidence needed for the next refinement

Current working cases are Emergent Dialog and 2RCon, selected with Rufus on 2026-09-23. The initial case evidence records the existing 2RCon issues, board observations, missing Emergent Dialog identification, and a compact comparison. This is a partial investigation, not a verified inventory or a completed walkthrough.

Use the reported cases above as starting points. The April course and upcoming Emergent Dialog interviews can expose the unresolved choices about where content lives and what accompanies its release; 2RCon offers a backlog case, and Dougald Hine a case of follow-through after publication. Follow both the main output and supporting outputs: what was intended, who owned the decisions and work, what actually happened, and what is still missing. Distinguish time spent working from time spent waiting. Record unknowns rather than inferring them from old task timestamps.

These cases feed the existing queue-evidence task lip-93f.2.1, whose wider scope remains 5–10 pieces and one end-to-end walkthrough. The strategic brief is already tracked by lip-93f.1.1. The diagram and reported examples supply context for the existing SCQ and issue-tree tasks; they do not complete their evidence gathering or human review.

Portfolio integration

Current 23 September framing records pipeline improvement as the working focus; operating model remains a hypothesis. The existing body and source links below/above remain the authority for detailed scope. Original planning note: Status: review draft, 2026-09-23. SCQ and compact issue tree are ready for discussion; the operating model remains a hypothesis. Next milestone: consult the existing issue tree and linked Bead for the next agreed outcome; no additional milestone or date is inferred by this metadata migration.