Prod Tips #001 - #005
Prod Tip #001: Use action words when taking notes.
The notes we take are essentially instructions for artists to get the version closer to approval. Using action words keeps the notes concise, to the point, and easier to follow.
Prod Tip #002: In bullet form, outline the action items for the team to do at the end of a review or discussion.
It's sometimes hard to know which comments are important to note during meetings, and typing dialogues verbatim isn't the best thing to do. Though it provides context, verbose text makes the notes confusing. Adding action items at the start or end of the note helps everyone be on the same page, clarifies what the next steps are and who is doing it.
Prod Tip #003: Type โ0000โ in the To/Cc field of an email to prevent it from sending too soon.
I do this before I start typing the email. After entering who the email should be sent to, I add "0000" in the distro. Most platforms will not let you send the email if an invalid entity is entered in the To/Cc field, so it's a good safety net from accidentally hitting send too soon, or a good popup reminder to proof read before sending. Another method is to NOT add anyone in the distro until the end, but I don't like it because I tend to forget the complete list if I wait.
Prod Tip #004: Spell peopleโs names correctly and ask how to properly pronounce it.
This one might be a pet peeve as people sometimes spell my name wrong. It's one vowel off, but it gets me everytime. Lol. (Especially when friends have known me for years ๐) But peeved or not, it comes down to respect. You wouldn't want to be called by a name that's not yours, right? Same for others. It's a small thing to cross check but goes a long way in building a good relationship with your team.
Prod Tip #005: When sending requests, be clear.
What is the request? Who is it assigned to? When is it needed?
โ- end of notes โ-