Read time: ~5 minutes · Series: Product Manager practice · Previous: Team collaboration · Next: Memory governance
What counts as "meeting-ready numbers"
Lantide doesn't require fancy pipelines for show; Report content must hold up. As PM, use the checklist below before Execute and the same bar after.
Before Execute: Plan must-haves
Before analyst presses Execute, Plan should answer:
| Check | Ask yourself |
|---|---|
| Goal | Which decision question does this Plan answer? |
| Denominator | For rates/conversion: numerator and denominator? Cancellations, refunds, duplicate users? |
| Grain | Per order or per user? Join fan-out risk? |
| Time window | Start/end, timezone, partial days? |
| Stage definitions (funnel) | Each stage filter understandable to business? |
| Checkpoints | Sanity checks before proceeding? |
Any item vague → annotate, don't Execute. Changing definition post-Execute costs more.
After Execute: Report acceptance
| Check | Pass | Fail |
|---|---|---|
| Concrete numbers | "1,623 orders, 1.63%" | "Severe drop at some stage" |
| Traceable definitions | Stages / denominator in Report | Conclusion only, no definition |
| limitations | States data gaps and assumptions | No limits mentioned |
| Causal caution | Separates correlation and causation | "A caused B" directly |
Funnel analyses should include largest drop stage and per-stage counts / rates (USER_GUIDE §2.7).
What is NOT the quality bar
These cannot replace the above:
- Many SQL steps
- Lineage / Source Run
- Long chat, busy-looking Agent
- HTML report with hollow numbers
May be nice-to-have, not minimum for sign-off.
Team norms (paste into wiki)
- External numbers must come from Executed Plan's Report
- Before Execute, PM or designated reviewer annotated Plan (small teams: analyst self-review + second spot check)
- Quick exploration defaults informal—not for finance or external PR
- Report limitations required; missing → send back