1 Define

Input: idea, intended use and any existing material. Decision: what is this track for, who is it for, what should it feel like, and what must remain true?

• Write a one-sentence project purpose.
• Name the emotional target and creative lane.
• Set constraints: genre, performance, structure, deadline, collaborators and intended use.
• Define what “better” or “finished” means before generation.

Finish line: you can explain the project and its success standard without mentioning a platform feature.

2 Create & Compare

Prepare human-origin inputs, generate controlled alternatives and compare before spending more credits or time.

• Save lyrics, notes, melody ideas, references and source material.
• Change one major variable at a time.
• Compare emotional impact, identity, performance, structure and edit potential.
• Select a keeper because it serves the brief—not because it is merely newest.

Finish line: one candidate is selected and you can explain why.

3 Shape

Diagnose what prevents the keeper from doing its job, then make the smallest useful production intervention.

• Repair structure, lyrics, vocals, timing, arrangement or instrumentation.
• Use stems, MIDI, recording or a DAW when those tools solve a defined problem.
• Compare the changed version against the keeper.
• Protect strong elements while revising weak ones.

Finish line: the project has survived intentional editing and still serves the brief.

If you use Suno and already have a keeper, the Studio 2.0 Training Map is one implementation gateway inside this pass.

4 Prove

Document the decisions and permissions that make the project understandable later.

• Record what you wrote, selected, changed, rejected, performed or added.
• Preserve serious prompts, source inputs, versions and edit history.
• Confirm collaborator roles and relevant permissions.
• Check current platform terms for the intended use.

Finish line: another informed person could understand how this version was made and what still needs verification.

5 Release

Validate the exact master and package only what the next destination requires.

• Check the final audio, versions, artwork, lyrics, credits and metadata.
• Resolve rights, voice, sample and collaborator questions before delivery.
• Choose distribution, direct sale, client delivery, licensing or controlled testing based on the actual goal.
• Create a small promotion package with one clear listener action.

Finish line: the correct asset is delivered with accurate supporting information.

6 Review

Turn the finished project into evidence for the next one.

• Check links, credits, claims and delivery.
• Review audience response, saves, shares, sales, signups or other goal-specific signals.
• Record what worked, what failed and what should become a reusable method.
• Archive masters, sources, stems, prompts, agreements and decisions.

Finish line: you know what to repeat, what to change and what the next project should begin with.