# data[].attributes.body
loved seeing a demo, though as a non-technical person, it was hard for me to follow along sometimes. or know what was a placeholder thing vs what we would really be experiencing

# data[].attributes.body
I was able to mostly stay on top of my email. yay!

# data[].attributes.body
as a remote participant I appreciate Shawn asking people to speak up, or be closer to the mics, and repeating questions/comments when necessary.

# data[].attributes.body
The willingness of all to stop and answer questions in real time (even for things outside the scope of the present topic) was really helpful.

# data[].attributes.body
Maybe we can get Chad a seat at the main table so he can better hear/record the questions and answers.

# data[].attributes.body
Very welcoming environment and collaborative discussion on how to tackle this change.

# data[].attributes.body
This is mostly due to the temperature in the room and the packed agenda, but an additional break would have been nice after lunch. People were tired for sure and the heat didn't help the situation.

# data[].attributes.body
It was good to hear all the changes that would take place during and once FI is implemented.

# data[].attributes.body
There were a few heavy hitter items brought up and seemed to have an answer to sum it up as "we are still addressing that". This is concerning especially around communicating expectation. While there are phases to this entire project, we definitely want to make sure communication continues and we are not kicking some cans down the road as there are many aspects to governance in the organization. While we want a secure enterprise organization, we also want a secure and efficient science organization. To sum it up, it would be good to determine how best can we all continue to work together during this time of change, have active communication and what does that look like.

# data[].attributes.body
The mix of IT and non-IT among participants was powerfully beneficial to the process. For those outside of IT, thank you for speaking up, asking good questions, and staying involved. For the presenters and those of us with an IT support role, it might be helpful from time to time to stop and check for understanding, particularly when diving into complex design described from the perspective of IT. Not a strong criticism, just wanting to be triple sure we aren't losing anyone at any point during the discussion.

# data[].attributes.body
It was great to see and interact with such a large group. I think it really helped to have more interaction and questions - particularly from Ammo and Garth. Well done you two!

# data[].attributes.body
While I was able to hear most everything that was being said as an in-person attendee, I felt like there were quite a few instances where the online attendees would not be able to follow the conversation. When people asked questions from the periphery of the room, it might have helped for the question to be restated along with the answer directly to the microphones.

# data[].attributes.body
It was great seeing 'inside' FI and seeing in detail what they have planned. At times, however, it was too detailed / technical.

# data[].attributes.body
It was great to be able to meet in person, as well as have a video option for those who couldn't make it. Being able to chat with folks during breaks added to the experience. I even met some people for the first time or people I didn't know before the meeting!

Food is always greatly appreciated - it perks people up in the mornings and helps keep the momentum going! THANK YOU!!

Having long enough breaks where we could get tasks done was hugely helpful.

The diversity of speakers was great, especially having contractors there.

# data[].attributes.body
Interspersing the Fischer and Moran folks with our own folks, rather than seating them and everybody in separated groups, seemed to work very well. It gave more of a feeling that this was all a team instead of isolated pockets of staff.

# data[].attributes.body
As others have mentioned. It was difficult to pay attention or stay awake when it was so hot. There are some folks that are naturally soft speakers. Being closer to the mics on the table would have helped. Perhaps a separate mic at the podium if that could be arranged in the future.

# data[].attributes.body
Just that this was a good reminder that as presenters we need to fight the overuse of acronyms. As an organization we historically use many while presuming that everybody knows what we are talking about. The same goes with mentioning technologies. Quick mentions of what LDAP is, PAM vs. PAM, etc., would not take long when first mentioned.