Cross-Functional Collaboration Charter
Create a comprehensive cross-functional collaboration charter for [product team]. Include: 1) Shared objectives and success metrics across functions, 2) Roles and responsibilities matrix with RACI designations, 3) Decision-making framework with escalation paths, 4) Communication norms and channels, 5) Meeting cadence and attendance expectations, 6) Documentation standards and accessibility, 7) Conflict resolution process, 8) Recognition and celebration approach, 9) Continuous improvement mechanism for collaboration, and 10) Team agreements for maintaining healthy collaboration practices.
How to Use This Prompt
- Copy the prompt using the button above
- Replace placeholders in [brackets] with your specific details
- Paste into your AI assistant (ChatGPT, Claude, Gemini, etc.)
- Iterate as needed - ask follow-up questions to refine the output
Why This Prompt Works
This prompt addresses the root causes of cross-functional dysfunction by requiring explicit agreements on decision rights, communication channels, and conflict resolution before problems arise. Unlike generic collaboration frameworks, it produces RACI designations that eliminate the ambiguity that causes most team friction. The recognition and continuous improvement components ensure the charter evolves as the team matures rather than becoming stale.
When to Use This Prompt
- When product, engineering, design, and marketing teams are working on a major initiative and you need alignment on who owns what decisions
- After repeated miscommunications or dropped balls between functions signal that implicit norms are not working
- When onboarding new cross-functional partners (a new marketing lead, design director) and you need to reset collaboration expectations
Tips for Better Results
- List the specific functions involved (product, engineering, design, data, marketing, sales) so the RACI matrix covers your actual org structure
- Describe your biggest collaboration pain points (slow decisions, unclear ownership, meeting overload) so the charter directly addresses them
- Mention your existing tools and channels (Slack, Jira, Figma, Notion) so communication norms reference platforms your team already uses