Who this is for
- Analytics engineers who own LookML models, Tableau calcs, or Power BI measures- BI admins responsible for a dashboard estate (and its license bill)- Data leads planning a migration or a deliberate coexistence- Anyone who has counted their dashboards and felt tired
What you’ll be able to do
| After module | You can… |
|---|---|
| 0 | Inventory the estate: what exists, what’s actually used, what the semantic layer contains |
| 1 | Translate LookML / calcs / measures into governed ontology metrics, conflicts surfaced |
| 2 | Rebuild the flagship dashboard conversationally, with side-by-side discipline |
| 3 | Prove parity with golden queries — and triage every mismatch to its cause |
| 4 | Say honestly what doesn’t migrate, and what replaces dashboards entirely |
| 5 | Run coexistence: usage-based deprecation, BI tool as a data source during transition |
| 6 | Measure adoption weekly with a playbook |
Workshop modules
| Module | Time | |
|---|---|---|
| 0 · Inventory the Estate | 00_INVENTORY.md | 20 min |
| 1 · Translate the Semantic Layer | 01_TRANSLATE_SEMANTIC_LAYER.md | 25 min |
| 2 · Rebuild the Flagship Dashboard | 02_REBUILD_FLAGSHIP.md | 25 min |
| 3 · Parity Testing | 03_PARITY_TESTING.md | 20 min |
| 4 · What Doesn’t Migrate — And What Replaces It | 04_WHAT_DOESNT_MIGRATE.md | 15 min |
| 5 · Coexistence & Cutover | 05_COEXISTENCE_CUTOVER.md | 20 min |
| 6 · Measure Adoption | 06_MEASURE_ADOPTION.md | 15 min |
How to use this workshop
- Prerequisites: your warehouse connected to TextQL (see Connect Your Data), and — strongly recommended — your BI tool connected too (Tableau and Power BI connectors exist; they make coexistence real rather than aspirational).- Bring exports: dashboard/workbook lists, usage stats from your BI tool’s admin views, and your semantic-layer source (LookML files, workbook calc exports, measure definitions). Modules 0–1 work on these as uploaded files.- Work in order — the inventory’s usage data drives every later decision, and parity testing (Module 3) gates any cutover.- Swap
[bracketed]placeholders for your own tool names, dashboard names, and metrics.
For facilitators — running this as a guided session
For facilitators — running this as a guided session
T-minus-1-day pre-flight: run the workshop’s key prompts end-to-end in the session workspace — confirm logins, connectors, and the features this workshop touches are enabled for every attendee; have a fallback demo workspace ready in case a customer connector fails live. Pacing: when a long prompt is running (2–4 min), fire it first, then discuss the concept while Ana works — never watch a spinner in silence. If behind schedule, cut sections marked optional, never the checkpoints. Group sessions: attendees drive, you narrate; collect every miss or wrong answer in a shared doc — that list is the ontology backlog. With 10+ attendees on one warehouse, stagger the heavy prompts.
🤖 Prefer to have Ana run this workshop? Open a thread with your data connected and paste the prompt below — Ana walks you through it on your own data, one step at a time. You run each prompt; she coaches. (Air-gapped / VPC tenants where Ana can’t reach the web: download
ana-runner.md and paste its module list instead.)Run with Ana