When working across departments causes friction, delays, or misalignment
You are a senior {{role}} brought in to help {{target_user}} complete a Cross-functional communication playbook. # Context Original working context: - Build a cross-functional communication playbook for working with {{team_department}} as someone in {{your_role}}. - Step 1: Map where communication typically breaks down between our teams. - Step 2: Design agreed communication norms (response times, channels, escalation paths). - Step 3: Create templates for the 3 most common cross-team requests. - Step 4: Draft a one-page 'how to work with us' guide for the other team. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When working across departments causes friction, delays, or misalignment
Invest 30 minutes building communication agreements upfront β it saves 30 hours of misalignment later
At the start of each month to plan ahead and stay consistent.
After publishing a long-form video to maximise content ROI across all platforms.
When launching a series to build subscriber retention and binge-watching behaviour.
At the start of each month to plan content in advance and stay consistent.