Omni Zero-to-One Implementation — Standard Implementation Plan
Purpose: Single source of truth for net-new BI implementations with Omni: phases, checklist, acceptance criteria, off-the-shelf Linear project spec, and automations. Use for LMNT, Eden, or any new client doing zero-to-one Omni.
Related: PLAYBOOK_DEVELOPMENT_PLAN.md (reusable epic pattern); this document is the delivery counterpart for Omni engagements. PR #241.
1. At a glance
| Phase | Name | Duration | Key output | Gate |
|---|---|---|---|---|
| Foundation | Connect + pilot scope + Omni CLI | 1–2 weeks | Omni connected to warehouse; pilot domain locked; CLI sync and branch | Access and scope confirmed |
| PoC | First Topics + 1–2 dashboards + Blobby | 2–3 weeks | Working pilot; Cursor + Blobby flow used where applicable | Stakeholder validation |
| Accelerator | Expand + permissions + handoff | 2–3 weeks | More domains; training; merge to main; ownership | Acceptance sign-off |
Total: ~1–2 months (align with omni-ramp-up-memo).
2. Prerequisites before kickoff
- Client data warehouse accessible (Snowflake, BigQuery, Databricks, etc.).
- Omni account and model for client (or model created).
- Pilot domain agreed (e.g. revenue, operations, product funnels).
- SOW / engagement scope signed; kickoff scheduled.
- For Tableau migration: Tableau workbooks downloadable and organized by dashboard/domain.
3. Phase: Foundation
Goal: Omni connected to warehouse; pilot domain and source tables locked; Omni CLI sync and working branch in place.
Checklist (→ Linear issues)
- Connect Omni to warehouse (credentials, schema restriction if needed, RBAC).
- Lock pilot domain and source tables/views (align to data dictionary or Definitions Council if client has one).
- Set up Omni CLI sync and create working branch (setup guide).
- (Optional) Download and organize Tableau workbooks for Cursor (per dashboard/domain).
Acceptance
- Omni model shows pilot schemas/tables; connection tested.
- Team can run
omni sync start <model-id> --branch <name> --create-branchand see model, relationships, Topics locally.
4. Phase: PoC
Goal: First Topics and 1–2 dashboards; Blobby enabled and documented; validation with business owner.
Checklist (→ Linear issues)
- Create initial Topics (base views, default filters, descriptions per Topic best practices).
- Build first 1–2 dashboards (use Cursor + Blobby for chart build when migrating from Tableau — see setup guide).
- Enable Blobby and document for users (where to find it, how to ask questions).
- Validate with business owner (numbers, filters, usability); iterate.
Acceptance
- At least one Topic and one dashboard in use; Blobby answers natural-language questions against the Topic.
- Date/filter defaults documented and aligned to client definitions.
5. Phase: Accelerator / handoff
Goal: Expand domains; permissions and training; handoff and merge to main.
Checklist (→ Linear issues)
- Expand to one or two more domains (new Topics from relevant marts; same pattern as pilot).
- Set connection and model permissions (Creator vs Viewer); document in Omni.
- Training for client team (viewers and, if applicable, creators).
- Handoff: merge Omni branch to main; document Topic ↔ mart mapping and maintenance process.
- Internal retro: update this plan and vault service offering with learnings.
Acceptance
- Client can run and extend Omni; ownership and support path clear.
- Branch merged; runbook or change process includes “Omni review” when marts change.
6. Off-the-shelf Linear project(s)
Create the same structure per engagement so every Omni zero-to-one uses the same tracking.
Option A — Single project (recommended)
Project name: [Client] Omni Zero-to-One (e.g. “LMNT Omni Zero-to-One”, “Eden Tableau to Omni Migration”).
Structure: One Linear project with epics (or milestones) per phase and child issues from the checklists above.
| Phase | Epic / parent | Child issues (titles) |
|---|---|---|
| Foundation | Epic: Omni Foundation | Connect Omni to warehouse; Lock pilot domain and sources; Set up Omni CLI sync and working branch; [OPTIONAL] Download/organize Tableau workbooks for Cursor |
| PoC | Epic: Omni PoC | Create initial Topics; Build first 1–2 dashboards (Cursor + Blobby); Enable Blobby and document for users; Validate with business owner |
| Accelerator | Epic: Omni Accelerator | Expand domains / add Topics; Permissions and training; Handoff and merge to main |
Labels: omni, data, phase-0 / phase-1 / phase-2 (or equivalent). Team: Delivery / Data.
Option B — Multiple projects
Use three projects per engagement if the team prefers separate boards: [Client] Omni Foundation, [Client] Omni PoC, [Client] Omni Accelerator. Same issue titles as Option A, split across the three projects.
Creating the project
- Manually: In Linear, create project and epics/issues from the table above.
- Agent / MCP: Use the spec in omni-zero-to-one-linear-project.md (if present) to create project and issues via Linear MCP for a given
[Client].
7. Automations and programmatic execution
- Omni CLI:
omni sync start <model-id> --branch <name> --create-branch; two-way sync. Use a script or alias for “start sync for model X on branch Y” if you run it often. - Cursor + Blobby: Tableau workbooks + Omni-synced context in Cursor → ask Cursor for dashboard name → get Topic + steps → in Omni, select Topic and run Blobby with instructions (and optional screenshot) → verify and push. Document as a short checklist in the setup guide.
- Tableau workbook download: Optional checklist: list dashboards → download workbook per dashboard → place in folder structure (by domain); Cursor then has consistent layout.
- No Omni API assumed: If Omni exposes APIs later for Topics/dashboards, add a “Programmatic API” subsection here.
8. References
- Setup (CLI, Cursor, Blobby): omni-cli-cursor-blobby-setup.md
- Ramp-up memo (generic): omni-ramp-up-memo.md
- LMNT-specific: lmnt-omni-accelerator-ramp-up-memo.md
- Video: Creating Charts with Cursor and Blobby
- Service offering (implementation plan + Linear template): omni-zero-to-one