Flying drones in disaster zones

This post is from Rakesh and Pascal of Crisis Commons, who know WAY more about drones than I ever will. I tweaked a bit for flow and readability. They’ll be hosting a conversation soon amongst folks who are sharing airspace to figure out how to be good neighbors to each other – hit us up if you’d like to be a part of that at connect@crisiscommons.org and my first name at this blog’s domain. That conversation will apply to Milton as well as Helene. 

On Thursday, the FAA reported 30 “near misses” of crewed flights in the Helene disaster area in one 24 hour period. 

TL;DR for operating aircraft <400ft

  • Uncoordinated shared airspace, and its near misses, bring crewed aircraft delivering aid or performing rescues to the ground for the safety of the crew. Crewed aircraft ALWAYS takes precedence over drones both for human safety and for response needs.
  • Drone pilots are always legally responsible for understanding any relevant restrictions and airspace authorizations necessary.
  • Local authority doesn’t have ownership of the skies. A police officer cannot (usually) tell you not to fly. The FAA coordinates the sky, and you should follow their guidance as best you can for the safety of all.
  • Here’s how the FAA would like you to be operating in disaster zones. (H/T to jdg for finding this link)

It is not your god given right as an American to crash into a helicopter.

Continue reading

Dealing with Money in disaster response

Co-written with Devin Balkind. Much love to Drew Hornbein, Seamus Brugh, and Mark Ferlatte for their input on this piece. 

At some point, if you are visible enough, people will want to give your group money to do what you’re doing in responding to the crisis. 

Ideally, you will have been tracking who is putting money into the response so you can later pay them back if outside donations start coming in. Have a spreadsheet somewhere that folks can see (but not necessarily edit – see “data security”).

Some quick models that might work for you

If you want to be able to take tax deductible donations quickly, you can partner with a 501c3 in something called fiscal sponsorship where they take the donation and then pass it through to you after taking a small amount as administrative overhead (I’ve seen 10% most often). Some bureaucracy and you have to partner with an org that is values-aligned. You’ll want to take a look at a Memorandum of Understanding (MOU) to see how these partnerships are set up.

If you want to move fast and are expecting small amounts of donations, and don’t care about tax deductible donations, you can just open up a business bank account as a sole proprietor. There will be confusing tax implications later, someone in your group who has been an independent contractor will have insights. If you want more folks on the account it can get more complicated by needing to form a business or nonprofit (see below for when you have more time), but a local bank or credit union will want to help you figure it out. 

Framing conversations about dealing with money

Money often starts coming in AFTER you’ve already figured out what you’re doing and why. But people will start to see what you’re doing after you’ve been doing it, and want to support you in doing so. This means some of the tenor of your work will already be shifting as funds start coming in. You’ll be shifting from the response phase (getting people off of roofs and from under rubble) and into the recovery phase (getting people food and medicine, gutting houses, setting up warming shelters; longer term rebuilding housing, reestablishing businesses).

Continue reading

Self and Community Care in Crisis

With love to Kate Falkenhart for her additional kind contributions and course corrections to this post.

We’ve all heard about self care at this point, and probably even have our own routines. However, when crisis strikes, it can be tempting to throw out your adaptive routines in favor of all the pressing work that surrounds you. When this is the case, we must both model the behavior ourselves as well as instigating strong guidelines across the community, lest people burn out and hurt themselves (or others). 

I struggled to do this for myself and those around me during digital response campaigns earlier in the 2010s, saw better success as more coordinators came online and came up to speed around 2015, and saw the best example yet during Occupy Sandy response in 2012.

Bringing joy

Take time and space to notice the things that bring you joy, make you pause to pay attention, shake your preconceived notions, or inspire those around you? Laughter and joy are important things to experience during a crisis, even though it may feel inappropriate at the time. This is something we can give to one another: time to stop and experience.

Embed assumptions into everything else

Everyone is always jumping from topic to topic as priorities change during a response. As systems fall into place, people start making notes in their “space” – whether physical space (as pictured above), in onboarding docs, or as reminders present in digital communication. Self-care guidelines should be included in this, along with an explicit expectation that people support each other if someone is struggling to follow community care guidelines. They may already be facing internal shame for not modeling the behavior.

For example, rotation of duties is an excellent way to build resilience of responsibility in your community and to strengthen the overall system by knowledge sharing. Taking at least one day off a week is a necessary additional example. Both come at a cost – a maximum of 5 days in one’s speciality – but the overall benefit to the system is well worth it.

Lead by obeying

You cannot go all out indefinitely and your body, relationships, and work will suffer if you try to. If someone (including you) is unwilling to take care of themselves, there is likely either a codependent need to be valued that needs self reflection, or they may be more interested in being seen as heroic than in actually being effective or modeling care for others, and that should be avoided. Life will continue after the crisis, and you have to have things worth going back to, that hopefully you’ve been able to enjoy and maintain in the meantime.

Pushing power outwards

Look for people invested in the cultural context of the group you’re working in. They will foster the emotional safety that will allow you to take informed risks. Look for people who make space for others, and ask them to lead. Quiet, competent leaders are often overlooked in favor of those who are brasher. However, the quiet, competent people can also be the most skilled at delivering on group goals while also uplifting the group. 

Those folks can be quiet, though! And quiet people sometimes like quiet spaces. Having a “sacred” quiet space to go amongst the chaos of response can help people recenter themselves and find balance. It’s a good place to practice gratitude and pause to be strategic rather than reactionary.

Support your leaders, IE if a quiet, competent leader is also a single parent, find a way to get them child care support while they coordinate your group. Additionally, it is a full time job to support the frontline workers. Those support roles ALSO need support and can succumb to burnout.

Data security in crisis situations

Shout out to Baron Oldenburg and Eleanor Saitta for feedback on this post!

Information is flying around fast and loose as you try to help people in need. Anyone who has capacity to help has been added to a spreadsheet tracking needs. If you’re in the thick of it, this piece isn’t for you yet. But even in those moments, be careful about who you share sensitive data with – there are big ramifications later if you get it wrong.

But when you can come back and slow down a little bit to think about the longer-term ramifications of data, you should come back and investigate this. Because while getting people the immediate help they need as quickly as possible is more important than keeping their data safe, the long term impacts of a data leak could put people already in harm’s way further in harm’s way. Example: collecting immigration status when determining which shelters will work for which folk could open you up to a subpoena or backdoor that leaks the data.

So far, I don’t know of any data breaches from community-led crisis response, but it’s frankly a second disaster waiting to happen. People offer admin access to EVERYONE involved in order to feel equitable. People are then scared to remove admin access to things because they don’t want to upset anyone. This leaves a very large attack surface for something to go wrong even beyond the flaws of the tool itself. So limit how many administrators you have, and have a regular cadence to check in on who has access as an admin and otherwise. Set up an impersonal rubric to remove access (“hasn’t accessed this data in x days” or “we’ll only have 3 admins, and we talk monthly about who is best in those roles” are two examples). 

To limit the impact of a data breach, collecting ONLY necessary data is the best way to design. You don’t need to be collecting demographic data unless you’re running an equitability study later. Example: address and risk level shouldn’t be cross referenced unless absolutely vital. 

Do not use one shared login for vital or administrative accounts. Most tools worth their salt will allow you to have multiple accounts log in for the same view, so set people up with individual accounts so the account access can be managed. Any person with a shared login will be able to change it for everyone else. 

Retrofitting later is a pain, but is worth the pain. If you’re in a place where you can migrate to a new tool for a longer-term vision, I’d recommend mapping out tool options against group considerations. I do a grid with rows for technical options, and columns for things I care about. Things like longevity of data, alignment of the org with your group’s politics, who the data is visible to, if the data can be sold to external parties, relationship with law enforcement, etc. I then indicate how aligned with my goals each option is, and discuss the resulting grid with the rest of the tech team. Here’s an example grid for picking which messaging platform to use with each other:

If you’re able to turn on multifactor authentication (MFA), that’s another point where you can limit who the admins are. Doing this can slow some things down and be at odds with people being able to take the day off, but it’s another vector along which security can be tightened up as things slow down in the response. 

As an individual thing, Google Advanced Protection is worth turning on if you’re using Google tools. If you’ve got a workspace domain that’s being used in the response, all the admins should have it on, even if you’re just using people’s personal ad hoc accounts for most of the response work. We’re generally in favor of keeping data in Workspace even for many sensitive NGOs in complex situations because it keeps it off of individual devices and out of chats/email where it’s hard or impossible to purge, update, or track access. This of course presumes you have good connectivity, but so do most of these tools.

If you do have to have shared accounts for some things, using a password safe that gives you shared vaults can let folks log in without having direct access to the password if they’re willing to install the plugin — mostly for third party logistics or data feeds or whatever, not for the primary collaboration tools.

What else should folks be doing?

Spontaneous Unaffiliated Volunteers

Anytime there’s a crisis, there’s a flood of people showing up to help. They’re called “spontaneous unaffiliated volunteers” (SUVs) in crisis response circles, and they’re generally considered a chaos amplifier. They’re mostly seen as getting in the way, of being untrained and untasked, and often as not being willing to be trained or tasked.

And at the same time, the amount of work to be done is huge, and there are never enough hands. These folks have dropped everything in their lives because their hearts have been broken open, and they are here to help.

So how to manage this?

When people show up, they are either there to help, or there to “help.” They are either there to serve others, even if it means digging the latrine pit; or they are there to feel better about themselves. Discerning this early on in your intake flow is vital. One way I’ve seen to do this so far is to give someone a task that is not very important (but still engaging) and see what they do with it. If they deliver on it and ask for more, they’re good to go and you can give them more visible things. If they dawdle, take lots of selfies, and ask for other work; redirect them to things that keep them out of the way like sorting and keeping things tidy. They’ll usually phase themselves out.

What are other ways to discern between these groups?

Arc of disaster response

There’s this standard graph of needs versus resources that emergency managers use.

A chart with two lines. X axis is time, Y axis is level. A red line indicates need, which starts flat, then quickly rises and then slowly dips before restabilizing. A blue line indicates resources, and also starts off steady but dips quickly after a crisis point. It rises until it is over the dipping need line, then restabilizes alongside the need line.

It indicates that needs for an area are usually pretty steady, but when a disaster strikes, needs rise. Needs rise because some resources are destroyed and because people are distressed and injured (needing more resources than usual). 

It also indicates that access to resources diminishes but then sees a huge surge in delivery, which then falls off. Access to resources fall when the infrastructure to maintain (like refrigerators) and gain (like a grocery store) might be out of commission, but then rise as external resources flow into the area, and then level off again as infrastructure is regained and external attention wanes. 

This is also aligned with what I’m theorizing is the arc of engagement. In this, frontline populations (hey that’s you!) are ALWAYS the first to respond. As official response comes in, frontline populations can take a bit of a breather, but then step up again for the transition from official response to the new normal. 

This also leads to some tensions – official response, while well practiced and educated in how to do response in general, do NOT know about the specifics of your region or your community’s needs. There are some time periods where you will need to show up and advocate for your unique situation, even if people providing you much needed resources struggle to listen. We are writing them a guide in HOW to listen, but YMMV. 

The place you come in best while official responders are here are in last mile logistics and data. They will be deploying to large parking lots and trying to get people to go there to pick up resources and detail damage. You can gather that information from your at risk neighbors and coordinate with all your neighbors about which resources to prioritize, then bring that to the official responders.

Calling artists and authors to help with a response zine!

As some of you know, I have cared about crisis response for a long time. And now, as a side project, as furthered recently at my birthday conference, I’m working on a guide for the formal sector to interact with the informal. I’m also starting work on a zine for informal groups to know what’s up in times of crisis. The informal groups are harder to reach as you don’t know who they are in advance, and so our goal is to make this zine something the formal sector is willing to hand off, something that is findable online, and something that activist groups might seek out themselves in advance.

I’m really excited about it, but it’s also a LOT of work. And I’m not the only person with writing or artistry skills out there, so I’d like to use this as an opportunity to commission some work. There’s a form at the bottom of this blog post to sign up for a section if you’re interested. What follows immediately are short write-ups of areas I think need better words and/or a piece of art to express.

Basics of response

Reviewing in an informal way things about WASH and food safety, plus common sense for physical safety for collapsed buildings (unit 7) etc. Slow is smooth and smooth is fast, it’s worth moving carefully. Would require some independent research to figure out what is being detailed by official sources.

Data safety

You’ll be setting up some basic things immediately – a place to chat (mailing list, Signal group, etc) and a place to store information (wiki, Google Drive, etc). When a crisis first kicks off, data is gathered fast and loose, and access is given to anyone who might be able to help. That is expected and we get it. However, after time wears on and things stabilize a bit, some thought needs to be given to data retention and security, including who has access to what.

Limit how many administrators you have. Use secure-enough tools, limit who has access, send over encrypted channels. Retrofitting is a pain, but is worth the pain. Do your best in the moment, without sacrificing efficacy.

This would be a conversation we have to flesh out details you might be interested in and to highlight what I think is important and reasonable here.

Sustainability & leadership

At odds with a do-acracy, it makes more sense to select each other for leadership positions. Be wary of narcissism, usually indicated by someone wanting full ownership of something. Quiet, competent leaders are great in American cultures. This is something for conversation if you don’t already have a background here.

Self and community care

Support your leaders, IE if they’re a single parent, get them child care support while they coordinate. Taking at least one day off a week is necessary. You cannot go all out indefinitely, and your work will suffer if you try to. Rotation of duties is an excellent way to build resilience of responsibility in your community and to strengthen things by knowledge sharing. Feeding the group is important work. Etc. This would be great for someone passionate about governance structures and self care. Happy to have conversations about this and the sub topics to deepen the thinking here, but if you’re already familiar with self organizing structures, you’ll have a great start.

Documentation

Documentation often seems like the BIGGEST waste of time, but it is SO important. It will help you with handoff to other people (sustainability), it will help you communicate and coordinate with other groups (impact), and it will help you tell your story later (learning). Share outward as much and as often as you can handle, it will help everyone, and they in turn can help you.

A documentarian can be see as an apprentice to a role, writing down what they’ll do as they learn about it. This builds resilience in your group in multiple ways.

Happy to have a conversation about this one, but if you already love libraries and/or wikis, you’re probably set here.

Dealing with money

Eventually, someone will probably want to give you money, or you’ll start running into ways that you’d like to get money to spend on certain things rather than always coordinating material goods directly. Some groups, like Occupy Sandy, just estimate that they’d like 10% to fraud and that it would cost 15% in overhead to track, and so just gave away cash to projects based on donations flowing in. Other groups, like Humanitarian OpenStreetMap Team, ended up forming a 501c3 so they could better accept funds to pay for people’s airline tickets. Each comes with risks and benefits. This would be a conversation with me and some other folks to get you set up on models and information.

Failure modes

Formalizing your group in different ways (often done to deal with the money problem) leads to different types of failure. People who form businesses (disaster capitalism) usually end up failing as a business because they thought their one-off crisis lessons applied everywhere else. Right-wing response groups over optimize for centralizing power, especially when things are going sideways, which leads to bits of the group breaking off to do their own things. Leftist response groups fail to build consensus around the next actions to take and dissolve. A conversation can be had here.

Some tips for interacting successfully with the formal sector

Like it or not, the formal sector is probably going to show up at some point and try to deploy to your area. Here are things to know about how they work and what they expect that can help everything run more smoothly. I’d write the intro to this section, but the subsections can all be conversations if they’re not clear enough already.

Have a person the formal sector can talk to

A broker liaison could be someone who has done CERT training or that otherwise has worked within a command structure before. They should be open to understanding where the formal groups are coming from, but firm in what will and won’t be accepted by the community. They will need to be available for lots of informational meetings. This is how the formal sector thinks of these folks. If someone wants to prepare for this in advance, FEMA’s independent study is great.

Flying drones

Drones are a really great way of checking out your area to see what is going on. However, if any planes are up in the air, the drones have to come down. Low flying planes are used to take photography for damage assessments to see where resources should be sent, as well as being used occasionally to deliver supplies, so they’re an important part of response and shouldn’t be interfered with (unless you’re in an adversarial environment).

Rule of thumb

If there is a SERIOUS safety issue, like a hazardous spill, if you cannot cover the entire area from view while holding up your thumb, you are too close.

Where and how your formal sector colleagues can talk with you

Formal entities can (and should!) be held accountable for decisions they make and actions they take. This means all communication has to be audit-able, which means they can’t talk to you on something like Signal. Their systems are also often locked down so they can’t install the latest and greatest new collaboration tool. Being willing to join them where they’re at (if they can get you an account) and/or to find new third places is a key component to opening up communication.

Interested in helping out?

Interested? Here’s a form to fill out to indicate interest! I’d love to see responses in by July 22nd. When estimating, please be kind to yourself, but while I’m making Bay Area money (NOT software engineer money), I also have a kid and stuff. I have worked as a contracting artist before and will limit myself to 2 revision rounds on each thing. You will absolutely be credited in the zine. You’re welcome to reach out to willow dot be el zero zero at gmail if you have any questions or want to see how progress is going.

Formal/Informal Crisis Response birthday party

A couple weeks ago was my 40th birthday. And as you may know, I occasionally throw conferences for my birthday party (CatCon in 2013 & 2016, Animal Talks in 2020, and governance structures in 2022). This year I did the same, focusing an intimate group on the interface between formal and informal groups in crisis response. You know, my jam

I was graced with the presence of John Crowley, Liz Barry, Joseph Pred, Evan Twarog, Suzanne Frew, and Schuyler Erle. I will forever be so grateful to these folks for showing up to share their brains and hearts on this topic. 

Continue reading

An Open Letter From Civic Hackers to Puerto Rico & USVI in the Wake of Hurricane Maria

We are a group of civic developers committed to supporting Hurricane victims for relief & recovery who have helped with the software development and data analysis of Hurricane Harvey and Hurricane Irma primarily in Texas and Florida. In the wake of Hurricane Maria, we want to help Puerto Rico and the U.S. Virgin Islands in the same way. Devastation has already occurred in Puerto Rico and the USVI, and we’re here to help in the response and recovery pending from Maria.

But, we won’t jump in without your permission. These places have a long history of imperialism, and we refuse to add tech colonialism on top of that.

Here’s how we might be able to help:

Rescue

Sometimes emergency services are overloaded fielding calls and deploying assistance. Remote grassroots groups help take in additional requests through social media and apps like Zello and then help to dispatch local people who are offering to perform rescue services (like the Cajun Navy in Houston after Hurricane Harvey).

Shelter updates

As people seek shelter while communication infrastructure remains spotty, having a way to text or call to findt the nearest shelter accepting people becomes useful. We can remotely keep track of what shelters are open and accepting people by calling them and scraping websites, along with extra information such as if they accept pets and if they check identification.

Needs matching

As people settle into shelters or return to their homes, they start needing things like first aid supplies and building materials. Shelter managers or community leaders seek ways to pair those offering material support with those in need of the support. We help with the technology and data related to taking and fulfilling these requests, although we don’t fulfill the requests directly ourselves.

If you are interested in this, please let us know by emailing me (willow dot bl00 at gmail) or finding us on Twitter at @irmaresponse and @sketchcityhou.

Here are other groups lending aid already (maintained by someone else).
If you’re looking to jump in an an existing task, Humanitarian OpenStreetMap Team already has a tasker active for helping to map the area for responders and coordination.

Humanitarian Technology Festival

I came on with Aspiration back in January as the Community Leadership Strategist, to merge the work I’ve been doing in the humanitarian and disaster response space with Aspiration’s practices and team. It’s been a *blast* so far, and continues to be.

Most of the work I’ve done in the last 5 years has been about what social justice looks like when we’re doing response, with a focus on technology (as that opens up paths to conversations we otherwise quit having). With Geeks Without Bounds, we did hackathons all over the world, including Random Hacks of Kindness and SpaceApps Challenge. I’ve been a coordinator for the Digital Humanitarian Network, keynoted the IEEE Global Humanitarian Technology Conference, was invited to the White House to talk about Sandy response, facilitated the first hackathon IN (not just for) Haiti, etc etc etc. I’ve also had a huge organizational crush on Aspiration since my first DevSummit in 2013, attending as many Aspiration-connected events as possible. When I was able to join Team Aspiration, I was overjoyed — even while much of the work I’ve continued to do on response had already existed, it’s been a slow shift to get those previously-defined objects to be a bit more Aspiraiton-shaped.

The Humanitarian Technology Festival in Cambridge May 9+10 is the first event that is both committed to response and framed on Aspiration ethos. I am SO EXCITED about this it hurts. Let me explain why.

The very way we deliver aid perpetuates the need for more aid, both for fast- and slow-onset disasters (or “extreme events” or “humanitarian issues” or “earthquake” or “famines” or whatever you’d like to say). When people need lodging after a hurricane, they’re either told to evacuate and/or they’re put into temporary homes, away from neighbors and family. There is little impetus to return and rebuild both social and tangible structures. People are uprooted, and must start from scratch. When, instead, we see that people don’t just need lodging but in fact need social fabric, responders (and the technologies used for response) can focus on how to maintain family and neighborhood ties. People are then less stressed as well as being more likely to take their own actions to return and rebuild.

For humanitarian aid, this is even more paternalistic and stratifying… while not actually “fixing” any of the things it aims to. Aid is primarily about making the giver feel better. But like Tom’s Shoes picking up on the “buy one, give one” idea that OLPC actually handled with cultural grace and systems thinking, instead Tom’s put some people out of work while trying to provide something THEY thought others needed. Even if it had been delivered in a less-jerky way, aid often ends up with locations dependant on that aid, rather than internally strengthened. This is one way we keep extracting resources out of other places without actually contributing to those locations. See also this bit of the paper I’m still working on. This allows the worst parts of globalization (erasure of cultures, consolodation of wealth, etc) to continue.

Some might say “fine, let them fend for themselves,” but that’s not ok either. When we don’t have to look at our neighbors (when we build walled housing complexes, or segregated schools), we can ignore how bad things are for them. And that’s also not an acceptable answer.

What we need are ways to listen to what people can offer, and what they need, under the assumptions that we are equals. This is why I’m so excited to see how the participatory methods I associate so strongly with Aspiration come to bear on this space. Just do a search-and-replace for “Nonprofits” to “Affected Communities” on our Manifesto and Participant Guidelines. People in these fragile situations are NOT a population to playtest new tools. Not only do failures have a larger impact in these spaces, but to think of another location and its people as “demo” space is undignified and unjust. We need better ways (not just better tools) for life EVERYWHERE, and to assume that we WEIRD (Western Educated Industrialized Rich Democratic)-o’s have all the answers is downright arrogant. By instead, as we do at Aspiration events, speaking to each other in easy-to-understand language, under the assumption that everyone is bringing something meaningful to the table, and that together we’ll figure it out; we can shift not only how we do response, but the after-effects of that response.

I’m especially excited to speak to people about distributed response, and how the tools we build for ourselves can be welcoming to others using as well. Check out NYCprepared and Taarifa to see what this can look like.