Team Development Arcs: Difference between revisions
From Portland NET Wiki
| Line 509: | Line 509: | ||
=== Operations Plan Check-In === | === Operations Plan Check-In === | ||
Learning Objective: | |||
Team members will review, update, and reaffirm their Team Operations Plan to ensure clarity on meeting locations, communication protocols, risks, and resources. | |||
Facilitation Guide: | |||
Begin by explaining that the Team Operations Plan (Ops Plan) is the foundation of a NET team’s readiness. It outlines where the team will gather, how they’ll communicate, and what they’ll focus on first after a disaster. Stress that reviewing it regularly is critical—neighborhood risks change, team membership changes, and communication systems evolve. | |||
Facilitation steps: | |||
Bring the Plan: Have a copy of the current Team Ops Plan available (printed or on a shared screen). If your team does not yet have one, frame this activity as the first step toward drafting it. | |||
Walk Through Key Sections: Guide the group through the major parts of the Ops Plan: | |||
Assembly Location: Where will the team meet after an earthquake? Do multiple members know the location? Is it still viable (accessible, safe)? | |||
Communication: How will team members check in with each other (radios, call/text tree, BEECN), and how will they relay info to PBEM or the City? | |||
Neighborhood Risks: What are the top hazards (URM buildings, bridges, hazardous materials sites, wildfire smoke, etc.)? Do these still feel accurate? | |||
Resources: What local facilities, organizations, or caches could support response? Are there new ones to add? | |||
Check for Gaps: Ask whether any section feels unclear, outdated, or missing. Encourage members to share observations (e.g., “That assembly location is under construction now” or “Our comms tree is missing three new volunteers”). | |||
Assign Updates: Identify who will update the plan, how changes will be documented, and where the latest version will be stored (e.g., NETwiki, shared drive). | |||
Remind the group that the Ops Plan is living: the goal is not perfection in one meeting, but continuous improvement. Encourage a cadence for reviewing it—perhaps once a year or after major exercises. | |||
Debrief Questions: | |||
What parts of our Ops Plan feel clear and reliable? | |||
What parts need updating (locations, contacts, risks, resources)? | |||
How confident do we feel that new volunteers could follow this plan in a disaster? | |||
Who will take responsibility for making edits and ensuring the updated version is shared? | |||
=== Local Business Outreach === | === Local Business Outreach === | ||
