# data[].attributes.headline
Moving forward, I think we'll want to lean more heavily on the product experts within these webinars...The "live demos" and "hearing from the experts" has been well received.

# data[].attributes.subject
Moving forward, I think we'll want to lean more heavily on the product experts within these webinars...The "live demos" and "hearing from the experts" has been well received.

# data[].attributes.headline
I vote for developing a GVA assessment.  We could dump the recording into a GVA lesson and send out to everyone after the webinar...Then, ask them to complete the GVA assessment ot demonstrate "mastery"...

# data[].attributes.subject
I vote for developing a GVA assessment.  We could dump the recording into a GVA lesson and send out to everyone after the webinar...Then, ask them to complete the GVA assessment ot demonstrate "mastery"...

# data[].attributes.headline
Some have commented they feel the depth of content is "too much"....they requested shorter, to the point (but these were mostly from sales...ICs would need more).

# data[].attributes.subject
Some have commented they feel the depth of content is "too much"....they requested shorter, to the point (but these were mostly from sales...ICs would need more).

# data[].attributes.headline
I would like to consider a GVA assessment...We could consider offering a prize (i.e. bribe) for completing the assessment.  :)

# data[].attributes.subject
I would like to consider a GVA assessment...We could consider offering a prize (i.e. bribe) for completing the assessment.  :)

# data[].attributes.headline
The key will be getting marketing messaging PRIOR TO these update calls...We can align sales talking points if we have this info prior to the calls...

# data[].attributes.subject
The key will be getting marketing messaging PRIOR TO these update calls...We can align sales talking points if we have this info prior to the calls...

# data[].attributes.headline
Right now, we are segmenting into:  (1) Curriculum/Product Updates, (2) Tech Updates, and (3) marketing Updates....I would think sales-driven initiatives could be included within marketing updates as needed.

# data[].attributes.subject
Right now, we are segmenting into:  (1) Curriculum/Product Updates, (2) Tech Updates, and (3) marketing Updates....I would think sales-driven initiatives could be included within marketing updates as needed.

# data[].attributes.headline
Agreed.  We should open these up for anyone to attend (even on AOP side, as well)...Transparency and communication are our goals.

# data[].attributes.subject
Agreed.  We should open these up for anyone to attend (even on AOP side, as well)...Transparency and communication are our goals.

# data[].attributes.headline
Quarterly seems to work well.  More frequently would lose its impact, as would less frequently (people wouldn't really "know" what these calls were about).  1 hour is a "doable" time frame for all.  Would like to keep these to 45 minutes (and include some Q&A time), but that is dependent upon the amount of info shared.

# data[].attributes.subject
Quarterly seems to work well.  More frequently would lose its impact, as would less frequently (people wouldn't really "know" what these calls were about).  1 hour is a "doable" time frame for all.  Would like to keep these to 45 minutes (and include some Q&A time), but that is dependent upon the amount of info shared.

# data[].attributes.headline
Having weekly planning calls worked well; however, not sure if that is feasible per quarter moving forward....Would like to consider bi-weekly calls and continue to get information from product briefs and experts, as needed.  

# data[].attributes.subject
Having weekly planning calls worked well; however, not sure if that is feasible per quarter moving forward....Would like to consider bi-weekly calls and continue to get information from product briefs and experts, as needed.  

# data[].attributes.headline
Agreed.  Overall goals are awareness and transparency.  No one can "claim" they didn't know something was coming...I think this does tie into the bigger picture of internal communication and transparency as a company goal.  

# data[].attributes.subject
Agreed.  Overall goals are awareness and transparency.  No one can "claim" they didn't know something was coming...I think this does tie into the bigger picture of internal communication and transparency as a company goal.  

# data[].attributes.body
follow up

# data[].attributes.body
We can consider internal development teams as well (dev, curriculum) as this is their work going out to the world?

# data[].attributes.body
You know I love an assessment :)

I could see the assessment taking the form of a GTT poll or quiz. It could give us an idea as to whether the greater group understands the information that was delivered to them and whether additional training or clarifications may be necessary.

# data[].attributes.body
Sales folks love to compete

# data[].attributes.body
I think the overall goal for the quarterly webinars is awareness. It arms the group with important information that can be shared with customers and (hopefully) generates excitement about things to come.

We always receive positive feedback about what is shared, so I would like to say, yes, we are meeting the goal.

I definitely believe that these webinars tie into the bigger picture of internal communication. Consistency in messaging is SO important, and being able to bring our teams together to hear the same messaging and the information is huge.

# data[].attributes.body
One measure of success is that we are continuing to see our attendance number increase. If people didn't find these webs of value, I think we would have seen a decline in attendance numbers. I think actual effectiveness will reside in the application of the information: are consultants and reps working the information into their presentations, trainings, and consultations? If we want feedback on effectiveness, we can always take advantage of the embedded polls in GTT.

I think that what we have offered has been the right depth because these webs are intended to give a high-level overview of what's coming or what has just been released. I do believe that certain topics and features will warrant additional, more in-depth, and more role-specific webinars to ensure understanding as well as ensure talking points are understood.

# data[].attributes.body
I think the prep for our webinars has gone really well. The structure that is currently in place has given us sufficient time to plan, develop, and prepare, and when additional meetings were needed, we have never had any trouble getting the necessary parties to add meetings to the calendar. As long as this continues, I don't know what else would be needed :)

# data[].attributes.body
We need to be mindful about what is being included. With only the three components mentioned above, we're often already at the hour mark. it may be difficult to add more to the agenda.

# data[].attributes.body
I completely agree. I think this information can be great for everyone regardless of their role. Just like we update everyone across teams during the Town Halls, I think these webinars can be used in a similar fashion.

# data[].attributes.body
I think quarterly is a good time frame. With only four a year, ICs, reps, tech, marketing, etc. aren't overwhelmed with webinars to attend, and this time span usually is enough for important curriculum, technology, and marketing updates to accumulate.

# data[].attributes.body
Overall, I think the webinars do a great job at bringing transparency to what is happening inside the org to empower field folks. Where I think we (the webinar team) fumble a bit is with handoffs in an order that looks like we have a united front. Product needs to get in front of development as well.

# data[].attributes.body
I like this rhythm as it follows the business quarters.

# data[].attributes.headline
What about regular marketing communication?

# data[].attributes.subject
What about regular marketing communication?

# data[].attributes.body
Yes, I thought it was great that we highlighted the Educator Impact awards and other campaigns last time. Anytime we can weave a story for sales internally, they will be able to deliver that same message externally. If we can tighten up the messaging on the other stuff, we will have room for other initiatives. If not, it's not a big deal at all -- I think we're hitting the right amount/good notes.

# data[].attributes.body
We need to be thinking about sales talking points earlier on and giving them a high level overview (ha!) during the webinar

# data[].attributes.body
I think we need to start planning our dates further in advance and not web to web :)

# data[].attributes.body
Much like our content design philosophy, it would be wise to start  with the end in mind. What are we trying to accomplish with these webinars? That will drive many of the questions on this Padlet:
-If it is to ensure Sales can speak effectively to what they have to sell, is that the best use of time of developers to attend?
-If it's to show what they are going to have vs already have, when is the best time of the quarter to have it? If the latter, does that change the timing?