II.
Workflow JSON
Structured · liveworkflow:product-launch-go-to-market
Product Launch Go-to-Market json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "workflow:product-launch-go-to-market",
"_kind": "Workflow",
"_file": "workflows/workflows/workflows-expanded-3.yaml",
"_cluster": "workflows",
"attributes": {
"displayName": "Product Launch Go-to-Market",
"workflowKind": "strategic",
"triggerType": "event-driven",
"typicalCadence": "per-launch",
"complexity": "cross-team",
"description": "Coordinating product launches across teams — positioning development,\nsales enablement, marketing campaign coordination, support readiness,\npricing finalization, and launch day execution. Includes post-launch\nmonitoring and rapid iteration.\n"
},
"outgoingEdges": [
{
"from": "workflow:product-launch-go-to-market",
"to": "role:product-manager",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:product-launch-go-to-market",
"to": "role:marketing-manager",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:product-launch-go-to-market",
"to": "role:solutions-architect",
"kind": "involves_role",
"attributes": {}
},
{
"from": "workflow:product-launch-go-to-market",
"to": "skill-area:brand-positioning",
"kind": "requires_skill_area",
"attributes": {}
},
{
"from": "workflow:product-launch-go-to-market",
"to": "skill-area:content-strategy",
"kind": "requires_skill_area",
"attributes": {}
},
{
"from": "workflow:product-launch-go-to-market",
"to": "domain:e-commerce",
"kind": "applies_to_domain",
"attributes": {}
},
{
"from": "workflow:product-launch-go-to-market",
"to": "responsibility:stakeholder-communication",
"kind": "triggers_responsibility",
"attributes": {}
}
],
"incomingEdges": []
}