Team Development Arcs: Difference between revisions
From Portland NET Wiki
| Line 209: | Line 209: | ||
Encourage volunteers to also talk about their favorite piece of gear that is not standard to the NET kit list. | Encourage volunteers to also talk about their favorite piece of gear that is not standard to the NET kit list. | ||
'''Debrief Questions:''' | |||
* What items did you discover were missing or expired from your kit? | |||
* Did you see any creative or useful additions from other team members? | |||
* How confident do you feel that your kit would support you for 24–48 hours of response work? | |||
* What steps can the team take to help each other fill common gaps? | |||
=== Local Fire Station Meeting === | === Local Fire Station Meeting === | ||
'''''Learning objective:''''' ''Team members will build relationships with their local firefighters, learn about station capabilities, and understand how NETs can support fire response during disasters.'' | '''''Learning objective:''''' ''Team members will build relationships with their local firefighters, learn about station capabilities, and understand how NETs can support fire response during disasters.'' | ||
'''''Facilitation:''''' The NET Team Leader should first contact their PBEM District Liaison to help them schedule a day with the NET's nearest fire station. | '''''Facilitation:''''' The NET Team Leader should first contact their PBEM District Liaison ({{EmailLink|addr=net@portlandoregon.gov|name=net@portlandoregon.gov}}) to help them schedule a day and time with the NET's nearest fire station. | ||
Begin the activity with introductions, briefly explaining the NET program and your team’s role in community preparedness. Encourage firefighters to share about their daily work, the equipment housed at the station, and their priorities during major incidents. During the tour, prompt your team to observe and ask questions about how the station responds to large-scale emergencies, what resources they can and cannot provide, and how volunteers like NETs might fit into the larger response picture. Keep the tone conversational and respectful of firefighters’ time—calls may interrupt, so be flexible. Close the session by thanking the firefighters, presenting them with your team contact information, and inviting them to attend or speak at a future NET meeting. Afterward, debrief with your team about what they learned and how that information might influence your local disaster planning. | Begin the activity with introductions, briefly explaining the NET program and your team’s role in community preparedness. Encourage firefighters to share about their daily work, the equipment housed at the station, and their priorities during major incidents. During the tour, prompt your team to observe and ask questions about how the station responds to large-scale emergencies, what resources they can and cannot provide, and how volunteers like NETs might fit into the larger response picture. Keep the tone conversational and respectful of firefighters’ time—calls may interrupt, so be flexible. Close the session by thanking the firefighters, presenting them with your team contact information, and inviting them to attend or speak at a future NET meeting. Afterward, debrief with your team about what they learned and how that information might influence your local disaster planning. | ||
'''Debrief Questions:''' | |||
* What surprised you about the station’s capabilities or limitations? | |||
* How do firefighters view volunteer support during major incidents? | |||
* Did anything you learned change how you think about your role as a NET? | |||
* What follow-up steps could strengthen this new relationship? | |||
=== NETwiki Team Page Discussion === | |||
'''''Learning objective:''''' ''Team members will collaboratively design and update their team’s NETwiki page to serve as a shared, accessible hub for operations, plans, and team information.'' | |||
'''''Facilitation:''''' Begin by projecting or sharing the team’s existing NETwiki page (or a blank one if it hasn’t been created). Explain that the wiki is intended to be a “living document” where the team records important details: operations plans, meeting schedules, contact protocols, and other resources that keep everyone aligned. Emphasize that it’s not just an archive, but a tool for both preparedness and active response. | |||
