Lightdash onboarding

Open-source BI that turns your dbt project into dashboards anyone can explore.

Lightdash

Data-tool signup that branches on your warehouse

Lightdash verifies email, asks role and org, then routes you by warehouse and dbt setup, with a demo project and a teammate invite for anyone who gets stuck.

B2BonboardingactivationSep 2024

01

Great, you're verified!

The verification success modal opens on top of the screen that was showing an error.

Lightdash: Great, you're verified!
  1. 1

    Celebrates the small win (working)

    A party emoji, a big green check and one Continue button.

    Habit formation

  2. 2

    Old error still visible (not working)

    "Your verification code has expired" remains right under the success modal.

    Consistency and standards

  3. 3

    Support on the blocker (working)

    "Chat to support here" sits on the page that gates access.

    Contextual help

  4. 4

    Three success signals (not working)

    Modal, check icon and a green toast all say the same thing.

    Signal vs noise

02

Nearly there

A short profile step before project setup.

Lightdash: Nearly there
  1. 5

    "Nearly there..." (working)

    The heading tells you the end is close.

    Goal-gradient effect

  2. 6

    Role question (working)

    A required role dropdown lets Lightdash route and segment users.

    Personalization

  3. 7

    Domain auto-join on (working)

    "Allow users with @yandex.kz to join" is pre-ticked, so colleagues can find the org.

    Network effects

  4. 8

    Pre-ticked newsletter (not working)

    "Keep me updated on new Lightdash features" is ticked for you.

    Informed consent

03

Select your warehouse

Setup starts with the one thing that decides the rest of the flow.

Lightdash: Select your warehouse
  1. 9

    Logos, not a form (working)

    Six warehouse tiles with familiar logos are quick to scan.

    Recognition over recall

  2. 10

    "Other" escape hatch (working)

    Users with an unlisted warehouse still have somewhere to click.

    User control and freedom

  3. 11

    Hand off to the expert (working)

    "If this is not you, invite them to Lightdash!" turns a stuck user into an invite.

    Human in the loop

04

Warehouse not supported

Choosing Other leads to an honest dead end with two ways forward.

Lightdash: Warehouse not supported
  1. 12

    Honest about limits (working)

    "We only support warehouses that have verified dbt adapters for now".

    Transparency

  2. 13

    A no becomes a vote (working)

    Vote on your warehouse in GitHub issues, so the request is captured.

    Visibility of system status

  3. 14

    Demo as fallback (working)

    "Try our demo project" keeps the user exploring instead of leaving.

    Reduce friction

05

How to upload your dbt project

Two clear paths: the CLI or pulling from a git repository.

Lightdash: How to upload your dbt project
  1. 15

    Assumes a dbt project (not working)

    "Upload your dbt project" is a hard wall for anyone without one.

    Mental models

  2. 16

    Two paths, one line each (working)

    "Using your CLI" with the exact command, or "Manually" from git.

    Cognitive load

  3. 17

    Docs one click away (working)

    "View docs" under the choices for anyone unsure.

    Contextual help

06

Define your columns

The manual path asks you to edit your dbt YAML before continuing.

Lightdash: Define your columns
  1. 18

    Shows the exact YAML (working)

    A copyable example of models and columns instead of a paragraph of docs.

    Show, don't tell

  2. 19

    Learn link as secondary (working)

    "Learn how to define them" for those who need more.

    Progressive disclosure

  3. 20

    Honor-system button (not working)

    "I've defined them!" moves on without checking, so mistakes surface later.

    Error prevention

Takeaways from Lightdash

  1. Branch setup on the one choice that decides the path (here, the warehouse) and ask it first.
  2. Give every dead end a next step: a demo project, a vote, or inviting the right colleague.
  3. Check the user's setup instead of asking them to confirm it.