Owned-lane next actions
Use this playbook when the product already made a recommendation and you need the most useful next bounded action.
This playbook is action-first. It turns a recommendation such as CMS first, newsletter first, both viable, or keep social-first into the next best operator move without broadening scope.
An action-oriented page type for bounded operator moves and next best steps.
The same recommendation should always lead to a bounded next move.
CMS first
Prepare a CMS draft.
Start the CMS owned draft when durable discoverability and bounded owned reach are the clearest job now.
Newsletter first
Prepare a newsletter draft.
Start the newsletter owned draft when direct delivery supports the current phase or a live offer more cleanly than CMS.
Both viable
Start with the cleaner lane.
Let the product tell you which lane goes first, then stage the second lane only if the post still merits it after the primary move is live.
Keep social-first
Do not force owned distribution.
Revisit offer linkage, strengthen the phase fit, or keep execution social-first until a cleaner owned move appears.
Once a lane is live, the right next action changes.
Use this when the owned lane is already live but the operator should refresh delivery truth before relying on the lane for execution decisions.
Use this when bounded metric truth exists and freshness matters more than repeating the earlier setup steps.
The playbook should reduce hesitation, not create more interpretation overhead.
- Confirm the lane recommendation shown in /posts or /posts/[id].
- Check whether the post is not started, in motion, limited, blocked, or already live.
- Match the action to the recommendation rather than choosing the lane manually out of habit.
- If the recommendation is social-first, do not force an owned artifact just to stay busy.
- If the lane is already published, move to delivery or metric actions instead of draft creation.
This keeps the page ready for future visual teaching assets.
Placeholder for later enrichment
[Annotated screenshot placeholder: /posts owned-lane rollup]
Placeholder for later enrichment
[Annotated screenshot placeholder: /posts/[id] owned distribution panel]
Owned-lane and workflow examples
Use these examples when the docs need to feel concrete and teachable instead of abstract, especially across adjacent workflows.
Measurement reality
Use this reference page when you need exact interpretation of readiness, delivery, and metric truth across CMS and newsletter.