Articles about industry - Nasty Rodent - Page 4

Question 1

How long does onboarding a game art outsourcing vendor actually take?

Accepted Answer

With a structured protocol and a complete onboarding package prepared in advance, eight weeks is sufficient to cover legal setup, documentation transfer, test asset validation, and first production batch. The eight weeks is not primarily vendor learning time — it is governance establishment time. A vendor with mature internal processes will absorb your art bible and technical spec quickly; the weeks are spent establishing the review cadence, acceptance criteria, and feedback loop that will carry the engagement through production. Without a protocol, onboarding happens informally during the first production milestone, and the structural questions that should have been resolved in week two are resolved at week eight, at scale.

Question 2

What is a first-pass approval rate and how do you track it?

Accepted Answer

First-pass approval rate is the percentage of delivered assets that meet all acceptance criteria on first review, without requiring revision before approval. To track it, you need two prerequisites: written acceptance criteria (not a subjective quality standard, but a specific checklist) and a per-asset validation log that records pass/fail status. Without both, first-pass approval rate is a feeling, not a metric. With both, it is the most useful leading indicator of brief quality, vendor calibration, and governance effectiveness that a producer or vendor manager has access to.

Question 3

What should be in a game art outsourcing brief package?

Accepted Answer

At minimum: a complete art bible, a technical specification sheet (polygon budgets, texture standards, naming conventions, LOD requirements, delivery format), two to three annotated keyframes showing what a passing delivery looks like, and written answers to the ten ambiguity questions that have historically generated the most revision requests in your pipeline. The brief package is your team's responsibility to produce, not the vendor's. If you do not know which ten questions generate the most revisions in your pipeline, that is diagnostic data — it means your revision tracking is not granular enough to be useful.

Question 4

How do you structure the test asset phase?

Accepted Answer

Select one asset that is representative of the production challenge — not the easiest in the batch, and not the most complex. Define acceptance criteria for that asset before the vendor begins. Run the asset through a staged review process: blockout approved before texturing begins, first full pass validated in engine before final delivery is accepted. Deliver feedback within 24 hours of each submission. Log the revision count and the root cause of each revision item. Use that data to update your brief and governance documentation before production begins.

Question 5

What causes the most slip in first-pass approval rates?

Accepted Answer

Brief ambiguity is the most common cause — when the brief describes intent without anchoring it to specific visual references, the vendor's interpretation diverges from yours without either side being aware of the divergence until delivery. Absent acceptance criteria is the second cause — when there is no written definition of what "done" means, every review becomes a negotiation. Feedback latency is the third — when internal reviews take five or more days, the vendor has already produced additional assets based on the same incorrect assumptions, compounding the revision load.

Blog - Page 4

Vendor Onboarding for Game Art Outsourcing: 8-Week Protocol That Prevents Milestone Slippage

In-House vs Outsource Game Art: How to Make the Right Call for Mid-core Projects