# data[].attributes.body
It would be great if we be more diligent about tracking who requested the invitee, when they were invited, and when people are moved from various statuses (like to invite --> invite) to better manage knowledge across the team

# data[].attributes.body
With all the difficulties with Splashthat syncing, it was decided to do all updates manually. This caused a fair bit of manual reconciliation.

# data[].attributes.body
I think there was a few individuals who had issues with enabling NFCs on their smartphones. We should try to included customized QR codes next year.

# data[].attributes.headline
Shiny app deployment (real time tracking of attendees)

# data[].attributes.subject
Shiny app deployment (real time tracking of attendees)

# data[].attributes.body
We should explore alternatives to making reprinting badges less manual.

# data[].attributes.headline
Update Campaign Status to make more clear

# data[].attributes.subject
Update Campaign Status to make more clear

# data[].attributes.body
Update campaign status to clarify process. For example:
0. Under Consideration
1. Internal Waitlist
2. Review Value-Add
3. Next Wave of Invites
4. Invite Sent
5. RSVP_Yes
6. RSVP_No
7. Do not invite

# data[].attributes.body
It feels like we have an opportunity to unify our datasets so that we can leverage our datasets more seamlessly. There were several instances where we had to use multiple google docs / SFDC reports / other references that made this less efficient and manual.

# data[].attributes.body
A charging station for attendees to charge their devices while at Summit.

# data[].attributes.headline
DST was ready to rock and roll this year

# data[].attributes.subject
DST was ready to rock and roll this year

# data[].attributes.body
We've done this a few times now and the DS&T team showed up ready to roll. Appreciated the push to always think about how we continue to improve the experience.

# data[].attributes.body
It would be nice if once attendees check it, it reflects on our site (or in some system) that non-DST people can check to confirm people are actually at the Summit.

# data[].attributes.body
I had multiple CEOs come up to me with their tear sheets on their phones, looking for people to meet. Showed me they liked the digital format.

# data[].attributes.headline
Integration of attendees with the website

# data[].attributes.subject
Integration of attendees with the website

# data[].attributes.body
While this is manageable as is, would be nice to streamline the process so we don't have to continually download/upload new lists.

# data[].attributes.body
Stood up app technology and email tear sheet deployment process in <1 week

# data[].attributes.body
Would have been better if we aligned sooner on a process to QC and review tear sheet tagging via the app instead of re-running PDFs

# data[].attributes.body
Would be great next year to use the app in both directions - eg. pull up a portco and see their tagged atteendees, or pull up an attendee and see their tagged portcos

# data[].attributes.body
Having a fast charging area in central areas for the guests and portable battery packs

# data[].attributes.body
Ask corporates what their pain points/interest areas are as part of registration

# data[].attributes.body
Contacts were dated, information was wrong and this all has implications invites and attendees.

# data[].attributes.body
Improving tear sheets, knowing who is the real relationship owner for individual contacts rather than the corporate account team lead as contacts are currently tied to.

# data[].attributes.body
Process was somewhat cumbersome and confusing (Google Sheet with Script, then SFDC which required multiple clicks). Value-tagging our ecosystem could be very valuable and I'd like to find a way for us to do this more seamlessly moving forward