Engineering-PM Collaboration Charter
Create a collaboration charter between Product Management and Engineering for [product team]. Include: 1) Shared principles and values, 2) Role clarity with specific responsibilities for each function, 3) Detailed RACI matrix for key activities (roadmapping, prioritization, specification, delivery, etc.), 4) Decision-making framework with escalation path, 5) Communication cadence and formats (meetings, documents, tools), 6) Artifact ownership and expectations (PRDs, tickets, technical docs), 7) Trade-off handling process, 8) Technical debt management approach, 9) Success metrics for healthy collaboration, and 10) Continuous improvement mechanisms.
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
The most common source of product team friction is ambiguity about who owns what. This prompt produces a detailed RACI matrix and decision-making framework that eliminates gray areas between PM and engineering responsibilities. By explicitly addressing trade-off handling and technical debt management, it tackles the two topics that cause the most conflict between product and engineering -- before they become problems.
When to Use This Prompt
- When joining a new team as a PM and you need to establish clear working agreements with engineering leadership
- When recurring friction between product and engineering is slowing down delivery and you need a reset
- When scaling from one engineering team to multiple squads and the informal collaboration norms no longer work
Tips for Better Results
- Describe your current pain points (e.g., "engineers feel specs are incomplete" or "PMs feel excluded from technical decisions") so the charter directly addresses real tensions
- Specify your development methodology (Scrum, Kanban, Shape Up) and tools (Jira, Linear, Shortcut) so the artifact ownership section is practical
- Share the charter draft with your engineering counterpart and ask the AI to incorporate their feedback into a revised version for true co-ownership