User:Brett Wuth/Working Notes/2012-12-01 leadership training
From PCSAR
(→Addresses) |
|||
(9 intermediate revisions not shown.) | |||
Line 1: | Line 1: | ||
- | == | + | {{Lesson plan/Header}} |
- | + | ||
- | + | == Subject == | |
- | + | {{prompt|What is this lesson plan about?}} | |
- | + | ||
- | * | + | == Authors == |
- | == | + | {{prompt|List who wrote this lesson plan.}} |
+ | * Brett Wuth | ||
+ | == Scope == | ||
+ | {{prompt|What is included in this lesson, what's not and why.}} | ||
* working with other SAR groups | * working with other SAR groups | ||
* working with other agencies | * working with other agencies | ||
+ | * merging field teams | ||
+ | |||
== Addresses == | == Addresses == | ||
* [[Critiques/2010-08-24/Sug21]] | * [[Critiques/2010-08-24/Sug21]] | ||
Line 14: | Line 19: | ||
* [[Critiques/2010-08-24/Sug10]] | * [[Critiques/2010-08-24/Sug10]] | ||
** clarify roles and command structure/hierarchy when several agencies are involved in/responding to the same incident. | ** clarify roles and command structure/hierarchy when several agencies are involved in/responding to the same incident. | ||
+ | * [[Critiques/2009-05-05/Sug3]] | ||
+ | ** Merging teams can cause confusion in command/reporting structure. Suggest clear language of merging vs. working together. Suggest switch to single FRS channel for new team. | ||
+ | ** need clear language of team designations, designation of combined team | ||
+ | ** need clear designation of combined team leader | ||
+ | ** overhead team can make effort to always have team leader designated | ||
+ | ** can practice developing leadership | ||
+ | |||
+ | == Prerequisites == | ||
+ | {{prompt|What should students already know/have accomplished before the lesson is presented.}} | ||
+ | |||
+ | == Objectives == | ||
+ | At the conclusion of this lesson the participants: | ||
+ | * will demonstrate the ability to | ||
+ | ** call for clarity of leadership | ||
+ | ** assume leadership | ||
+ | ** resolve issues of leadership between themselves and others | ||
+ | ** hand-off leadership | ||
+ | |||
+ | == Time Plan == | ||
+ | Total Time: ?? minutes | ||
+ | |||
+ | {{lesson slides start}} | ||
+ | {{lesson slide|00:00|3 min}} | ||
+ | Introduce topic title | ||
+ | |||
+ | Introduce Instructor | ||
+ | |||
+ | Present Objectives | ||
+ | |||
+ | {{lesson slide|00:03|}} | ||
+ | '''present outline of ICS org structure''' | ||
+ | * Inicident Commander | ||
+ | * Operations Section Chief | ||
+ | * Planning Section Chief | ||
+ | * Logistics Section Chief | ||
+ | * Finance/Admin Section Chief | ||
+ | * Ground Search Team Unit (Leader, Members) | ||
+ | * Call Out Team | ||
+ | * Agency Executive | ||
+ | |||
+ | {{lesson slide||}} | ||
+ | When position is not filled, the next position up does the job. | ||
+ | |||
+ | * May not be enough work for a dedicated person | ||
+ | * May not be enough people yet | ||
+ | |||
+ | * Expand and collapse as needed | ||
+ | |||
+ | |||
+ | {{lesson slide||}} | ||
+ | Scenario | ||
+ | |||
+ | Sunday morning May 19, 2013, Victoria Day weekend, Beautiful weekend. | ||
+ | |||
+ | PCSAR gets a call from RCMP upon a report of a 5-year girl missing | ||
+ | from a random campsite on the Carbondale river. | ||
+ | |||
+ | PCSAR is tasked. A search manager is in charge. Call-out has been | ||
+ | activated for ground searchers, quads, and road vehicles. | ||
+ | |||
+ | |||
+ | {{lesson slide||}} | ||
+ | Who do you report to? | ||
+ | * when requested | ||
+ | * when signed in | ||
+ | * when assigned field task | ||
+ | * when debriefed | ||
+ | * when available for reassignment | ||
+ | * when released, returning home | ||
+ | |||
+ | {{lesson slide||}} | ||
+ | Principles | ||
+ | * everybody reports to somebody | ||
+ | * everybody report to only one person -- Unity of Command | ||
+ | * everyone on the incident reports up the chain eventually to the same person - Chain of Command | ||
+ | |||
+ | Why? | ||
+ | * Efficiency in an emergency | ||
+ | |||
+ | {{lesson slides end}} | ||
+ | |||
+ | == Aids == | ||
+ | {{prompt|What materials are needed or useful in presenting this lesson.}} | ||
+ | |||
+ | == Question bank == | ||
+ | {{prompt|List of questions suitable for an review/exam of this section.}} | ||
+ | == Frequently Asked Questions == | ||
+ | {{prompt|What are some of the questions that students typically ask. Include the answers.}} | ||
+ | |||
+ | == Feedback == | ||
+ | {{prompt|When has this lesson been presented. What was the feedback.}} | ||
+ | |||
+ | == License == | ||
+ | {{prompt|What can others do with this lesson?}} | ||
+ | |||
+ | Recommended license below. Fill in the year and the author's name(s): | ||
+ | |||
+ | Copyright © 2012, Brett Wuth. | ||
+ | This work is licensed under a | ||
+ | Creative Commons Attribution-NonCommercial 2.5 Canada License. | ||
+ | To view a copy of this license, visit | ||
+ | http://creativecommons.org/licenses/by-nc/2.5/ca/ | ||
+ | or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. | ||
+ | |||
+ | == Reference Material == | ||
+ | {{prompt|If you need to cite sources, do so here.}} | ||
+ | Related lesson plans: | ||
+ | * [[2000-12-05 being in charge/Lesson plan]] | ||
+ | * [[2009-03-03 mtg/Overhead tabletop]] | ||
+ | |||
+ | == Notes == | ||
+ | {{prompt|Any additional notes, etc.}} | ||
+ | |||
+ | * Should always know "Who am I reporting to?" | ||
+ | ** If don't know, ask. | ||
+ | ** Report to only one person -- Unity of Command | ||
+ | *** not two different people or two different organizations, two different branches | ||
+ | *** not to both your team leader and your team leader's leader | ||
+ | **** give examples using ICS chart | ||
+ | *** "Am I reporting to you and no longer to ... ?" "I need to get a message to ... that I'm not longer reporting to that person." | ||
+ | ** No one knows who you report to. | ||
+ | *** "Who do you report to?" Follow the chain up until you find someone that can tell you who you should report to. | ||
+ | * If all you find are people that don't know who they themselves report to ... | ||
+ | ** No chain of command | ||
+ | ** Have you tried using radio / phone to contact more senior personnel? | ||
+ | ** Ultimately need to organize yourselves |
Current revision
Contents |
[edit] Subject
What is this lesson plan about?
[edit] Authors
List who wrote this lesson plan.
- Brett Wuth
[edit] Scope
What is included in this lesson, what's not and why.
- working with other SAR groups
- working with other agencies
- merging field teams
[edit] Addresses
- Critiques/2010-08-24/Sug21
- General training - every team needs a leader.
- Renew training for all members, including senior members, that whenever together must identify a team leader.
- Critiques/2010-08-24/Sug10
- clarify roles and command structure/hierarchy when several agencies are involved in/responding to the same incident.
- Critiques/2009-05-05/Sug3
- Merging teams can cause confusion in command/reporting structure. Suggest clear language of merging vs. working together. Suggest switch to single FRS channel for new team.
- need clear language of team designations, designation of combined team
- need clear designation of combined team leader
- overhead team can make effort to always have team leader designated
- can practice developing leadership
[edit] Prerequisites
What should students already know/have accomplished before the lesson is presented.
[edit] Objectives
At the conclusion of this lesson the participants:
- will demonstrate the ability to
- call for clarity of leadership
- assume leadership
- resolve issues of leadership between themselves and others
- hand-off leadership
[edit] Time Plan
Total Time: ?? minutes
Time | Material
|
00:00 3 min |
Introduce topic title Introduce Instructor Present Objectives
|
00:03
|
present outline of ICS org structure
|
|
When position is not filled, the next position up does the job.
|
|
Scenario Sunday morning May 19, 2013, Victoria Day weekend, Beautiful weekend. PCSAR gets a call from RCMP upon a report of a 5-year girl missing from a random campsite on the Carbondale river. PCSAR is tasked. A search manager is in charge. Call-out has been activated for ground searchers, quads, and road vehicles.
|
|
Who do you report to?
|
|
Principles
Why?
|
[edit] Aids
What materials are needed or useful in presenting this lesson.
[edit] Question bank
List of questions suitable for an review/exam of this section.
[edit] Frequently Asked Questions
What are some of the questions that students typically ask. Include the answers.
[edit] Feedback
When has this lesson been presented. What was the feedback.
[edit] License
What can others do with this lesson?
Recommended license below. Fill in the year and the author's name(s):
Copyright © 2012, Brett Wuth. This work is licensed under a Creative Commons Attribution-NonCommercial 2.5 Canada License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc/2.5/ca/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.
[edit] Reference Material
If you need to cite sources, do so here.
Related lesson plans:
[edit] Notes
Any additional notes, etc.
- Should always know "Who am I reporting to?"
- If don't know, ask.
- Report to only one person -- Unity of Command
- not two different people or two different organizations, two different branches
- not to both your team leader and your team leader's leader
- give examples using ICS chart
- "Am I reporting to you and no longer to ... ?" "I need to get a message to ... that I'm not longer reporting to that person."
- No one knows who you report to.
- "Who do you report to?" Follow the chain up until you find someone that can tell you who you should report to.
- If all you find are people that don't know who they themselves report to ...
- No chain of command
- Have you tried using radio / phone to contact more senior personnel?
- Ultimately need to organize yourselves