# data[].attributes.body
Our team coordination was outstanding! I love how everyone showed up to help during the event and went above and beyond to support (some even over the weekend prior to the AM)

# data[].attributes.body
I was a bit dissapointed with the atendee numbers. Was hoping we would get closer to 500. Unsure what we could have done to increase our numbers though.

# data[].attributes.body
There was a LOT of excitement aound Jane Goodall. I wish we had advertised this a bit more (eventhough it was a recorded session) - also, maybe we could have made this a live broadcast on our YouTube channel too.

# data[].attributes.body
The AM really showed how much GLOBE means to the community. I am excited to amplify this feedback through our external commumications and internal input to NASA and other sponsors in the coming months.

# data[].attributes.body
I think this was really helpful to have in place.

# data[].attributes.body
I think there are two potential options 1) assume that you will only have 50% attendance from registration (and that's probably high) to keep it open to more people and/or 2) ask people to let you know if they can no longer attend so that you can open up a spot for someone else.

# data[].attributes.body
I was surprised at the interest in the DIS session. I think people would have liked more time to ask questions and dig into their presentation. So this could be a potential follow-up topic.

# data[].attributes.body
Create an edited playlist that only features each song for 1-2 minutes before moving on. This also allows you to stop early if that feels better.

# data[].attributes.body
Lots of good content from the AM! Looking forward to sharing these with the wider GLOBE community.

# data[].attributes.body
There was some really practical advice offered during Q&A in both breakout sessions I attended. It would be interesting to collect those nuggets of wisdom and see if they can inform any of the resources, etc. that we're sharing with the community to help support and sustain the program (e.g., around establishing partnerships, doing GLOBE in low resource areas).

# data[].attributes.body
Equal distribution of event across the meeting was very successful. Having Jane Goodall session in first day and the Poem in the second day allowed participants to experience each event without having the events overshadowing each other. EK

# data[].attributes.body
The planning and preparation for the meeting was well done, resulting in a very organized meeting. Having all the documents needed to run the meeting in addition to the presentations recorded and combined, worked very well.

# data[].attributes.body
Perhaps having a nominal registration fees to make sure those registered are actually interested in attending and intend to join.

# data[].attributes.body
I know some GLOBE members who were not able to attend. Sharing contents with community so those who couldn't join can view what they missed.

It's also good time to ask for feedback from community during the first couple of weeks after the meeting.

# data[].attributes.body
I wish the Dance party included videos from the international and local communities. Many of the international students love to show their traditional costumes and dance. Having a collection of videos showing students and community members in their traditional costumes dancing and celebrating GLOBE would be great. The videos could be edited to match some songs or background music.

# data[].attributes.body
I realized after watching the poem how important the use of videos. I think utilizing that in the future would be very effective.

# data[].attributes.headline
The prerecorded presentations for the breakout groups helped everything run smoothly.

# data[].attributes.subject
The prerecorded presentations for the breakout groups helped everything run smoothly.

# data[].attributes.body
Some presenters provided their role, organization, and GLOBE country while others did not so we may want to give them more specific guidance when asking for their submissions to ensure consistency in names and titles

# data[].attributes.headline
Would suggest not having a meeting on a Monday the next time. 

# data[].attributes.subject
Would suggest not having a meeting on a Monday the next time. 

# data[].attributes.body
In all my other projects, we always intentionally avoid Mondays and Fridays for big events. It impacts participation. And several staff end up working on the weekend prior to the weekend, like many of us did on both Sat and Sun to finalize and review everything and be prepared for Monday.

# data[].attributes.body
The end product was really inspirational and it worked well to have a video instead of a live performance. This will be a great keepsake for the future.

# data[].attributes.body
Since we have MN, would be good to think about using it more effectively to build community and also facilitate connections and collaborations between RCOs and WG chairs and Alumni.

# data[].attributes.headline
Keeping team member or globe meetings copied on correspondences

# data[].attributes.subject
Keeping team member or globe meetings copied on correspondences

# data[].attributes.body
It was tricky to follow up and know the status of things. In all my other projects while planning meetings, its been good practice to always have one other person from the team or the project email always copied on any correspondences with speakers. This helps with better coordination in planning and also takes the burden off one person, esp if there are emergencies etc.

# data[].attributes.body
I confess that I only saw some of the flashtalks, but for a few of them that I did see, some of the meaty part of their presentations came up at the very end. For future presenter guidelines, I wonder if we could encourage them to skip some of the "throat clearing" and dig into the unique and interesting pieces of their stories/what they wanted to share.