iteration log
Submission Workflow
Four versions to decide who absorbs the variance when work backs up
format
Standard operating procedure
scope
Commission intake
ownership
Built & owned end-to-end
01 what i built
This is the workflow I reworked longest — across my entire tenure. The company kept growing, and with it the volume of work moving through review, so the system needed near-constant adjustment. The mechanics barely changed; each version moved work from submission to review to onboarding in roughly the same steps. What changed every time was who absorbed the variance.
Version one was unstructured: submit any amount, any time, all costs on us. Demand was unpredictable and quality uneven, so the pipeline couldn't plan. Version two overcorrected into a single annual window — predictable for the company, punishing for artists. Miss the window, and you fell behind for a year, and for a population where producing and shipping work is already effortful, one date concentrated all the pressure in the wrong place. Rolling intake came next — submit anytime, with a per-artist limit each quarter — and it was better, but intake never paused, so it still arrived unevenly and outran what capture and post-production could absorb. It also let the most prolific artists compound their advantage: more submissions, more feedback, more sales, while quieter artists fell further behind.
The fourth version resolved it. Instead of a per-artist limit on continuous intake, a quarterly cap bounded the whole batch of submissions each quarter and reviewed it on a fixed cycle — which matched intake to what capture and post-production could absorb, and made budget forecasting more reliable. It also allocated access deliberately: the cap held submission slots so high-engagement artists couldn't crowd out the quieter ones.
02 the artifact
↳ the cap decides where the variance sits — that's the whole redesign
03 What it proved
50%+
reduction in review and decision timelines — from moving review async, not from the cap
4
versions to land the structure that held — each change driven by artist feedback and throughput data
December
surge forecast and redirected to summer every year — no backlog, no artist pushback
Every version of this workflow worked mechanically. The earlier ones just left the variance on whoever was least able to absorb it — sometimes the artists, when a single annual date fell on whoever couldn’t make it; sometimes the team, when that same window landed a year’s worth of work at once and slowed everyone’s turnaround; sometimes the quieter artists a rolling pipeline let fall behind. The fourth version was right because it made that a deliberate choice: the cap decided where the variance would sit — on planned capacity the program controlled — instead of leaving it on whoever couldn’t absorb it, and held slots so the most consistent high-volume submitters couldn’t crowd out the rest.