Team Development Arcs: Difference between revisions

From Portland NET Wiki
Line 320: Line 320:
|}
|}
</div>
</div>
== Braiding the arcs together ==
[[File:BRAID.jpg|thumb|''I needed a metaphor here, so how's this? It's got...like, survival rope. In the metaphor. The metaphor for braiding together different arcs of your team's development. Look, I don't get paid to be profound okay?'']]
Sometimes the most effective way to plan is to bring the whole team together for a “braiding session.” In this meeting, the team looks at the five arcs side by side and decides which modules they want to tackle in the coming months. Instead of treating arcs as separate tracks, the team weaves them together into a shared path of growth.
'''How to Facilitate a Braiding Session:'''
# '''Lay out the options:''' Print or display all the modules (for example, as cards). Briefly remind the team what each arc is designed to build.
# '''Set the vision:''' Ask the group to picture what they want the team to look like six months or a year from now (e.g., more confident with radios, stronger neighborhood ties, smoother command post setup).
# '''Choose priorities:''' As a group, select a mix of modules from different arcs that best support that vision. For example, combine “NETwiki Page Discussion” (Cohesion) with “Ops Plan Check-In” (Operations) and “Radio Speaking Skills” (Communications).
# '''Build a sequence:''' Decide on a rough order. Some modules might be prerequisites for others; others can run in parallel.
# '''Assign facilitators:''' Encourage different volunteers to take responsibility for leading modules, so that leadership and knowledge are shared.
# '''Capture the plan:''' Record the braided arc in your team’s Ops Plan or NETwiki page so it can guide future meetings.
This process helps ensure the team’s development is purposeful, balanced, and shared, and not just driven by the Team Leader alone.


== Development Arc I: Team Organization and Cohesion ==
== Development Arc I: Team Organization and Cohesion ==