​

Quality Bar & Review Checklist

Use this checklist to ensure your Boa workflows produce high-quality, actionable insights. Whether you’re running Chips or using Conversational Mode, these quality standards help you get the most value.

---

​

Before you start: Input quality

​

✅ Clear question or goal stated

Check:

• I know what I’m trying to learn or achieve
• My question is specific, not vague
• I’ve chosen the right workflow (Discover, Diagnose, Generate, Forecast, Monitor)

Good examples:

• ✅ “What fantasy RPG ads are performing well in the last 60 days?”
• ✅ “Why did our campaign underperform vs genre benchmarks?”
• ✅ “Create a brief for a new cozy puzzle campaign.”

Weak examples:

• ❌ “What’s working?” (too vague)
• ❌ “Tell me about creatives.” (no clear goal)

---

​

✅ Sufficient context provided

Check:

• Genre or category specified
• Time window defined (if relevant)
• Competitors or references included (if relevant)
• Theme or pattern focus stated (if relevant)

Minimum context for each workflow:

Workflow	Required Context	Optional Context
Discover	Genre, Time window	Theme, Competitors, Market
Diagnose	Creative (link or upload)	Benchmark for comparison
Generate	Goal, Deliverable type	Source insights, References
Forecast	Genre, Time window (90+ days)	Theme, Competitors
Monitor	What to track (competitors or theme)	Alert frequency, Thresholds

---

​

✅ Correct goal/workflow chosen

Check:

• I’ve matched my question to the right workflow

Quick decision guide:

• “What’s working?” → Discover
• “Why did this perform?” → Diagnose
• “Create a brief or report.” → Generate
• “What’s coming next?” → Forecast
• “Alert me when…” → Monitor

---

​

After you get results: Output quality

​

✅ Evidence cited in the result

Check:

• Results include specific creative examples
• Performance data is provided (e.g., “Top 10% in genre”)
• Patterns are backed by multiple examples, not single creatives
• Visual references are included (thumbnails, links, or screenshots)

Good output:

• ✅ “Top performers use hero’s journey narratives 3x more than bottom performers. Examples: [Creative A], [Creative B], [Creative C].”

Weak output:

• ❌ “Hero’s journey works well.” (no evidence, no examples)

---

​

✅ Patterns identified, not just individual creatives

Check:

• Results highlight what’s consistent across multiple creatives
• Patterns are described clearly (tone, theme, pacing, etc.)
• Outliers are noted separately, not confused with patterns

Good analysis:

• ✅ “80% of top performers use fast hooks (0-3 seconds) and epic orchestral music.”

Weak analysis:

• ❌ “This creative is good.” (no pattern, just a single example)

---

​

✅ Actionable next step included

Check:

• Results suggest a specific action (test, create, avoid, monitor)
• Next step is concrete, not vague
• Recommended action is grounded in the evidence

Good next steps:

• ✅ “Test hero’s journey narratives in your next campaign (proven pattern).”
• ✅ “Avoid slow intros — they correlate with underperformance in this genre.”
• ✅ “Create a brief incorporating epic tone and fast hooks from top performers.”

Vague next steps:

• ❌ “Consider these insights.” (what should I do with them?)
• ❌ “Interesting patterns.” (okay, but what’s the action?)

---

​

✅ Relevance to your brand and goals

Check:

• Insights are aligned with your brand positioning
• Patterns are executable given your resources
• Recommendations match your campaign goals
• You’re not chasing trends that don’t fit your identity

Relevance filter:

If the insight is…	And your brand is…	Then…
Epic, cinematic tone	Casual, playful brand	❌ Skip or adapt
Fast-paced, urgent CTA	Premium, patient brand	❌ Skip or adapt
Proven pattern, strong fit	Well-aligned	✅ Test confidently
Emerging trend, good fit	Aligned + agile	✅ Test cautiously

---

​

Before you share: Deliverable quality

If you’re creating a Report or Creative Brief, check:

​

✅ Clear executive summary or objective

Check:

• Reports: 2-3 sentence summary of key finding and recommendation
• Creative Briefs: Clear objective and hypothesis stated upfront

​

✅ Visual references included

Check:

• At least 3-5 visual examples provided
• Each reference is annotated (what to notice, why it’s relevant)
• Performance context included (e.g., “Top 5% in genre”)

​

✅ Specific creative direction (Briefs only)

Check:

• Tone described specifically (not “exciting” — “epic, cinematic, aspirational”)
• Theme stated clearly
• Pacing guidance included (hook timing, rhythm)
• Character and framing direction provided
• Must-haves and guardrails listed

​

✅ Rationale and evidence (Briefs and Reports)

Check:

• Recommendations are backed by data
• Performance metrics cited
• Patterns explained, not just stated

​

✅ Clear next steps

Check:

• Actionable recommendations provided
• Prioritization included (quick wins vs long-term bets)
• Success metrics defined (how you’ll know it worked)

---

​

Quality standards by workflow

---

​

Common quality issues and fixes

Issue	Fix
Results are too generic	Add more context (genre, theme, time window)
No actionable next steps	Ask follow-up: “What should I do with this?”
Missing visual references	Request examples: “Show me creatives that demonstrate this pattern.”
Unclear patterns	Ask for clarification: “What’s consistent across top performers?”
Insights don’t fit brand	Filter through positioning: “Does this align with our values and capabilities?”
Deliverable lacks evidence	Add performance data and annotated references
Brief is too vague	Be more specific with tone, theme, pacing guidance
Report has no “so what”	Add executive summary and clear recommendations

---

​

Quality culture: team standards

For teams using Boa regularly:

​

Weekly quality review

• Review 1-2 Reports or Briefs as a team
• Discuss what made them strong or weak
• Update this checklist with team learnings

​

Shared quality bar

• Agree on minimum standards for deliverables
• Create templates that enforce quality
• Share strong examples internally

​

Continuous improvement

• Track which insights led to successful campaigns
• Refine prompt patterns based on what works
• Update team workflows quarterly

---

​

Related resources