Instrument tour experiences so prospects understand the platform quickly

Why instrumented tours win adoption

Busy directors and driven candidates will not guess how SageStepper works—they need one guided path that delivers a concrete win fast. Tours are where you set that expectation. If you instrument them well, you’ll consistently show what matters: a first Nova interview, a visible readiness score on the progress radar, and a clear next step on an action board.

• Stakes: programs hit readiness goals when prospects convert into daily users. We regularly see a 22–35% lift in offer rate when candidates maintain a 10+ day streak and reach a 15-point readiness score gain in their first Interview Sprint.
• Reality: most tours over-index on features. We need evidence. Measure time-to-first-simulation, comprehension of the progress radar, and creation of a plan on an action board.
• Target: within 10 minutes, a prospect should complete a Nova simulation, view auto-scored feedback on their progress radar, and add at least one task to their action board. That sequence predicts a 2.4x higher Day 7 retention.

SageStepper is the workspace that ties it all together—Nova interviews, feedback, flashcards, and community—so your tour should model that workflow from minute one.

Map the “aha in 10” tour

The tour should compress a week of learning into a single, confident loop. Keep it simple:

1. Launch Nova with a role-relevant prompt (e.g., “PM panel: scope a v1 metrics plan”).
2. View the progress radar to see strengths and gaps tied to the rubric.
3. Create or import an action board with next steps; schedule an Interview Sprint.

Ritualize it:

• “3-3-3” rule in tours: 3 minutes to first simulation, 3 insights on the radar, 3 actions on the board.
• Always end with a commitment: join the Sprint, set a streak goal, or share a transcript with a mentor.

Here’s a tight live flow you can reuse tomorrow:

Tour talk track (12 minutes)
- 0:00–1:00: Outcome framing: “We’ll simulate one interview, show you your radar, and leave with a 3-step plan.”
- 1:00–3:00: Launch Nova → record 90 seconds.
- 3:00–6:00: Review radar: call out 1 strength, 1 gap, 1 quick win.
- 6:00–9:00: Add 3 tasks to action board; start a 5-day Interview Sprint.
- 9:00–12:00: Show flashcards for the gap area; share transcript → mentor.

For self-serve tours, mirror the same milestones with tooltips and inline prompts. Both paths feed the same metrics.

Instrument the tour: a minimal, durable event schema

Instrument once, then iterate content freely. Track comprehension, not just clicks. Use this shared taxonomy across live, recorded, and self-serve tours.

# analytics/events.yaml
namespace: sagestepper.tour
version: 1
entities:
  user: {id, role, cohort, org}
  tour: {id, channel: [live, self-serve, recorded], variant}
  session: {id, device, ua}

metrics:
  - time_to_first_simulation_ms
  - time_to_radar_ms
  - actions_created_count
  - radar_competency_scanned_count
  - flashcard_quiz_started
  - sprint_scheduled
  - transcript_shared

events:
  tour_started            {user_id, tour_id, channel, entry: [product, /product, email]}
  nova_simulation_started {scenario_id, duration_target_s}
  nova_simulation_done    {transcript_id, score_overall, rubric_version}
  radar_viewed            {competencies_viewed, avg_dwell_ms}
  action_board_created    {board_template, tasks_count}
  flashcards_opened       {deck, mode: [learn, quiz]}
  sprint_scheduled        {days, start_date}
  transcript_shared       {destination: [mentor, peer, self], medium}
  tour_completed          {steps_completed, aha_reached: bool}

cohorts:
  - first_aha: aha_reached == true
  - day7_retained: streak_days >= 7
  - mentor_saver: transcripts_shared_to_mentor >= 1

Example client snippet:

// instrumentation.ts
import { track } from "@analytics/core";

export function markAhaIfQualified(ctx: { startedAt: number; didSim: boolean; sawRadar: boolean; tasks: number }) {
  const aha = ctx.didSim && ctx.sawRadar && ctx.tasks >= 1;
  track('sagestepper.tour.tour_completed', {
    aha_reached: aha,
    steps_completed: [ctx.didSim ? 'sim' : null, ctx.sawRadar ? 'radar' : null, ctx.tasks ? 'plan' : null].filter(Boolean),
    time_ms: Date.now() - ctx.startedAt,
  });
  return aha;
}

Guardrails:

• Keep event names stable; evolve with versioned properties (e.g., rubric_version).
• Attach tour.channel to every event so you can compare live vs self-serve outcomes.
• Tag cohorts and orgs to spot institutional bottlenecks early.

Build both live and self-serve tours that converge on the same “aha”

You’ll run both modalities—open house cohorts and on-demand trials. Instrument so you can hold them to the same standard.

• Live tour checklist:
  • Start on the Nova launcher with 2–3 preloaded scenarios by role.
  • Keep the mic check inside Nova to avoid Zoom toggling.
  • Use the progress radar to highlight a single rubric dimension and connect it to flashcards.
  • End by creating an action board and scheduling a 5-day Interview Sprint.
• Self-serve tour checklist:
  • Use drip:tooltip on first launch to highlight Nova’s scenario picker.
  • Auto-open the progress radar with a guided “3 insights” overlay.
  • Preload an action board template (PM First Week, Data Analyst Portfolio) with 3 tasks.

Alert thresholds that keep both paths healthy:

# ops/alerts.yaml
alerts:
  - name: slow_time_to_first_sim
    condition: p95(time_to_first_simulation_ms) > 180000
    notify: slack:#tour-ops
  - name: nova_failure_rate
    condition: error_rate(event='nova_simulation_done') > 0.02
    notify: pagerduty:oncall
  - name: radar_not_viewed
    condition: rate(event='radar_viewed') < 0.7 of tour_started
    notify: slack:#tour-ops

These alerts save mentor hours. When tours consistently deliver a first transcript and radar view, mentors start with evidence, not guesswork, cutting 1.5–2.3 hours per candidate in the first week.

Role-based empathy: tours for common archetypes

One script doesn’t fit every learner. Keep the instrumentation the same, but tailor scenarios and outcomes.

• Career switcher (non-tech to data):
  • Nova scenario: explain a simple A/B test and choose a metric.
  • Radar emphasis: problem framing and clarity.
  • Action board: 3 tasks—“Mock A/B critique,” “SQL warm-up deck,” “Sprint signup.”
• International grad (communication practice):
  • Nova scenario: behavioral panel—“Tell me about a time you resolved ambiguity.”
  • Radar emphasis: structure and brevity.
  • Flashcards: STAR and concise phrasing deck; enable quiz mode to speed feedback loops.
• Senior IC (portfolio defense):
  • Nova scenario: system design walkthrough.
  • Radar emphasis: tradeoffs and stakeholder alignment.
  • Action board: tasks that prompt artifacts to share with mentors.

Use tour.variant to segment archetypes and compare Aha Rates. In pilots, role-based variants lifted Aha Rate by 14–21% and improved Day 7 streak retention by 9 points.

Dashboards, loops, and reliability you can trust

Directors need to see more than activation—they need proof the tour is building habits and saving faculty time.

Key dashboards (weekly review):

• Aha Rate: percent of tour_completed with aha_reached=true.
• Time-to-first-simulation (median, p95).
• Radar comprehension proxy: radar_competency_scanned_count >= 3.
• Plan adoption: action_board_created within the tour session.
• Streak Day 3 and Day 10 retention.
• Mentor Hours Saved: transcripts shared to mentors before first 1:1.

Sample query:

-- tours.sql
WITH base AS (
  SELECT user_id, MIN(CASE WHEN event='nova_simulation_done' THEN ts END) AS first_sim,
         MIN(CASE WHEN event='radar_viewed' THEN ts END) AS first_radar,
         MIN(CASE WHEN event='action_board_created' THEN ts END) AS first_plan,
         MIN(CASE WHEN event='tour_started' THEN ts END) AS started,
         MAX(CASE WHEN event='tour_completed' THEN (props->>'aha_reached')::boolean END) AS aha
  FROM events
  WHERE namespace='sagestepper.tour' AND ts >= current_date - interval '30 days'
  GROUP BY user_id
)
SELECT
  COUNT(*) FILTER (WHERE aha) / NULLIF(COUNT(*),0) AS aha_rate,
  PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY EXTRACT(EPOCH FROM (first_sim - started))) AS ttf_sim_median_s
FROM base;

Close the loop:

• Send weekly snapshots to #student-success and #sales with Aha Rate and top friction point.
• Review 5 failed tours every Friday. Replace assumptions with clips and transcripts.
• Ship one micro-fix weekly (e.g., preloading a scenario or shortening a tooltip). Small wins compound.

Make SageStepper the default prep workspace with simple rituals

Instrumentation gets you the truth; rituals make it stick.

• Interview Sprint in week one:
  • Auto-create a 5-day Sprint when a tour ends with aha_reached=true.
  • Email cadence: Day 0 transcript and radar summary, Day 2 flashcard quiz, Day 4 Sprint check-in.
  • Programs that do this see a 12–18 point lift in readiness score over 7 days.
• Streaks and progress radar:
  • Encourage a minimum 5-day streak post-tour. Streaks above 10 days correlate with 1.6x offer rate.
  • Link radar improvements to specific tasks on the action board.
• Mentor-facing artifacts:
  • Share the Nova transcript and radar snapshot automatically to mentors. This routinely saves 90–140 minutes in the first two 1:1s.
• Community reinforcement:
  • Post “First Aha” wins in the cohort channel. Social proof boosts Day 3 retention by ~8%.

Template follow-up sequence:

# followup.sh (pseudo)
send "Congrats on your first simulation. Here’s your radar and 3 quick wins." --to=$user --link=/login?utm_source=blog&utm_medium=workflow&utm_campaign=instrumented-tours
wait 1d
send "2-minute quiz on your gap area (flashcards)." --to=$user --link=/workflow?utm_source=blog&utm_medium=workflow&utm_campaign=instrumented-tours#flashcards
wait 2d
send "Sprint check-in: keep your streak alive." --to=$user --link=/workflow?utm_source=blog&utm_medium=workflow&utm_campaign=instrumented-tours#sprint

Every touch drives them back to the same workspace—Nova, radar, action boards, flashcards—until it becomes default behavior.

What to cut, what to keep

Make hard choices in tours. Prospects don’t need everything; they need a win they can feel.

• Cut: long product overviews, pricing rabbit holes (link to /pricing), multi-feature detours.
• Keep: one Nova run, one radar insight loop, one action board with 3 tasks.
• Link out for depth: /product, /workflow, /community, and /pricing with UTMs.

Celebrate progress, not perfection. A fast “aha” beats a perfect lecture every time.

Once your tours are instrumented and reliable, you’ll see an activation curve you can actually manage—and cohorts that hit readiness goals without burning mentor time.