How the Writing Production Studio interfaces with business systems, feedback loops, and the broader content lifecycle
What determines WHAT gets written, for WHOM, and WHY. This layer should drive the Writing Studio, not the other way around.
1/3/5 year goals. Revenue targets. Growth vectors. Market positioning. What is ProActive trying to become? Content must serve this.
PARTIALLY EXISTSThe bridge between business strategy and what gets written. Maps thought leadership themes to business objectives. Defines content pillars, cadence, channel mix.
DOES NOT EXISTWho are we writing for? Segmented: HR leaders, union reps, C-suite, policymakers, academics, practitioners, media. What does each segment need to hear?
DOES NOT EXISTHealthcare, education, government, tech, extractive industries. Sector-specific pain points, language, regulatory context, decision-makers. Which sectors are priority?
DOES NOT EXISTCampaigns, launches, seasonal cycles. Speaking engagements calendar. Conference schedule. Content must align to these windows of opportunity.
PARTIALLY EXISTSWhat are other conflict transformation firms publishing? Where are the white spaces? Which conversations is ProActive NOT in that it should be?
DOES NOT EXISTFive principles (No Blame, Normalize, Listen-In, Power-With, Behaviors First). Three-tone system. Anti-convergence rules. Visual identity (trillium, color triad).
EXISTS (proactive-resolutions/)Client list, sector, engagement history, pain points discussed, proposals sent. Which clients need what kind of content touchpoint? Relationship Register exists but is disconnected.
FRAGMENTEDThe Writing Studio currently has NO upstream strategic driver. Content topics are chosen by intellectual interest alone. There is no mechanism asking: "Will this article move the business forward?" This is the single biggest structural gap.
The production infrastructure. Currently well-architected for academic/professional output. Needs connective tissue to everything else.
Voice Profile (Section B complete). Argument Bank (stub). Reading Notes (Zettelkasten). Publication Intelligence. Grey Literature. Current Awareness Queue. Theoretical Framework working notes.
Obsidian vault planned but not yet connected.
EXISTS - PHASE 1WSD-driven state management. Pattern library (Practitioner Article, Trade Article). 4-mode HITL (AI Product / AI-driven / Collaborative / Human-driven). Bias Mitigation Protocol. Stage-gated approval.
8 slash commands operational.
EXISTS - OPERATIONALSource Registry. 7-dimension Confidence Schema. 3-layer Verification Pipeline. Zotero integration. Research Rabbit + Elicit + Scite protocol (Phase 2). Connected Papers.
EXISTS - SOLIDFailure Library. Pattern Retrospectives. Outcome Analysis. Continuous Excellence Protocol. Signal Log. Component Registry. These feed back into studio improvement.
EXISTS - FOUNDATIONALProject Registry. Editorial Calendar. Submission Tracker. Relationship Register.
EXISTSPublisher Disclosure Matrix (8 publishers). AI Contribution Documentation. Artifact retention for compliance.
EXISTSOne piece of thought leadership should cascade: Article -> LinkedIn series -> Newsletter excerpt -> Speaking points -> Proposal language -> Social posts -> Infographic. Currently: each piece is a dead end.
DOES NOT EXISTVoice Profile handles Scholarly vs. Professional. But: LinkedIn voice? Newsletter voice? Proposal voice? Social media voice? Website copy voice? Each channel has different constraints and norms.
DOES NOT EXISTEvery article is currently a one-shot deliverable. Zero repurposing infrastructure means 80% of content value is left on the table. A single practitioner article should generate 8-12 derivative assets across channels.
Where finished work goes, how it reaches audiences, and how it's managed over time.
Central repository for ALL finished content (not just git). Searchable by topic, audience, sector, date, format, channel. Metadata-rich. The "library" that the whole business draws from.
Currently: finished pieces live in git project folders with no discoverability beyond file browsing.
DOES NOT EXISTProActive website content. Blog posts. Resource library. SEO-optimized landing pages per sector.
EXISTS - BASICArticles, posts, carousel content. Richard's personal brand + ProActive company page. Thought leadership primary channel.
EXISTS - AD HOCClient updates. Thought leadership digest. Sector-specific campaigns. Nurture sequences.
EXISTS - BASICJournals, book chapters, conference papers. Peer-reviewed. The Submission Tracker handles this well.
EXISTS - WELL SERVEDKeynotes, workshops, webinars. Canva decks. Content from articles repurposed into presentation format.
EXISTS - CANVABespoke proposals drawing on thought leadership. Sector-specific framing. Case study references.
EXISTS - MANUALTrade publications (Canadian HR Reporter, OHS Canada). Op-eds. Expert commentary. Media kit.
EXISTS - TARGETEDNotebookLM audio overviews. Guest appearances. Own podcast potential. Audio ambient assets already exist in brand repo.
NASCENTFrom "finished piece" to "distributed across all relevant channels" is currently unspecified. No checklist, no automation, no tracking of which channels received which content.
DOES NOT EXISTIf a client asks "what have you written about healthcare?" there is no system that answers this question. Content is produced but not indexed for business use.
How visual assets are created, managed, and connected to written content.
Logos (trillium, tagline, legacy). Color palette (Yellow/Green/Blue triad). Typography (Avenir/Arial). Email templates. Audio assets. Naming convention enforced.
EXISTS (proactive-resolutions/)Presentation templates. Social media templates. Brand kit integration. Used for speaking decks and visual content.
EXISTS - ACTIVEEvery article needs: hero image, social sharing card, pull-quote graphics, infographic (if data-driven), presentation slide deck derivative. Currently: no systematic connection between writing and visual production.
DOES NOT EXISTAvailable via Pencil (.pen), Canva AI, and standalone tools. Brand guidelines must constrain generation: vibrant triad, real workplace moments, authentic tension, never stock corporate.
AVAILABLE - UNGOVERNEDWho approves visuals? What's the review process? How do AI-generated images get checked against brand guidelines? The brand repo has an asset lifecycle workflow but it's not connected to the Writing Studio's output flow.
FRAGMENTEDArticle hero image template. LinkedIn carousel template. Newsletter header template. Infographic template. Each output type from the Writing Studio should have a corresponding visual template.
PARTIAL - CANVA ONLYWhat happens AFTER publication. The loops that should drive what gets written next. Currently the weakest layer.
LinkedIn: impressions, engagement rate, shares, comments, follower growth per post. Website: page views, time on page, bounce rate, SEO ranking. Email: open rate, click rate, unsubscribe. Which content performs?
DOES NOT EXISTWhich articles generate inquiries? Which thought leadership pieces get referenced in client conversations? Which content drives proposals? This is the ultimate business feedback loop and it's completely missing.
DOES NOT EXISTComments, DMs, shares, saves, mentions. Who is engaging? What sectors? What seniority? Are the RIGHT people reading? Qualitative signals that quantitative metrics miss.
DOES NOT EXISTCitation count. Altmetrics. Download stats. Peer review feedback. Conference invitations triggered by publications. Scite citation sentiment analysis.
PARTIALLY EXISTS (Scite planned)Failure Library, Pattern Retrospectives, Outcome Analysis. Currently tracks PROCESS outcomes (what worked in production). Needs to also track BUSINESS outcomes (what worked in market).
EXISTS - PROCESS ONLYPost-engagement surveys. "How did you hear about us?" tracking. Client perception of thought leadership quality. Direct feedback on shared articles.
DOES NOT EXISTWhat topics are trending in target sectors? What are editors at target publications requesting? What conversations are happening that ProActive should be part of? Current Awareness Queue exists but is internal-facing only.
DOES NOT EXISTThe Writing Studio has a sophisticated internal learning loop (Failure Library, Retrospectives) but ZERO external learning loops. It optimizes how it writes but has no mechanism to learn what's worth writing. It's a precision instrument with no targeting system.
The technical substrate connecting everything. Determines whether this is an ecosystem or a collection of disconnected tools.
Writing Studio, brand assets, governance docs all version-controlled. Strong foundation for content provenance.
EXISTS - SOLIDCanonical source of truth for citations. API-accessible. Integrates with Research Rabbit, Elicit.
EXISTSPlanned as knowledge base interface. Smart Connections for semantic search. Vault = knowledge-base/ directory. Not yet operational.
PLANNED - NOT SET UPClaude Code, Gemini, Codex. Human+AI role pairs defined. MCP servers for tool integration. Governance framework operational.
EXISTS - MATUREDrive, Docs, Sheets, Calendar, Gmail. gws CLI operational. NotebookLM for research. Connected to agent ecosystem.
EXISTSNo automated flow from: Strategy -> Editorial Calendar -> Writing Studio -> CMS -> Distribution -> Analytics -> back to Strategy. Each handoff is currently manual. The ecosystem has powerful individual tools but no connective tissue.
DOES NOT EXISTA unified schema for tagging content across all systems: topic, audience, sector, format, channel, status, performance. The brand repo has asset-metadata.schema.json but the Writing Studio has no equivalent for content.
DOES NOT EXISTTask tracking for governance and development work. Could serve as the orchestration layer connecting strategic decisions to content production tasks. Underleveraged for content workflow.
EXISTS - UNDERLEVERAGEDThe Writing Studio is an exceptionally well-designed production engine that has no navigation system. It can produce high-quality content with rigorous process controls, HITL governance, and source verification. But it cannot answer: "What should we write next, and why will it matter to the business?"
The studio optimizes how content is made. It has zero infrastructure for what content to make (strategic alignment), who it's for (audience intelligence), where it goes after production (distribution), or whether it worked (performance feedback). It is a factory with no sales team, no market research, and no customer feedback loop.
Content topics are driven by intellectual interest. There is no document that says: "In Q2 2026, ProActive's priority is penetrating the healthcare sector in Western Canada, therefore we need 3 pieces addressing [specific pain points] targeting [specific roles]." The Editorial Calendar tracks what's being written; it should be driven by why.
There is no way to know if the writing matters to the business. If a LinkedIn article generates 3 client inquiries, that data doesn't flow back to the Writing Studio to inform what gets written next. This makes every content decision a guess.
A single article should cascade into 8-12 derivative assets. Currently every piece dies at first publication. This is the single biggest ROI multiplier available.
Completed work sits in git project folders. No one can ask "show me everything we've written about restorative justice for healthcare" and get an answer. Content has no second life.
The Writing Studio knows about publishers but not about readers. No audience segmentation, no persona development, no understanding of what each stakeholder group needs to hear. Writing for "practitioners" is too vague.
The Failure Library and Retrospectives track writing process quality. Nothing tracks market performance. The studio learns to write better but not to write smarter.
Brand assets exist. Canva exists. AI image generation exists. But there's no systematic workflow that says: "This article is being published, therefore create: hero image, 3 social cards, 1 infographic, presentation slides." Each visual is ad hoc.
A closed-loop content ecosystem where:
The Writing Studio is step 4 of 11. It's the best-built component. But without the other 10, it's an engine running on a test bench.