Launch Director: portfolio of launches

01

From launch manager to launch director

In simple words

A cook makes one great dinner. A head chef runs a kitchen that makes great dinners every night, even when the chef is not at the stove. A launch director is the head chef of launches.

Before this course: Launch Systems: funnels, partners and post-launch (course 3.13.3), which builds on Launch Basics (course 3.13.1) and Launch Marketing: Hype, Waitlists, Drops (course 3.13). You can already draw a funnel, tag links, plan an email sequence, run partners with disclosure, keep a claims register, handle delivery and refunds, and write a runbook and post-mortem. This course asks a bigger question: how do you lead many launches, run by many people, so each one is better and more honest than the last?

Key facts

A launch is one product or offer going out on one date. A launch programme is all the launches a team runs over a season or year. A portfolio of launches is the record of those launches: plans, numbers, post-mortems and what changed.
A launch director owns four things:

Area	What it means	Proof it works
Portfolio	Which launches happen, when, and why	A calendar with a reason for each launch
Standards	The rules every launch must meet (gates, ethics code)	Gates passed and recorded
People	Owners, partners, roles and access	One named owner per task
Learning	Post-mortems, a launch library, tracked actions	Each launch starts from the last one

The director does less hands-on work and more deciding, checking and teaching. If every launch still depends on you doing everything, you have a launch, not a programme.
Capacity is real. A small team can only run so many launches well. Example: 3 people with about 30 spare hours each a week for 4 weeks have about 360 hours. If one launch takes about 150 hours, two launches (300 hours) fit; three do not.
Audiences need rest. The same list getting launch emails every few weeks learns to ignore them. Space launches out and send useful, non-selling messages in between.
The launch library from course 3.13.3 becomes shared: one folder per launch with the plan, claims register, sequence, launch table and post-mortem, all named the same way.

Step by step

List every launch you (or a practice team) might run in the next 12 months.
For each one, write one line: who it is for and why now.
Estimate the hours each launch needs and the hours your team really has. Write both numbers.
Cut or move launches until the hours fit, with some time to spare.
Write the four director areas (portfolio, standards, people, learning) and rate yourself Strong, Shaky or Missing for each.
Set up one shared launch library folder with a naming rule, for example "2027-03 spring-course launch".
Check: a 12-month list with reasons, an hours check that fits, four ratings and one library folder.

LESSON 01From launch manager to launch director

LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:00

Voice

Read the video script

[Host] "A cook makes one dinner. A head chef runs the kitchen."
[Text on screen: Portfolio · Standards · People · Learning] "A launch director owns four things: which launches happen, the rules they follow, who does the work, and what the team learns."
[Text on screen: 3 people x 30 hours x 4 weeks = 360 hours] "Count your hours. If a launch takes 150 hours, two fit. Three do not."
[Host] "Fewer, better launches beat many tired ones."

Try it now

Write your 12-month launch list with a reason for each, check it against your team's real hours, and rate the four director areas.

ClaudeStuck? Copy a ready-made prompt for Claude

Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.

For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.

I'm learning "Launch Director: portfolio of launches" on The Future Market. Lesson 1: "From launch manager to launch director".

What the lesson teaches:
- A launch is one product or offer going out on one date. A launch programme is all the launches a team runs over a season or year. A portfolio of launches is the record of those launches: plans, numbers, post-mortems and what changed.
- A launch director owns four things:
- Area - What it means - Proof it works
- Portfolio - Which launches happen, when, and why - A calendar with a reason for each launch
- Standards - The rules every launch must meet (gates, ethics code) - Gates passed and recorded
- People - Owners, partners, roles and access - One named owner per task
- Learning - Post-mortems, a launch library, tracked actions - Each launch starts from the last one

The exercise I'm working on:
Write your 12-month launch list with a reason for each, check it against your team's real hours, and rate the four director areas.

I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.

I'm a parent helping my child (about 8 years old) with a lesson called "From launch manager to launch director" from the course "Launch Director: portfolio of launches".

Here's what the lesson says:
A cook makes one great dinner. A head chef runs a kitchen that makes great dinners every night, even when the chef is not at the stove. A launch director is the head chef of launches.

The activity:
Write your 12-month launch list with a reason for each, check it against your team's real hours, and rate the four director areas.

Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.

Open Claude

Sources

Earlier courses in this track: 3.13, 3.13.1 and 3.13.3. The capacity example is simple arithmetic.

My notes

I learned this

02