Team Development Arcs: Difference between revisions

From Portland NET Wiki
← Older edit
VisualWikitext
No edit summary
 
(23 intermediate revisions by one other user not shown)
Line 7: Line 7:


The use of Team Development Arcs are completely optional, and can be changed or edited to suit the needs of NETs who use them. They are intended as a supplementary resource for NET Team Leaders.  
The use of Team Development Arcs are completely optional, and can be changed or edited to suit the needs of NETs who use them. They are intended as a supplementary resource for NET Team Leaders.  
{| class="wikitable"
|+
! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents
! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated
|-
|Form: [https://app.smartsheet.com/b/form/45b4b43047e74ce0842e3dc924f43f4e Development Arc Feedback]
|2025.10.04
|-
|Form: [https://app.smartsheet.com/b/form/104dab042ef84ca5a9fce7b2076d5ad3 I Would Like to Create a Module]
|2025.10.04
|-
|Form: [https://app.smartsheet.com/b/form/0199b17984a073d69aad94f410695792 I Would Like to Instruct a Module]
|2025.10.04
|}
<br/>


<br>
<br>


{|style="border:1px solid black; border-collapse:collapse;"
{|style="border:1px solid grey; border-collapse:collapse;"
|+
|+
!style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|<small>Contents</small>
!style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|<small>Contents</small>
|-
|-
|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Team Development Arc Leadership Approach|Team Development Arc Leadership Approach]]
|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Team Development Arc Leadership Approach|<small>Team Development Arc Leadership Approach</small>]]
|-
[[Team Development Arcs#Team Development Arcs Table|<small>Team Development Arcs Table</small>]]
|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Team Development Arcs Table|Team Development Arcs Table]]
 
|-
[[Team Development Arcs#Braiding the Arcs Together|<small>Braiding the Arcs Together</small>]]
|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Braiding the Arcs Together|Braiding the Arcs Together]]
 
|-
[[Team Development Arcs#Development Arc I: Team Organization and Cohesion|<small>'''Development Arc I:''' Team Organization and Cohesion</small>]]
|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Development Arc I: Team Organization and Cohesion|Development Arc I: Team Organization and Cohesion]]
 
|-
[[Team Development Arcs#Development Arc II: Response Operations Planning|<small>'''Development Arc II:''' Response Operations Planning</small>]]
|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Development Arc II: Response Operations Planning|Development Arc II: Response Operations Planning]]
 
|-
[[Team Development Arcs#Development Arc III: Exercises and Tabletops|<small>'''Development Arc III:''' Exercises and Tabletops</small>]]
|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Development Arc III: Exercises and Tabletops|Development Arc III: Exercises and Tabletops]]
 
|-
[[Team Development Arcs#Development Arc IV: Communications|<small>'''Development Arc IV:''' Communications</small>]]
|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Development Arc IV: Communications|Development Arc IV: Communications]]
 
|-
<small>[[Team Development Arcs#Development Arc V: Basic Response Skills|'''Development Arc V:''' Basic Response Skills]]</small>
|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Development Arc VI: Disaster DIY|Development Arc VI: Disaster DIY]]
 
[[Team Development Arcs#Development Arc VI: Disaster DIY|<small>'''Development Arc VI:''' Disaster DIY</small>]]
|}
|}


Line 49: Line 66:
As a NET Team Leader, your most important responsibility is '''helping your team grow together''' into a capable disaster response group. The purpose of this Development Arc curriculum is to give you a clear roadmap for building your team’s overall capacity.
As a NET Team Leader, your most important responsibility is '''helping your team grow together''' into a capable disaster response group. The purpose of this Development Arc curriculum is to give you a clear roadmap for building your team’s overall capacity.


At the same time, each volunteer is also on their own personal growth journey. NET volunteers are largely responsible for their '''individual development''', which is where the Volunteer Support Function (VSF) system comes in. VSFs provide pathways for volunteers to specialize in skills that interest them and strengthen the team.
At the same time, each volunteer is also on their own personal growth journey. NET volunteers are largely responsible for their '''individual development''', which is where the [[Volunteer Support Functions Directory|Volunteer Support Function (VSF)]] system comes in. VSFs provide pathways for volunteers to specialize in skills that interest them and strengthen the team.


Your role as Team Leader is to see both sides: to think about your team as a whole unit, and also to recognize the unique skills and strengths each volunteer brings. You don’t need to control an individual’s development, but you can guide them—helping them choose VSFs that align with team needs, and working with PBEM to make sure those paths stay open. In short: '''you shape the team, while supporting each volunteer in shaping themselves as volunteer responders'''.
Your role as Team Leader is to see both sides: to think about your team as a whole unit, and also to recognize the unique skills and strengths each volunteer brings. You don’t need to control an individual’s development, but you can guide them—helping them choose VSFs that align with team needs, and working with PBEM to make sure those paths stay open. In short: '''you shape the team, while supporting each volunteer in shaping themselves as volunteer responders'''.
Line 249: Line 266:
|-
|-
|IV.01
|IV.01
|Personal Accountability Reporting (PAR)
|[[Team Development Arcs#IV.01 Personal Accountability Reporting (PAR)|Personal Accountability Reporting (PAR)]]
|Either
|Either
|-
|-
Line 577: Line 594:
* If there is time (i.e. at least two weeks before the session), the facilitator should encourage all team members to check they have all the equipment PBEM issues: ID card, hard hat (which should be replaced every five years), hard hat chin strap, and vest. Any missing items or items in need of replacement can be requested at the '''[https://app.smartsheet.com/b/form/5b3303eec5114f6ba0d6ffa52e496933 NET/BEECN ID Card, Helmet, and/or Vest Request Form]'''. PBEM also issues FRS/GMRS radios (if a volunteer cannot afford one), Field Operating Guides (FOGs), and waterproof backpack covers as supplies are available.
* If there is time (i.e. at least two weeks before the session), the facilitator should encourage all team members to check they have all the equipment PBEM issues: ID card, hard hat (which should be replaced every five years), hard hat chin strap, and vest. Any missing items or items in need of replacement can be requested at the '''[https://app.smartsheet.com/b/form/5b3303eec5114f6ba0d6ffa52e496933 NET/BEECN ID Card, Helmet, and/or Vest Request Form]'''. PBEM also issues FRS/GMRS radios (if a volunteer cannot afford one), Field Operating Guides (FOGs), and waterproof backpack covers as supplies are available.


'''<mark>Facilitation</mark>'''[[File:Netpack.jpg|right|265x265px]]Ask each team member to bring their NET bag or response kit to the meeting. Begin by reviewing the [[Basic NET Training Standard Syllabus#Equipment: Basic NET Response Packs|official NET kit list]]. Explain that the purpose of this exercise is not to judge completeness but to help everyone become more familiar with their gear, share practical tips, and make sure nothing critical is missing.
'''<mark>Facilitation</mark>'''
 
[[File:Netpack.jpg|right|265x265px]]Ask each team member to bring their NET bag or response kit to the meeting. Begin by reviewing the [[Basic NET Training Standard Syllabus#Equipment: Basic NET Response Packs|official NET kit list]]. Explain that the purpose of this exercise is not to judge completeness but to help everyone become more familiar with their gear, share practical tips, and make sure nothing critical is missing.


Facilitate a guided walkthrough of major kit categories—personal safety/PPE (helmet, vest, gloves), communication (radio, whistle, contact sheet), medical (first aid supplies), tools, and comfort items (snacks, water). Invite volunteers to share how they’ve adapted their kits to fit their neighborhood context or personal needs (e.g., dog leash, maps, laminated cards). Keep the conversation focused on functionality and portability. End with a brief “gap check”: have members note items they need to add or replace, and suggest a timeline for completing those updates. If possible, document any common shortages so the team can discuss bulk purchases or supply-sharing at a future meeting.
Facilitate a guided walkthrough of major kit categories—personal safety/PPE (helmet, vest, gloves), communication (radio, whistle, contact sheet), medical (first aid supplies), tools, and comfort items (snacks, water). Invite volunteers to share how they’ve adapted their kits to fit their neighborhood context or personal needs (e.g., dog leash, maps, laminated cards). Keep the conversation focused on functionality and portability. End with a brief “gap check”: have members note items they need to add or replace, and suggest a timeline for completing those updates. If possible, document any common shortages so the team can discuss bulk purchases or supply-sharing at a future meeting.
Line 1,015: Line 1,034:
<div class="mw-collapsible mw-collapsed">
<div class="mw-collapsible mw-collapsed">
=== VSF Gap Analysis ===
=== VSF Gap Analysis ===
'''''Learning objective:''' Team members will understand the purpose of Volunteer Support Functions (VSFs), identify their own areas of specialization, and consider how their team’s mix of VSFs can strengthen neighborhood response.''
'''<mark>Learning Objective</mark>'''


'''''Facilitation:''''' Begin by explaining that PBEM organizes all volunteers (NETs, BEECN, ATVs) into Volunteer Support Functions (VSFs). These are specialized areas of disaster skills or knowledge—such as Search & Rescue, Medical, Communications, Logistics, or Public Information. VSFs serve two main purposes: they allow volunteers to deepen skills in areas they’re interested in, and they give teams and PBEM a clear picture of what capabilities exist across the city.
''Team members will understand the purpose of Volunteer Support Functions (VSFs), identify their own areas of specialization, and consider how their team’s mix of VSFs can strengthen neighborhood response.''
 
'''<mark>Supplemental Resources</mark>'''
 
'''<mark>Preparation</mark>'''
 
'''<mark>Facilitation</mark>'''
 
Begin by explaining that PBEM organizes all volunteers (NETs, BEECN, ATVs) into Volunteer Support Functions (VSFs). These are specialized areas of disaster skills or knowledge—such as Search & Rescue, Medical, Communications, Logistics, or Public Information. VSFs serve two main purposes: they allow volunteers to deepen skills in areas they’re interested in, and they give teams and PBEM a clear picture of what capabilities exist across the city.


Provide a simple overview of how VSFs work:
Provide a simple overview of how VSFs work:
Line 1,036: Line 1,063:
Wrap up by encouraging interested members to contact PBEM if they want to update their VSF, and consider recording your team’s VSF mix on your NETwiki page for future reference.
Wrap up by encouraging interested members to contact PBEM if they want to update their VSF, and consider recording your team’s VSF mix on your NETwiki page for future reference.


'''Debrief Questions:'''
'''<mark>Debrief Questions</mark>'''


*Which VSFs are represented on our team right now? Where are the gaps?
*Which VSFs are represented on our team right now? Where are the gaps?
Line 1,045: Line 1,072:


*How can we support each other in building depth in these areas (peer training, shared resources, guest speakers)?
*How can we support each other in building depth in these areas (peer training, shared resources, guest speakers)?
'''<mark>Module Outputs</mark>'''
</br>
</br>
<hr>
<hr>
Line 1,320: Line 1,350:
== Development Arc IV: Communications ==
== Development Arc IV: Communications ==
<div class="mw-collapsible mw-collapsed">
<div class="mw-collapsible mw-collapsed">
=== Personal Accountability Reporting (PAR) ===
=== IV.01 Personal Accountability Reporting (PAR) ===
'''Learning Objective:'''
'''Learning Objective:'''


Line 1,479: Line 1,509:
'''Learning Objective:'''
'''Learning Objective:'''


''Team members will practice using proper radio etiquette, including prowords, clear phrasing, and the phonetic alphabet, to ensure efficient and accurate communication during disaster response.''
''Team members will practice clear, efficient radio communication by developing practical message-handling skills—using phonetics, “I spell,” pacing, and fills—to ensure information is accurately sent and received during disaster response.''


'''Facilitation Guide:'''
'''Facilitation Guide:'''


Begin by highlighting that clear, concise radio communication is '''critical under stress'''. Unlike phone calls, radio transmissions are one-to-many, brief, and subject to interference. A little discipline goes a long way in reducing confusion and speeding operations.
Begin by setting expectations clearly:


'''Step 1 – Review the Basics of Radio Etiquette:'''
This module is not radio certification training. It is a practical, team-based exercise designed to help all NET volunteers—especially those who use radios infrequently—communicate clearly and confidently under stress. The focus is not perfection, but making sure the person on the other end actually understands the message.


* Think before you speak: Plan your message in your head before keying the mic.
Emphasize that good radio communication is less about sounding “professional” and more about being helpful, patient, and precise.
* Press, pause, then talk: Wait 1 second after pressing transmit so your first words aren’t cut off.
* Keep it short: Use plain language, avoid unnecessary chatter.
* Identify who you’re calling, then yourself: Example: “Staging, this is Team Alpha.”


* Acknowledge messages: Use “Copy,” “Affirmative/Negative,” or repeat back essential details.
'''Step 1 – What Radios Are Good (and Bad) At:'''
* One at a time: Pause before speaking in case someone else is transmitting.


'''Step 2 – Introduce Prowords:'''
Briefly discuss radio realities:


Explain that '''prowords''' are standard words that carry agreed-upon meanings in radio traffic. Review and practice common ones:
* Radios are shared channels
* Messages may be missed or cut off
* Background noise is common
* Stress affects how we speak and listen
Frame the goal:


* '''“Over”''' – I’m done speaking and expect a reply.
“Your job on the radio is not to talk fast or fancy. Your job is to make it easy for the listener to copy your message.”
* '''“Out”''' – I’m done, no reply expected.
* '''“Say Again”''' – Repeat your last transmission.
* '''“Copy”''' – I received and understood.
* '''“Standby”''' – I acknowledge but need more time.
* '''“Affirmative” / “Negative”''' – Yes / No.
* '''“Break”''' – Used to separate different portions of a message.


'''Step 3 – Phonetic Alphabet Practice:'''
'''Step 2 – Call-Up Basics (Keep It Simple):'''


Provide the NATO phonetic alphabet (Alpha, Bravo, Charlie, etc.) and stress its importance when spelling out names, addresses, or codes over a noisy channel.
Review the basic call-up pattern: Who you are calling → who you are


'''Practice exercise:''' Have each member spell their last name phonetically. Then practice with addresses, street names, or team designators.
Example: ''“Staging, this is Team Alpha.”''


'''Step 4 – Transmission Exercise:'''
Reinforce:  


Pair up participants with radios.
* Use tactical identifiers, not names
* Pause briefly before speaking
* Speak clearly, not loudly


Provide each pair with a short scripted message to relay (e.g., “Requesting medical supplies at 123 Pine Street”).
'''Step 3 – Message Handling Skills (Core Focus):'''


Have them practice proper call-up, use of prowords, and phonetic spelling when needed.
Explain that most radio problems are message problems, not equipment problems. Introduce the four core skills adapted from GRO practice.


Rotate scripts so participants adapt to new scenarios.
'''A.) Pacing (speed)'''


'''Step 5 – Group Drill:'''
Demonstrate the difference between:
* Talking at conversation speed
* Talking at radio speed (slower, deliberate)
Practice:
* Read a short message too fast
* Then read it slowly enough that someone could write it down
Key coaching point: ''"If someone is writing, you are probably talking too fast"''


Set up a mock NET radio net with one person as '''Net Control'''. Assign others roles (Team Alpha, Team Bravo, Logistics, etc.). Practice a short scenario (e.g., small fire, blocked road, injured resident) where teams must report in using proper etiquette.
'''B.) Phonetics (Flexible, not formal)'''
 
Explain: Phonetics simply means using words to make letters clear. There is no requirement to memorize a specific alphabet.
 
Examples:
 
* “J as in Jelly”
* “B as in Boy”
* “M as in Mountain”
Encourage improvisation — clarity matters more than correctness.
 
Practice:
 
* Spell names, street names, or intersections using any clear phonetics
* Listener repeats back what they heard
 
'''C.) "I spell"'''
 
Introduce “I spell” as a listener-friendly cue. Example:
 
''“The street name is I spell: J as in Jelly, E as in Eagle, R as in Raspberry.”''
 
Practice:
 
* Have volunteers announce “I spell”
* Spell slowly
* Pause between letters
 
'''D.) Fills, Repeats, and Corrections'''
 
Explain that mistakes are normal. What matters is fixing them clearly. Useful techniques:
 
* “Correction…”
* “Say again from…”
* Repeating critical info twice (addresses, numbers)
 
Practice:
 
* Intentionally introduce a garbled message
* Ask the listener to request a fill
* Practice clean corrections without frustration
 
'''Step 4 – Numbers and Addresses:'''
 
Review best practices:
 
* Speak numbers slowly
* Group long numbers
* Repeat addresses if important
 
Example: ''"Address is one-two-three Pine Street. I repeat: one-two-three Pine Street."''
 
Practice with:
 
* Addresses
* Block numbers
* Unit counts
 
'''Step 5 – Paired Message Practice:'''
 
Pair participants with radios. Give each pair short, realistic messages:
 
* Requesting supplies
* Reporting damage
* Checking in on status
Focus coaching on:
 
* Pacing
* Phonetics
* Listener confirmation
 
Rotate roles so everyone speaks and listens.
 
'''Step 6 – Group Net Practice'''
 
Set up a simple radio net:
 
* One Net Control
* Several teams checking in
 
Inject common challenges:
 
* “Say again”
* Missed numbers
* Competing traffic
 
Pause occasionally to coach: ''What could make that message easier to copy?"''


'''Debrief Questions:'''
'''Debrief Questions:'''


* Which habits helped messages come through most clearly?
* What made messages easiest to understand?
* What mistakes did we make that caused confusion?
* When did pacing matter most?
* How can we reinforce consistent use of prowords and phonetic spelling in future drills?
* What helped you as a listener?
* What challenges might we face under stress, and how do we prepare for them?
* What habits do we want to practice regularly as a team?
</div>
 
'''Module Outputs:'''
 
By the end of this module, teams should have:
 
* Practiced pacing messages for clarity
* Used phonetics flexibly and confidently
* Used “I spell” appropriately
* Corrected and repeated messages effectively
* Increased confidence speaking on the radio without overthinking it</div>
 
== Development Arc V: Basic Response Skills ==


== Development Arc VI: Disaster DIY ==
== Development Arc VI: Disaster DIY ==
Retrieved from "https://volunteerpdx.net/index.php/Team_Development_Arcs"