Analysis Report

Workflow

Use templates/analysis-report-template.md to document every analysis.

1. Clarify Purpose (Section 1): What do you want to know? Why is this analysis needed? Who will use it?

   Domain knowledge confirmation:

   • Confirm factual background with the user — do not assume or speculate on business context (e.g. "cost is high" vs "volume is high")
   • If analyzing a feature/initiative, confirm its exact specifications and parameters (thresholds, targets, display conditions, etc.) before designing queries

   Questions to answer when comparing pre/post periods:

   • How will you ensure comparison periods are unified across all metrics?
   • Are the thresholds appropriate for business reality (weekday/weekend patterns, seasonality)?
   • Do any metrics depend on events that haven't occurred yet in the analysis period?
   • What normalization method is appropriate for volume or seasonal variation?
   • How will you account for lead time lag at period boundaries?