Eden Omni Stakeholder Training — Run of Show (45 min)
Audience: mixed (stakeholders + a few builders)
Format: ~half overview / ~half hands-on
Goal: preserve familiar dashboards, explain Topics + AI, and operationalize “snapshots → workflow.”
Source anchors (for facilitator)
- Invite list + key links:
../omni_migration/notes.md - Licensing/seat types + tokens:
../omni_migration/omni_pricing_internal_bi.pdf - Eden-specific context:
- Seats/AI expectations + “exports to reduce seats”:
../../transcripts/2026-02-13_eden_daily_standup_b1092874.md - Topics definition + semantic layer intent:
../../transcripts/2026-02-12_eden_omni_migration_sprint_planning_hudd_cf694071.md
- Seats/AI expectations + “exports to reduce seats”:
Pre-reqs (do before the session)
- Access
- All attendees can log into Omni.
- At least 2 builders have Standard access (can create charts/dashboards; AI if enabled).
- Facilitator can export/download and can create (or at least view) deliveries/alerts settings.
- Demo content
- Pick 1 “daily driver” dashboard for the hands-on (one dashboard is enough).
- Confirm at least 1 Topic/dataset is available for charting and AI.
Key messages to reinforce (Eden-specific)
- Familiar dashboards first: prioritize P0 dashboards that stakeholders use daily.
- Topics = curated datasets (joins + definitions + governance). Dashboards can include charts from multiple Topics; each chart points to one Topic.
- Definitions must stay consistent across Topics (don’t fork “revenue” by department).
- AI is an entitlement + budget (tokens). Give AI-enabled seats to people who will use it and can sanity-check it.
- Snapshots → workflow: scheduled PDF/CSV deliveries + alerts replace screenshots and reduce seat pressure.
Minute-by-minute agenda
0:00–0:03 — Welcome + outcomes
- What we’ll accomplish today:
- Understand roles (Developer / Standard / Viewer)
- Navigate dashboards + export
- Understand Topics (and why they matter)
- Use AI safely (when enabled)
- Turn snapshots into a workflow (deliveries/alerts)
0:03–0:10 — Users + roles (conceptual; no pricing numbers)
Use the licensing deck framing:
- Developer: models, connections, permissions
- Standard: create dashboards/charts; AI + context editing
- Viewer: explore dashboards; filter/drill/download; schedule + alerts
Talking points:
- Eden doesn’t need everyone as a builder.
- Most stakeholders should be Viewers; a small set should be Standard.
0:10–0:14 — Pricing strategy (how to think about it)
Keep it high-level:
- Seat mix is the main lever (fewer builders; broad distribution via deliveries).
- AI features are valuable but not everyone needs them.
- Tokens are a monthly AI usage budget (don’t roll over).
0:14–0:22 — Familiar dashboards: find, filter, export
Live demo (facilitator):
- Open the chosen “daily driver” dashboard.
- Change:
- date window
- one business filter (product / pharmacy / plan / channel)
- Export/download a table to CSV.
Emphasize:
- You can answer 80% of questions via filters + exports—without building anything new.
0:22–0:30 — Topics (semantic layer) in plain English
Explain:
- Topic = approved dataset for a set of questions.
- Topics contain:
- joins (how tables connect)
- definitions + assumptions (grain, inclusion/exclusion rules)
- governance (who can see what)
Eden guidance:
- Organize Topics by use-case or team if helpful, but keep core definitions consistent.
0:30–0:35 — AI features: what it’s for + guardrails
Demo (facilitator, if AI enabled):
- Ask 1–2 natural language questions tied to the dashboard.
- Sanity-check results.
Guardrails to repeat:
- confirm timeframe (partial days?)
- confirm grain (order vs transaction vs customer)
- confirm filters (paid vs pending vs cancelled)
0:35–0:38 — Mobile view (quick expectations)
- Show mobile layout toggle (if available in your instance).
- What “good” looks like on mobile (readable KPIs; minimal scrolling).
0:38–0:45 — Hands-on block (split path: Viewer vs Builder)
Goal: everyone completes a confidence loop.
Step A (Everyone — 4 min)
- Open the demo dashboard
- Change 2 filters (date + one dimension)
- Export/download a table
Step B (Viewers — 2–3 min)
- Find deliveries/schedules/alerts from the dashboard
- Draft a daily delivery (PDF or CSV) to email/Slack
- If you can’t create it: identify recipients + cadence + owner
Step C (Builders — 2–3 min)
- Create a simple chart from the relevant Topic:
- metric (revenue / orders / SLA %)
- group by (product / pharmacy)
- Save to a “Training” dashboard
Wrap (final minute)
- Ask: “What’s one daily screenshot we should replace with a scheduled delivery?”
Follow-ups after the session (recommended)
- Decide seat mix for this phase (who is Viewer vs Standard; who needs AI).
- Create 1 scheduled delivery that replaces a daily snapshot.
- Identify the top 3 Topics needed for P0 dashboards and safe AI use.