Team Development Arcs: Difference between revisions

From Portland NET Wiki
← Older edit
VisualWikitext
 
(56 intermediate revisions by one other user not shown)
Line 1: Line 1:
<mark>Another term for a "Team Development Arc" in the context of NETs is "developmental pathway".</mark> PBEM asks NET teams to meet regularly, but to do what? Without a defined purpose, team meetings can drift, prompting some members to stop attending meetings, and teams do not build their capacity as neighborhood-based disaster responders. The purpose of Team Developmental Arcs are to structure a team's movement from a baseline of organization to higher level disaster response skills and capacity. '''Arcs give TLs a roadmap through team development rather than convening meetings around "what should we talk about this month?"'''
<mark>Another term for a "Team Development Arc" in the context of NETs is "developmental pathway".</mark> PBEM asks NET teams to meet regularly, but to do what? Without a defined purpose, team meetings can drift, prompting some members to stop attending meetings, and teams do not build their capacity as neighborhood-based disaster responders. The purpose of Team Developmental Arcs are to structure a team's movement from a baseline of organization to higher level disaster response skills and capacity. '''Arcs give TLs a roadmap through team development''' rather than convening meetings around "what should we talk about this month?"
 
'''There is a two part objective to this program:'''
 
# '''Provide Team Leaders with team meeting activity modules that can be easily planned, like a recipe, for team meetings.'''
# '''Help teams move along a path or paths of development towards greater efficacy as a team of disaster responders.'''


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>
{|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;"|[[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>]]
[[Team Development Arcs#Braiding the Arcs Together|<small>Braiding the Arcs Together</small>]]
[[Team Development Arcs#Development Arc I: Team Organization and Cohesion|<small>'''Development Arc I:''' Team Organization and Cohesion</small>]]
[[Team Development Arcs#Development Arc II: Response Operations Planning|<small>'''Development Arc II:''' Response Operations Planning</small>]]
[[Team Development Arcs#Development Arc III: Exercises and Tabletops|<small>'''Development Arc III:''' Exercises and Tabletops</small>]]
[[Team Development Arcs#Development Arc IV: Communications|<small>'''Development Arc IV:''' Communications</small>]]
<small>[[Team Development Arcs#Development Arc V: Basic Response Skills|'''Development Arc V:''' Basic Response Skills]]</small>
[[Team Development Arcs#Development Arc VI: Disaster DIY|<small>'''Development Arc VI:''' Disaster DIY</small>]]
|}


__NOTOC__
__NOTOC__
Line 19: 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 164: Line 211:
|Either
|Either
|-
|-
|11.14
|II.14
|Response Debrief
|Response Debrief
|Either
|Either
Line 176: Line 223:
{| class="wikitable sortable" style="width: 70%;"
{| class="wikitable sortable" style="width: 70%;"
|+
|+
! colspan="3" |<big>Development Arc III: Exercises and Tabletops</big>
! colspan="3" |<big>[[Team Development Arcs#Development Arc III: Exercises and Tabletops|Development Arc III: Exercises and Tabletops]]</big>
|-
|-
!style="background-color:#94AC96;"|
!style="background-color:#94AC96;"|
Line 191: Line 238:
|-
|-
|III.03
|III.03
|Tabletop: Windstorm
|[[Team Development Arcs#III.03 FEMA's CERT Tabletops|FEMA's CERT Tabletops]]
* Earthquake Response
|Indoors
|Indoors
|-
|-
Line 218: 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 307: Line 355:
|VI.01
|VI.01
|[[Team Development Arcs#VI.01 DIY Air Cleaner|DIY Air Cleaner]]
|[[Team Development Arcs#VI.01 DIY Air Cleaner|DIY Air Cleaner]]
|Either
|-
|VI.02
|[[Team Development Arcs#VI.02 Hands-Free Portable Sink|Hands-Free Portable Sink]]
|Either
|-
|VI.03
|[[Team Development Arcs#VI.03 Easy-Build Handwashing Station|Easy-Build Handwashing Station]]
|Either
|Either
|}
|}
Line 538: 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 976: 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>'''
 
''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>'''


'''''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.
'''<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 997: 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,006: 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,260: Line 1,329:
=== Scenario Village Preparation ===
=== Scenario Village Preparation ===


=== Tabletop: Windstorm ===
=== III.03 FEMA's CERT Tabletops ===
'''<mark>Learning Objective</mark>'''
 
====== Earthquake Response Scenario ======
'''''Note: This tabletop used to be part of Basic NET training, so some members may already be familiar with it.'''''
 
"A major earthquake has struck at 1:00 p.m. on a mid-week afternoon. The day is cool and cloudy. It has been raining lightly all day, and the temperature is expected to fall quickly by 5:30 p.m. The local CERT has been activated to assess damage in its neighborhood. CERT members have just arrived at the pre-designated meeting point."
 
:''[[Media:FEMA CERT Tabletop Exercise 1.Facilitator.pdf|Facilitator Packet FEMA CERT Tabletop Exercise #1]]'' (one copy for the facilitator); 31 pages.
 
:''[[Media:FEMA CERT Tabletop Exercise 1.Participants.pdf|Participant Packet FEMA CERT Tabletop Exercise #1]]'' (each participant should receive one packet); 14 pages.


=== Disasterville Board Game ===
=== Disasterville Board Game ===
Line 1,271: 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,430: 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:
 
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.


'''Step 1 – Review the Basics of Radio Etiquette:'''
Emphasize that good radio communication is less about sounding “professional” and more about being helpful, patient, and precise.


* Think before you speak: Plan your message in your head before keying the mic.
'''Step 1 – What Radios Are Good (and Bad) At:'''
* 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.
Briefly discuss radio realities:
* One at a time: Pause before speaking in case someone else is transmitting.


'''Step 2 – Introduce Prowords:'''
* 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:


Explain that '''prowords''' are standard words that carry agreed-upon meanings in radio traffic. Review and practice common ones:
“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.”


* '''“Over”''' – I’m done speaking and expect a reply.
'''Step 2 – Call-Up Basics (Keep It Simple):'''
* '''“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:'''
Review the basic call-up pattern: Who you are calling → who you are


Provide the NATO phonetic alphabet (Alpha, Bravo, Charlie, etc.) and stress its importance when spelling out names, addresses, or codes over a noisy channel.
Example: ''“Staging, this is Team Alpha.”''


'''Practice exercise:''' Have each member spell their last name phonetically. Then practice with addresses, street names, or team designators.
Reinforce:  


'''Step 4 – Transmission Exercise:'''
* Use tactical identifiers, not names
* Pause briefly before speaking
* Speak clearly, not loudly


Pair up participants with radios.
'''Step 3 – Message Handling Skills (Core Focus):'''


Provide each pair with a short scripted message to relay (e.g., “Requesting medical supplies at 123 Pine Street”).
Explain that most radio problems are message problems, not equipment problems. Introduce the four core skills adapted from GRO practice.


Have them practice proper call-up, use of prowords, and phonetic spelling when needed.
'''A.) Pacing (speed)'''


Rotate scripts so participants adapt to new scenarios.
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"''


'''Step 5 – Group Drill:'''
'''B.) Phonetics (Flexible, not formal)'''


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.
Explain: Phonetics simply means using words to make letters clear. There is no requirement to memorize a specific alphabet.


'''Debrief Questions:'''
Examples:


* Which habits helped messages come through most clearly?
* “J as in Jelly”
* What mistakes did we make that caused confusion?
* “B as in Boy”
* How can we reinforce consistent use of prowords and phonetic spelling in future drills?
* “M as in Mountain”
* What challenges might we face under stress, and how do we prepare for them?
Encourage improvisation — clarity matters more than correctness.
</div>


== Development Arc VI: Disaster DIY ==
Practice:
<div class="mw-collapsible mw-collapsed">
 
=== VI.01 DIY Air Cleaner ===
* Spell names, street names, or intersections using any clear phonetics
'''<mark>Learning Objective</mark>'''
* 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:'''


''Team members will learn how to construct a low-cost, do-it-yourself air cleaner using readily available materials, understand when and why it should be used during smoke or poor air quality events, and practice assembling one together to build skills they can share with neighbors.''
Review best practices:


'''<mark>Materials List</mark>'''
* Speak numbers slowly
{| class="wikitable"
* Group long numbers
|+
* Repeat addresses if important
!Item
 
!Qty.
Example: ''"Address is one-two-three Pine Street. I repeat: one-two-three Pine Street."''
!Example
 
!Cost
Practice with:
|-
 
|20" x 20" box fan
* Addresses
|1
* Block numbers
|
* Unit counts
|
 
|-
'''Step 5 – Paired Message Practice:'''
|20" x 20" x 1" or 4" [https://www.epa.gov/indoor-air-quality-iaq/what-merv-rating MERV] 13 air filter
 
|1 to 5
Pair participants with radios. Give each pair short, realistic messages:
|
 
|
* Requesting supplies
|-
* Reporting damage
|Sheet of scrap cardboard (at least 20" x 20"
* Checking in on status
|1
Focus coaching on:
|
 
|
* Pacing
|-
* Phonetics
|Clamps, bungee cords, or duct tape
* 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:'''
 
* What made messages easiest to understand?
* When did pacing matter most?
* What helped you as a listener?
* What habits do we want to practice regularly as a team?
 
'''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 ==
<div class="mw-collapsible mw-collapsed">
=== VI.01 DIY Air Cleaner ===
{{#ev:youtube|aw7fUMhNov8|430|right|'''''Video: How to Make a DIY Air Filter'''''|frame}}
'''<mark>Learning Objective</mark>'''
 
''Team members will learn how to construct a low-cost, do-it-yourself air cleaner using readily available materials, understand when and why it should be used during smoke or poor air quality events, and practice assembling one together to build skills they can share with neighbors.''
 
'''<mark>Materials List</mark>'''
 
{| class="wikitable"
|+
!Item
!Qty.
!Example
!Cost
|-
|20" x 20" box fan
|1
|
|
|-
|20" x 20" x 1" or 4" [https://www.epa.gov/indoor-air-quality-iaq/what-merv-rating MERV] 13 air filter
|1 to 5
|
|
|-
|Sheet of scrap cardboard (at least 20" x 20"
|1
|
|
|-
|Clamps, bungee cords, or duct tape
|
|
|
|
Line 1,530: Line 1,710:
|2024.08.26
|2024.08.26
|}
|}
<br>
=== VI.02 Hands-Free Portable Sink ===
'''<mark>Learning Objective</mark>'''
''Team members will learn how to build a portable, hands-free handwashing station using two plastic buckets and a one-way squeeze pump, with an option to organize a community “work party” to produce multiple stations. Volunteers will also recognize how pre-positioning several units across the neighborhood—along with stored water—ensures immediate access to safe, sanitary handwashing after a disaster. This module was created by NET volunteer Merilee Karr.''
'''<mark>Materials List</mark>'''
See instructions.
'''<mark>Instructions</mark>'''
{| class="wikitable"
|+
! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents/Resources
! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated
|-
|[https://www.instructables.com/Portable-Foot-pump-Handwashing-Station/ Hands-Free Portable Sink at Instructables]
|≈ 2020
|}
<br>
=== VI.03 Easy-Build Handwashing Station ===
'''<mark>Learning Objective</mark>'''
''Team members will recognize the importance of maintaining safe handwashing practices when plumbing is unavailable—whether due to a major or minor disaster, or in everyday off-grid settings such as community events or camping. Volunteers will explore low-cost, portable solutions that ensure hygiene and reduce the spread of illness when conventional water systems are disrupted. This module was created by NET volunteer Merilee Karr.''
'''<mark>Materials List</mark>'''
See instructions.
'''<mark>Instructions</mark>'''
{| class="wikitable"
|+
! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents/Resources
! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated
|-
|[https://www.instructables.com/Easy-Build-Handwashing-Station-With-Videos/ Easy-Build Handwashing Station at Instructables]
|2021.02.26
|}
<br>


== Team Development Arcs Frequently Asked Questions (FAQs) ==
== Team Development Arcs Frequently Asked Questions (FAQs) ==
Retrieved from "https://volunteerpdx.net/index.php/Team_Development_Arcs"