Notion Services Path Notion 服務認證路徑

Project Kickoff & Discovery 專案啟動與探索

Ready to launch with confidence? This lesson focuses on the post-scoping kickoff and deeper discovery that set delivery up for success. You'll refine assumptions, align on the vision, confirm resourcing and timelines, and translate insights into a clear plan with measurable checkpoints. 準備好自信啟動了嗎？本課聚焦於範疇界定後的專案啟動會議與更深入的需求探索，為成功交付奠定基礎。你將修正假設、對齊願景、確認資源與時程，並將洞察轉化為具可衡量檢查點的清晰計畫。

Unit 1單元 1 Unit 2單元 2 Unit 3單元 3 Unit 4單元 4 Unit 5單元 5

After this lesson, you will be able to… 完成本課後，你將能夠…

  1. Facilitate a kickoff that aligns the vision for success, confirms resourcing, maps a realistic timeline, and locks in success metrics. 主持啟動會議，對齊成功願景、確認資源配置、規劃務實時程，並鎖定成功指標。
  2. Capture current usage and business structure through targeted discovery, then surface and document key risks and assumptions. 透過針對性的探索掌握目前使用狀況與業務結構，並浮現及記錄關鍵風險與假設。
  3. Convert kickoff and discovery outputs into a clear plan of record with owners, checkpoints, and measurable outcomes. 將啟動與探索的產出轉化為清晰的正式計畫，包含負責人、檢查點與可衡量的成果。
🎉
Where are we?我們在哪個階段？ You've gotten your customer to sign the SOW! Now it is time to kick off the project the right way — gaining alignment with your stakeholders on key factors that will make your project successful. 你已經讓客戶簽署了 工作說明書（SOW）！現在是用正確方式啟動專案的時候了——與利害關係人在決定專案成敗的關鍵因素上達成共識。
Project Milestones: SOW Signed, Kick-Off & Discovery, Solution Build, Solution Deliver, Engagement Close

Project Kickoff 專案啟動

In this section, we'll walk through how to run a strong project kick-off, craft a focused agenda that sets the stage, and set the tone for a healthy partnership. You'll see practical tips and examples that align stakeholders, prevent early missteps, and set up smooth collaboration. 本節將介紹如何主持一場出色的專案啟動會議、設計聚焦的議程來奠定基調，以及建立健康的合作關係。你會看到對齊利害關係人、預防早期失誤、建立順暢協作的實用建議與範例。

A strong project kick-off sets the tone for everything that follows: it aligns stakeholders on goals, scope, success metrics, roles, and ways of working before momentum builds. Invest in the kick-off, and you accelerate time-to-value while paving the way for smoother delivery and stronger outcomes. 一場強而有力的啟動會議為後續一切定下基調：在動能累積之前，先對齊利害關係人在目標、範圍、成功指標、角色與協作方式上的共識。投資在啟動會議上，你就能加速價值實現，同時為更順暢的交付和更強的成果鋪路。

Setting the Agenda設定議程

A crisp agenda and clear decision owners prevent misalignment from compounding later. Here are the general topics to include in a kickoff call: 清晰的議程和明確的決策者能防止後續對齊失調的累積。以下是啟動會議應包含的一般主題：

Vision for Success成功願景

Discuss the client's goals and expectations for Notion implementation. Outline key use cases and priorities. 討論客戶對 Notion 導入的目標與期望。概述關鍵使用案例和優先事項。

Resourcing資源配置

Ensure the right people are engaged at the right times, so timelines, scope, and expectations stay realistic and on track. 確保合適的人在合適的時間參與，讓時程、範圍和期望保持務實且在軌道上。

Timeline時程規劃

Set and confirm key dates, phases, and dependencies at kickoff to align expectations and avoid bottlenecks. 在啟動時設定並確認關鍵日期、階段和依賴關係，達成共識並避免瓶頸。

Success Metrics成功指標

Define measurable outcomes and a clear "definition of done" so priorities stay focused and progress can be tracked objectively. 定義可衡量的成果與清晰的「完成定義」，讓優先事項保持聚焦，進度能被客觀追蹤。

Vision for Success成功願景

Aligning on a vision for success at the start creates a shared north star — why this matters, who it serves, and what "great" looks like — so every decision ties back to impact. It reduces misalignment and rework, accelerates decision-making, and keeps scope anchored to meaningful outcomes. 在一開始就對齊成功願景，能建立共同的北極星——為什麼重要、服務誰、「卓越」是什麼樣子——讓每個決策都能回溯到影響力。這能減少對齊失調和返工、加速決策，並讓範圍錨定在有意義的成果上。

Reviewing Key Stakeholders審視關鍵利害關係人

Talking about key stakeholders early clarifies who decides, who does the work, and who needs to be informed — preventing delays and rework. It secures sponsorship, aligns expectations, and ensures the right people are engaged at the right moments. 及早討論關鍵利害關係人能釐清誰做決策、誰做事、誰需要被告知——預防延遲和返工。這能確保贊助、達成共識，並確保合適的人在合適的時刻參與。

Stakeholder Pyramid: Team Champions, Department Ambassadors, Workspace Owners, IT Admins, Executive Sponsor, Executive Team
ℹ️
Note:注意： Depending on the size and complexity of the customer, some roles may overlap. A 100-person company may only provide 1-3 project team members, while a 1,000-person company might provide 10+ given their capacity. 根據客戶的規模和複雜度，有些角色可能會重疊。100 人的公司可能只派 1-3 位專案團隊成員，而 1,000 人的公司可能會提供 10+ 位。

Resourcing資源配置

A resources overview at kickoff should align key stakeholders and clarify who does what, when. Confirm the executive sponsor, day-to-day owner, and decision rights; list core team roles, SMEs, and any vendor contacts; note availability, time zones, and capacity constraints; define a simple RACI and escalation path; and set the communication cadence and working channels. 啟動時的資源概覽應對齊關鍵利害關係人並釐清誰做什麼、何時做。確認執行層贊助人、日常負責人和決策權；列出核心團隊角色、SME 和供應商聯繫人；註記可用性、時區和產能限制；定義簡單的 RACI 和升級路徑；並設定溝通節奏和工作頻道。

Guiding Principles指導原則

📌
  • Setting clear time commitment expectations during kickoff is essential在啟動時設定清楚的時間投入期望至關重要
  • Roles and time commitments vary depending on project complexity and scope角色和時間投入會因專案複雜度和範圍而異
  • Following standard time commitment guidelines ensures alignment and efficient collaboration遵循標準的時間投入指引能確保對齊和高效協作

Time Commitments by Role各角色時間投入

Trust doesn't just appear — it's earned by making stakeholder commitments explicit on day one. Time commitments depend on engagement complexity and customer size. 信任不會憑空出現——它是透過在第一天就明確化利害關係人的投入承諾來贏得的。時間投入取決於服務複雜度和客戶規模。

Engagement Role:參與角色： Project Oversight專案監督
Estimated Commitment:預估投入： ~1 hr/week每週約 1 小時

Note: roles may overlap and do not need to be mutually exclusive. 注意：角色可能重疊，不必互相排斥。

Engagement Role:參與角色： Project management and coordination專案管理與協調
Estimated Commitment:預估投入： ~2 hr/week每週約 2 小時
Engagement Role:參與角色： Notion policies and settings, provisioning, securityNotion 政策與設定、配置、安全性
Estimated Commitment:預估投入： ~4 hr/week每週約 4 小時
Engagement Role:參與角色： Input and feedback into change management and enablement plans為變革管理和啟用計畫提供意見與回饋
Estimated Commitment:預估投入： ~3 hr/week每週約 3 小時

Timeline時程規劃

Reviewing Proposed Timelines審視提議的時程

Sharing and aligning on a proposed timeline helps both the customer and consultant align on: 分享並對齊提議的時程，能幫助客戶和顧問在以下方面達成共識：

Sample project timeline

Success Metrics成功指標

Success metrics create a shared definition of "what good looks like," aligning expectations and reducing ambiguity from day one. 成功指標建立了「什麼叫做好」的共同定義，從第一天就達成共識並減少模糊空間。

Examples:範例：
  • # of active users活躍使用者數
  • Workspace engagement numbersWorkspace 參與度數據
Examples:範例：
  • Time saved節省的時間
  • Reduced context-switching減少情境切換
Examples:範例：
  • Streamlined knowledge sharing簡化的知識分享
Examples:範例：
  • % of pages teams leveraging Notion for團隊在 Notion 上使用的 Page 佔比

Tips for Measuring Success衡量成功的建議

Set the stage for success為成功做好準備
Make sure metrics:確保指標：
  • Align expectations between the customer & yourself對齊客戶與你之間的期望
  • Provide a clear direction and measurable outcomes提供清晰方向和可衡量的成果
  • Help track progress and demonstrate impact幫助追蹤進度並展示影響力
Ask the right questions during discovery在需求探索問對的問題
  • What does success look like?成功是什麼樣子？
  • What challenges are you hoping Notion solves?你希望 Notion 解決哪些挑戰？
  • How will our key stakeholders want to define success?關鍵利害關係人會如何定義成功？
  • What workflows are you hoping to improve?你希望改善哪些工作流程？
Track progress & document success along the way過程中追蹤進度並記錄成果
  • Capture measures of success in a shared Notion dashboard for visibility在 Notion 共享 Dashboard 中記錄成功指標以提升可見度
  • Establish cadence to review progress, gather feedback and adjust as needed建立節奏來檢視進度、收集回饋並視需要調整
  • Use outcomes to reflect on impact and next steps at engagement close在合作結束時用成果回顧影響力和下一步

Tips for a Healthy Partnership健康合作關係的建議

Practical moves to maintain momentum and show progress your customers can feel. 維持動力並展示客戶能感受到的進展的實用做法。

Track What's Real追蹤真實進度
Spot slippage early and fix it before it hits the date. Compare your plan to what has actually occurred by task and by role. Tag the cause: scope, effort, availability, or sequencing. 及早發現落後並在影響日期之前修正。按任務和角色比較計畫與實際進展。標記原因：範圍、工作量、可用性或排序。

Create a one-slide variance snapshot with a short, actionable note to share with your stakeholders!製作一頁差異摘要搭配簡短可行動的備註，分享給利害關係人！
Level the Load平衡工作量
Resolve over-allocation without blowing up the timeline. Use a role-by-week heatmap. Try sequence, split, or substitute before you add capacity. 在不破壞時程的情況下解決過度分配。使用角色-週次熱力圖。在增加產能之前，先嘗試調整順序、拆分或替換。

Ask yourself: "Which tasks can decouple or slice to lower WIP for the bottleneck role?"問自己：「哪些任務可以解耦或切分，來降低瓶頸角色的在製品數量？」
Reforecast with Intent有目的性地重新預測
Keep dates honest and buffers meaningful. Conduct a weekly reforecast and determine clear triggers for when to re-estimate. 保持日期誠實、緩衝有意義。每週進行重新預測，並確定何時重新評估的明確觸發條件。

Watch path buffer consumption and replenish or trade scope when needed!監控路徑緩衝消耗，並在需要時補充或交換範圍！
Change Control that Moves推動變更控管
Stay collaborative while protecting the critical path. When presented with a request to change the plan, present three options with quantified impacts and give a recommendation. Document decisions with a decision owner and date. 在保護關鍵路徑的同時維持協作。當收到變更計畫的請求時，提出三個帶有量化影響的選項並給出建議。記錄決策內容、決策者和日期。
Communicate like a Pro像專業人士一樣溝通
Set communication cadence, keep updates short, log all decisions, and use one source of truth. Use a traffic-light status with clear next actions and owners. 設定溝通節奏、保持更新簡短、記錄所有決策，並使用單一資料來源。使用紅綠燈狀態搭配明確的下一步行動和負責人。
Assess Backlog Opportunities評估待辦機會
Capture high-value ideas uncovered during delivery. Record all ideas now, decide later what to add. 捕捉交付過程中發現的高價值構想。現在記錄所有構想，之後再決定加入哪些。

Use opportunity scoring: Value, Effort, Risk, Dependencies, Time-to-Impact. 使用機會評分：價值、工作量、風險、依賴關係、影響時間。

To prioritize, ask:優先排序時，問：
  • What problem does this solve and for whom?這解決了什麼問題？為誰解決？
  • What metric would move and by how much?會影響哪個指標？影響多大？
  • What is the smallest viable slice to validate value?驗證價值的最小可行切片是什麼？
Build a Notion Success Roadmap建立 Notion 成功路線圖
Turn opportunities into a phased, realistic plan aligned to capacity and change readiness. Use a Now, Next, Later approach aligned to adoption milestones. 將機會轉化為分階段、務實的計畫，與產能和變革準備度對齊。使用與採用里程碑對齊的 Now, Next, Later 方法。

To build your roadmap, ask:建立路線圖時，問：
  • Which 2-3 opportunities fit in the next quarter without exceeding bottleneck capacity?哪 2-3 個機會適合放在下一季而不超過瓶頸產能？
  • What dependencies or approvals must land first?哪些依賴關係或核准必須先到位？
  • What user outcomes will signal readiness for the next phase?哪些使用者成果能標示已準備好進入下一階段？
Next: Discovery →下一節：需求探索 →

Discovery 需求探索

In this section, we'll introduce discovery across all offerings and go deeper on the criteria for each. You'll finish by drafting your own discovery questions tailored to different scenarios. 本節將介紹所有服務方案的探索流程，並深入各方案的具體標準。最後你將針對不同情境撰寫自己的探索問題。

Discovery has two jobs: assess and plan. First, we get a shared, evidence-based picture of today — current usage, workflows, business cases, and where complexity lives. Then we turn that into a defensible plan with early solution artifacts, documented assumptions, and clear estimates that de-risk change and speed time to value. 探索有兩個任務：評估與規劃。首先，我們建立一個共享的、以證據為基礎的現況全貌——目前的使用狀況、工作流程、商業情境，以及複雜度所在。然後將其轉化為一份有根據的計畫，包含早期的解決方案雛型、已記錄的假設，以及清晰的估算，以降低變革風險並加速價值實現。

During discovery, confirm the following:在探索過程中，確認以下事項：

Current Usage Inventory目前使用狀況盤點

What's already in Notion, what's working, and what's just noise — so we know what to keep, fix, or retire. Notion 中已有什麼、什麼在運作、什麼只是雜訊——讓我們知道該保留、修正或淘汰什麼。

Business Structure Map業務結構圖

Who does what, how decisions flow, and the key workflows, so IA and permissions match reality. 誰做什麼、決策如何流動、關鍵工作流程，讓資訊架構和權限符合現實。

Prioritize Challenges & Opportunities排序挑戰與機會

The short list of pains and bets that actually ladder up to success metrics. 真正能對齊成功指標的痛點和機會的精選清單。

Initial Assumptions & Risks初始假設與風險

What must be true and what might bite us, with owners and "when to check back" triggers. 什麼必須成立、什麼可能出問題，加上負責人和「何時回頭檢查」的觸發條件。

Discovery Criteria: For All Offerings探索標準：適用所有方案

This criteria keeps the project realistic, helps price and staff accurately, and drives predictable outcomes across engagements. 這些標準讓專案保持務實、幫助準確定價和配置人力，並在各項服務中推動可預測的成果。

Criteria標準 Why it's important為何重要 Example Questions範例問題
Org structure組織架構 Right-size scope, training, and change management by aligning to team structure and user counts透過對齊團隊結構和使用者數量來適當調整範圍、培訓和變革管理 How is your organization structured? How many users/departments will need training?你的組織結構是什麼樣的？有多少使用者/部門需要培訓？
Stakeholder involvement利害關係人參與 Establish clear ownership and fast decision-making建立明確的權責和快速決策 Who will be the key stakeholders and project owners? How involved are they?誰是關鍵利害關係人和專案負責人？他們的參與度如何？
Integration requirements整合需求 Ensure a reliable day-one experience with data, context, and critical workflows preserved確保第一天就有可靠的體驗，保留資料、脈絡和關鍵工作流程 What level of support do you need for data migration or system integration?你在資料遷移或系統整合方面需要什麼程度的支援？
Timeline expectations時程預期 Set realistic milestones and resourcing plans設定務實的里程碑和資源計畫 What is your desired timeline for implementation and go-live?你期望的導入和上線時程是什麼？
Process mapping流程盤點 Design solutions that fit how work actually gets done設計符合實際工作方式的解決方案 Can you walk me through your current workflow?你能帶我走一遍你目前的工作流程嗎？
Success metrics成功指標 Create a shared definition of "done" with measurable outcomes建立帶有可衡量成果的「完成」共同定義 How will you measure the success of this implementation?你會如何衡量這次導入的成功？

Discovery Criteria: Specific to Each Offering探索標準：各方案專屬

Accelerated Launch加速啟動
Key criteria:關鍵標準：
Organization size
Customization requirements
Change management needs組織規模
客製化需求
變革管理需求
Workflow Implementation工作流實施
Key criteria:關鍵標準：
Number & complexity of workflows
Level of customization/automation
User adoption & training工作流程的數量與複雜度
客製化/自動化程度
使用者採用與培訓
Technical Advisory技術顧問
Key criteria:關鍵標準：
Integration complexity
Data migration needs
Scalability整合複雜度
資料遷移需求
可擴展性

Click to flip點擊翻轉

Discovery Criteria: Accelerated Launch探索標準：加速啟動

Criteria標準 What You Need to Know你需要了解的事 Example Questions範例問題
Workspace Design complexityWorkspace 設計複雜度 # of teams included in design — tells you how large/complex the audience is設計中包含的團隊數量——告訴你受眾規模和複雜度 How many teams are we launching? How differently will they use Notion?我們要啟動多少個團隊？他們使用 Notion 的方式差異有多大？
Administrative Policies & Operations管理政策與營運 # of guests, groups with specialized settings, people creating Teamspaces訪客數量、需特殊設定的群組、建立 Teamspace 的人員 Do you have contractors or seasonal employees? How might they create or use Teamspaces?你們有約聘或季節性員工嗎？他們會如何建立或使用 Teamspace？
Change Management & Enablement變革管理與啟用 # of weeks to deploy, # of live trainings部署週數、現場培訓次數 How fast will this be deployed? Where are the employees located (time zones, languages)?部署速度要多快？員工分佈在哪裡（時區、語言）？
Use Cases & Workflows使用案例與工作流 # of systems Notion to replace, pain points, gap between desired stateNotion 要替換的系統數量、痛點、與理想狀態的差距 What systems is Notion replacing? What pain points were previous systems causing?Notion 要替換哪些系統？先前的系統造成了哪些痛點？
Migration / Replacement Strategy遷移/替換策略 Complexity of data cleanup, reusing legacy data資料清理的複雜度、重用歷史資料 Are we migrating data? Can we re-use legacy data or start from scratch?我們要遷移資料嗎？能重用歷史資料還是從頭開始？

Discovery Criteria: Workflow Implementation探索標準：工作流實施

Criteria標準 What You Need to Know你需要了解的事 Example Questions範例問題
Stakeholders & Decision Structure利害關係人與決策架構 Executive sponsor goals, day-to-day owner availability, approvers, impacted teams執行層贊助人的目標、日常負責人的可用性、核准人、受影響的團隊 Who is the executive sponsor and what outcome are they prioritizing? Who signs off on scope changes?誰是執行層贊助人、他們優先重視什麼成果？誰核准範圍變更？
Current Process & Pain Points目前流程與痛點 Start/end triggers, major steps/handoffs, SLAs, top bottlenecks開始/結束觸發條件、主要步驟/交接、SLA、最大瓶頸 What event starts this process? Walk me through current steps. Where do delays happen?什麼事件觸發這個流程？帶我走一遍目前的步驟。延遲發生在哪裡？
Data, Artifacts, & Integrations資料、產出物與整合 Required fields, documents produced, systems to integrate, compliance constraints必要欄位、產出文件、需要整合的系統、合規限制 What information is necessary and where is the source? Which tools must Notion connect to?哪些資訊是必要的、來源在哪？Notion 必須連接哪些工具？

Discovery Criteria: Technical Advisory探索標準：技術顧問

Tool consolidation is a core Notion strength. Although complex migrations are usually carried out by Notion's Technical Architect team, these criteria are shared for awareness. 工具整合是 Notion 的核心優勢。雖然複雜的遷移通常由 Notion 的 Technical Architect 團隊執行，這些標準在此分享供你了解。

Criteria標準 What You Need to Know你需要了解的事 Example Questions範例問題
Source System Structure來源系統結構 Entities, hierarchy, relationships, status lifecycles, custom fields, volume estimates實體、層級、關聯、狀態生命週期、自訂欄位、容量估算 How is content organized in the source system? What is the content volume including attachments?來源系統中的內容如何組織？包含附件的內容量是多少？
Source System Specifics來源系統細節 Exact tools/versions, critical fields, naming conventions, automation rules, reporting artifacts確切的工具/版本、關鍵欄位、命名慣例、自動化規則、報表產出物 How many items need to be migrated? What features (tables, charts, macros, plug-ins) are utilized?有多少項目需要遷移？使用了哪些功能（表格、圖表、巨集、外掛）？
Permission Mapping權限映射 Current permission model, sensitive data areas, exceptions, expected access patterns, compliance目前的權限模型、敏感資料區域、例外、預期的存取模式、合規 What is the permissions structure? How will permissions be mapped to Notion?權限結構是什麼？權限如何映射到 Notion？
Integrations / Workflow Dependencies整合/工作流程依賴 Upstream/downstream systems, integration mechanisms, event triggers, failure modes上游/下游系統、整合機制、事件觸發、失敗模式 What integrations are connected? What custom functionality must be maintained?連接了哪些整合？必須維持哪些自訂功能？

Best Practices最佳實踐

Create standardized discovery documents建立標準化的探索文件
  • Discovery session notes and AI transcripts探索會議筆記和 AI 逐字稿
  • Complexity assessment scores複雜度評估分數
  • Resource estimates (SC hours, TA hours)資源估算（SC 工時、TA 工時）
  • Clear scope breakdown and deliverables清晰的範圍拆分和交付物
Establish clear boundaries建立清楚的邊界
  • Define what's explicitly in-scope vs. out-of-scope明確定義範圍內 vs. 範圍外
  • Require written change orders for scope modifications範圍修改需要書面變更單
  • Set expectations around customer resource commitments設定客戶資源投入的期望
Cost expectations as guidelines費用預期作為參考
  • Accelerated Launch (1-300 users): $5K-$15K USD range加速啟動（1-300 位使用者）：$5K-$15K 美元區間
  • Keep services under 20% of Annual Contract Value (ACV) for typical launches一般啟動的服務費用維持在年合約價值（ACV）的 20% 以下
  • Complex workflows requiring API development need additional scoping需要 API 開發的複雜工作流程需額外範疇界定
🔍
Don't forget the review process!別忘了審查流程！ If you're co-delivering with Notion, have a Technical Architect review the plan. 如果你與 Notion 共同交付，請讓 Technical Architect 審查計畫。

Now it's your turn! — Run Discovery現在換你了！ — 執行探索

Given what you already know, what discovery questions would you want to cover in a kickoff call with Milestone Mint? 根據你已知的資訊，你會在與 Milestone Mint 的啟動會議中想涵蓋哪些探索問題？

🏢
Customer Brief: Milestone Mint客戶簡介：Milestone Mint
  • Industry:產業： Financial Technology金融科技
  • Employees:員工數： 2,000+
  • Users:用戶數： 18M+
  • Key Tools Replaced:替換的主要工具： Confluence, Coda, Asana
  • Reason for Notion:選擇 Notion 的原因： IT Cost Savings & SimplificationIT 成本節約與簡化
  • Challenges:挑戰： Siloed workflows, rising IT costs, delayed SLAs, low tool adoption孤島式工作流程、IT 成本上升、SLA 延誤、工具採用率低
←
Previous上一單元
Unit 1: Introduction to Consulting ServicesUnit 1：顧問服務入門
Next下一單元
Unit 3: Solution BuildUnit 3：解決方案建構
→

2026-04-09 crawled and archived from academy.notion.com