Team Development Arcs: Difference between revisions
| Line 24: | Line 24: | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|+ | |+ | ||
! colspan="3" style="background-color:#e6cfe3;" | <big> | ! colspan="3" style="background-color:#e6cfe3;" | <big>Developmental Arc I:</big> | ||
|- | |- | ||
!style="background-color:#cc9fc8;"|Neighborhood | !style="background-color:#cc9fc8;"|Neighborhood | ||
| Line 30: | Line 30: | ||
!style="background-color:#cc9fc8;"|Hours | !style="background-color:#cc9fc8;"|Hours | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
| Line 95: | Line 47: | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|+ | |+ | ||
! colspan="3" style="background-color:#f9d0ca;" |<big> | ! colspan="3" style="background-color:#f9d0ca;" |<big>Developmental Arc II</big> | ||
|- | |- | ||
!style="background-color:#f2a096;"|Neighborhood | !style="background-color:#f2a096;"|Neighborhood | ||
| Line 101: | Line 53: | ||
!style="background-color:#f2a096;"|Hours | !style="background-color:#f2a096;"|Hours | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
| Line 214: | Line 70: | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|+ | |+ | ||
! colspan="3" style="background-color:#cbecd5;"|<big> | ! colspan="3" style="background-color:#cbecd5;"|<big>Developmental Arc III</big> | ||
|- | |- | ||
!style="background-color:#98daab;"|Neighborhood | !style="background-color:#98daab;"|Neighborhood | ||
| Line 220: | Line 76: | ||
!style="background-color:#98daab;"|Hours | !style="background-color:#98daab;"|Hours | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
| Line 301: | Line 93: | ||
{| class="wikitable sortable" | {| class="wikitable sortable" | ||
|+ | |+ | ||
! colspan="3" style="background-color:#fff7c6;"|<big> | ! colspan="3" style="background-color:#fff7c6;"|<big>Developmental Arc IV</big> | ||
|- | |- | ||
!style="background-color:#fff08d;"|Neighborhood | !style="background-color:#fff08d;"|Neighborhood | ||
| Line 307: | Line 99: | ||
!style="background-color:#fff08d;"|Hours | !style="background-color:#fff08d;"|Hours | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
|- | |- | ||
| | | | ||
| | | | ||
| | | | ||
Revision as of 12:24, 28 August 2025
Another term for a "Team Development Arc" in the context of NETs is "developmental pathway". PBEM asks NET teams to meet regularly, but many Team Leaders have requested guidance on the "why" of meeting. 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 is to structure a team's movement from a baseline of organization to higher level disaster response skills and capacity. Arcs give TLs a roadmap rather than running meetings by "what should we talk about this month?"
Team Development Arc Leadership Approach
A NET Team Leader is responsible for developing their team. PBEM recommends NET Team Leaders approach the task with the following in mind:
- Use team meetings to develop the team (not necessarily individual NETs)
- Think of your operations plan
- Begin with the end in mind: TLs should visualize what a capable NET team for their neighborhood looks like. For example, by the end of the arc, the team...
- Can set up a command post quickly and assign roles.
- Knows local hazards and prospective resources.
- Can deploy BEECN, DAMM, or other comms with little prompting.
- Has regularly practiced light search and rescue and other basic skillsets.
- Has team cohesion and a predictable meeting rhythm.
- Delegate: A TL is responsible for being the "conductor" at the front of the orchestra, but the conductor does not play an instrument. After a TL develops their team's Development Arcs, they should assign responsibility for most meeting topics to different members of the team
- Braid arcs together and pursue simultaneously
(TBA)
Team Development Arcs Table
The table below proposes five major Team Development Arcs and team activities that move the team down the path.
| Developmental Arc I: | ||
|---|---|---|
| Neighborhood | Volunteers | Hours |
| Developmental Arc II | ||
|---|---|---|
| Neighborhood | Volunteers | Hours |
| Developmental Arc III | ||
|---|---|---|
| Neighborhood | Volunteers | Hours |
| Developmental Arc IV | ||
|---|---|---|
| Neighborhood | Volunteers | Hours |