2014

1. Education Team Excellence Recognition ProcessTimeline, Criteria Overview, Template, Scoring Guidelines and Glossary 2014

2. Education Team Excellence Recognition Guideline Index Timeline 3 Criteria Overview Guide 4 – 11 Criteria PowerPoint Template 12– 71 Criteria Scoring Rubric 72 – 76 Glossary 77 – 82

3. Education Team Excellence Timeline MARCH 15TH JUNE 15TH

4. EDUCATION TEAM EXCELLENCE RECOGNITION (ETER) CRITERIA OVERVIEW GUIDE 2014

5. ETER Criteria Overview Guide In this guide, the word "organization" is intended to encompass a wide variety of educational service units including, but not limited to: school district, university, trade school, day care centers, community colleges, individual buildings/schools, grade level teams, departments and individual classrooms. The Education Team Excellence Recognition criteria can be applied to any of these types of organizations and work units and can be used to make process improvements, enhance student achievement results, and share team learning to leverage performance within other units of the organization.

6. ETER Criteria Overview Guide • Project Selection (4 items @ 3 points = 12 points possible) In the Project Selection Category, teams are asked to explain several key factors related to their project’s selection. Note: The project may have been selected by the team or assigned by management. Regardless of who selected the project, teams should clearly describe how the project was selected (be responsive to each criteria item) including any data and information used in the selection.

7. ETER Criteria Overview Guide 2. Analysis (4 items @ 3 points = 12 points possible) In the Analysis Category, teams are asked to explain how they determined the potential root cause(s) associated with their project. Their explanation should include how data and information were used in the determination, what key data and information were actually used, and how the team ensured it identified the actual root cause.

8. ETER Criteria Overview Guide 3. Solution Development (4 items @ 3 points = 12 points possible) In the Solution Development Category, teams are asked to explain the approach, process, method, tools, etc., they used to identify potential solutions as well as their final solution. Teams are also asked to identify their final solution(s) and the expected benefits of that solution(s) and to provide an explanation of how they determined the expected benefits. Teams’ responses should include specific examples from their project and any applicable data and information they used in their solution development.

9. ETER Criteria Overview Guide 4. Solution Implementation (4 items @ 3 points = 12 points possible) In the Solution Implementation Category, teams are asked to explain how they planned for and implemented the final solution(s) they identified in 3c. The Solution Implementation Category also asks for an explanation of how the team achieved buy-in for implementing its solution(s), how the team measured the results associated with implementing its solution, and how the team ensured the results would be sustained.

10. ETER Criteria Overview Guide 5. Team Effectiveness (4 items @ 3 points = 12 points possible) In the Team Effectiveness Category, teams are asked to explain how their team members were selected and prepared to participate in the improvement project. The Team Effectiveness Category also asks teams to explain how they ensured all team members contributed throughout the project as well as how the team managed their performance to ensure they were an effective team. It must be clear that this was a team project - not an individual’s project.

11. ETER Criteria Overview Guide 6. Results, Knowledge Sharing, and Application (4 items @ 3 points = 12 points possible) In the Results, Knowledge Sharing, and Application Category, teams are asked to describe the actual results of their project–tangible and less tangible–and how those results support their organization’s overarching strategy and direction. Teams are also asked to explain how, and with whom, they shared the results of their project to promote organizational knowledge sharing and learning.

12. Mandatory slide headers are in red Criteria-based expectation examples are outlined below criteria-headers. Slide data presentation should be in colors, format & manner befitting the team & project. Education Team Excellence Recognition (ETER) PROCESSCriteria Powerpoint Template

13. ETER Overview • Your PowerPoint presentation needs to tell your story using the ETER criteria as an organizing framework. Select colors, graphics, and data to illustrate your criteria compliance, but remember: quality not quantity is your best practice. • Unless your team used the ETER criteria as your process, there may be criteria elements not present in your project. If this is the case, simply explain on that criteria slide why your team did not address this element. Do not try to Fake-it-to-make-it!

14. ETER Overview • Make sure your project title or your criteria 1a explanation identifies your project as either a problem-solving or an improvement project. • A Problem-Solving Project is usually a search for a new solution or practice that does not currently exist to resolve an issue or satisfy desired expectations. • An Improvement Project is changing an existing practice that is not meeting expectations, for the better in order to comply, approach, meet, or exceed desired performance levels.

15. PROJECT SELECTION 1.a EXPLAIN how the project was selected. (1 of 2) ETER Template Mandatory Slide Header • Clear summary (key data/information) • Selection data/information included • Project driver(s) • Personal initiative, • Organizational OFI, • Grant commitment • Other Criteria Slide Precursor It is a best practice to keep individual slide contents lean and meaningful. This indicator informs judges of this intent and to foreshadow additional information on subsequent slides. Do not include this textbox in your presentation. Its only purpose on the template is to keep your explanation focused on the criteria measure expectation! Suggested Criteria Elements Should be addressed in the team’s story, or presented on the criterion standard slide. EXPLAIN – Sufficient details to completely understand or replicate.

16. ETER Template PROJECT SELECTION 1.a EXPLAIN how the project was selected. (1 of 2) • Clear summary (key data/information) • Selection data/information included • Project driver(s) • Personal initiative, • Organizational OFI, • Grant commitment • Other EXPLAIN – Sufficient details to completely understand or replicate.

17. ETER Template 1.a EXPLAIN how the project was selected. (2 of 2) • Project Declaration – Identify project type. • A Problem-Solving project is a search for a new solution or practice. • An Improvement project is changing an existing practice for the better. • Team Approach/Process/Method/Tools • Education Team Excellence criteria driven process • PDSA • PDCA • DMAIC • Organizational Adopted Procedure • Other EXPLAIN – Sufficient details to completely understand or replicate.

18. ETER Template 1.b EXPLAIN how the project supports organizationgoals, performance measures, and/or strategies. • Link between team project and organization goals/strategies • Organizational goals (vision, mission, objectives …) • Project goals, intents, aims … • Project importance is explained • “Why is this project important to the organization?” • What organization owns/benefits from this project? • Improved test scores and organization link, connection, importance … EXPLAIN – Sufficient details to completely understand or replicate.

19. ETER Template 1.c DESCRIBE how the team identified key stakeholders (i.e., those most affected) (1 of 3) • Key stakeholders listed • Internal/external customers, employees, students, parents, key suppliers (List both internal and external) • Unique group/one or more individuals? LIST – Identify via lists, tables, flowcharts (quantitatively or qualitatively). DESCRIBE – Detailed sufficiently to basically understand.

20. ETER Template 1.c DESCRIBE how the team identified key stakeholders(i.e., those most affected) (2 of 3) • Stakeholder identification method described DESCRIBE – Detailed sufficiently to basically understand.

21. ETER Template 1.c DESCRIBE how the team identified key stakeholders(i.e., those most affected) (3 of 3) • Stakeholders selection described/justified DESCRIBE – Detailed sufficiently to basically understand.

22. ETER Template 1.d IDENTIFY the key stakeholders (1 of 2) • Identify Key Stakeholder(s) from previous list (“1c” slides 5-6-7) with impact affect/effect. IDENTIFY – Lists, tables, flowcharts (quantitatively or qualitatively)

23. ETER Template 1.d EXPLAIN how the project impacts key stakeholders (2 of 2) • Team understands and communicates expected “Stakeholder-Project-Impact” factor(s) completely. EXPLAIN – Sufficient details to completely understand or replicate.

24. ETER Template ANALYSIS 2.a EXPLAIN how team identified problem to be solved and/or key performance indicators. • Root cause approaches/processes/methods identified • Problem-solving approach/methodology described • Key performance factors/indicators described LIST – Identify via lists, tables, flowcharts (quantitatively or qualitatively). IDENTIFY – Lists, tables, flowcharts (quantitatively or qualitatively). DESCRIBE – Detailed sufficiently to basically understand. EXPLAIN – Sufficient details to completely understand or replicate.

25. ETER Template ANALYSIS2.a EXPLAIN how team identified improvement need and anticipated benefits. • Change/Improvement process described • Introduction and Implementation • Anticipated benefits noted • Key performance factors/indicators linked to improvement need/benefit LIST – Identify via lists, tables, flowcharts (quantitatively or qualitatively). IDENTIFY – Lists, tables, flowcharts (quantitatively or qualitatively). DESCRIBE – Detailed sufficiently to basically understand. EXPLAIN – Sufficient details to completely understand or replicate.

26. ETER Template 2.b EXPLAIN root cause analysis with data and information (1 of 3) • Data and information used to reveal root causes (depth and breadth) EXPLAIN – Sufficient details to completely understand or replicate.

27. ETER Template 2.b EXPLAIN root cause analysis with data and information (2 of 3) • Specific data/information root cause analysis examples (depth and breadth). EXPLAIN – Sufficient details to completely understand or replicate.

28. ETER Template 2.b EXPLAIN root cause analysis with data and information (3 of 3) • Root cause analysis conclusions present (depth and breadth) EXPLAIN – Sufficient details to completely understand or replicate.

29. ETER Template 2.c IDENTIFY key data and information used in team analysis • Key data/information used to reveal potential root causes • Key data/information connection from “2b” present • Specific data/information examples noted IDENTIFY – Lists, tables, flowcharts (quantitatively or qualitatively).

30. ETER Template 2.d EXPLAIN actual root cause identification and assurance. (1 of 2) • Root cause possibilities identified as suggested previously in 2a, 2b, and 2c (named, labeled, and referenced) EXPLAIN – Sufficient details to completely understand or replicate.

31. ETER Template 2.d EXPLAIN actual root cause identification and assurance. (2 of 2) • Key data and analysis ensures the validation of the actual root cause (depth and breadth) EXPLAIN – Sufficient details to completely understand or replicate.

32. ETER Template SOLUTION DEVELOPMENT 3.a EXPLAIN potential solution(s) identification (1 of 3) • Potential solutions listed LIST – Identify via lists, tables, flowcharts (quantitatively or qualitatively). EXPLAIN – Sufficient details to completely understand or replicate.

33. ETER Template 3.a EXPLAIN potential solution(s) identification (2 of 3) • Potential solutions connected to previously identified root causes (“2d”) • Formally/Informally/Organizationally EXPLAIN – Sufficient details to completely understand or replicate.

34. ETER Template 3.a EXPLAIN potential solution(s) identification (3 of 3) • Clear potential solution identification methodology identified EXPLAIN – Sufficient details to completely understand or replicate.

35. ETER Template 3.b EXPLAIN final solution selection (1 of 2) • Final solution selection approach/process/methods/tools identified • Specific examples EXPLAIN – Sufficient details to completely understand or replicate.

36. ETER Template 3.b EXPLAIN final solution selection (2 of 2) • Final solution process applied to potential solution list (“3a”) • Specific examples EXPLAIN – Sufficient details to completely understand or replicate.

37. ETER Template 3.c IDENTIFY final solution (1 of 2) • Final root cause solution identified • Final root cause solution connected to solution selection approach (“3b’) IDENTIFY – Lists, tables, flowcharts (quantitatively or qualitatively).

38. ETER Template 3.c EXPLAIN expected solution benefits (2 of 2) • Expected/anticipated solution benefits explained EXPLAIN – Sufficient details to completely understand or replicate.

39. ETER Template 3.d DESCRIBE expected benefits determination (1 of 2) • Expected benefits determination approach/process/methods/tools described. EXPLAIN – Sufficient details to completely understand or replicate.

40. ETER Template 3.d DESCRIBE expected benefits determination (2 of 2) • Connection with “3c” (solution expected benefit list) illustrated/explained • Specific examples DESCRIBE – Detailed sufficiently to basically understand.

41. ETER Template SOLUTION IMPLEMENTATION 4.a DESCRIBE solution implementation plan (1 of 2) • Planned solution implementation process illustrated/explained • Specific examples (depth and breadth) DESCRIBE – Detailed sufficiently to basically understand.

42. ETER Template 4.a IDENTIFY potential challenges (2 of 2) • List of potential implementation challenges • Describe how challenges were identified IDENTIFY – Lists, tables, flowcharts (quantitatively or qualitatively). DESCRIBE – Detailed sufficiently to basically understand.

43. ETER Template 4.b DESCRIBE solution implementation (1 of 2) • Actual implementation steps with specific examples • Key steps and associated milestones noted/identified DESCRIBE – Detailed sufficiently to basically understand.

44. ETER Template 4.b DESCRIBE solution process, procedures, changes ... (2 of 2) • Concise description to understand solution implementation procedures/changes … DESCRIBE – Detailed sufficiently to basically understand.

45. ETER Template 4.c EXPLAIN solution implementation support and buy-in (1 of 4) • Achieving solution implementation buy-in • Specific examples EXPLAIN – Sufficient details to completely understand or replicate.

46. ETER Template • 4.c EXPLAIN solution implementation support and buy-in (2 of 4) • Buy-in “working relations” • Noting with whom they worked. EXPLAIN – Sufficient details to completely understand or replicate.

47. ETER Template ETER Template 4.c EXPLAIN solution implementation support and buy-in (3 of 4) • Stakeholder(s) noted in “1d” BUY-IN connection • Expected impact and resistance reaffirmed/noted • Stakeholders • Others EXPLAIN – Sufficient details to completely understand or replicate.

48. ETER Template ETER Template 4.c EXPLAIN how solution implementation challenges were addressed (4 of 4) • Specific examples of addressing implementation challenges EXPLAIN – Sufficient details to completely understand or replicate.

49. ETER Template ETER Template 4.d EXPLAIN project’s Results-Measurement-System Plan (1 of 2) • Effectiveness-Results measurement plan detailed • Specific examples: • Applicable data, measures, data, information … EXPLAIN – Sufficient details to completely understand or replicate.

50. ETER Template 4.d EXPLAIN how the PLAN ensured results would be sustained (2 of 2) • Specific actions, plans … to ensure sustained results EXPLAIN – Sufficient details to completely understand or replicate.