Feedback

When giving feedback keep in mind:

Be specific and actionable

• 1. If it's approved or approved with notes, be direct and talk about next steps.

     1. • Ex - "This looks great!  High poly is approved, after the you remove the 2 bolts highlighted in the image below.  Please move onto low poly and bake and then resubmit once you have a 1st pass."

  2. Define your needs, don't ask them to experiment without a roadmap.

     1. • Ex - "I've provided a mood board and some past examples of final deliverables in the Box folder.  As a first step I'd like you guys to a page of 25 rough thumbnails (example sheet on box) for us to review.  Then we will pick a few an move onto line work."

  3. If you call out something you make sure you point it out in your image so there can be no confusion.

  4. Don't use slang or pop culture references unless you also include visual reference.

Examples examples examples

• 1. Provide as much technical or stylistic examples of what you'd like to see from them as possible.  Weather its photos, example source assets, or tweaks you make to their asset.

  2. It always helps to reference previous assets that they have built as workflow/quality/style examples.

  3. If no example exists, spend 10 minutes and create an example with part of the delivered source assets.

Customize feedback to the external team

• 1. Do the artists speak english, if not, be aware that a non-artist will probably be translating your text. If possible do not put text in your images, it makes it harder to copy/paste and translate.

  2. Some teams will respond better to video feedback

  3. Some teams work better with a bulleted text list

  4. If a problem persists call them on Skype/Hangouts and talk though what your seeing with them.

Build trust with the external lead/artist

• 1. The external artist or lead on the vendor side is your swim buddy.  Build connection with them and a deep understanding of what good looks like.  That way if a delivery comes that in that's off target you can call it out and have them fix it without having to provide detailed feedback.

Know when to cut it off

• 1. There is a point of diminishing return.  If the fixes to an asset are less than 1 hour, pull it in and do it yourself.  Then make sure to send the revised file back to the external team and explain what you did.  Use this as a teachable moment so that they can learn from it for next time.

  2. If you've iterated more than 3 times in one phase, something is wrong.  Either they don't understand what you're asking for or we did were not provided with enough initial source material/direction.  Get them on a call and talk though it.

Keep an eye on your friction %

• 1. Ideally you should not spend more and 15% of the time it would take you to create the asset in feedback.

  2. Example: If you could make an asset your outsourcing in 8 hours, don't spent more than 1.5 hours giving feedback.

  3. If you've gone over 15% take a look at what you're sending them to start with and the kind of feedback you're giving them.