1 Educational Team Excellence Recognition Criteria Powerpoint Template Mandatory slide headers are in red iteria-based expectation examples are outlined below criteria-header ta presentation should be in colors, format & manner befitting the team & pr
59
Embed
1 Educational Team Excellence Recognition Criteria Powerpoint Template Mandatory slide headers are in red Criteria-based expectation examples are outlined.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
Educational Team Excellence Recognition
Criteria Powerpoint Template
Mandatory slide headers are in redCriteria-based expectation examples are outlined below criteria-headers.
Slide data presentation should be in colors, format & manner befitting the team & project.
2
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!
3
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.
4
PROJECT SELECTION1.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 CommitmentOther
EXPLAIN – Sufficient details to completely understand or replicate.
Criteria Slide PrecursorIt 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!
Suggested Criteria ElementsShould be addressed in the team’s story,
or presented on the criterion standard slide.
Mandatory Slide Header
5
PROJECT SELECTION1.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 CommitmentOther
EXPLAIN – Sufficient details to completely understand or replicate.
6
• 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
1.a EXPLAIN how the project was selected. (2 of 2)
EXPLAIN – Sufficient details to completely understand or replicate.
7
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.
8
1.c DESCRIBE how the team identified key stakeholders (i.e., those most affected) (1 of 3)
LIST – Identify via lists, tables, flowcharts … (Quantitatively or Qualitatively)DESCRIBE – Detailed sufficiently to basically understand.
9
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.
10
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.
11
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)
12
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.
13
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.
14
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.
15
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.
16
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.
17
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)
18
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.
19
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.
20
SOLUTION DEVELOPMENT3.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.
21
3.a EXPLAIN potential solution(s) identification (2 of 3)
EXPLAIN – Sufficient details to completely understand or replicate.
36
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.
37
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.
38
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.
39
TEAM EFFECTIVENESS5.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.
40
5.a DESCRIBE team member selection (2 of 2)
• Why each member was selected Skills, knowledge, qualifications …
DESCRIBE – Detailed sufficiently to basically understand.
41
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.
42
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.
43
5.c DESCRIBE team member participation & contribution assurance (2 of 2)
• Specific examples of team member roles & responsibilities
DESCRIBE – Detailed sufficiently to basically understand.
44
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.
45
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.
46
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.
47
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.
48
5.d EXPLAIN team performance management to ensure effectiveness (5 of 6)
• Effective team communications (Evidence)
EXPLAIN – Sufficient details to completely understand or replicate.
49
5.d EXPLAIN team performance management to ensure effectiveness (6 of 6)
EXPLAIN – Sufficient details to completely understand or replicate.
56
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.
57
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.
58
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)
59
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.