prompt

Cross-Functional Data Request Scope

Translate a business request from {{stakeholder}} into data specifications, effort estimate, and trade-offs.

Updated June 2026
The prompt
Scope the data request: {{request_description}}

Provide:
1. Clarifying questions:
   - What is the business decision this data informs?
   - What is the time sensitivity?
   - Who are the end users?

2. Data specifications:
   - Which tables / events needed?
   - Required dimensions (filters, breakdowns)?
   - Time range and grain (daily, hourly, etc.)?
   - Update frequency needed?

3. Technical approach:
   - Option A: Query existing data (effort: low)
   - Option B: Transform / aggregate existing data (effort: medium)
   - Option C: Instrument new events (effort: high, timeline: 2+ weeks)
   - Recommend which option fits constraints

4. Effort estimate:
   - Hours for data work
   - Dependencies (eng, PM sign-off?)
   - Delivery date

5. Trade-offs:
   - Would a dashboard MVP vs one-time report work?
   - What can we deprioritize?

Format as scoping document or email.
Did it work? Rate this prompt

Variables

Team requesting data (e.g. 'Marketing', 'Product')
What data do they want? (e.g. 'Weekly email campaign conversion by geo')

Details

Author

AI Khazna

License

Security

Type

prompt

Related assets

More curated picks in Data & Analytics.

Audit before you install

Run any source through our checks - AI visibility, security, performance, and stack detection.

More in Data & Analytics