Brainforge Knowledge

training_slides_outline

4 min read

Eden Omni Stakeholder Training — Slides Outline (copy into Google Slides)

Style: simple, visual, minimal text.
Rule: we keep pricing conceptual (seat strategy), not dollar amounts.

Slide 1 — Title

Eden Analytics in Omni
Stakeholder training: dashboards, Topics, AI, and operational workflows

Speaker notes:

  • Today is half overview, half hands-on.
  • Goal is confidence: find answers fast, and operationalize daily reporting.

Slide 2 — What’s changing (Tableau → Omni)

  • Same business questions
  • Faster iteration + governed self-serve
  • AI-assisted exploration (with guardrails)

Speaker notes:

  • “Familiar dashboards” matter: we will preserve the daily drivers first.

Slide 3 — Outcomes (what you’ll be able to do)

  • Find dashboards you’re used to
  • Filter/drill/export confidently
  • Understand Topics (why some questions work and others don’t)
  • Use AI safely
  • Convert “snapshots” into deliveries/alerts

Slide 4 — Users + roles (seat types, not dollars)

Three seat types

  • Developer: models, connections, permissions
  • Standard: build charts/dashboards + AI
  • Viewer: explore + export + schedule + alerts

Speaker notes:

  • Most stakeholders should be Viewers.
  • A small number should be Standard (builders).
  • Very few should be Developers.

Slide 5 — Seat strategy (how to control cost + complexity)

  • Fewer builders, more viewers
  • Use deliveries for broad distribution
  • Treat AI as an entitlement (and token budget)

Speaker notes:

  • Viewer seats can schedule and set alerts—this is key for “snapshots → workflow.”

Slide 6 — Where to start: “daily driver” dashboards

Examples to look for:

  • Unit Economics / Profitability
  • Order Journey / SLA / pharmacy turnaround
  • Retention / marketing cohorts

Speaker notes:

  • Ask the room: which 1–2 dashboards are daily drivers for you?

Slide 7 — Demo: navigation + filters (show, don’t tell)

Checklist:

  • Find dashboard
  • Change date filter
  • Change one business filter (product, pharmacy, plan, cohort)

Speaker notes:

  • Emphasize speed: filtered views are often enough—no new build required.

Slide 8 — Demo: export patterns

  • Export a table to CSV
  • Save/share a filtered view (if supported)

Speaker notes:

  • This replaces spreadsheets that are manually recompiled every morning.

Slide 9 — Topics (semantic layer) in plain English

Topic = approved dataset for a set of questions

  • joins live here
  • definitions and assumptions live here
  • governance (who can see what) lives here

Speaker notes:

  • If a question “doesn’t work,” it’s usually a Topic/definition problem—not a user problem.

Slide 10 — Topics and dashboards: how it composes

  • A dashboard can contain charts from multiple Topics
  • Each chart points to one Topic

Speaker notes:

  • This is how we avoid “mega-datasets” and improve governance.

Slide 11 — Consistent definitions (Eden-specific rule)

  • Keep core business definitions consistent across Topics
  • Don’t fork “revenue” by department

Speaker notes:

  • Light departmental steering is OK; conflicting definitions is not.

Slide 12 — AI: what it’s good at

  • Find the right slice
  • Summarize trends
  • Draft a chart/query

Speaker notes:

  • AI quality depends on Topic definitions and context.

Slide 13 — AI: guardrails (how to avoid bad decisions)

Always validate:

  • timeframe (partial days?)
  • grain (order vs transaction vs customer)
  • filters (paid vs pending vs cancelled)

Slide 14 — Mobile view: what to expect

  • Mobile vs desktop layouts
  • “Check a KPI quickly” use case

Speaker notes:

  • Don’t over-optimize; ensure key tiles remain readable.

Slide 15 — Turning snapshots into a workflow (the big win)

Replace:

  • screenshots + manual Slack posts With:
  • scheduled PDF/CSV deliveries
  • alerts when thresholds are crossed

Speaker notes:

  • This reduces seats needed and increases operational discipline.

Slide 16 — Hands-on instructions (split path)

Everyone

  • Open dashboard, change filters, export

Viewers

  • Draft a delivery/alert (or identify where it would live)

Builders

  • Create a chart and save it to a Training dashboard

Slide 17 — Close: what happens next

  • Identify top 3 dashboards + top 3 workflows
  • Confirm seat mix (Viewer vs Standard) + AI access plan
  • Decide which Topics are needed for P0 dashboards

Slide 18 — Q&A

Prompts:

  • “What’s one daily screenshot we should replace with a delivery?”
  • “What’s one metric you wish you had an alert for?”

Graph View