2023-2024 NET Program Changes - Revision history

Net@portlandoregon.gov: Blanked the page

2023-11-11T17:09:52Z

Blanked the page

← Older revision		Revision as of 10:09, 11 November 2023
Line 1:		Line 1:
	~~This page presents a proposal for realigning elements of PBEM's volunteer programming (which includes NETs, BEECN, and ATVs). '''The objectives of these changes would be to:'''~~

	* Address the fall-off of meeting attendance at routine NET Team Meetings;
	* Prepare PBEM volunteer programming to meet and weather through the many changes coming to the City of Portland's government structure and the structural changes taking place at PBEM;
	* Ensure programming is structured logically to meet the challenges of both climate change/extreme weather events, '''''and''''' the threat of a Cascadia Subduction Zone earthquake;
	* Encourage the growth and development of block-scale neighborhood teams.
	~~<br/>~~
	~~__TOC__~~
	~~<br/>~~

	The notion of '''''realignment''''' is important for this proposal. There is no intention to radically restructure PBEM volunteer programming. Instead, the intention is to better coordinate disparate parts of what we have and assemble them into a program that opens more doors to participating, from full NET volunteers to untrained neighbors.

	~~== Forces Driving Realignment ==~~

	~~=== Climate change ===~~
	[[File:NPR Climate Change.jpg\|alt=Actual photo of a PBEM intern before and after he found out Jeremy stole his lunch out of the fridge. Also, a fair illustration of climate extremes.\|thumb\|''Actual photo of a PBEM intern before and after he found out Jeremy stole his lunch out of the fridge. Also, a fair illustration of climate extremes.'']]
	Since NET's founding in 1994, the threat of a Cascadia Subduction Zone earthquake provided the urgency behind disaster preparedness and response programming. That threat remains. But a new fighter has entered the ring: extreme weather events caused by climate change. Extreme weather, such as heat domes and snow storms, have (and will continue to) take lives and result directly in more NET volunteers deployed for more hours.

Net@portlandoregon.gov: /* Forces Driving Realignment */

2023-11-09T21:51:29Z

Forces Driving Realignment

← Older revision		Revision as of 14:51, 9 November 2023
Line 14:		Line 14:

	=== Climate change ===		=== Climate change ===
			[[File:NPR Climate Change.jpg\|alt=Actual photo of a PBEM intern before and after he found out Jeremy stole his lunch out of the fridge. Also, a fair illustration of climate extremes.\|thumb\|''Actual photo of a PBEM intern before and after he found out Jeremy stole his lunch out of the fridge. Also, a fair illustration of climate extremes.'']]
			Since NET's founding in 1994, the threat of a Cascadia Subduction Zone earthquake provided the urgency behind disaster preparedness and response programming. That threat remains. But a new fighter has entered the ring: extreme weather events caused by climate change. Extreme weather, such as heat domes and snow storms, have (and will continue to) take lives and result directly in more NET volunteers deployed for more hours.

Net@portlandoregon.gov at 21:42, 9 November 2023

2023-11-09T21:42:47Z

← Older revision		Revision as of 14:42, 9 November 2023
Line 5:		Line 5:
	* Ensure programming is structured logically to meet the challenges of both climate change/extreme weather events, '''''and''''' the threat of a Cascadia Subduction Zone earthquake;		* Ensure programming is structured logically to meet the challenges of both climate change/extreme weather events, '''''and''''' the threat of a Cascadia Subduction Zone earthquake;
	* Encourage the growth and development of block-scale neighborhood teams.		* Encourage the growth and development of block-scale neighborhood teams.
			<br/>
			__TOC__
			<br/>

	The notion of '''''realignment''''' is important for this proposal. There is no intention to radically restructure PBEM volunteer programming. Instead, the intention is to better coordinate disparate parts of what we have and assemble them into a program that opens more doors to participating, from full NET volunteers to untrained neighbors.		The notion of '''''realignment''''' is important for this proposal. There is no intention to radically restructure PBEM volunteer programming. Instead, the intention is to better coordinate disparate parts of what we have and assemble them into a program that opens more doors to participating, from full NET volunteers to untrained neighbors.

Net@portlandoregon.gov at 21:42, 9 November 2023

2023-11-09T21:42:29Z

← Older revision	Revision as of 14:42, 9 November 2023
Line 1:	Line 1:
		This page presents a proposal for realigning elements of PBEM's volunteer programming (which includes NETs, BEECN, and ATVs). '''The objectives of these changes would be to:'''

		* Address the fall-off of meeting attendance at routine NET Team Meetings;
		* Prepare PBEM volunteer programming to meet and weather through the many changes coming to the City of Portland's government structure and the structural changes taking place at PBEM;
		* Ensure programming is structured logically to meet the challenges of both climate change/extreme weather events, '''''and''''' the threat of a Cascadia Subduction Zone earthquake;
		* Encourage the growth and development of block-scale neighborhood teams.

		The notion of '''''realignment''''' is important for this proposal. There is no intention to radically restructure PBEM volunteer programming. Instead, the intention is to better coordinate disparate parts of what we have and assemble them into a program that opens more doors to participating, from full NET volunteers to untrained neighbors.

		== Forces Driving Realignment ==

		=== Climate change ===

Net@portlandoregon.gov: Blanked the page

2023-11-09T01:46:43Z

Blanked the page

← Older revision		Revision as of 18:46, 8 November 2023
Line 1:		Line 1:

	<span style="background:#FFFF00; color:#FFFF00">.</span><span style="background:#FFFF00">'''THIS PAGE IS UNDER CONSTRUCTION AND NOT FINAL.'''</span><span style="background:#FFFF00; color:#FFFF00">.</span>

	~~Jeremy Van Keuren here.~~

	This is a "read ahead" page for NET volunteers and others reviewing proposed changes to the Portland NET program. A feedback survey link will be posted to this page after the presentation on November 8, 2023.

	~~==BACKGROUND: The case for making changes to the NET program==~~
	Both PBEM and the City of Portland are undergoing (and undertaking) the most sweeping bureaucratic changes seen in decades. This is resulting in reprioritizing and movement of resources, and that does impact NET programming directly. Expanding our view beyond City government and into the sociological, the COVID pandemic and climate change has made permanent changes to how we view disaster, resilience, and community organizing.
	~~<br/>~~
	~~<br/>~~
	~~=== People are accustomed to meeting and organizing on virtual platforms ===~~
	It's difficult to believe that before the pandemic, virtual meetings were still a relative novelty. Sure, we had Skype ([https://www.wired.co.uk/article/skype-coronavirus-pandemic remember them?]) but that was more often used to connect with your granny living thousands of miles away. Today, we're meeting over Zoom with people sitting literally in the next ''room''.

	From the NET community organizing perspective, there are both pros and cons to plan around. On the plus side, '''meeting online reduces obstacles to NET participation.''' Where a parent used to have to book childcare to take part in a NET meeting, now they can join online. Where someone who doesn't speak English fluently might feel self conscious requesting live interpretation, it's simpler for PBEM to detail a live interpreter to an online meeting. Where a less committed ATV might groan at the prospect of getting off the couch to go meet with neighbors, joining online may feel more palatable. And so on.

	~~There are a few problems as well:~~

	* There's an old saw that '''80% of communication is nonverbal.''' [https://www.psychologytoday.com/us/blog/beyond-words/201109/is-nonverbal-communication-a-numbers-game That may oversimplify thing a bit], but the notion is still relevant. Even if online communication doesn't deaden nonverbal communication [https://www.forbes.com/sites/forbescoachescouncil/2021/09/30/body-language-in-a-virtual-world-how-to-communicate-your-message-effectively/?sh=4308c9524964 it does stymie it]. Blotting nonverbal communication makes misunderstandings and misfired social behaviors more likely. <ref>No joke, just a couple weeks ago, I was in a neighborhood association hybrid meeting where everyone was being chill until one person ("Person A") at the table stood up and started angrily yelling at someone online and off camera ("Person B") because the latter participant's tone and meaning were completely misunderstood. Not only that, but I speculate Person A would not have expressed themselves so aggressively if Person B had been there in person.</ref>
	* '''AI bots are taking notes.''' Some of you may have noticed that folks are sending surrogate bots to take notes instead of arriving themselves. I think any reasonable person would agree that doesn't constitute "active participation". But it's better than not participating at all.
	* '''Virtual meetings make hands-on team training more challenging,''' though certainly not impossible.
	My position is that meeting online is not as good as meeting in person, but that online meetings are here to stay and teams should accommodate neighbors who need to use it. PBEM recommends that NET teams, team leaders, and PBEM address challenges:

	~~# '''PBEM should help develop best practices for NETs to do hybrid meetings.''' Hybrid meetings are still challenging, but they're getting easier.~~
	# '''PBEM encourages each team to get their own free Google Meet account.''' PBEM can no longer support a paid Zoom account for NET (though we are retaining a single Zoom account that NETs might use for exceptionally large, long, or complicated meetings).
	~~# '''NET Team Leaders should accept that not all volunteers (active NET/BEECN/ATV) will participate in person.''' But they can/should reasonably request occasional "all hands" in person meetings.~~
	~~# PBEM should work with NETs/FPN to '''develop team training/exercise curriculum that can work for online and hybrid audiences.'''~~
	~~<br/>~~

	~~=== The urgency of climate change resilience is supplanting earthquake resilience in Portland ===~~
	NET is an all-hazards response resource and responding to the threat of a CSZ earthquake will always be the standard PBEM wants to train NETs to. But an earthquake hasn't killed anyone in Oregon for at least three centuries. Meanwhile, extreme weather events in Oregon linked to climate change, such as the 2021 heat dome, have killed hundreds and contribute to ongoing health problems for many.

	NET doesn't need to "choose" between preparing for an earthquake and climate change resilience, so we won't. But, NET training and outreach should reflect and incorporate the threats posed by extreme weather events.

	* '''PBEM should offer a proportionally appropriate number of training events relevant to extreme weather event response and climate change resilience.''' This might include shelter response training, polishing training for heat illness response, outreach, and more.
	~~<br/>~~

	~~=== Neighborhood-based response teams exist for no other purpose than to respond to an earthquake ===~~
	''Every'' NET deployment since 1994 has been centralized through PBEM. PBEM sets the volunteer position descriptions, the shift schedules, and the NETs ultimately report to PBEM. The reason is that, per NET Guidelines, NETs will only self deploy if there is a citywide disaster '''''and''''' routine communication systems are disabled. In other words: an earthquake.<ref>Yeah ok, and the off chance of an [https://www.economist.com/the-world-if/2017/07/13/the-disaster-that-could-follow-from-a-flash-in-the-sky EMP]. But let's keep this simple.</ref>

	~~This realization opens a few other implications that help us organize our work:~~

	~~# Teams of NET volunteers exist really for only two divisible reasons: for local self deployment after an earthquake, and for socializing/training together.~~
	~~# NET "Operations Plans" are really "Earthquake Plans".~~
	~~# ATVs are a resource that NETs should recruit, but generally only as part of a Neighborhood Earthquake Plan.~~

	~~With all these implications in mind, I suggest the following changes:~~

	* Operations Plans now be called Neighborhood Earthquake Response Frameworks (NERFs...no, seriously)
	* Team service area boundaries for earthquake response, instead of conforming to neighborhood association boundaries, reflect the block scale areas a team decides on.
	* Developing a NERF:
	** Includes any interested NET volunteers, ATV, and neighbors inside a team service area;
	** PBEM develop curriculum to step teams through the arc of developing a NERF, to include initial community outreach/recruitment, progressive community involvement, response capacity analysis, and capacity planning.
	** PBEM develop an online system of reporting for every NERF/neighborhood team, taking into account their capacity planning, and providing a resilience score. This will give teams (and PBEM on a broader scale) quantifiable goals to meet.

	~~=== NET meeting numbers are generally low ===~~
	This was happening before COVID, but the pandemic certainly appeared to exacerbate the problem. Not all teams are in this situation, but many Team Leaders report low meeting turnouts. At the same time, PBEM fairly consistently sees high turnouts for deployments. So, we suspect the reason low meeting turnout is happening is not because volunteers are unengaged.

	~~<br /><br />~~

	~~==What are Jeremy's proposed solutions?==~~

	~~=== Phase 1 (what we're working on right now): ===~~

	# '''In progress:''' PBEM completes policies for [[Volunteer Statuses#Affiliated Trained Volunteers (ATVs)\|Affiliated Trained Volunteers (ATVs)]] so that Active NET volunteers have a clear option to move to ATV status if they wish.
	~~# '''In progress:''' Finish NET active membership audit (i.e. confirm which volunteers are meeting criteria for active status).~~
	~~# '''Not started:''' Send Team Leaders revised rosters after audit is complete.~~
	~~# '''In progress:''' PBEM completes GIS contract so that teams can [[Team Service Areas\|change/declare new service area boundaries]].~~
	~~# '''Not started:''' Change NET Guidelines to reflect a clear distinction between Centralized Deployments and Earthquake Deployments~~

	~~=== Phase 2 (a period of major change in NET, will take 3 - 6 months): ===~~

	# '''Not started:''' '''Develop NET Training Centers''' A NET Training Center is actually a person; a NET volunteer who holds training events (which they create on their own and/or draw from pre-made curriculum). My model for this is Mark Ginsberg, the TL in Woodstock. He periodically holds training events not just for Woodstock, but for anyone in a SE Portland team who would like to join.
	~~#* PBEM requests neighborhood NET Training Centers from the NET community.~~
	~~#* PBEM releases NET training schedule (including Basic NET).~~
	~~#* PBEM publishes directory of NET Training Centers.~~
	~~#* PBEM publishes citywide training calendar (either through MIP or through Smart Sheet, and through the Bulletin).~~
	~~#* PBEM works with FPN to publish training "recipes" to the Wiki.~~
	~~# '''Not started:''' '''Develop the NERFs'''~~
	~~#* PBEM/FPN work on development arc for block-scale NETs. Milestones will/may include:~~
	~~#** Service area boundaries~~
	~~#** Decide on radio frequencies~~
	~~#**Capacity assessment (which VSFs do you have already?)~~
	~~#**Capacity planning (which VSFs and how many)~~
	~~#**Neighborhood resilience scoring (not unlike BEECN scoring)~~
	~~#**Neighborhood outreach~~
	~~#***PBEM develops solid plans around curriculum)~~
	#***Many curriculum options, including the Community Resilience Workbook, PocketPrep, Speakers Bureau, [https://coolblock.org/ Cool Blocks], Map Your Neighborhood, Pearl District Curriculum, postcard drops/neighborhood block parties..
	~~#**Assembling a roster (which includes NETs, neighbors, ATVs)~~
	~~#* Block-scale NETs declare intent to have a NERF, submit their service area boundaries~~

	~~=== Phase 3 (long term projects/ongoing program maintenance): ===~~

	* Create a revised NET Task Book that Training Centers can use as a tool.
	* Emphasize development of most important VSFs: 02, 06, 08, 09, and 15.

	~~== Notes ==~~

Net@portlandoregon.gov: /* Phase 2 (a period of major change in NET, will take 3 - 6 months): */

2023-10-30T23:31:31Z

Phase 2 (a period of major change in NET, will take 3 - 6 months):

← Older revision		Revision as of 16:31, 30 October 2023
Line 83:		Line 83:
	#**Capacity assessment (which VSFs do you have already?)		#**Capacity assessment (which VSFs do you have already?)
	#**Capacity planning (which VSFs and how many)		#**Capacity planning (which VSFs and how many)
			#**Neighborhood resilience scoring (not unlike BEECN scoring)
	#**Neighborhood outreach		#**Neighborhood outreach
	#***PBEM develops solid plans around curriculum)		#***PBEM develops solid plans around curriculum)

Net@portlandoregon.gov: /* Phase 2 (a period of major change in NET, will take 3 - 6 months): */

2023-10-30T23:27:16Z

Phase 2 (a period of major change in NET, will take 3 - 6 months):

← Older revision		Revision as of 16:27, 30 October 2023
Line 81:		Line 81:
	#** Service area boundaries		#** Service area boundaries
	#** Decide on radio frequencies		#** Decide on radio frequencies
	#**Capacity assessment		#**Capacity assessment (which VSFs do you have already?)
	#**Capacity planning (which VSFs and how many)		#**Capacity planning (which VSFs and how many)
	#**Neighborhood outreach		#**Neighborhood outreach

Net@portlandoregon.gov: /* Phase 2 (a period of major change in NET, will take 3 - 6 months): */

2023-10-30T23:26:54Z

Phase 2 (a period of major change in NET, will take 3 - 6 months):

← Older revision		Revision as of 16:26, 30 October 2023
Line 71:		Line 71:
	=== Phase 2 (a period of major change in NET, will take 3 - 6 months): ===		=== Phase 2 (a period of major change in NET, will take 3 - 6 months): ===

	# '''Not started:''' '''Develop NET Training Centers'''		# '''Not started:''' '''Develop NET Training Centers''' A NET Training Center is actually a person; a NET volunteer who holds training events (which they create on their own and/or draw from pre-made curriculum). My model for this is Mark Ginsberg, the TL in Woodstock. He periodically holds training events not just for Woodstock, but for anyone in a SE Portland team who would like to join.
	#* PBEM requests neighborhood NET Training Centers from the NET community.		#* PBEM requests neighborhood NET Training Centers from the NET community.
	#* PBEM releases NET training schedule (including Basic NET).		#* PBEM releases NET training schedule (including Basic NET).
Line 91:		Line 91:
	=== Phase 3 (long term projects/ongoing program maintenance): ===		=== Phase 3 (long term projects/ongoing program maintenance): ===

	* Emphasize development of most important VSFs: 02, 06, 08, 09, and 15.		* Create a revised NET Task Book that Training Centers can use as a tool.
			* Emphasize development of most important VSFs: 02, 06, 08, 09, and 15.

	== Notes ==		== Notes ==

Net@portlandoregon.gov: /* Phase 2 (a period of major change in NET): */

2023-10-30T22:59:06Z

Phase 2 (a period of major change in NET):

@@ Line 69: / Line 69: @@
 # '''Not started:''' Change NET Guidelines to reflect a clear distinction between Centralized Deployments and Earthquake Deployments
-=== Phase 2 (a period of major change in NET): ===
+=== Phase 2 (a period of major change in NET, will take 3 - 6 months): ===
-# '''Not started:''' PBEM requests neighborhood Training Centers from the NET community.
+# '''Not started:''' '''Develop NET Training Centers'''
-# '''Not started:''' PBEM publishes list of NET trainers and requesting system.
+#* PBEM requests neighborhood NET Training Centers from the NET community.
-# '''Not started:''' Formally request Team Leaders submit their NERF Service Areas.
+#* PBEM releases NET training schedule (including Basic NET).
 === Phase 3 (long term projects/ongoing program maintenance): ===
 * Emphasize development of most important VSFs: 02, 06, 08, 09, and 15.
 == Notes ==

Net@portlandoregon.gov: /* What are Jeremy's proposed solutions? */

2023-10-30T22:27:18Z

What are Jeremy's proposed solutions?

← Older revision		Revision as of 15:27, 30 October 2023
Line 61:		Line 61:
	==What are Jeremy's proposed solutions?==		==What are Jeremy's proposed solutions?==

	=== Phase 1: ===		=== Phase 1 (what we're working on right now): ===

	* PBEM completes policies for [[Volunteer Statuses#Affiliated Trained Volunteers (ATVs)\|Affiliated Trained Volunteers (ATVs)]] x		# '''In progress:''' PBEM completes policies for [[Volunteer Statuses#Affiliated Trained Volunteers (ATVs)\|Affiliated Trained Volunteers (ATVs)]] so that Active NET volunteers have a clear option to move to ATV status if they wish.
			# '''In progress:''' Finish NET active membership audit (i.e. confirm which volunteers are meeting criteria for active status).
			# '''Not started:''' Send Team Leaders revised rosters after audit is complete.
			# '''In progress:''' PBEM completes GIS contract so that teams can [[Team Service Areas\|change/declare new service area boundaries]].
			# '''Not started:''' Change NET Guidelines to reflect a clear distinction between Centralized Deployments and Earthquake Deployments

			=== Phase 2 (a period of major change in NET): ===

			# '''Not started:''' PBEM requests neighborhood Training Centers from the NET community.
			# '''Not started:''' PBEM publishes list of NET trainers and requesting system.
			# '''Not started:''' Formally request Team Leaders submit their NERF Service Areas.

	~~In order, we propose~~:		=== Phase 3 (long term projects/ongoing program maintenance): ===

	#In the NET Guidelines, simplify and toss out the distinctions between "PBEM Initiated Deployments", "Self Deployments", and "Standing Orders". Replace with rules governing "Centralized Deployments" and "Earthquake Deployment".

			#
	#Dispense with the term "Operations Plans" and call them "Earthquake Plans" to reflect what the plan is actually for and to help put NETs in the mindset of forming a plan around earthquake response.		#Dispense with the term "Operations Plans" and call them "Earthquake Plans" to reflect what the plan is actually for and to help put NETs in the mindset of forming a plan around earthquake response.
	#Using GIS, allow Teams to decide on service area boundaries that reflect the [[Team Service Areas\|response area]] they want to/feel comfortable responding inside of after an earthquake.		#Using GIS, allow Teams to decide on service area boundaries that reflect the [[Team Service Areas\|response area]] they want to/feel comfortable responding inside of after an earthquake.