Cloud team at a large company

• 20Episodes planned
• 5 areasAdmin, developer, monitoring, billing, FAQ

How we planned it

1. 1

   We started by analyzing live sessions

   We sat through the live onboarding the team gives each customer twice, transcribed the recordings, and analyzed them. Instead of listing screens in order, we started from the flow the presenter uses and the points repeated again and again.

2. 2

   We defined the viewer first

   We decided the viewer is a customer engineer who has used other clouds before. So we cut the basics and focused on moving existing data, operating, and finding problems. Sentences were kept short to suit English narration with Korean subtitles.

3. 3

   Why 20 episodes

   One long video makes it hard to find a single feature, and cutting too finely loses context. So we followed real usage order and feature units, four to six minutes each across 20 episodes, so a policy change means editing only one episode. Features that may still change were left out of this series.

4. 4

   We rebalanced from feedback

   After the first outline, we heard that developers far outnumber administrators among real viewers. We kept 20 episodes, merged the admin episodes into four, and expanded developer episodes to seven, split by way of working.

5. 5

   Shot by shot scripts and review

   Each episode starts with learning goals and flow, then a table per shot with screen, English narration, Korean subtitles, and direction notes. Official documentation and the real console are the reference, and open questions were collected separately and confirmed through the client team review.

Deliverables

• 20 videos
• Scripts
• Screen capture
• Voice and edit

Photos set the mood and are not from the project.