Read time: ~5 minutes · Series: Business & Ops advanced · Previous: vs BI and meetings
Old habits undo Lantide
After rollout, if business / ops still ask for numbers the old way, Plan / Execute boundaries become meaningless. Six anti-patterns from pilots:
Anti-pattern list
| # | Anti-pattern | Why it hurts | Fix |
|---|---|---|---|
| 1 | Verbal metric change, no Plan annotation | Meeting agreed, file unchanged, Execute runs old definition | Metric change → Plan annotate + Resolve |
| 2 | "Execute first, fix later" | Formal numbers on wrong metrics; rework costly | Six checks before Execute (review Plan) |
| 3 | Quick screenshots in weekly / finance | No Plan, no limitations, no accountability | Label informal or upgrade project through Execute |
| 4 | Edit Report prose only, metrics still wrong | Numbers and definitions diverge | Wrong metrics → new Plan rerun |
| 5 | Plan at v3, chat still shares v1 screenshot | Decisions on different versions | Trust latest Plan / Report in project; chat sends links only |
| 6 | Change numbers in HTML only, Report not rerun | External story decoupled from formal analysis | Wrong calc → new Plan; HTML presentation only (Report to HTML) |
| 7 | Never Archive after Resolve | Resolved cards clutter panel; hard to find open items | After Resolve → Archive; history via View changes |
Team norms alignment
PM: rollout playbook Step 3 minimum rules:
- External numbers from Executed Report only
- Plan reviewed before Execute
- Quick results labeled "informal"
Business / ops are the main enforcers—refusing non-compliant numbers beats chasing after the fact.
One thing to do now
Align with analysts: "Numbers I use externally need Executed Report link or HTML; Quick screenshots are reference only."