Owned-lane and workflow examples
Use these examples when the docs need to feel concrete and teachable instead of abstract, especially across adjacent workflows.
Examples are where the documentation becomes operational. They show how phase, offer linkage, setup quality, and measurement reality combine in the kinds of posts and workflow decisions an operator actually sees.
A scenario page type that shows how the system behaves in real cases instead of abstract language.
These examples mirror the recommendation patterns the operator will most often encounter.
Thought leadership post
Recommendation: CMS first
Why: The post is educational, durable, and better suited to owned discoverability than direct offer delivery.
What you can measure: Bounded CMS pageview snapshots plus delivery verification signals.
Next best action: Prepare CMS draft.
[Example placeholder: Thought leadership post -> CMS-first]
Offer-led post
Recommendation: Newsletter first
Why: The post is tied to a live offer or a clear commercial follow-up, so direct delivery is more useful than broad discoverability.
What you can measure: Delivery verification signals now. Newsletter-native opens and clicks stay deferred until a real provider-native source exists.
Next best action: Prepare newsletter draft.
[Example placeholder: Offer-led post -> Newsletter-first]
Weak owned-fit post
Recommendation: Keep social-first
Why: The post does not yet have strong enough phase or offer linkage to justify a clean owned move.
What you can measure: No owned metric layer should be forced onto the post yet.
Next best action: Revisit offer linkage first.
[Example placeholder: Weak owned fit -> Keep social-first]
These examples show how setup quality and the broader operating flow change what the product recommends next.
New user choosing CMS vs Newsletter
Recommendation: Complete workspace setup, then choose CMS first
Why: The onboarding answers establish commercial posture, publishing priority, cadence, and approval expectations before the owned-lane recommendation becomes trustworthy.
What you can measure: A stronger first recommendation in /strategy and a cleaner owned-lane readout in /posts once workspace truth is persisted.
Next best action: Finish setup, confirm the operating posture in Settings, then review the first CMS vs Newsletter recommendation.
[Example placeholder: A new user choosing CMS vs Newsletter]
Thought leadership workflow from idea to owned distribution
Recommendation: Generate the batch, review the draft, reinforce it through CMS first, then stage any follow-up lane intentionally
Why: The idea belongs to a durable narrative arc, so the workflow should move through queue health, review quality, and owned-lane fit instead of skipping straight to distribution.
What you can measure: Queue health, readiness truth, delivery verification, and bounded CMS evidence once the owned item is live.
Next best action: Move from /posts queue management to review, then publish through the lane that best matches the current phase.
[Example placeholder: Thought leadership workflow from idea to owned distribution]
Both viable does not mean publish everywhere immediately.
The post has enough quality and context to support more than one owned lane, but the product still chooses a primary lane so the operator can act without guessing.
Move the primary lane first. Only stage the second lane after the first move is underway or live, unless there is a concrete reason to prepare both immediately.
Examples become stronger when they are later paired with visual assets.
Placeholder for later enrichment
[Illustration placeholder: CMS vs Newsletter decision tree]
Placeholder for later enrichment
[Illustration placeholder: How phase + offer + metric contract affect recommendation]