Milestone 9: Build a Realistic Production Plan for Your Creator Project
Gary WhittakerBuild a Realistic Production Plan for Your Creator Project
Convert the approved structure from Milestone 8 into a production system that shows what must be made, in what order, by whom, under which standards and through which repeatable working cycle.
Understand production planning
Complete the free seven-day plan3. Build · VIP
Create advanced production control
Jack Righteous normally uses a black, white and gold identity. Academy lessons use a lighter working format because their planning tables and records are intended to be printed, highlighted, annotated and saved as PDFs. The lighter presentation uses less ink and remains readable in colour or black and white. Gold remains the Academy accent.
What this milestone changes
Before
“I have six podcast episodes and a workbook to create.”
After
“I know every task, dependency, owner, review gate, version and completion standard required to produce and deliver them.”
1. Separate the planning layers
| Layer | Question | Example |
|---|---|---|
| Content map | What does the project contain? | Six episodes and six workbook sections. |
| Task list | What actions produce it? | Outline, write, record, edit and package. |
| Schedule | When should work happen? | Script review on Thursday. |
| Production system | How does work become ready, move, get approved and finish? | Approved outline → script → review → recording → edit → package. |
2. Define production units
A project unit is part of the audience experience. A production unit is the smallest deliverable that can move and be reviewed. A task is an action that creates or changes it.
3. Choose the smallest useful flow
An adaptable flow is: backlog, not ready, ready, in progress, review, revision, approved, packaging, delivered and archived. Use only stages with clear entry and exit rules.
4. Write tasks that can be completed
Every task should name the action, owner, required input, deliverable, definition of done, dependency, review requirement and storage location.
Weak
Work on Episode 1.
Strong
Draft Episode 1 from the approved outline and references. Deliver a complete script containing every teaching beat, example and workbook cue.
5. Make dependencies and blockers visible
Track finish-to-start, approval, asset, contributor, platform and rights/evidence dependencies. A blocker record should state what is blocked, why, who resolves it, the decision required, the next review point and the fallback.
6. Assign ownership and roles
| Role | Responsibility |
|---|---|
| Owner | Accountable for completion. |
| Contributor | Provides work, information or an asset. |
| Reviewer | Evaluates against criteria. |
| Approver | Authorizes movement forward. |
| Informed | Needs the result or status. |
A solo creator may hold all roles but should still separate creating, reviewing and approving.
7. Define ready and done
A task is ready when purpose, input, owner, deliverable, criteria, location and dependencies are known. It is done when the deliverable exists, review comments are resolved, naming and records are correct, approval is recorded and the next task can begin.
8. Put review gates where risk changes
Use outline, accuracy, rights/evidence, technical, brand and final-release gates only where they prevent meaningful downstream rework. Every gate needs a trigger, reviewer, criteria, pass evidence and correction owner.
9. Limit work in progress
Work-in-progress limits reduce context switching, version confusion and unfinished work. When a stage is full, finish or unblock existing work before starting more.
10. Build the working cycle
The cycle may be daily, weekly, biweekly, monthly or release-based. It must reflect real capacity.
Apply Core Squared: Flame protects purpose; Rock defines the non-negotiable result; Cycle defines rhythm; House holds tools and files; Operator resolves conflicts.
11. Plan capacity, buffers and fallbacks
Classify work as light, moderate, heavy, specialist or blocked. Consider research, creation, editing, assets, review and coordination. Preserve task, review and delivery buffers. Decide what may be simplified, delayed, replaced or removed—and what cannot be compromised.
12. Control files and versions
EP01_SCRIPT_V01
EP01_SCRIPT_REVIEWED_V02
EP01_SCRIPT_APPROVED
EP01_AUDIO_MASTER
EP01_RELEASE_PACKAGE_FINAL
Define the source, draft, approved, final and archive locations before production grows.
13. Preliminary readiness filter
Rate task clarity, ownership, dependency visibility, ready/done definitions, review design, capacity fit, file control, buffer and delivery confidence from 1 to 5. A critical rights, approval, dependency or capacity weakness overrides the total.
- Name production units and stages
- Convert one unit into strong tasks
- Identify dependencies and blockers
- Assign owners and reviewers
- Define ready and done
- Choose a realistic cycle and WIP limits
- Explain file and version control
Continue the milestone
The free implementation produces a complete Creator Production Plan and Working Cycle Record. VIP adds assumptions validation, critical-path control, bottleneck analysis, change control, advanced review architecture and collaborator-ready handoffs.
Create with intention. Document the decisions. Release with purpose. Build something you own.
