How this studio is built

From brief to finished asset

Production Pipeline

One Role owns the look, another owns the files, and a third owns sound. Assets are generated by hand today, and the reviewing Role decides whether the Owner needs to look at all.

Production Pipeline: how it runs, as a flowchart1The project lists the assets itneedsan asset list, to the Art DirectorThe project's Agent2Requirements writtena requirements brief per asset, to the Sprite ManagerArt Director3Asset generated and fittedBy Sprite Manager, with the Owner generatingcandidate assets that pass the technical checks4ReviewedBy Art Director; the Owner too for animationaccepted, or rejected with a reason for the next prompt5Delivered to the projectthe accepted asset with its source recordArt Director6Used in the projectthe asset, in the finished workThe project's AgentProduction Pipeline: how it runs, as a flowchart1The project lists the assets itneedsBy The project's Agentan asset list, to the Art Director2Requirementswrittena requirements brief per asset, to theSprite ManagerArt Director3Asset generated and fittedBy Sprite Manager, with the Ownergeneratingcandidate assets that pass the technicalchecks4ReviewedBy Art Director; the Owner too foranimationaccepted, or rejected with a reason forthe next prompt5Delivered to theprojectthe accepted asset with its source recordArt Director6Used in the projectBy The project's Agentthe asset, in the finished work

The pieces

Style sets
A named look, written down, so it can be asked for again.
Prompts
The subject and the convention — most requests write only the first.
Verdicts
Reviewed against a written standard, not a mood.
Sound
The Audio Manager owns sound until it is delivered to a project: sourcing, licensing, review and storage.

Where this was worked out