# data[].attributes.body
There was a lot more consistency this time around, but there were still some hiccups (e.g., the lesson narrator used a different pronunciation than the passage narrator). One possible solution, if possible, is if AudioLink could play a clip of a passage recording for the lesson narrator, or vice versa.

# data[].attributes.body
It's great to represent a wider variety of accents, and not just in fiction where the character would/might have one, but there were also cases where I wondered whether a VO with an accent was the right choice, even if they were of the same background as the character. Sometimes the backgrounds matched but the character would most likely not have an accent so having a VO with an accent felt like we were layering that on in a way that didn't fit. The other option was a VO that didn't match the background which also didn't feel like the best choice. We could use some more discussion or guidelines around audible accents... though I also don't want to overthink this.

# data[].attributes.body
I completely agree with above note on pronunciations! I think we need to have an audio clip ready of pronunciations made by the voice artist for the passage or lesson. It would help tremendously.

# data[].attributes.body
Waiting until the VO comes back in a future batch to record the pick up can delay a lesson for weeks for just one line, or force us to live with a recording that is really not ideal. How can we reduce the need for pick ups, and get pick ups in more quickly when we do need them?

# data[].attributes.body
Sharing scheduling meetings to all editors ahead of time improved the process but was sometimes inconsistent. If all editors were invited to all audio meetings from the start, that would make things easier for full transparency.

# data[].attributes.body
We hand edit scripts for pronunciation, emphasis, VO assignments. Are there ways we could make this easier or automate?

# data[].attributes.body
We hired a wonderful set of voice artists who brought a lot to the passages. However the assignment process became quite a puzzle since we needed specific people for specific passages, but those passages were ready at a certain point and couldn't wait to be recorded. So there could be situations where we have a batch where every passage would ideally have a different narrator, which isn't great for using the recording time efficiently. This wasn't always a problem but definitely happened more than once. If we shared more VOs across projects it could help us be more nimble about scheduling, getting pick ups, and making sure we use their time wisely.

# data[].attributes.body
Having step-by-step documentation for the audio process helps for such a multi-layered process, although sometimes steps change on the fly, etc. Video tutorial, etc. might help new people understand the process too.

# data[].attributes.body
Because of the sign-up page, it was easier to know whether to accept or decline invitations. But what would really be helpful would be to list the lessons being recorded in the session, not just the talent's name. +1

# data[].attributes.body
Scripts are organized well, but perhaps can be formatted in an order more conducive to editorial. Some people have the first lesson and fifth lesson in a script and we end up jumping around the script to let editorial off the hook, as opposed to setting up the order of lessons that way.

# data[].attributes.body
Is there a way we could know sooner when our lessons will be recorded? Also, to the above comment, there was a time gap between when the invitations went out for the sessions and when we found out which session was being recorded when. Could we tighten that up?

# data[].attributes.headline
Guessing which backgrounds/accents we want represented in our audio

# data[].attributes.subject
Guessing which backgrounds/accents we want represented in our audio

# data[].attributes.body
Our guesses were pretty spot on but these decisions had to be made quickly before we knew what and who some of our passages would be about. We had VOs who weren't used, and passages that didn't have a cultural match that could have really benefitted from it. How do we get better foresight or adjust the process to increase our ability to match culture/background/accent when necessary?

# data[].attributes.body
We capped at 10 per usual, which was just enough for this project, but we could do even better with aligning content to voices and increasing representation if we were able to work with more people. Could sharing VOs across projects help?

# data[].attributes.body
Although this worked well, there's always room for improvement!