1. People
1.1. Client Team
1.1.1. Tech Point
1.1.2. Business Point
1.1.3. Steering Point
1.2. TW Team
1.2.1. BA
1.2.2. UX
1.2.3. PM
1.2.4. Tech
1.2.5. QA
2. Process
2.1. Planner
2.2. Key Activities
3. Pitfalls
3.1. Over stressful / Less stressful
3.2. Over elevate clients' expectation
3.3. No enough flexibility to adapt changes
3.4. Over focus on the results
4. Practical Tips
4.1. Gain Interests & Trust
4.1.1. Manage as a project, use agile practices
4.1.2. Build ONE-team
4.1.3. Demonstrates expertise
4.2. Collaborate Driving
4.2.1. Collaborative facilitation
4.2.2. Draw out their own design skills
4.3. Adapt to Changes over Following plan
4.3.1. Expect unexpected
4.3.2. Daily catchup/consolidation/replan
4.4. Homework
4.5. Continuous "Integration" & "Deploy"
5. Purpose
5.1. Client Expectation
5.2. TW Expectation
5.3. Team Expectation
6. Product
6.1. Big Picture of Client's Business
6.1.1. History, Industry
6.1.2. Business Model
6.1.2.1. Offering
6.1.2.2. Infrastructure
6.1.2.3. Customer
6.1.2.4. Finance
6.1.3. People
6.2. The Problem
6.3. The High-level Solution(s)
6.3.1. The Vision
6.3.2. The Strategy
6.3.3. ROI Evaluation
6.3.4. Assumptions
6.3.5. Risk Evaluation
6.4. Shape the Delivery Plan
6.4.1. High-level Requirements
6.4.2. User Persona, Goals
6.4.3. Core User Journeys
6.4.4. Cross Functional Requirements
6.4.5. Master Story List
6.4.6. Technical Arch Discoveries/Spikes
6.4.7. RAIDs
6.4.8. Estimation & Prioritization
6.4.9. Release Plan
6.4.10. Communication Plan
6.4.11. Governance & Steering
6.4.12. ...
7. Preparation
7.1. Learn Inception Techniques from Previous Cases
7.2. Rehearsal of key activities/exercises
7.3. Business Spike beforehand
7.3.1. Business Model Canvas
7.3.2. Glossary