Audit Your Signup-to-Activation Flow and Find the Steps to Cut First

Get a step-by-step friction audit of your onboarding flow, a before/after count of steps, fields and waits, and the three cuts worth A/B testing first.

You getFlow walkthrough table, before/after summary table and top 3 cuts to test first

Prompt

Prompt
Act as a senior product manager who specializes in onboarding and activation.

I will paste my product's signup-to-activation flow right after this prompt as screenshots, step notes or both. If I have not stated it, first ask me in one message: 1. What single action counts as activated (the aha moment)? 2. Who is the typical new user? 3. Which steps are required by legal, security or billing? Then wait for my answers.

Walk the flow step by step as a first-time user who has never seen the product.

Rules:
- Number every screen and log each field, decision and wait (email check, loading, approval) as a separate item.
- Tag each item Keep, Cut, Defer (move after activation) or Merge, with a one-line reason tied to reaching the aha moment sooner.
- Never cut an item I marked as required. If it still looks weak, say so in Open questions.
- Count steps, fields, decisions and waits before and after using the same counting method.
- Rank cuts by likely impact against build effort, and give each a success metric and a guardrail metric.

Output format:
1. Flow walkthrough table: Step | Item | Type | Friction note | Verdict
2. Before/after summary table
3. Top 3 cuts to test first: change, why, effort, success metric, guardrail
4. Open questions

End with one line naming your assumptions and what you could not see in my material.

Example output

At a glanceOnboarding flow before and after the auditCounts from the before/after summary
ItemBeforeAfter
Screens85
Fields63
Decisions52
Waits32

Example for: Slotwise, a fictional B2B scheduling tool. Activation means sharing your first booking link. Users are freelance consultants. Email verification is required by security.

1. Flow walkthrough

StepItemTypeFriction noteVerdict
1Email, password, confirm passwordField x3Confirm field adds typing with no gainMerge (show/hide toggle)
1Company nameFieldFreelancers often have noneDefer
2Verify emailWaitRequired. Average 4 min away from tabKeep
3Role dropdown (12 options)DecisionNot used until reportingCut
3Team sizeDecisionSales routing onlyDefer
4Connect calendar (Google/Outlook)DecisionCore to the aha momentKeep
4Calendar sync loadingWait8-15 s blank spinnerKeep, add progress copy
5Set weekly availability gridField7 days to edit before any value is shownMerge (prefill 9-5 Mon-Fri)
6Choose planDecisionPaywall before first linkDefer (trial default)
7Product tour (5 tooltips)WaitDelays the share buttonCut
8Copy booking linkDecisionAha momentKeep

2. Before/after summary

MeasureBeforeAfter
Screens85
Fields63
Decisions52
Waits32

3. Top 3 cuts to test first

  1. Remove the plan picker before the first link

    • Why: it is the only step that asks for money before value.
    • Effort: Low (default to a 14-day trial).
    • Success metric: % of signups who share a link within 24 h.
    • Guardrail: trial-to-paid rate at day 14.
  2. Prefill availability at 9-5 Mon-Fri

    • Why: it turns a blank grid into one confirm click.
    • Effort: Low.
    • Success metric: time from calendar connect to link copied.
    • Guardrail: % of bookings rescheduled in week 1.
  3. Cut the role and team size questions

    • Why: they add 2 decisions that do not help the user.
    • Effort: Medium (sales routing must move to a later prompt).
    • Success metric: step 3 completion rate.
    • Guardrail: qualified demo requests per week.

4. Open questions

  • Can users verify their email after copying their first link? That would remove the longest wait.
  • Does sales need team size at signup, or within 7 days?

Assumptions: the step timings come from your notes. I could not see the error states or the mobile layout.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Logging fields, decisions and waits separately exposes hidden friction like spinners and email checks that step counts miss.
  • Tying every verdict to the activation event stops cosmetic suggestions and keeps cuts focused on time-to-value.
  • Guardrail metrics on each test protect revenue and lead quality, so the fastest flow does not quietly break the business.

Use before an onboarding redesign or growth sprint. Paste screenshots into Claude, ChatGPT or Gemini, or list each screen with its fields and buttons. Know your activation event and which steps are mandatory.

Common edits

  • Ask for a mobile-only walkthrough if most signups come from phones.
  • Add a column for estimated drop-off if you have funnel data to paste.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Product Management