Educational Team Excellence Recognition
Criteria Powerpoint
Template
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.
1
Overview
• Your power point 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!
2
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.
3
Mandatory Slide Header
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
Suggested Criteria Elements
Should be addressed in the team’s story,
or presented on the criterion standard slide.
Criteria Slide Precursor
It is a best practice to
keep individual slide
contents lean &
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!
EXPLAIN – Sufficient details to completely understand or replicate.
4
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.
5
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.
6
1.b EXPLAIN how the project supports organization
goals, performance measures and/or strategies.
• Link between team project & 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 & organization link, connection, importance …
EXPLAIN – Sufficient details to completely understand or replicate.
7
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 & external)
– Unique group / one or more individuals?
LIST – Identify via lists, tables, flowcharts … (Quantitatively or Qualitatively)
DESCRIBE – Detailed sufficiently to basically understand.
8
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.
9
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.
10
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)
11
1.d EXPLAIN how the project impacts key stakeholders (2 of 2)
• Team understands and communicates expected “StakeholderProject-Impact” factor(s) completely.
EXPLAIN – Sufficient details to completely understand or replicate.
12
ANALYSIS
2.a EXPLAIN how team identified potential root cause(s)
and key performance characteristics for the selected project.
• Root cause identification methods used identified
• Change / Improvement process described.
– Greater detail on root cause approach/process/methods/tools
• Anticipated benefits noted
• Key performance factors/indicators linked to root cause identifiers.
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.
13
2.b EXPLAIN root cause analysis with data and information (1 of 3)
• Data & information used to reveal root causes (Depth & Breadth)
EXPLAIN – Sufficient details to completely understand or replicate.
14
2.b EXPLAIN root cause analysis with data and information (2 of 3)
• Specific data/information root cause analysis examples
(Depth & Breadth).
EXPLAIN – Sufficient details to completely understand or replicate.
15
2.b EXPLAIN root cause analysis with data and
information (3 of 3)
• Root Cause Analysis conclusions present (Depth & Breadth).
EXPLAIN – Sufficient details to completely understand or replicate.
16
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)
17
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.
18
2.d EXPLAIN actual root cause identification and assurance. (2 of 2)
• Key data & analysis assures the validation of the actual root cause
(Depth & Breadth)
EXPLAIN – Sufficient details to completely understand or replicate.
19
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.
20
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.
21
3.a EXPLAIN potential solution(s) identification (3 of 3)
• Clear potential solution identification methodology identified
EXPLAIN – Sufficient details to completely understand or replicate.
22
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.
23
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.
24
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)
25
3.c EXPLAIN expected solution benefits (2 of 2)
• Expected/anticipated solution benefits explained
EXPLAIN – Sufficient details to completely understand or replicate.
26
3.d DESCRIBE expected benefits determination (1 of 2)
• Expected benefits determination approach/process/methods/tools
described.
DESCRIBE – Detailed sufficiently to basically understand.
27
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.
28
SOLUTION IMPLEMENTATION
4.a DESCRIBE solution implementation plan (1 of 2)
• Planned solution implementation process illustrated / explained
• Specific examples (Depth & Breadth)
DESCRIBE – Detailed sufficiently to basically understand.
29
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.
30
4.b DESCRIBE solution implementation (1 of 2)
• Actual implementation steps with specific examples
• Key steps & associated milestones noted/identified
DESCRIBE – Detailed sufficiently to basically understand.
31
4.b DESCRIBE solution process, procedures, changes... (2 of 2)
• Concise description to understand solution implementation
procedures / changes …
DESCRIBE – Detailed sufficiently to basically understand.
32
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.
33
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.
34
4.c EXPLAIN solution implementation support and buy-in (3 of 4)
• Stakeholder(s) noted in “1d” BUY-IN connection
•
Expected impact & resistance reaffirmed / noted
 Stakeholders
 Others
EXPLAIN – Sufficient details to completely understand or replicate.
35
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.
36
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.
37
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.
38
TEAM EFFECTIVENESS
5.a DESCRIBE team member selection (1 of 2)
• Team evidence (Names or other identifiers …)
• Actual team member selection method
DESCRIBE – Detailed sufficiently to basically understand.
39
5.a DESCRIBE team member selection (2 of 2)
• Why each member was selected
 Skills, knowledge, qualifications …
DESCRIBE – Detailed sufficiently to basically understand.
40
5.b DESCRIBE team member participation preparation
• Team member preparations – prior to or during




Specific training
Tools
Process Improvement
Team dynamics, etc…
• Team building efforts – prior or during
DESCRIBE – Detailed sufficiently to basically understand.
41
5.c DESCRIBE team member participation & contribution
assurance (1 of 2)
• Specific examples - team member ability to & contributions to project




Team norms
Meeting availability
Management tools/techniques
Special accommodations
DESCRIBE – Detailed sufficiently to basically understand.
42
5.c DESCRIBE team member participation & contribution
assurance (2 of 2)
• Specific examples of team member roles & responsibilities
DESCRIBE – Detailed sufficiently to basically understand.
43
5.d EXPLAIN team performance management to
ensure effectiveness (1 of 6)
• Specific examples of effective team management
EXPLAIN – Sufficient details to completely understand or replicate.
44
5.d EXPLAIN team performance management to
ensure effectiveness (2 of 6)
• Project lifecycle team management assured
EXPLAIN – Sufficient details to completely understand or replicate.
45
5.d EXPLAIN team performance management to
ensure effectiveness (3 of 6)
• Capitalization on individual team members skills, knowledge &
contributions
EXPLAIN – Sufficient details to completely understand or replicate.
46
5.d EXPLAIN team performance management to
ensure effectiveness (4 of 6)
• Team member data/information sharing evidence
EXPLAIN – Sufficient details to completely understand or replicate.
47
5.d EXPLAIN team performance management to
ensure effectiveness (5 of 6)
• Effective team communications (Evidence)
EXPLAIN – Sufficient details to completely understand or replicate.
48
5.d EXPLAIN team performance management to
ensure effectiveness (6 of 6)
• Performance management – Evidence meeting deadlines/
deliverables/milestones
EXPLAIN – Sufficient details to completely understand or replicate.
49
RESULTS, KNOWLEDGE SHARING & APPLICATION
6.a DESCRIBE results achieved-tangible and less
tangible results. (1 of 5)
• Identifies actual solution implementation results
DESCRIBE – Detailed sufficiently to basically understand.
50
6.a DESCRIBE results achieved-tangible and less
tangible results. (2 of 5)
• Tangible results
 Specific Measure or Metric Improvement
 % proficient, cycle time, attendance …
 Cost, grades, participation
DESCRIBE – Detailed sufficiently to basically understand.
51
6.a DESCRIBE results achieved-tangible and less
tangible results. (3 of 5)
• Less-Tangible results (Linked to a variety of indicators)
 Specific Measure or Metric Improvement
 Morale
 Professional Work Environment
 Employee/student/staff satisfaction
• Less-Tangible indicators identified
DESCRIBE – Detailed sufficiently to basically understand.
52
6.a DESCRIBE results achieved-tangible and less
tangible results. (4 of 5)
• Indicator (Tangible & Less Tangible) “rationalization” of
improvement-beliefs
DESCRIBE – Detailed sufficiently to basically understand.
53
6.a DESCRIBE results achieved-tangible and less
tangible results. (5 of 5)
• Before & After performance results demonstrate a causal
relationship (Improvement project and/or end results)
DESCRIBE – Detailed sufficiently to basically understand.
54
6.b EXPLAIN results achieved impact on organizations goals,
performance, measures, and/or strategies. (1 of 2)
• Connect “6a” results (Tangible & Less-Tangible results) with “1b”
(Project supports organizational goals …)
EXPLAIN – Sufficient details to completely understand or replicate.
55
6.b EXPLAIN results achieved impact on organizations goals,
performance, measures, and/or strategies. (2 of 2)
• Demonstrate positive results / impacts on Category 1 areas (i.e.,
organizational / project goals, objectives, strategies …
EXPLAIN – Sufficient details to completely understand or replicate.
56
6.c DESCRIBE project results “sharings” (1 of 2)
• How results were shared
• Specific “sharing” examples provided
• Sharing methods/approaches
DESCRIBE – Detailed sufficiently to basically understand.
57
6.c IDENTIFY with whom the results were shared (2 of 2)
• Results were shared with whom
 Inside
 Outside
IDENTIFY - Lists, tables, flowcharts … (Quantitatively or Qualitatively)
58
6.d Clarity of application and effective use of
charts/graphs












Criteria aligned, sequenced and labeled
Page numbers present
Third party voice of the team utilized
Clarity – Sufficient information/data for complete understanding and
commensurate with the verbal qualifiers (i.e. Identify, describe, list,
explain)
Non-generic or industry-based terminology explained
Abbreviations (LSS, NP, UCL, LCL …) should be defined on initial use
Professionally written (Proper grammar and spelling).
Visual aides, charts, graphs… easily read and understood
Visual aides colors are complementary and not difficult to perceive
Project story is told according to the Educational Team Excellence
Criteria
Lean slide presentations – 6 bullets / 6 words per bullet per slide
Slide Notes should complement slide data and not be redundant of it.
59