Team Development Arcs: Difference between revisions
From Portland NET Wiki
| Line 619: | Line 619: | ||
=== I.05 NETwiki Team Page Discussion === | === I.05 NETwiki Team Page Discussion === | ||
''' | '''<mark>Learning Objective</mark>''' | ||
''Team members will collaboratively design and update their team’s NETwiki page to serve as a shared, accessible hub for operations, plans, and team information.'' | ''Team members will collaboratively design and update their team’s NETwiki page to serve as a shared, accessible hub for operations, plans, and team information.'' | ||
''''' | '''<mark>Supplemental Resources</mark>''' | ||
:[[Teams|Neighborhood Emergency Teams Directory<br />]] | |||
'''<mark>Preparation</mark>''' | |||
Encourage any team member who can to bring their own laptop so they can review the page; and/or, if possible, put the page up on a screen that everyone in the meeting can see. | Encourage any team member who can to bring their own laptop so they can review the page; and/or, if possible, put the page up on a screen that everyone in the meeting can see. | ||
''' | '''<mark>Facilitation</mark>''' | ||
Begin by projecting or sharing the team’s existing NETwiki page (or a blank one if it hasn’t been created). Explain that the wiki is intended to be a “living document” where the team records important details: operations plans, meeting schedules, contact protocols, and other resources that keep everyone aligned. Emphasize that it’s not just an archive, but a tool for both preparedness and active response. | Begin by projecting or sharing the team’s existing NETwiki page (or a blank one if it hasn’t been created). Explain that the wiki is intended to be a “living document” where the team records important details: operations plans, meeting schedules, contact protocols, and other resources that keep everyone aligned. Emphasize that it’s not just an archive, but a tool for both preparedness and active response. | ||
| Line 635: | Line 638: | ||
Encourage the team to treat the page as iterative: it doesn’t need to be perfect in one sitting. Reinforce that consistent use of the wiki will reduce confusion, help onboard new volunteers, and preserve institutional memory as team membership changes. | Encourage the team to treat the page as iterative: it doesn’t need to be perfect in one sitting. Reinforce that consistent use of the wiki will reduce confusion, help onboard new volunteers, and preserve institutional memory as team membership changes. | ||
''' | '''<mark>Debrief Questions</mark>''' | ||
*What information do we want future volunteers (or responders) to easily find on our team’s page? | *What information do we want future volunteers (or responders) to easily find on our team’s page? | ||
| Line 644: | Line 647: | ||
*How might we use this page during an actual activation or deployment? | *How might we use this page during an actual activation or deployment? | ||
'''<mark>Module Outputs</mark>''' | |||
<br> | <br> | ||
<hr> | <hr> | ||
