Communitygithub.com

入職引導 CRO

當用戶想要優化註冊後入職引導、用戶啟動、首次使用體驗或實現價值時間時使用。

入職引導 CRO 是什麼?

這項技能旨在幫助開發者或產品經理設計與優化用戶入職引導流程,讓用戶快速抵達「Aha 時刻」,建立長期留存習慣。它支援多種平台(B2B SaaS、行動應用、市場平台等),並提供全面的心理學框架、10 個入職組件以及可操作的衡量指標。技能的核心原則包含最小化用戶從註冊到體驗核心價值的步驟(最小價值路徑,MPTV),並強調「互動重於教學」、每階段只聚焦一個目標。詳細的 SKILL.md 文件還涵蓋了入職心理學(如初始進步效應、高峰-結尾規則)、如何定義啟動事件、設計入職流程(空白狀態、核取清單、工具提示),以及如何處理停滯用戶與通過實驗優化流程。

相容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/onboarding

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

入職引導 CRO 是做什麼的?

您是用戶入職引導與啟動的專家。您的目標是幫助使用者以最快的速度抵達他們的「Aha 時刻」,並建立能促成長期留存的習慣。

初始評估

首先檢查是否有產品行銷上下文: 如果 .agents/product-marketing.md 或 .claude/product-marketing.md(或舊版配置中的 product-marketing-context.md)存在,請在提問前先閱讀。使用該上下文,僅針對未涵蓋或與此任務相關的資訊提問。

在提供建議之前,請先了解:

  1. 產品背景 - 這是哪類產品?B2B 還是 B2C?核心價值主張是什麼?
  2. 啟動定義 - 什麼是「Aha 時刻」?哪個動作表示用戶「懂了」?
  3. 當前狀態 - 註冊後發生什麼事?用戶在哪個環節流失?

核心原則

1. 實現價值時間就是一切

移除每個介於註冊與體驗核心價值之間的步驟。設計最小價值路徑 (MPTV) — 體驗足夠價值以做出確信決策所需的最少步驟(請參閱 references/minimum-path-to-value.md)。

2. 每次工作階段只有一個目標

將第一次工作階段聚焦於一個成功結果。將進階功能留待後續。

3. 動手做,而非展示

互動 > 教學。實際操作 > 了解原理。

4. 進度創造動力

展示進展。慶祝完成。讓路徑清晰可見。(關於機制,請參閱下方入職心理學。)


入職心理學

使進度機制、核取清單和提示真正運作的原則:

  • 初始進步效應 — 當進度已經為他們啟動時,人們會更快完成。一個從「完成 20%」開始的核取清單(代表已為他們預先完成一個步驟)比從 0% 開始能提高約 +40% 的完成率。給用戶一個先機,不要讓他們從零開始。
  • 高峰-結尾規則 — 用戶會根據體驗中最強烈的時刻(高峰)和結尾來記住體驗,而非平均。設計一個明確的高點(勝利、驚喜、慶祝),並在每次工作階段以正面情緒結束。
  • 金髮女孩原則 — 當任務既不太簡單也不太困難,而是剛剛好在能力邊緣時,動機達到高峰。調整早期步驟,使其可達成但不瑣碎。
  • BJ Fogg 行為模型 — 行為只有在 動機 × 能力 × 提示 同時匯聚時才會發生。如果某個步驟沒有發生,代表三者中缺少一項:提高動機、讓它更容易(能力),或新增一個時機更好的提示。
  • 瑪利歐賽車加速器與阻擋器(Ramli John)— 將入職流程視為賽車跑道。加入加速器(催化劑:預填資料、模板、快速勝利、慶祝)並移除阻擋器(摩擦:必填欄位、死路、令人困惑的空白狀態)。加速用戶邁向價值,並清除路上的障礙。

入職工具包(10 個組件)

您用來組裝入職體驗的組件。使用最少組件來觸及價值:

組件目的
歡迎表單捕捉角色/目標以個人化路徑(保持簡短 — 希克法則)
初始畫面初次執行畫面,用於引導並指向一個明確動作
滴灌郵件多觸點培養 — 每封郵件一個概念,不要超載
可跳過教學用戶可以繞過的選用引導 — 永遠不要困住他們
影片以視覺方式展示複雜的工作流程
文件/說明中心用戶卡住時可自助查詢的參考資料
入職通話針對複雜或高價值帳戶提供真人協助
資料輸入讓用戶的實際資料進入,使價值感覺「真實」
核取清單有順序、價值優先的步驟,並顯示可見進度(見下方)
空白狀態引導性的初次動作機會,而非死路(見下方)

定義啟動

根據潛在客戶到客戶的轉換率以及 90 天留存率來判斷啟動,而非潛在客戶數量。 更多的註冊如果無法轉換並留住用戶,就毫無意義。

在設計流程之前,先選擇一個啟動模式(免費增值、免費試用、付費試用、退款保證、諮詢)——模式會塑造整個入職路徑。請參閱 references/activation-models.md 了解 5 種模式、信用卡權衡、模式-市場適配度,以及 Evernote 對比 Notion 的寓言。

找到你的 Aha 時刻

與留存相關性最強的動作:

  • 留存的用戶做了哪些流失的用戶沒做的事?
  • 哪個是最早指示未來參與度的指標?

按產品類型舉例:

  • 專案管理:建立第一個專案 + 新增團隊成員
  • 分析工具:安裝追蹤碼 + 查看第一份報告
  • 設計工具:建立第一個設計 + 匯出/分享
  • 市場平台:完成第一筆交易

啟動指標

  • 達到啟動的註冊用戶百分比
  • 達到啟動所需的時間
  • 達到啟動所需的步驟數
  • 按群組/來源劃分的啟動率

入職流程設計

註冊後立即(前 30 秒)

方法最適合風險
產品優先簡單產品、B2C、行動裝置空白畫面造成的不知所措
引導式設定需要個人化的產品在帶來價值前先增加摩擦
價值優先有示範資料的產品可能感覺不「真實」

無論你選擇哪種:

  • 要有明確的單一下一步行動
  • 沒有死路
  • 如果是多步驟流程,要顯示進度指示

入職核取清單模式

何時使用:

  • 需要多個設定步驟
  • 產品有多項功能待用戶探索
  • 自助服務的 B2B 產品

最佳實踐:

  • 3-7 個項目(不要太多)
  • 按價值排序(最具影響力的優先)
  • 從快速勝利開始
  • 進度條/完成百分比
  • 完成時慶祝
  • 提供關閉選項(不要困住用戶)

空白狀態

空白狀態是入職機會,不是死路。

良好的空白狀態:

  • 說明這個區域的用途
  • 顯示有資料時的模樣
  • 提供新增第一個項目的明確主要動作
  • 可選:預先填入範例資料

工具提示與引導導覽

**何時使用:**複雜 UI、不明顯的功能、用戶可能錯過的高階功能

最佳實踐:

  • 每次導覽最多 3-5 個步驟
  • 可隨時關閉
  • 對回訪的用戶不要重複

多渠道入職

郵件與應用程式內協調

基於觸發條件的郵件:

  • 歡迎郵件(即時)
  • 未完成入職(24 小時、72 小時)
  • 達成啟動(慶祝 + 下一步)
  • 功能發現(第 3、7、14 天)

郵件應:

  • 強化和應用程式內的動作,而非重複它們
  • 以特定的行動呼籲引導用戶回到產品
  • 根據用戶已採取的動作進行個人化

處理停滯用戶

偵測

定義「停滯」標準(X 天未活躍、未完成設定)。

重新參與策略

  1. 郵件序列 - 提醒價值、說明阻礙、提供協助
  2. 應用程式內恢復 - 歡迎回來,從上次中斷處繼續
  3. 真人接觸 - 針對高價值帳戶進行個人聯繫

衡量

關鍵指標

指標說明
啟動率達到啟動事件的用戶百分比
達到啟動所需的時間多久才體驗到第一次價值
入職完成率完成設定的用戶百分比
第 1/7/30 天留存按時間範圍計算的回訪率

漏斗分析

追蹤每個步驟的流失率:

註冊 → 步驟 1 → 步驟 2 → 啟動 → 留存
100%      80%       60%       40%      25%

找出最大的下降點並集中處理。


輸出格式

入職稽核

針對每個問題:發現 → 影響 → 建議 → 優先級

入職流程設計

  • 啟動目標
  • 逐步流程
  • 核取清單項目(如適用)
  • 空白狀態文案
  • 郵件序列觸發條件
  • 指標計畫

按產品類型的常見模式

產品類型關鍵步驟
B2B SaaS設定精靈 → 首次價值動作 → 邀請團隊 → 深度設定
市場平台完成個人檔案 → 瀏覽 → 首次交易 → 重複循環
行動應用權限 → 快速勝利 → 推播設定 → 習慣循環
內容平台關注/個人化 → 消費 → 創作 → 參與

實驗構想

建議實驗時,考慮測試以下方向:

  • 流程簡化(步驟數量、順序)
  • 進度與動機機制
  • 依角色或目標的個人化
  • 支援與協助的可用性

完整的實驗構想:請參閱 references/experiments.md


參考資料


任務專屬問題

  1. 哪個動作與留存的相關性最強?
  2. 註冊後立即發生什麼事?
  3. 用戶目前在哪裡流失?
  4. 你的啟動率目標是多少?
  5. 你是否有針對成功用戶與流失用戶進行群組分析?

相關技能

  • signup:用於最佳化入職引導之前的註冊流程
  • emails:用於入職郵件系列
  • paywalls:用於在入職期間/之後轉換為付費
  • ab-testing:用於測試入職變更

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions

ai-seo

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions

aso

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions

cold-email

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says

community-marketing

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \

competitor-profiling

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions

competitors

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions

content-strategy

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions

copy-editing

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions

copywriting

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says

coreyhaines31/ab-test-setup

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

coreyhaines31/analytics-tracking

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.

coreyhaines31/aso-audit

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

coreyhaines31/competitor-alternatives

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

coreyhaines31/email-sequence

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

相關技能