Team Development Arcs: Difference between revisions

From Portland NET Wiki
Line 704: Line 704:


=== Incident Objectives Discussion ===
=== Incident Objectives Discussion ===
Learning Objective:
'''Learning Objective:'''
 
Team members will practice creating clear, actionable incident objectives to guide NET operations during a disaster response.
Team members will practice creating clear, actionable incident objectives to guide NET operations during a disaster response.


Facilitation Guide:
'''Facilitation:'''
 
Introduce the idea that in the Incident Command System (ICS), objectives are the foundation of response operations. Objectives clarify what needs to be achieved, not how to do it, and they provide direction for the whole team. Without clear objectives, response efforts can become scattered or inefficient.
Introduce the idea that in the Incident Command System (ICS), objectives are the foundation of response operations. Objectives clarify what needs to be achieved, not how to do it, and they provide direction for the whole team. Without clear objectives, response efforts can become scattered or inefficient.


Facilitation steps:
Facilitation steps:


Explain the Basics: Review what makes a good objective:
# '''Explain the Basics:''' Review what makes a good objective:
 
#* '''Specific:''' Clear and focused.
Specific: Clear and focused.
#* '''Measurable:''' Can be tracked or confirmed.
 
#* '''Achievable:''' Realistic with available resources.
Measurable: Can be tracked or confirmed.
#* '''Relevant:''' Tied to the situation and priorities.
 
#* '''Time-bound:''' Accomplishable in the operational period (often the next few hours). Example: “Conduct a windshield survey of all blocks north of Main Street within 2 hours.”
Achievable: Realistic with available resources.
# '''Group Exercise:''' Present a simple scenario (e.g., after an earthquake, reports of damage in the neighborhood). Ask the team to brainstorm possible objectives. Capture them on a whiteboard or flipchart.
 
# '''Refine Together:''' As a group, refine the brainstormed ideas into clear objectives. Encourage participants to move from vague (“Check on neighbors”) to specific (“Knock on every door on Pine Street and report back within 3 hours”).
Relevant: Tied to the situation and priorities.
# '''Prioritize:''' Once objectives are written, guide the team in deciding which are most important for safety, life-saving, or communication. Emphasize that objectives should be achievable with current personnel and time.
 
# '''Document & Share:''' Practice writing objectives on an ICS 202 form or in team notes. Stress that sharing objectives aloud ensures everyone is on the same page.
Time-bound: Accomplishable in the operational period (often the next few hours).
Example: “Conduct a windshield survey of all blocks north of Main Street within 2 hours.”
 
Group Exercise: Present a simple scenario (e.g., after an earthquake, reports of damage in the neighborhood). Ask the team to brainstorm possible objectives. Capture them on a whiteboard or flipchart.
 
Refine Together: As a group, refine the brainstormed ideas into clear objectives. Encourage participants to move from vague (“Check on neighbors”) to specific (“Knock on every door on Pine Street and report back within 3 hours”).
 
Prioritize: Once objectives are written, guide the team in deciding which are most important for safety, life-saving, or communication. Emphasize that objectives should be achievable with current personnel and time.
 
Document & Share: Practice writing objectives on an ICS 202 form or in team notes. Stress that sharing objectives aloud ensures everyone is on the same page.
 
Debrief Questions:
 
What made some objectives clearer than others?
 
How do clear objectives help us avoid confusion in the field?


How many objectives are realistic for one operational period?
'''Debrief Questions:'''


How might we incorporate writing objectives into our team’s regular drills or activations?
* What made some objectives clearer than others?
* How do clear objectives help us avoid confusion in the field?
* How many objectives are realistic for one operational period?
* How might we incorporate writing objectives into our team’s regular drills or activations?