7-Day First Production Unit Plan: Create, Review and Improve
Gary WhittakerCreator Project Milestone 10 · Article 2 of 3 · Apply
7-Day First Production Unit Plan
Create one complete, representative unit; review it against real standards; improve the work and the system; then decide whether the wider project should proceed.
1. Learn
Understand pilot production
Build scale-readiness control
Understand pilot production
2. Apply
Create and validate the pilot
3. Build · VIPCreate and validate the pilot
Build scale-readiness control
Answers save automatically on this device.
Why this Academy lesson uses a light colour format
Jack Righteous normally uses a black, white and gold identity. Academy lessons use a lighter working format because their exercises, production logs, review tables and records are intended to be printed, highlighted, annotated and saved as PDFs.
Jack Righteous normally uses a black, white and gold identity. Academy lessons use a lighter working format because their exercises, production logs, review tables and records are intended to be printed, highlighted, annotated and saved as PDFs.
Save a PDF: Click Print / Save as PDF, then choose Save as PDF in your browser.
Privacy: Your answers are stored only in this browser on this device. They are not submitted to Jack Righteous or Shopify. Clearing browser storage may remove them.
Required foundation: Complete Article 1 and bring your Milestone 9 production record.
Running example: Episode 1 of a six-episode AI music education podcast, plus its connected workbook section.
Decision
Which unit provides the best realistic test?
Which unit provides the best realistic test?
Why
The pilot must reveal useful evidence.
The pilot must reveal useful evidence.
Time
About 45–75 minutes.
About 45–75 minutes.
Complete when: the unit is representative, bounded and capable of exposing real production evidence.
Common mistake: Choosing the easiest unit rather than the most informative realistic unit.
Decision
Can production begin responsibly?
Can production begin responsibly?
Why
Missing prerequisites become expensive later.
Missing prerequisites become expensive later.
Time
About 45–75 minutes.
About 45–75 minutes.
| Requirement | Status | Evidence | Gap/resolution | Owner |
|---|---|---|---|---|
| Approved structure and outcome | ||||
| Inputs, sources and assets | ||||
| Dependencies, rights and approvals | ||||
| Tools, files, review and definition of done |
Stop when: a critical right, owner, input, approval or technical delivery path remains unresolved.
Decision
What was expected before work started?
What was expected before work started?
Why
You need a fair planned-versus-actual comparison.
You need a fair planned-versus-actual comparison.
Time
About 60–90 minutes.
About 60–90 minutes.
Complete when: production has started from approved inputs and the baseline is preserved.
Decision
Is a complete version ready for review?
Is a complete version ready for review?
Why
A fragment cannot validate the real workflow.
A fragment cannot validate the real workflow.
Time
Varies by format and evidence.
Varies by format and evidence.
Rights note: Documentation supports transparency; it does not itself determine legal ownership or copyright eligibility.
Decision
What passed and what failed?
What passed and what failed?
Why
General opinion is not actionable evidence.
General opinion is not actionable evidence.
Time
About 60–120 minutes.
About 60–120 minutes.
| Layer | Criteria/reviewer | Evidence | Pass or revision | Owner/priority |
|---|---|---|---|---|
| Content | ||||
| Audience fit | ||||
| Technical/accessibility | ||||
| Rights/evidence | ||||
| Brand/continuity/delivery |
Decision
What belongs to the unit and what belongs to the system?
What belongs to the unit and what belongs to the system?
Why
Surface fixes should not hide repeatable problems.
Surface fixes should not hide repeatable problems.
Time
Based on evidence and risk.
Based on evidence and risk.
| Feedback/issue | Classification | Root cause | Correction | System update/decision |
|---|---|---|---|---|
Common mistake: Applying every comment without testing it against the approved project outcome.
Decision
Proceed, revise or hold?
Proceed, revise or hold?
Why
The pilot must change future production.
The pilot must change future production.
Time
About 60–90 minutes.
About 60–90 minutes.
First Complete Production Unit and Validation Record
Milestone complete when: one representative unit has been produced, reviewed, corrected and approved through the intended system, and the pilot evidence has been used to decide whether the wider project is ready to continue.
Free result or VIP?
The free result is enough when:
- One creator controls most work
- The workflow is reasonably linear
- Review and rights risks are manageable
- Remaining units are similar
Continue to VIP when:
- Several contributors or workstreams must synchronize
- Feedback sources conflict
- Rights, technical or delivery risk is high
- Formal scale-readiness evidence is needed
Create with intention. Document the decisions. Release with purpose. Build something you own.
