Team Development Arcs: Difference between revisions
From Portland NET Wiki
| Line 30: | Line 30: | ||
Many of the individual modules in the Arcs curriculum have a direct bearing on completion of an Ops Plan. For example, researching and exploring your neighborhood's risk profile or reaching out to local businesses. Therefore, completion of some modules will lead towards completion of an Ops Plan (or refreshing an existing Ops Plan). Teams that need more work on their Ops Plan should prioritize modules that will bring them closer to that goal. [[Team Development Arcs#Development Arc II: Response Operations Planning|Development Arc II: Response Operations Planning]] particularly includes modules related to Operations Plan development. | Many of the individual modules in the Arcs curriculum have a direct bearing on completion of an Ops Plan. For example, researching and exploring your neighborhood's risk profile or reaching out to local businesses. Therefore, completion of some modules will lead towards completion of an Ops Plan (or refreshing an existing Ops Plan). Teams that need more work on their Ops Plan should prioritize modules that will bring them closer to that goal. [[Team Development Arcs#Development Arc II: Response Operations Planning|Development Arc II: Response Operations Planning]] particularly includes modules related to Operations Plan development. | ||
===== The relationship between Arc modules, team meeting agendas, and delegation ===== | |||
Most modules in this guide take about an hour for a team to complete. Some are shorter, and a few may run longer. That flexibility gives you options when planning agendas. A single module might fill an entire meeting, or you might use part of a module alongside other agenda items. And since modules are optional, you don’t need to use one at every meeting. | |||
Modules are also a great tool for delegation. Team Leaders should practice handing off responsibilities, and team members should practice taking them on. This skill is vital in a real response, but it also prevents burnout by making sure the Team Leader isn’t doing all the work during “blue sky” times. PBEM encourages Team Leaders to assign modules to different team members and let them facilitate. This builds confidence, spreads knowledge, and makes meetings more engaging for everyone. | |||
== Team Development Arcs Table == | == Team Development Arcs Table == | ||
