Team Development Arcs: Difference between revisions
From Portland NET Wiki
No edit summary |
|||
| 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 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. | <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 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 == | == 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. | |||
