How to interpret AI Research-generated reports? Which parts are most important?
Question Type
User Manual Question
Quick Answer
The 3 Most Important Parts:
- Executive Summary: Core findings (3-5 insights)
- Actionable Recommendations: Specific action plans
- Highlight Conversation Excerpts: Evidence for insights
Reading Order:
- First read executive summary (5 minutes) → Understand core findings
- Then read actionable recommendations (5 minutes) → Know what to do
- When in doubt, read detailed interviews (30 minutes) → Understand "why"
Complete Report Structure Interpretation
Part 1: Executive Summary (Most Important)
Location: First page of report
Content:
- Research objectives
- Participant personas (count and types)
- Core findings (3-5 insights)
Example: Sparkling Coffee New Product Test
How to Interpret Executive Summary
Understand Core Findings:
- ⚠️ Warning: Risks to note
- ✅ Opportunity: Advantages to leverage
- 💰 Key Data: Important quantitative indicators
- 📸 User Insights: Deep psychology and motivations
- 🔀 Difference Analysis: Variations between groups
Quick Judgment:
- Is research direction correct?
- Any unexpected findings?
- Which findings most important?
Part 2: Actionable Recommendations (Most Important)
Location: Report end or separate section
Content:
- Specific action plans based on insights
- Expected effects
- Priorities
Example: Sparkling Coffee Actionable Recommendations
How to Interpret Actionable Recommendations
Understand Priorities:
- High priority: Execute immediately, major impact
- Medium priority: Execute when resources allow
- Low priority: Selectively execute
Evaluate Feasibility:
- Can this recommendation be done?
- How many resources needed?
- Are expected effects reasonable?
Create Action Plan:
- Select 2-3 high-priority recommendations
- Assign responsible persons and timeline
- Track execution results
Part 3: Individual Interview Details (Read for Deep Understanding)
Location: Middle of report
Content:
- Detailed interview records for each persona
- User profiles
- Highlight conversation excerpts
Example: Linda's Interview Details
When to Read Detailed Interviews
Situation 1: Don't Understand Insight
- Executive summary says "unwilling to risk in afternoon"
- Don't understand why?
- Read detailed interview to understand underlying logic
Situation 2: Need to Persuade Others
- When reporting to boss
- Use highlight conversation excerpts as evidence
- "User Linda said: 'No mood to risk in afternoon'"
Situation 3: Deeply Optimize Product
- Want to understand users' complete thought process
- Path from awareness → hesitation → decision
- Discover more optimization opportunities
Part 4: Cross-user Analysis (Read to Understand Differences)
Location: Middle or back of report
Content:
- Common points (consensus)
- Difference points (disagreements)
- User segmentation
Example: Cross-user Analysis
How to Use Cross-user Analysis
Understand Consensus:
- Points all users agree on
- Use as core selling points
- Communicate first
Understand Disagreements:
- Differentiated needs of different users
- Segmented marketing
- Avoid "one-size-fits-all"
User Segmentation:
- Identify core target users
- Design differentiated strategies
- Prioritize
Interpretation Tips
Tip 1: Read Executive Summary and Recommendations First
5-minute Quick Understanding:
- What are core findings?
- What's recommended to do?
- Any unexpected findings?
Don't Start with Detailed Interviews:
- Information overload
- Miss key points
Tip 2: Use Highlight Conversations to Persuade Others
Don't Just Say: "Users think it's expensive"
Say Instead:
"User Linda said: '¥18 exceeds my daily budget, I usually buy ¥12 Americano.' This reflects real feelings of price-sensitive users."
Original Conversations:
- More persuasive
- Authentic and credible
- Easy to understand
Tip 3: Focus on "Why" Rather Than "What"
Not Important: "40% of users think it's expensive"
Important: "Why do users think it's expensive? - Price-sensitive types: Exceeds budget - Health-anxious types: Not sure if worth it - Solution: Show value, address concerns"
Deep Insights > Surface Numbers
Tip 4: Identify Unexpected Findings
Expected Findings:
- "Users care about price" (common)
Unexpected Findings:
- "Unwilling to risk in afternoon energy-boost scenario" (insight)
- This is real value
Prioritize Unexpected Findings:
- Challenge assumptions
- Discover new opportunities
- Avoid strategic mistakes
Common Misreadings
Misreading 1: Over-focus on Percentages
❌ Wrong: "40% of users like it, so product doesn't work"
✅ Correct: "2 out of 5 like it, 3 don't. Those who like are health-anxious types, those who don't are price-sensitive types. Recommend marketing to health-anxious types, price ¥15-16 to cover more people."
Reason:
- Small sample (5-10 people), percentages meaningless
- What matters is "why" and "what to do"
Misreading 2: Ignore Actionable Recommendations
❌ Wrong: Only read insights, not recommendations
✅ Correct: Read insights + recommendations together, know what to do
Misreading 3: Accept All Recommendations Wholesale
❌ Wrong: Do whatever AI says
✅ Correct:
- Evaluate recommendation feasibility
- Consider actual situation
- Select 2-3 high-priority ones to execute
Best Practices
Recommendation 1: Interpret as Team
Workflow:
- Research lead reads report first
- Extract core findings
- Team meeting discussion
- Jointly create action plan
Recommendation 2: Annotate Key Points
On Report:
- Highlight core findings
- Mark priorities
- Record questions
For:
- Future review
- Present to others
- Track execution
Recommendation 3: Continuous Tracking
Don't:
- End after reading report
Do:
- Execute recommendations
- Track results
- Validate if insights accurate
Bottom Line
"Interpret report: First read executive summary and recommendations (10 minutes), if questions read detailed interviews (30 minutes). Key is taking action based on insights, not just reading report."
Remember:
- ✅ Most important: Executive summary + Actionable recommendations
- ✅ Deep understanding: Read detailed interviews
- ✅ Persuade with conversations: Quote highlight excerpts
- ✅ Focus on "why": Not just "what"
- ✅ Take action: Execute based on recommendations
Related Feature: Plan Mode, Report Doc Version: v2.1