Structuring+Our+Thinking

This page provides a basic framework that was discussed during the March 22, 2011 meeting that might help to structure how we approach our work.

I think the basic framework includes three categories of information. In addition to pages we will create for the the new member training, I will create at least one page for the other two categories. These pages can serve as "parking lots" for ideas that surface that we feel belong to one of the other categories. Feel free to "park" any such items on these pages in whatever way you like.

Three Categories of Information/Work:
(NOTE TO ALL: PLEASE FEEL FREE TO EDIT THESE CATEGORIES/DESCRIPTIONS...THEY ARE JUST FROM MY NOTES/INTERPRETATION/MEMORY OF THE MEETING AND ARE NOT MEANT TO BE ETCHED IN STONE)

1) **New member training** - K-12 **(our focus is here for now)** - each standard will have multiple competencies; some will be content-focused, others process-focused - standards should be broad and applicable across K-12
 * Standards (key chunks/clusters of information that should be addressed in any new member SAP training)
 * content competencies
 * (what a new SAP team member should know about what the SAP team addresses)
 * process competencies
 * (what a new SAP team member should know about how the team should operate/function)

- in addition to the above categorization, competencies may be differented in terms of elementary vs. secondary

2) **Other potential training topics**
 * advanced member training
 * content-specific trainings (re: resiliency, mental health issues, substance issues, family, etc.)
 * "leadership" training
 * SAP liaison training
 * refreshers

3) **Systems issues** (I think these issues may be best addressed via some of the following mechanisms, not necessarily in the new member training (unless a new member needs to know it...TR)
 * guidelines
 * best practices
 * Q & A's
 * directive from interagency
 * CATs by-law
 * BEC updates

We also need to remind ourselves of the context in which we are working:
 * tough economic times in schools,
 * a multitude of challenges facing kids and a need to focus on those for which SAP is the best answer (or at least part of it,
 * other concurrent initiatives in schools and communities with which to coordinate in addressing the needs of kids,
 * a desire to develop K-12 standards and competencies to be differientated as needed when identifying training components
 * a basic premise that "less is more" when in comes to the ultimate number of standards and competencies.

Of course, feel free to join in the pontification if you like :-)