Back to the Playbook
Strategy & DiscoverySD-18
Coordinate a go-to-market launch
Coordinate product availability and market readiness with clear dependencies; distinguish launch approval from publishing or deployment.
Product statusAssisted workflowTeklens drafts the plan from Jira and the positioning; the readiness decision and the publishing actions stay with people.
Input3 required inputsConfirmed scope and availability · Positioning, adoption goals and team constraints · Initiative focus and approved Product Brain guidance
SkillsPlan a release launch · Record decisions and follow-up · Prepare task contextProduct Marketing + Product Marketeer Agent
OutcomeLaunch plan: audiences, channels, assets with owners, sequencing and readiness checklist; then the record of what launched and the adoption review.Artifact: Launch plan
Owner
Product Marketing
Human-led
Participants · Agents
Product ManagerSales & SupportEngineerProduct Marketeer Agent
Trigger
A product change and its target launch audience are confirmed.
Required context
JiraConfirmed scope and availabilityProduct BrainPositioning, adoption goals and team constraintsProduct BrainInitiative focus and approved Product Brain guidance
Optional context
ConfluencePositioning briefFilesChannels the team operates
Skills
Plan a release launchRecord decisions and follow-upPrepare task context
Suggested conversation arc
- 1Agree audience and launch outcomeClarify who benefits, the promise being made, what adoption means and the scale of coordination justified by the change.Skills: Prepare task context
- 2Draft the shared launch planLay out messages, channels, assets, dates, owners and readiness dependencies using confirmed product capabilities. Keep uncertainty and draft dates explicit.Skills: Plan a release launch
- 3Hold the readiness decisionReview actual product access, truthful claims, customer-facing team readiness and unresolved blockers. Have the launch owner decide go, revise or postpone.
- 4Capture authorised launch outcomesAfter separately authorised publication/access changes, collect what actually launched and to whom, plus early customer responses; do not infer execution from an approved plan.
- 5Review adoption and next decisionsCompare evidence with launch goals, note limitations and summarise agreed improvements and ownership without implying automatic task creation.Skills: Record decisions and follow-up
Output
Launch plan: audiences, channels, assets with owners, sequencing and readiness checklist; then the record of what launched and the adoption review.
Artifacts
Creates: Launch plan
What good looks like
- Every asset has a named owner and the channel it serves.
- Claims rest on confirmed product capabilities.
- Launch approval, publishing and deployment stay separate decisions.
Quality gate
The launch owner decides go, revise or postpone at the readiness review.
Destination
ConfluenceRelease channel
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.