Read time: ~5 minutes · Series: Business & Ops advanced · Previous: Annotate Plan · Next: Common mistakes
Two tools, two questions
| BI dashboard (Looker, Tableau, etc.) | Lantide Report | |
|---|---|---|
| Strength | Daily monitoring of defined metrics | Exploration and review before metrics are final |
| Change metrics | Usually via metrics platform process | Iterate on Plan, annotate, Execute |
| Typical use | Daily GMV, fixed funnel | Promo review, metric disputes, adhoc projects |
| Your role | Watch trends, flag anomalies | Review Plan, accept Report, sign off this analysis |
Many teams use both: Lantide for "this analysis" sign-off; BI for daily dashboards.
Weekly deck with Lantide deliverables
Suggested flow:
- Before meeting receive HTML Report for Executed Report (exportable file)
- Slides cite Report numbers + stage definitions + limitations (HTML should match)
- If metrics differ from BI dashboard, state this analysis's special definition (point to Plan)—don't mix two numbers silently
Anti-pattern: slides use BI numbers while verbally citing Lantide conclusions with inconsistent definitions.
After sign-off: move to BI?
After pilot, team may decide which metrics after finalization enter BI or metrics platform. Lantide doesn't replace BI—it helps write the contract clearly while metrics are still debated.
See PM: vs Chat / BI coexistence strategy.
One thing to do now
List next week's meeting numbers: mark each BI or Lantide Executed Report; if mixed, prepare one sentence on "denominator for this adhoc analysis."