# data[].attributes.body
The attendance for these many leaders was great. It shows the importance of having meetings like this take place - the value that leaders from throughout the PDC and connected departments hold for this opportunity to get together to share.

# data[].attributes.body
Great aspect to keep things focused and on track. It felt like accurate time was given to each topic and we moved along at a great pace.

# data[].attributes.body
We should follow the standards established by the company's meeting culture. For this long of a meeting there should be a break, and it should not be scheduled for the entirety of the two hours. For example, it could be set to end at the 1 hour 50 minute mark to allow everyone to get to their next meeting - then hold to having a hard stop for the meeting and questions at that point.

# data[].attributes.body
It would be beneficial for all groups to call out the meanings behind acronyms. For example, BTA? CRM?, etc.

# data[].attributes.body
A standard / expectation was set for asking questions, but then it wasn't followed. Yes, in most of these cases there was time remaining for that person or subject, but a best practice should be set and followed.

# data[].attributes.body
Appreciate all who contributed to the actual presentation and how well they are aware of their business. Look forward to seeing how this evolves and the continued improvement of information.

# data[].attributes.body
I think ti would be even better if we have the Executive strategy, then the PDC as a whole before moving into each area. This would help trace back each area's deliveries to the greater mission.

# data[].attributes.body
I enjoyed being grounded in our executive strategy and working through what each area is doing to support that.

# data[].attributes.body
Find a way for people to capture their questions for later in the meeting. Maybe provide some sticky notes to write on if we do not want folks on their laptops.

# data[].attributes.body
I think the timer helped to keep the meeting on track. Appreciate Carl coming up with the idea.

# data[].attributes.body
Great session! looking forward to more to come in the future!

# data[].attributes.body
Provide a bit more structure and detail on what exactly you want reported out to not only the responsible parties, but to the individual in charge of pulling these slides together.

# data[].attributes.body
Definitely work in a 5-minute restroom break.

# data[].attributes.body
Everything! I seriously enjoyed this time together and learning about what everyone is working on. In our busy, dynamic world, it was great to get together as a group and talk through our big rocks we are working on.

# data[].attributes.body
The QBR should be done after the quarter is complete. So Q3 QBR should be done in October. This would make it a true QBR with accurate data for the quarter.