Milestone 9: Build a Repeatable Production Working Cycle
Jack Righteous20 Milestones: From Project to Platform — Milestone 9 of 20
Build a Repeatable Production Working Cycle
Milestone 8 planned the work. Milestone 9 makes the work move.
You will establish a practical cycle for selecting one manageable production unit, preparing it properly, completing focused work, controlling versions, managing review and revision, documenting approval and improving the next cycle.
Why a production plan is not enough
A strong plan can still fail when too much work is started, source files become confused, feedback arrives without clear criteria or work remains “almost finished” without formal approval. A working cycle provides one repeatable route through active production.
Control the start
Begin only when the task, inputs, owner, dependencies and completion standard are ready.
Control the work
Use focused sessions and limit the number of active production units.
Control the evidence
Preserve versions, decisions, review notes and approval records.
Improve the next cycle
Use actual production evidence instead of assumptions about what slowed or helped the work.
The nine-stage production working cycle
| Stage | Question | Required result |
|---|---|---|
| 1. Select | Is this the correct production unit to start now? | One required, manageable unit is chosen. |
| 2. Prepare | Are its inputs, dependencies and standards ready? | The unit passes the Ready check. |
| 3. Produce | What focused work must happen? | A defined session objective is completed. |
| 4. Record | What changed and what must be preserved? | A traceable version and decision record exist. |
| 5. Review | Does the work meet the approved criteria? | Specific feedback or approval is recorded. |
| 6. Revise | Which accepted changes are required? | A controlled revised version is produced. |
| 7. Approve | Has the production unit passed its required gates? | The authoritative version is accepted. |
| 8. Close | Are files, evidence and status complete? | The approved unit is properly closed. |
| 9. Improve | What should change in the next cycle? | One evidence-based workflow improvement is recorded. |
Choose a manageable production unit
The cycle should operate on a finishable, reviewable part of the project—not the entire project at once.
Book or guide
One chapter, worksheet, editing pass or formatted section.
Podcast or video
One script, recording, edit or show-notes package.
AI music or audio
One song draft, arrangement revision, mix review or contribution record.
Course or workshop
One lesson, exercise, recorded module or learner test.
Campaign
One landing page, email, asset group or tracking configuration.
Creator platform
One page, offer, navigation section or customer-journey test.
A useful unit is specific, finishable, reviewable, traceable and connected to a required Milestone 8 deliverable.
Do not confuse selected with Ready
A task becomes Ready only when the creator can begin responsibly.
- The correct production unit is selected.
- Required inputs and source files are available.
- Dependencies are complete.
- One accountable owner is identified.
- The expected output is clear.
- The definition of done is visible.
- Review criteria and reviewer are known.
- No unresolved blocker prevents the work.
Limit active work
Opening more tasks than you can finish creates unfinished inventory. Set a practical limit for work that may be active at one time. A solo creator might allow one active writing unit, one editing unit and one item waiting for review. A different project may need another limit.
The number is not universal. Base it on actual capacity, review availability and complexity.
Use focused working sessions
- Confirm the production unit.
- Open the latest authoritative working file.
- State the session objective.
- Define the stopping condition.
- Complete the focused work.
- Save a new controlled version.
- Record decisions and unresolved items.
- Update the task status.
- Identify the next action.
Session objective formula: During this session, I will [specific action] on [production unit] until [observable stopping condition].
Example: During this session, I will revise the opening of Chapter 2 until every paragraph supports the approved central message and the file is ready for editorial review.
Give every status an operational meaning
| Status | Meaning |
|---|---|
| Not Ready | A required input, dependency, standard or decision is missing. |
| Ready | The unit can begin without reopening foundational decisions. |
| In Progress | Focused production work is actively happening. |
| Waiting | Work can continue after a known external input or response. |
| Under Review | A specific version is being checked against stated criteria. |
| Revision Required | Recorded changes must be completed before approval. |
| Approved | The authoritative version passed its required review. |
| Complete | The approved version, evidence, storage and records are closed. |
| Blocked | Work cannot continue until a defined problem is resolved. |
Approved and Complete are not identical. Approval accepts the work. Completion confirms that the accepted work and its evidence have been properly closed.
Use simple version control
At minimum, record the project, deliverable, production unit, version number, date, owner, change made, current status, approved version, replaced version and storage location.
Useful naming pattern: Project_Deliverable_Version_Date_Status
Example: CreatorGuide_Chapter02_v03_2026-07-29_UnderReview
- Never overwrite the only usable previous version.
- Identify one current working file.
- Identify one authoritative approved version.
- Keep source material separate from final exports.
- Record why a version was accepted or replaced.
Turn feedback into controlled decisions
- Submit the correct version.
- Review against pre-set criteria.
- Record the feedback.
- Separate required changes from suggestions.
- Accept, reject, defer or clarify each item.
- Assign revision responsibility.
- Complete and verify approved revisions.
- Approve or begin another defined review cycle.
Useful categories include required correction, quality improvement, audience concern, technical issue, rights or attribution issue, accessibility issue, optional suggestion and out-of-scope request.
New ideas that expand Version 1 should be recorded for later consideration rather than added automatically.
Use the definition of done as the exit condition
A definition of done should be observable, specific, connected to audience and quality requirements, and clear enough for another reviewer to understand.
Too weak
“Episode completed.”
Operational
“Episode 1 has an approved edited audio file, verified title and description, completed transcript, documented music permissions, final artwork and delivery-ready export.”
Respond accurately when the cycle is interrupted
| Condition | Meaning | Response |
|---|---|---|
| Delay | The work remains possible but later than planned. | Update the schedule and affected dependencies. |
| Blocker | The work cannot continue. | Name the required decision and owner. |
| Issue | A current problem is affecting production. | Record and resolve it through the issue process. |
| Risk | A possible future problem may affect production. | Track its trigger, prevention and response. |
| Scope change | A proposed change alters approved Version 1. | Use change control or return to the relevant earlier milestone. |
Use AI without surrendering production authority
AI can help clarify tasks, prepare checklists, compare versions, organize feedback, identify possible missing steps and assess schedule effects. It should not approve its own output, invent completed work, manufacture contribution evidence, assume rights, silently change requirements or mark a task complete without human verification.
Cycle-audit prompt: Review this production-cycle record using only the supplied task, files, status definitions, review criteria and decisions. Identify missing evidence, unclear status changes, possible version confusion and unresolved blockers. Do not claim that work was completed or approved unless the record explicitly shows it.
Continue preserving human decisions and revisions through the Milestone 4 human-contribution system.
When Milestone 9 is complete
- One correct production unit moved through the full cycle.
- Readiness was confirmed before work began.
- The working session had a clear objective and stopping condition.
- Active work stayed within a manageable limit.
- Versions and important decisions were recorded.
- The correct version passed through review.
- Required revisions were completed and verified.
- Approval and closure evidence were preserved.
- The final status is accurate.
- One improvement is recorded for the next cycle.
Apply the cycle through your Creator Road
Find Your Sound can use the cycle for generations, arrangements, recordings, mixes and masters. Find Your Voice can use it for research, drafting, editing and language approval. Find Your Brand can use it for pages, offers, visual assets, platform setup and customer-experience testing.
Frequently asked questions
Is Milestone 9 another production plan?
No. Milestone 8 planned the work. Milestone 9 operates one manageable unit through preparation, production, review, approval and closure.
How large should one production unit be?
It should be small enough to finish and review, but meaningful enough to advance a required deliverable.
Do I need project-management software?
No. A document, spreadsheet, folder system or simple board is enough when statuses, files, decisions and evidence remain clear.
What is the difference between Approved and Complete?
Approved means the work passed review. Complete means the approved file, evidence, storage and records were also properly closed.
Can AI manage the working cycle for me?
AI can assist with organization and review, but the creator remains responsible for readiness, decisions, rights, approval and accurate completion records.
