Product-Legal Collaboration Template

During the design phase, after the product spec is finalized. This gives legal enough detail to review meaningfully and enough time to resolve issues before engineering builds features that may need to change. For high-risk features (new data processing, new jurisdictions, AI/ML), engage legal during the discovery phase with a preliminary assessment.

No. Features that do not change data processing, user agreements, billing, or regulatory scope can skip formal legal review. Create a "legal review required" checklist with your legal team that lists the triggers. If none apply, you are clear to proceed. Common triggers: new personal data collection, new third-party data sharing, new jurisdiction, pricing changes, AI/ML features, and user-generated content.

This is the exact scenario the template prevents. If legal blocks the feature, ask for specific changes needed and a timeline for re-review. In most cases, the block is addressable (add a consent flow, modify data retention, update the privacy policy). If the block is fundamental (the feature itself creates unacceptable legal risk), escalate to your VP Product and General Counsel for a risk-acceptance discussion.

This is one of the most common tensions in product management. A cookie consent banner hurts conversion. A mandatory data retention limit reduces feature value. Work with legal to find the minimum viable compliance approach. Often there is a way to meet the legal requirement without destroying the UX. Present options, not just the problem.

For features with significant legal implications (data privacy, AI, financial transactions), yes. Invite legal to the design review as an observer. They can flag issues at the mockup stage that would be expensive to fix later. For routine features, the written review request is sufficient.