Back to GrowthDex
Growth idea action plan

Slack onboarding starts at the first invocation context

Start onboarding from the first Slack surface the user actually touches, and vary the flow for App Home clicks versus slash-command intent instead of making every newcomer take the same route.

rare tacticlow budget

Why this can grow a startup

A shared onboarding script usually hides the exact clue the user already gave you. Slack's onboarding guide explicitly says onboarding should start when the first meaningful event happens, such as `app_home_opened` or a slash command, and notes that those users should get different onboarding because the command user has already shown more expertise. That matters because good onboarding is less about introduction and more about preserving momentum. If someone typed a command, they are trying to get work done now. If someone clicked into App Home, they may still need the basic mental model.

Company example

Slack's onboarding guide says `app_home_opened` is a good trigger for onboarding, but says a slash-command user should start onboarding then and take a different path because that action shows a different level of expertise.

Source and metric

Source: Slack Developer Docs: Onboarding users to your app · Browse Slack Developer Docs: Onboarding users to your app tactics

Slack recommends designing around the key tasks a user should finish in the first 30 seconds.

OnboardingProductActivationslack appsactivationevent-driven onboardinguser intent
GrowthDex operator note

When to use it

Use this when Onboarding, Product, Activation is relevant to slack apps, activation, event-driven onboarding and you can run a bounded test with a low budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read Slack Developer Docs: Onboarding users to your app and identify what is directly supported.
  2. Choose one channel context: Onboarding, Product, Activation.
  3. Define the test around Slack recommends designing around the key tasks a user should finish in the first 30 seconds..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian