Editing Critiques

From PCSAR

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Current revision Your text
Line 1: Line 1:
-
Critiques are one of the most effective ways Pincher SAR has to
+
Critiques are one of the most effective ways PC SAR has to
improve the manner in which it works. The purpose of a critique is
improve the manner in which it works. The purpose of a critique is
not to be critical but to share an understanding of what worked
not to be critical but to share an understanding of what worked
well and what could be improved.
well and what could be improved.
-
By building on this shared understanding,
 
-
Pincher SAR can continuously improve its responses.
 
-
Pincher SAR performs a critique after all but minor incidents.
+
PC SAR performs a critique after all but minor incidents.
== Principles ==
== Principles ==
Line 15: Line 13:
The person selected to chair the critique and manage the critique process should
The person selected to chair the critique and manage the critique process should
not have been involved in the incident.
not have been involved in the incident.
-
A critique should not be hindered by the blind spots that we each have.
+
A critique should not be hindered the blind spots that we each have.
-
If the facilitator is someone that was involved in the incident,
+
If the facilitator is someone that was involved in the search,
especially a member of the overhead team or Incident Commander,
especially a member of the overhead team or Incident Commander,
there's a risk that
there's a risk that
Line 59: Line 57:
=== Facts first ===
=== Facts first ===
-
Before getting into discussions,
+
Before getting in to discussions,
all the participants should know the facts.
all the participants should know the facts.
This allows all the participants to discuss ideas with a clearer understanding of the situation.
This allows all the participants to discuss ideas with a clearer understanding of the situation.
Line 75: Line 73:
=== Focus on learnings ===
=== Focus on learnings ===
A critique is not about criticism.
A critique is not about criticism.
-
It should not become a forum for blame or guilt.
+
It should not become a situation for blame or guilt.
Instead a critique should be about learning.
Instead a critique should be about learning.
Line 84: Line 82:
But it's just as important to bring up learnings from things that worked well
But it's just as important to bring up learnings from things that worked well
and should be repeated or further developed.
and should be repeated or further developed.
-
 
=== Ideas, not decisions ===
=== Ideas, not decisions ===
The critique is a brainstorming session.
The critique is a brainstorming session.
Many of the ideas that are brought up during the critique will take some serious thought before they are implemented.
Many of the ideas that are brought up during the critique will take some serious thought before they are implemented.
We don't want the meeting to get bogged down in debate.
We don't want the meeting to get bogged down in debate.
-
So the focus should be on capturing the idea and not on deciding whether or not to implement it.
+
So the focus should be on capturing the idea and not deciding on whether or not to implement it.
Sometimes the decision will be obvious, but most often it's better to leave the idea
Sometimes the decision will be obvious, but most often it's better to leave the idea
as a ''suggestion'' directed to the parts of the organization that would normally handle such ideas.
as a ''suggestion'' directed to the parts of the organization that would normally handle such ideas.
-
Pincher SAR has a number of committees that specialize in areas of governance, budget, standard operating procedures, call-out, equipment, training and membership.
+
Pincher SAR has a number of committees that specialize in areas of governance, budget, standard operating policies, equipment, training and membership.
=== Discuss around functional areas ===
=== Discuss around functional areas ===
After an incident of any size there is a lot to discuss.
After an incident of any size there is a lot to discuss.
If every person brings up every point they can think of,
If every person brings up every point they can think of,
-
the meeting will be so long that everyone would be exhausted.
+
the meeting will be so long everyone will be exhausted.
To bring out the most relevant points and focus discussion,
To bring out the most relevant points and focus discussion,
Line 106: Line 103:
There is a list of possible functional areas in the sample agenda below.
There is a list of possible functional areas in the sample agenda below.
Usually there won't be enough time to discuss all functional areas
Usually there won't be enough time to discuss all functional areas
-
so the facilitator should select the ones that are likely to be most relevant.
+
so the chair should select the ones that are likely to be most relevant.
=== Round table ===
=== Round table ===
Line 119: Line 116:
* Pick a time (Tuesday evening?) when most participants in the search are available.
* Pick a time (Tuesday evening?) when most participants in the search are available.
* book a room ([[Fire Hall]], [[MD Meeting Room]], [[Town Hall Gym]])
* book a room ([[Fire Hall]], [[MD Meeting Room]], [[Town Hall Gym]])
-
* {{subpage|Announce}} by e-mail or call out.
+
* Announce by e-mail or call-out.
-
* Have someone (usually the last Search Manager involved) draft a 1 page summary of the incident. (see [[Template:Incident Report]])
+
* Have someone (usually the last Search Manager involved) draft a 1 page summary of the incident. (see [[Incident Summary Form Task]])
-
* Review the Incident Report. If you have questions, check the [[Incidents|incident files]].
+
-
* Decide which are the most important functional areas to discuss.
+
* Invite the tasking agency and other organizations we worked with to send a representative. Many SAR groups are listed at: http://www.saralberta.ca
* Invite the tasking agency and other organizations we worked with to send a representative. Many SAR groups are listed at: http://www.saralberta.ca
* Decide whether snacks are needed and arrange them.
* Decide whether snacks are needed and arrange them.
Line 129: Line 124:
=== At the critique ===
=== At the critique ===
-
Your effort: 1.5 hrs
 
* Chair the meeting.
* Chair the meeting.
-
*: Your function is to focus and facilitate the discussion. Let the participants do most of the talking. If you get involved in bringing out your own suggestions or teaching, it's very easy to get distracted from your facilitation role. Perhaps you can add any suggestions you have to the report in the same way as you'll add any suggestions emailed to you by those who could not attend.
+
** Your function is to focus and facilitate the discussion. Let the participants do most of the talking.
-
* Ask someone to take detailed notes. This shouldn't be someone who will be doing a lot of talking during the critique (e.g. a central person in the incident).
+
* Ask someone to take detailed notes.
-
==== Sample agenda ====
+
* Sample agenda (usually there is not enough time for all of these items; focus on the important ones)
-
(usually there is not enough time for all of these items; focus on the important ones)
+
** introductions
-
* introductions
+
** sign in (to the critique)
-
* sign in (to the critique)
+
** confidentiality
-
* note taker
+
** brief report from person in charge of post op activities (last search manager?) re expenses, lost and found, work needing doing, etc.
-
* confidentiality
+
** what a critique is
-
* brief report from person in charge of post op activities (last search manager?) re expenses, lost and found, work needing doing, etc.
+
*** understanding
-
* what a critique is
+
*** learning, improvement
-
** understanding
+
*** suggestions, ideas
-
** learning, improvement
+
*** how suggestions will be distributed
-
** suggestions, ideas
+
*** committees that will make decisions on suggestions
-
** how suggestions will be distributed
+
** incident summary (from draft 1-page report)
-
** committees that will make decisions on suggestions
+
** functional areas of incident (there likely will only be time to cover the most significant)
-
* incident summary (from draft report)
+
*** mandate
-
* functional areas of incident (there likely will only be time to cover the most significant)
+
*** first notification / tasking
-
*: The ''leading questions'' are just to help the participants think about the subject matter of the functional area. The chair can read them if the participants are stumped about what to say about a functional area. They don't have to be asked or answered, if the group is already jumping into discussion about the functional area.
+
*** call-out
-
** mandate
+
**** typical questions: Was the appropriate type of personnel requested? Were there people that met the criteria that were not called?
-
**: leading questions: Does our team have a mandate to respond to these types of situations? Should it? Are there other organizations that have a mandate to be involved?
+
*** investigation
-
** first notification / tasking
+
*** communications
-
**: leading questions: Was the emergency detected promptly? How was it detected? Who called who? Was the magnitude of the emergency assessed correctly at the start? What means were used for this assessment? Are any guides or aids needed to assist emergency evaluation? Was our information adequate?
+
*** resources
-
** call-out
+
*** (de)briefing
-
**: leading questions: When was Callout notified? Was it appropriate to mobilize PCSAR resources and was this promptly initiated? How could the response time improve? Was a search manager notified promptly? Were search personnel notified promptly? Were the appropriate type of personnel requested? Were there people that met the criteria that were not called? Was their an appropriate response? Were contact numbers up to date?
+
*** searching
-
** investigation
+
*** access/return from segment
-
**: leading questions: What investigations were happening beyond the search effort? What information was key to shaping the search? What could be done to obtain trustworthy information in a timely manner?
+
*** extrication
-
** communications
+
*** stand down
-
**: leading questions: Were communications adequate? What technology was or could have been used? Did messages get passed when they were needed? Was communications clear and accurate?
+
*** CISM
-
** (de)briefing
+
*** prevention, public education
-
**: leading questions: How were teams briefed? Were they provided sufficient background information? Did they understand their assignment and operating procedures? Were teams efficiently debriefed? Did all the information that was needed get recorded?
+
*** travel
-
** searching
+
*** planning
-
**: leading questions: What was the initial strategy for response to this emergency? What techniques proved effective? How did the stategy evolve and change during the emergency and how were thes changes implemented? What problems did seachers encounter? What improvements could be made in searching?
+
*** logistics
-
** access/return from segment
+
*** media
-
**: leading questions: How was access to/from the search segments?
+
*** family
-
** extrication
+
*** post ops
-
**: leading questions: How was the subject extricated? What would have made it more complicated? Was the team prepared for the possible situations?
+
*** learning (How has/could the critique support learning? For exercises, how did/could the goals/techniques promote learning?)
-
** stand down
+
*** miscellaneous
-
**: leading questions: When was the decision made to stand down? Were there problems demobolizing?
+
** round table (anyone have points that they need to bring up that wasn't already mentioned)
-
** CISM
+
Your effort: 1.5 hrs
-
**: leading questions: What were/could have been the critical stresses on this incident? What support was available/used?
+
-
** prevention, public education
+
-
**: leading questions: How could this incident have been prevented? Was this incident used to educated the public?
+
-
** travel
+
-
**: leading questions: How did responders get to and from their home/station to the site? Were convoys used? Was there a need for people to check in when they returned? Was travel safety evaluated?
+
-
** Plans Section
+
-
**: leading questions: What preplans were in place to help with this incident? Were maps, situation reports, weather and hazard forecasts provided to all who needed them? Was the selection of team assignments guided by analysis of the situation? Was the plan for the next op period ready before it started? Were clues, PODs, map updates and recommendations from the field being used to focus search efforts and provide updated information to teams going to the field?
+
-
** Logistics Section
+
-
**: leading questions: What teams/personnel/equipment/materiel was mobilized? How were they mobilized? How did utilization change with time? Were resources used effectively? Were they easy to obtain? Do we have adequate knowledge of resource availability? Are there other resources in our team that we didn't know we had?
+
-
** safety
+
-
**: leading questions: Who performed the functions of the Safety Officer? How were safety concerns identified? What safety issues arose? What near misses were there? How were safety issues addressed? How was it verified that individuals had the skills, physical and mental comfort for what they were asked to do?
+
-
** media
+
-
**: leading questions: How was the media handled? What problems were encountered?
+
-
** family
+
-
**: leading questions: What support did the family need? What critical information came from the family? Was the family kept informed? Did we use other teams to link with family in other communities?
+
-
** post ops
+
-
**: leading questions: What were the major post op activities? When was the team fully ready to be deployed again? Was this work left to only a few volunteers?
+
-
** learning
+
-
**: leading questions: How could this critique have been made a stronger learning opportunity? For exercises, how did/could the goals/techniques promote learning?
+
-
** miscellaneous
+
-
**: leading questions: Are there any subject areas we haven't touched on?
+
-
* round table (anyone have points that they need to bring up that wasn't already mentioned)
+
=== After the critique ===
=== After the critique ===
* Report
* Report
** Edit the incident summary to include information that came out in the critique.
** Edit the incident summary to include information that came out in the critique.
-
** Sort and write up the suggestions (we have examples of this). See [[PCSAR DOC-97 Critique form|PCSAR Doc-97]]
+
** Sort and write up the suggestions (we have examples of this). See PCSAR Doc-97 on [http://pcsar.dyndns.org:8080/documents.html]
** Assign suggestions to be reviewed by PC SAR board, PC SAR preplan committee, PC SAR equipment committee, PC SAR call out committee, PC SAR training committee or one of our partner organizations.
** Assign suggestions to be reviewed by PC SAR board, PC SAR preplan committee, PC SAR equipment committee, PC SAR call out committee, PC SAR training committee or one of our partner organizations.
-
* place the critique suggestions on the wiki under the "Critique" subpage of the [[Incident]].
+
* Forward your report to each group.
-
* {{subpage|Email Report|Forward your report to each group.}}
+
* Send the sign-in list from the critique to the Membership Coordinator.
* Send the sign-in list from the critique to the Membership Coordinator.
-
* Update this page on the wiki to make it easier and better to run another critique.
 
Your effort: 2.5 hrs.
Your effort: 2.5 hrs.
== Critique notes ==
== Critique notes ==
-
* {{subpage|2009-05-05}} : mock search, Anderson search
+
* [[/2009-05-05]] : mock search, Anderson search
-
* {{subpage|2009-09-23}} : Perry search
+
* [[/2009-09-23]] : Perry search
-
* {{subpage|2010-03-21}} : avalanche, mock search
+
* [[/2010-03-21]] : avalanche, mock search
-
* {{subpage|2010-08-24}} : quad, Table Mountain incidents
+
* [[/2010-08-24]] : quad, Table Mountain incidents
-
* {{subpage|2011-01-18}}
+
* [[/2011-01-18]]
-
* {{subpage|2011-09-06}}
+
* [[/2011-09-06]]
-
* {{subpage|2012-03-04}}
+
* [[/2012-03-04]]
-
* {{subpage|2012-04-25}} : for [[2012-04-14 Honda CRV]] search
+
* [[/2012-04-25]] : for [[2012-04-14 Honda CRV]] search
-
* {{subpage|2012-06-06}} : re Victoria Peak
+
* [[/2012-06-06]] : re Victoria Peak
-
* {{subpage|2012-10-02}} Mock/Critque
+
* [[/2012-10-02]] Mock/Critque
-
* {{subpage|2013-02-23}} Mock/Critque
+
* [[/2013-02-23]] Mock/Critque
-
* {{subpage|2013-07-07}} Carpenter Creek/critique for [[2013-06-20]] search
+
* [[/2013-07-07]] Carpenter Creek/critique for [[2013-06-20]] search
-
* {{subpage|2013-07-07}} High River assist [[2013-06-24]]
+
* [[/2013-07-07]] High River assist [[2013-06-24]]
-
* {{subpage|2013-09-17}} : for [[2013-09-14 Westcastle Hike]]
+
-
* {{subpage|2013-10-15}} Waterton spot response
+
-
* {{subpage|2014-01-20}} Oldman Dam
+
-
* {{subpage|2014-03-03 No. 1}} : for [[2014-02-17 South Castle snowmobilers]]
+
-
* {{subpage|2014-03-03 No. 2}} : for [[2014-02-23 CMR skier]]
+
== See also ==
== See also ==

Please note that all contributions to PCSAR are considered to be released under the Attribution-Share Alike 3.0 Unported (see PCSAR:Copyrights for details). If you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION!


Cancel | Editing help (opens in new window)

Templates used on this page:

Personal tools