Team Development Arcs: Difference between revisions

From Portland NET Wiki
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. '''Arcs give TLs a roadmap rather than running meetings by "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?"'''
__NOTOC__
__NOTOC__
== 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)
===== What is a Team Development Arc and how does a Team Leader use them? =====
* 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)
===== Developing a team of NETs vs. developing individual volunteers =====
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.


Maintenance and recycling...
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.


Individual vs. Team development
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'''.
 
===== The relationship between Arcs and Team Operations Planning =====
Every NET Team should have an Ops Plan that defines for the team, after a disaster, such things as where their staging area is, who will take what role, where the neighborhood's most significant hazards are, and so on.
 
Many of the individual modules


== Team Development Arcs Table ==
== Team Development Arcs Table ==