# data[].attributes.headline
provide KEY info - enough that will support facilitator adaptability.

# data[].attributes.subject
provide KEY info - enough that will support facilitator adaptability.

# data[].attributes.headline
To provide guidance for what facilitators should say and do for the slide, as well as the amount of time to spend on the slide.

# data[].attributes.subject
To provide guidance for what facilitators should say and do for the slide, as well as the amount of time to spend on the slide.

# data[].attributes.headline
Doesn't really work well for either returning/veteran or new facilitators - too much for returners, too scripted for new facilitators so they focus on the words more than the meat of the slide (the takeaway) and lose their voice.

# data[].attributes.subject
Doesn't really work well for either returning/veteran or new facilitators - too much for returners, too scripted for new facilitators so they focus on the words more than the meat of the slide (the takeaway) and lose their voice.

# data[].attributes.headline
To signal what materials are necessary for participants to access (and how to access them)

# data[].attributes.subject
To signal what materials are necessary for participants to access (and how to access them)

# data[].attributes.body
I think of the speaker notes and slides like a lesson plan from a curriculum. It gives the generic must-haves, but facs still need to go through and internalize/create their own lesson from the resource

# data[].attributes.body
Provide key talking points, inform our facilitators with content/knowledge to facilitate beyond what is on the slide, provide section consistency across the pathway

# data[].attributes.headline
to highlight any activities that accompany the slide

# data[].attributes.subject
to highlight any activities that accompany the slide

# data[].attributes.headline
for leadership, the purpose statement is the main/key takeaway or outcome for the participants. Like, if all else fails, this is what needs to get across.

# data[].attributes.subject
for leadership, the purpose statement is the main/key takeaway or outcome for the participants. Like, if all else fails, this is what needs to get across.

# data[].attributes.body
Say/Do: describe the major points to be made and directions for activities. vs. Consider: potential detours and how to refocus

# data[].attributes.headline
include (possible) answers to questions that are on the slide

# data[].attributes.subject
include (possible) answers to questions that are on the slide

# data[].attributes.body
currently: somewhat scripted "say" guidance and directions for activities

goal: key points and directions, only script when absolutely necessary

# data[].attributes.body
Many are just the activity type (group work, discussion, etc)

# data[].attributes.body
More helpful/succinct (and less likely to be read) if in bullet point rather than sentence form

# data[].attributes.headline
Currently, a script of what to say with a ton of information/evidence - too much.  Do section usually revolves around directions. Consider section is usually suggestions for variations for activities or some things to keep in mind from participant responses and the like.

# data[].attributes.subject
Currently, a script of what to say with a ton of information/evidence - too much.  Do section usually revolves around directions. Consider section is usually suggestions for variations for activities or some things to keep in mind from participant responses and the like.

# data[].attributes.body
The notes as a learning tool work if the facilitators translate the slide notes into their own words. However, I have seen new to UE read the notes, so that was not effective.

# data[].attributes.body
varies on each slide. May be just a few bullet points or a few paragraphs. Consider always has model answers for work or discussion questions

# data[].attributes.headline
There are as many responses as facilitators in my experience - some really appreciate the slide notes, context, and background, and some would like fewer and more succinct directions. 

# data[].attributes.subject
There are as many responses as facilitators in my experience - some really appreciate the slide notes, context, and background, and some would like fewer and more succinct directions. 

# data[].attributes.headline
Explain purpose of each part of notes as part of fac training

# data[].attributes.subject
Explain purpose of each part of notes as part of fac training

# data[].attributes.body
Of all things - the main point of the slide - what participants should get out of it.

# data[].attributes.body
Slide- Highest visual lever 3-5 takeaways

Speaker Notes-

1. High level overview - What we need them to say

2. What we need participants to do

3. What participants should know before moving to the next slide/topic

4. Context/More details - address participant questions

# data[].attributes.body
if you have NOTHING else, you can facilitate WELL with the speaker notes

# data[].attributes.headline
I have stopped scripting exactly what to say.  But I do not divide by "Say" and "Do" - Under "Speaker Notes" I provide the bullets in the order things should happen.  Say/do got really confusing

# data[].attributes.subject
I have stopped scripting exactly what to say.  But I do not divide by "Say" and "Do" - Under "Speaker Notes" I provide the bullets in the order things should happen.  Say/do got really confusing

# data[].attributes.body
Key points (sometimes a script)

Facilitator preparation when it is needed (logistical things that make the slide or activity work)

Answers/Listen fors

# data[].attributes.body
Fac seem to appreciate notes

# data[].attributes.body
We don’t use say do in our pathways

# data[].attributes.body
Move from script to bullet points where possible

Move extra "nice to know" information to the bottom.

# data[].attributes.body
Have gotten feedback that they are helpful, but need refining and tightening. Especially to reduce redundancy. Overall, I see facilitators print and then maker them up