Launch ChatGPT Insight Dashboard

Project Background

OpenAI wants to launch a new internal analytics surface, the ChatGPT Insight Dashboard, for enterprise customers using ChatGPT Team and Enterprise. The dashboard will show weekly usage trends, top workflow categories, and adoption signals to help admins understand value and reduce churn. You are the AI/ML Analyst partnering with Product, Engineering, Design, GTM, and Legal to deliver the first version in 10 weeks.

The core team includes 10 people: 1 PM, 1 AI/ML Analyst, 4 engineers, 1 designer, 1 data engineer, 1 legal/privacy partner, and 1 GTM lead. Leadership wants the launch ready for a major enterprise sales push next quarter, so timing matters.

Key Stakeholders

Enterprise Product Lead wants a credible v1 shipped on time, even if scope is narrow.
Sales/GTM Lead wants customer-facing metrics broad enough to support renewals for 20 priority accounts.
Legal/Privacy requires strict aggregation thresholds and may block any user-level reporting.
Engineering Manager wants to avoid adding fragile pipelines or launch debt that will slow future roadmap work.

These priorities conflict: GTM wants more detail, Legal wants less, and Engineering wants a smaller surface.

Constraints

Timeline: 10 weeks, with executive review in Week 4 and launch/no-launch decision in Week 8
Budget: $120,000 for contractor support and user research; no additional full-time headcount
Dependencies: event instrumentation from the ChatGPT product team by end of Week 3; privacy review sign-off by end of Week 6
Capacity: 2 engineers are only available at 50% because they also support a separate ChatGPT reliability initiative

Complications

Instrumentation coverage for two key admin actions is currently missing and may take 2 extra weeks to add.
A large enterprise prospect has asked Sales for user-level drill-downs that Legal is unlikely to approve.
Design is shared with another launch and can only support one major revision cycle.

Your Task

Build a 10-week execution plan with milestones, owners, and dependencies.
Propose how you would align Product, GTM, Legal, and Engineering on v1 scope.
Define launch criteria and what you would cut if instrumentation slips by 2 weeks.
Identify the top risks, mitigations, and escalation points.
Recommend how to communicate trade-offs to leadership before the Week 8 go/no-go review.

Project Background

Key Stakeholders

Enterprise Product Lead wants a credible v1 shipped on time, even if scope is narrow.

Sales/GTM Lead wants customer-facing metrics broad enough to support renewals for 20 priority accounts.

Legal/Privacy requires strict aggregation thresholds and may block any user-level reporting.

Engineering Manager wants to avoid adding fragile pipelines or launch debt that will slow future roadmap work.

These priorities conflict: GTM wants more detail, Legal wants less, and Engineering wants a smaller surface.

Constraints

Timeline: 10 weeks, with executive review in Week 4 and launch/no-launch decision in Week 8

Budget: $120,000 for contractor support and user research; no additional full-time headcount

Dependencies: event instrumentation from the ChatGPT product team by end of Week 3; privacy review sign-off by end of Week 6

Capacity: 2 engineers are only available at 50% because they also support a separate ChatGPT reliability initiative

Your Task

Build a 10-week execution plan with milestones, owners, and dependencies.

Propose how you would align Product, GTM, Legal, and Engineering on v1 scope.

Define launch criteria and what you would cut if instrumentation slips by 2 weeks.

Identify the top risks, mitigations, and escalation points.

Recommend how to communicate trade-offs to leadership before the Week 8 go/no-go review.

Problem

Project Background

Key Stakeholders

Constraints

Complications

Your Task

Launch ChatGPT Insight Dashboard

Problem

Project Background

Key Stakeholders

Constraints

Complications

Your Task