126 lines
4.9 KiB
Markdown
126 lines
4.9 KiB
Markdown
# Strategy Session
|
|
|
|
|
|
# Operational Workflow
|
|
|
|
The operational workflow is a cycle of 5 steps:
|
|
|
|
1. Planning Session
|
|
2. Research & Writing
|
|
3. SEO Review, Channel Adaptation & Action List
|
|
4. Publishing
|
|
5. Analytics & Reporting
|
|
|
|
*Within the different Agent Projects, start a fresh conversation for each cycle. Don't stack multiple briefs into one conversation — the drafts will bleed into each other and the note fetching becomes harder to track.*
|
|
|
|
## Phase 1 — Planning Session
|
|
|
|
Conversation with the Content Strategist to create an editorial plan for the coming period. **The result** is an approved editorial brief for each piece of content.
|
|
|
|
[-> Prompt](Phase%201%20-%20Planning%20Session.md)
|
|
|
|
Go back and forth until the full plan is agreed. Then say:
|
|
|
|
_"The plan is approved. Now produce the final editorial brief for each piece."_
|
|
|
|
The Strategist outputs one clean brief per piece, ready to hand to the Writer.
|
|
|
|
## Phase 2 — Research & Writing
|
|
|
|
The Writer picks up each brief and produces a first draft. For each piece it also flags: what claim needs a source, what angle is assumed vs. verified, and any questions for the Human where the brief was ambiguous.
|
|
**The result** is a set of first drafts.
|
|
|
|
[-> Prompt](Phase%202%20-%20Research%20&%20Writing.md)
|
|
|
|
The Writer confirms which notes it fetched, then produces the draft with inline flags and the DRAFT NOTES section at the end. You review it and either:
|
|
|
|
- Approve it and move it to the SEO & Distribution Project
|
|
- Send it back with specific edits or directions: _"Rework the opening, it's too generic"_ or _"The section on risk assessment is thin, fetch note X and expand it"_
|
|
- Resolve any VALIDATE or SOURCE NEEDED flags yourself by providing the missing information directly in the chat
|
|
|
|
Once you're satisfied, say:
|
|
|
|
_"Draft approved. This is ready for the SEO and Distribution Specialist."_
|
|
|
|
Then paste the approved draft into the SEO & Distribution Project.
|
|
|
|
## Phase 3 — SEO Review & Channel Adaptation
|
|
|
|
The SEO & Distribution Specialist reviews each draft for on-page optimization (structure, headings, meta, internal links) and then adapts the core content into channel-specific formats:
|
|
|
|
- A LinkedIn post (or sequence of posts)
|
|
- A newsletter section or standalone issue
|
|
- A forum/community version (less promotional, more contribution-framed)
|
|
- Premium website content if applicable
|
|
|
|
Each adaptation is a distinct asset, not just a copy-paste.
|
|
|
|
Once satisfied, say: _"Approved. I will execute the action list."_
|
|
|
|
[-> Prompt](Phase%203%20-%20SEO%20Review%20&%20Channel%20Adaptation.md)
|
|
|
|
Output:
|
|
- **SEO-optimized draft** — the revised version of the Writer's draft with SEO improvements applied
|
|
- **Channel adaptations** — a standalone asset for each channel specified in the brief
|
|
- **Action list** — the executable checklist telling you what to publish, where, and when
|
|
|
|
## Phase 4 — Publishing
|
|
|
|
The Human executes the action list.
|
|
|
|
Published content across the channels specified in the action list. Logged in your Obsidian cycle log with:
|
|
|
|
- What was published
|
|
- Where
|
|
- When
|
|
- Any deviations from the action list (something you changed last minute, a channel you skipped, timing you shifted)
|
|
|
|
That log is important — the Analytics agent will need it in Phase 5.
|
|
|
|
Here's a template for the log:
|
|
```
|
|
## Publish Log — [Cycle date]
|
|
|
|
### [Content title]
|
|
- [ ] Newsletter — sent [date/time]
|
|
- [ ] LinkedIn — posted [date/time] — [link]
|
|
- [ ] Forum/community — posted [date/time] — [link]
|
|
- [ ] Website — published [date/time] — [URL]
|
|
|
|
Deviations from action list:
|
|
[note anything you changed, skipped, or delayed and why]
|
|
```
|
|
|
|
|
|
## Phase 5 — Analytics & Reporting
|
|
|
|
After a defined window following publication, you gather performance data from each channel and bring it to the Analytics agent. The agent interprets the data, identifies patterns, forms hypotheses, and produces a report structured for the Content Strategist to act on in the next cycle.
|
|
|
|
**Output**
|
|
|
|
A structured analytics report containing findings, interpretations, hypotheses, and ranked recommendations — ready to paste into the Content Strategist Project to open the next cycle.
|
|
|
|
|
|
**Collect before running this phase**
|
|
|
|
From each channel:
|
|
|
|
- **Newsletter:** open rate, click rate, unsubscribes, replies
|
|
- **LinkedIn:** impressions, engagement rate, clicks, follows gained
|
|
- **Forum/community:** views, replies, upvotes, profile clicks
|
|
- **Website:** pageviews, time on page, bounce rate, conversions (signups, clicks to product)
|
|
|
|
Pull this from your respective platform dashboards and paste it in raw. The agent will make sense of it.
|
|
|
|
[-> Prompt](Phase%204%20-%20Analytics%20&%20Reporting.md)
|
|
|
|
---
|
|
|
|
|
|
## The Loop
|
|
|
|
The Analytics report feeds back into Phase 1. The strategy conversation in the next cycle starts with what the data said, not from a blank slate. Over time the Strategist builds a picture of what content actually moves the needle for ISO27DIY specifically — not just generic B2B content wisdom.
|
|
|
|
|
|
|
|
|