Where does community organizing end and civic tech begin?

Earlier this month, we gathered 30 community technology practitioners from around the country together for a convening about the Experimental Modes of Civic Engagement in Civic Tech. Over the course of a day, we dug into big questions about civic tech conceptually (and whether and how and when it actually fits the work that we do), how to document our work for ourselves and others, and the strategies we use to do what we do.

You can see full documentation of our meeting and conversation here.

At the end of the day, we took time to reflect on our discussion. Below, I’ve rounded up excerpts from the group’s final thoughts and organized them by theme.

Major Takeaways

Language

The words that we use to describe our work. “Civic tech” is a new term that, while literally descriptive of the work of the practitioners we brought together, doesn’t always resonate with these practitioners or the communities they work with. (See more here.) We talked in detail about how the interest in this new idea was destructive…as well as how it could provide opportunity.

Greta Byrum: “Think about words like “disruption”: it captures the interest in short term impact, but it has this problem of not speaking to the long term of real social change and transformation, and it changes our understanding of what work does.

Civic tech is the hot new thing. Can we use it in a way that’s useful? Can we use it to fuel the work we do? Or will this term undermine the work that we do?”

SHAPING THE NARRATIVE AND THE PRACTICE

Storytelling. Much of our afternoon was focused on questions about documentation: where and how we collect our work and share our models.

Dan O’Neil: “We’re in a sliver of a sliver in the tech space. We need to move from glorifying the anecdotes, the stories we tell to get funding, to sharing the modes and methods and the ways that we do that. That’s how revolutions happen, when people share their understandings, when people come together and share with each other the exact ways that we do things.”

Adam Horowitz: “Where are the stories about the innovations I’ve heard about today told and how they can be told bigger? We read about Uber in the paper, not about community tech. What’s the role of storytellers in making this work more noticeable?”

Maegan Ortiz:“I’m thinking about how this tech space was created: who was in the mind of the folks who created it and who wasn’t, and how, by using community organizing models, we can either replicate that or we can use it and imagine it and push it to be something different that may even disrupt, interrupt the original vision.”

Community Organizing

More than their use and creation of community technologies, what united the people in the room was their focus on community organizing. What is a collaborative process to make tech if not the collective, organized effort of a group of people looking to make their lives better?

Demond Drummer: “I’m a tech organizer. I’ve always had a problem with the distinction between organizing and tech. But from this conversation today, particularly with Maegan (Ortiz), I’ve come to own and better understand the deliberate, conscious, purposeful use of the “tech organizer” as a tool and a field of play where power itself is contested.”

Diana Nucera: “It’s clear from this gathering of community organizers that we’re in a time where community organizing extremely important in government. So the question is, how do we get government to adopt community organizing? It’s always been clear that government should adopt community organizing, but it’s now clear there’s a need for it. The use of technology has revealed that need. As we go forward from here, I hope we stay true to community organizing practices.”

Earlier in the day, we talked “ingredients for engagement”: what qualities an organizer instills to not only get people in the door, when it comes time to work together, but to keep them there, make them feel comfortable, and enable an environment where people as individuals and together as a collective can share power and take action. The practices and ideas that came up over and over included  “invitation”, “permission”, “comfort”, and “active listening”.

On comfort:

Sabrina Raaf: “I keep thinking about how Chicago has this interesting history in the art world of walk-ups and basement galleries traditionally called ‘uncomfortable spaces’. I’m struck by the conversations we had today about ‘comfort,’ and hoping hoping for new tradition of ‘comfortable spaces’.”

On tension:

Allan Gomez: “It’s important to remember the default settings. The status quo. The default ends up being such an inertia-creating force, it’s difficult to change. So I want to semantically challenge the idea of “comfort” because tension needs to be created to change the default. If we’re looking for real innovation, we need to look for examples grounded in people’s lives from all over the world. Language of reclamation. And we need to reflect on how we want to use this tech versus how this tech forces us to behave.”

Bringing the focus into the immediate presence, Tiana Epps-Johnson reflect that even our work in the room that day was an impression of the comfort/tension dynamic:

Tiana Epps-Johnson: “Comfort in spaces has a lot to do with the people in the room. It’s refreshing that a conversation about civic tech is not dominated by white men, and it’s not a coincidence that the people who think about community reflect that.”

Experimental Modes convening attendees looking serious. Photo by DXO.

Experimental Modes convening attendees looking serious. Photo by DXO.

Expanding on this idea, we discussed that much of our conversation from the day would have been the same if we called it a “community organizers” convening instead of a “community tech” convening, but the people who chose to come (and opt out) would have changed.

Marisa Jahn: “One of the things that struck me about the different people in the room today is that everyone identifies as a something and something else. Multiple identities. I also have a varied background between advocacy and tech and arts stuff. It’s always seemed ad hoc: I used to do things because they interested me or because I wanted to learn or to help people.

Now I’m thinking about how the way people arrive at tech is through relationships, through connections that validating all the ampersands, all the hats that people wear, all the paths taken.”

Many of the Experimental Modes are focused on relationships. Relationships are community fuel and sinew. They are the foundation upon which all community collaboration — tech related or not — is built. Without understanding how social ties work and without investing energy in creating strong, genuine social ties, truly collaborative projects are impossible.

Whitney May, exploring this idea in her own work with local election officials, came up with a formula based on the “ingredients for engagement” discussion earlier in the day:

Information + Invitation = Participation.

Whitney May: “Local government really struggles with reaching out to people, with invitation. And so do we. Our project focuses so much on information, but we need to do more inviting.

Technology as its best is a way that expands_____. Insert what you will here. For tech to expand community organizing and access to civic information, for me, if I distill that down, it’s actually just participation. So how can we use tech to expand participation?”

We do more inviting.

Jenn Brandel: “Information + Invitation = Participation. Thinking about this at a metal level, before I was invited into this conversation about civic tech, I didn’t realized I belonged here — or in community organizing. Now I feel like I’m part of something far bigger than I realized.”

Real-world Civic Tech Strategies

At the Experimental Modes convening, practitioners from all over civic tech to came together to discuss, in their own words, how they do what they do. You can see our full meeting notes here. We tore into this subject, looking at how we relate to civic tech explicitly, the general tools we use in our work, and the strategies & tactics we wield.

The case study sprint, a documentation project inspired by booksprints, is one way we’re continuing to capture this information and open the door to people who couldn’t be in the room with us. On site, we also conducted an active listening exercise to bust the language barriers of our professional and personal backgrounds and explore ways to explain our work to new audiences.

As part of this exercise, which you can try for yourself here, we reviewed the 5 Modes of Civic Engagement in Civic Tech, which I created based on my own analysis of these and other practitioners’ work, and dug into the similarities and differences in the strategies we use.

Below is results of our share-out, taken from our meeting notes. Each pair reflected back to the group on what techniques were present in both their projects or what made finding commonalities difficult.  Taken together, this forms a picture of the lack of one-size-fits-all in civic tech.

The comments have been slightly edited for formatting and clarity and annotated, when appropriate, with corresponding Modes of Civic Engagement in Civic Tech for further reading. You can read the raw meeting notes of the share-out here.

Stef Milovic of the Hidden Valley Nature Lab and Naheem Morris of the Red Hook Digital Stewards program discuss strategy at the Experimental Modes Convening. April 4, 2105. Photo by Dan O'Neil.

Stef Milovic of the Hidden Valley Nature Lab and Naheem Morris of the Red Hook Digital Stewards program discuss strategy at the Experimental Modes Convening. April 4, 2105. Photo by Daniel X. O’Neil.

Strategy Share-out

Marisa Jahn (of the The NannyVan App) and Tiana Epps-Johnson (of ELECTricity)

Anca Matioc (of AbreLatAm) and Josh Kalov (of Smart Chicago Collaborative)

Laura Walker McDonald (of SIMLab) and Geoff Hing (of Chicago Tribune)

  • Didn’t have commonalities. Work is done at very different orientations. Geoff’s work as a code writer VS Laura’s work coordinating stakeholders around technology
  • Geoff drew images to show the tangle of networks each works in (see below), and they both found the people left out of that tangle tend to be the community (the people you’re serving): they are not necessarily the people who are raising the funds and having to produce “outcomes” or the bottom line

Robert Smith (of Red Hook Digital Stewards) and Sanjay Jolly (of The Prometheus Radio Project)

Jennifer Brandel (of Curious Nation) and Danielle Coates-Connor (of GoBoston2030)

Demond Drummer (of Large Lots Program) and Maegan Ortiz (of Mobile Voices)

Asiaha Butler (of Large Lots Program) and Allan Gomez (of The Prometheus Radio Project)

Sabrina Raaf (of University of Illinois at Chicago) and Sonja Marziano (of CUTGroup/Smart Chicago Collaborative)

Maritza Bandera (of On The Table)  / Whitney May (of ELECTricity)

Adam Horowitz (of US Department of Arts & Culture) and Diana Nucera (of Allied Media Projects)

Show Your Work: Submit a Civic Tech Case Study

Through the Experimental Modes project, I’ve been researching and analyzing methods for community-controlled civic tech. These “modes” of civic engagement in civic tech were distilled through a process of evaluation, research, and interviews.

Now, we’re inviting you to tell your own story as part of our Civic Tech Case Study Sprint. This documentation project (inspired by bookprints and Beautiful Trouble) was set in motion at our practitioner convening last Saturday.

In the afternoon, I led an exercise on storytelling and documentation. After presenting on the 5 Modes of Civic Engagement in Civic Tech, we discussed additional strategies and tactics used in our work. We also discussed this sprint and what we, as practitioners, would like to see in documentation of our work, and adjusted the form based on based on this feedback.

Digging into documentation and civic tech at the Experimental Modes Convening on April 4, 2015.

Digging into documentation and civic tech at the Experimental Modes Convening on April 4, 2015.

The case studies produced as part of this exercise will be published on the Smart Chicago website and will be spread as far and wide as we can. To contribute to the sprint, all you have to do is fill out this form. We are open to examples from within the United States as well as abroad and don’t care whether the examples are 10 years or 10 minutes old.

After completing your DIY Case Study, you will get a copy of your submission immediately by email. Everything Smart Chicago publishes is Creative Commons 4.0.

Once we have all of the case studies in from everyone who attended our convening, I will compile of the responses into a document that reviews quantitative info (number of times a particular mode was used, prevalence of specific tactics, etc.) along with an analysis of trends & insights from your narratives. (The Smart Chicago CUTGroup Final Reports are good examples of this type of analysis.)

Submit your case study before Sunday, April 19, 2015 to be included in this report. All of these outputs, including the raw form data (example) will be housed shared on the Experimental Modes project page, where we’ll also post and link to the case studies as individual PDFs.

Questions? Comments? . Otherwise, get cracking!

Primer for Experimental Modes Meeting

Here at Smart Chicago, we’ve always had three areas of focus:

  • Access to technology and the internet
  • Digital skills for all
  • Meaningful products from data

This focus keeps us on the right path— one that requires us to lay practical groundwork before delivering cool apps— to put people first. We’ve done this since day one.

On a personal note, I’ve been a worker in community technology for a long time. I love it. In the early 2000s, I started a side business to help people get an internet life. I learned that nearly no one goes beyond default configurations, or even knows they can.

Internet Life Services

In 2004, I conducted bilingual computer training at my church to teach people how to post to our blog. I learned that everyone has a thirst to express themselves.

Bilingual computer training

In 2006, I taught a 6-week course in websites for small businesses. I learned that people love certificates.

Websites for small businesses

I’ve also been a part of a parallel path, which started taking off right about this time: the open data and civic tech movements. As a co-founder of EveryBlock, one of the earliest examples of a site that sought to use civic data in communities, I helped shape and build things like the 8 Principles of Open Government Data and  Open Gov Chicago, a gathering of technologists in the field started in 2009.

EveryBlock Launch Screenshot

We like to think these worlds— those of community technology, grounded in the needs of the people, and civic technology, driven by the most technical people, are aligned. When we’re at our best, they are. Very often, however, they are worlds apart.

This is why Smart Chicago exists. Our mission, grounded in our areas of focus, situated directly in the community (as we work here at the region’s community foundation), based in community technology research (lead by the MacArthur Foundation), and fully engaged with the governments and institutions that serve the people (including the City of Chicago, one of our founders)—this is us. This is why we’re here today.

We designed this project to fit under a larger area of work that Smart Chicago: the Knight Community Information Challenge grant awarded under their Engaged Communities strategy to the Chicago Community Trust “as it builds on its successful Smart Chicago Project, which is taking open government resources directly into neighborhoods through a variety of civic-minded apps”.

Materials for today:

  • Here’s all of the research and synthesis that led us to this meeting in one handy PDF.
  • Here’s live meeting notes— follow along starting at 9AM Saturday, April 4, Central time.
  • Here’s the form we’ll be using in our Case Study Sprint: https://smartchicago2012.wufoo.com/forms/diy-case-study-civic-engagement-in-civic-tech. Fill it out!

There is no other organization in the country that is more qualified to lead this thinking. I am proud of where we are, and steeled for the work ahead.

Mode #5: Distribute Power

This is the final piece in a five-part series exploring how to develop civic technology with, not for communities. Each entry in this series reviews a different strategy (“mode”) of civic engagement in civic tech along with common tactics for implementation that have been effectively utilized in the field by a variety of practitioners. The modes were identified based on research I conducted with Smart Chicago as part of the Knight Community Information Challenge. You can read more about the criteria used and review all of the 5 modes identified here.

MODE: Distribute Power

The art of leading a collaborative process is the art of getting out of the way. You can follow best practices — building your work through public commons, rooting your projects in the existing social and technical practices of a community, and teaching new technical skills while listening — but if you can’t get out of the way, you can’t run a community-driven development process.

Getting out of the way means sharing project control with the group. Below are four essential tactics for sharing and releasing power that have been applied in the creation of civic technology:

Treat Volunteers as Members

Another title for this tactic could be: value your participants equally. Put everyone on the same level. No matter their status — whether or not a person contributes once to project or 50 times, whether they lead a process or follow along, whether they’re paid staff or high school students — treat the folks who participate in your project as equals, and use titles for participants that make this status explicitly.

  • Facebook journalism outlet, Jersey Shore Hurricane News, considers anyone who submits a photo, an event, a story, or a tip to be a “contributor.”
  • Although technically a non-profit, Public Lab, the DIY citizen science group, identifies all participants (folks who contribute to the listservs, wiki, in-person events around the world, etc) as part of Public Lab itself (see the org chart below) and has created structures (like working groups) for community input on decision-making.
  • Free Geek is a non-profit works with communities to transform old technology into new electronics made available to those in need. Free Geek runs on human power and uses community service as a currency. However, it makes little distinction between roles as all are essential. So, whether you’re learning how to refurbish technology, building computers in the shop, teaching a class, sorting donations, or helping to keep the facility clean, you’re a “volunteer” and you are essential.
Public Lab's organizational chart demonstrates how to include a variety of participants with equitable footing.

Public Lab’s organizational chart demonstrates how to include a variety of participants with equitable footing.

This is a foot-in-the-door technique to build trust and a way of demonstrating that any contributions a person offers as part of the co-development process will be valued — an important message to send if you want actually want a diverse group of community members to feel invested and free to drive a project.

Teach Students to Become Teachers

Handing off control and treating people as equals doesn’t mean removing structure or leadership. Projects that sustain community development are those that enable participants to expand their skills and responsibilities as they’re interested in doing so, with specific tracks for leadership that are accessible to everyone from the onset.

  • As noted above, by default, all participants in Public Lab are identified as part of Public Lab. But for those participants who are interested or active in coordinating projects or contributing to the Lab at a different scale (from helping with communications to moderating community discussion lists), Public Lab has an open call for community leaders called “organizers” which anyone can join.
  • Digital Stewards programs often enable graduates to mentor, if not fully teach, the next group of stewards, further developing the technical skills individuals pick-up from the program and deepening the communal history and relationship with the wireless networks the stewards oversee.
  • Mobile Voices (or VozMob) is a content and technology creation platform built for, by, and with immigrant and low-wage workers in Los Angeles. VozMob has a few mechanisms for individual and group-level leadership, including a tier of “Affiliates”, peer organizations and groups active in sharing stories through the platform who decision-making.

White-label Your Approach

“White-labeling” means putting a product, service, or program model out into the world in such a way that anyone can rebrand it as though they made it.

An illustration of the Digital Stewards approach. Image via OTI.

An illustration of the Digital Stewards approach. Image via OTI.

For example, several times throughout this series we’ve looked at a program called “Digital Stewards” in both Detroit and Red Hook, Brooklyn. Although these two programs use the same language (“Digital Stewards”) in reference to a training program to help design, build, and maintain community wireless networks, the programs are not one and the same, nor are they “chapters” or the expression of a single brand.

Rather, each Digital Stewards program is an imprints of a white-labeled training course on digital stewardship developed by the Open Technology Institute (OTI) at New America in conjunction with Allied Media Projects (AMP) that is available for anyone to adopt and use. OTI identifies its role in the creation of Digital Stewards not as the parent or owners, but as a “resource center”, adding to the Digital Stewardship materials over time and responding to requests from communities (like Red Hook, Brooklyn) for support in training. Neither OTI nor AMP exerts copyright or brand control over how the program exists in the world and neither identifies as “owning” the program.

Removing “ownership” is a direct expression of the open ethos that drives civic tech and way of ensuring that communities get genuine ownership over a technology or other civic project, even if the development of this project is guided by an external organization.

Other examples:

  • DiscoTechs (short for “Discovering Technology”) are a model of collaborative events for creating and exploring community technologies. The DiscoTech model was developed by the Detroit Digital Justice Coalition (DDJC), but DiscoTechs maintain no branding affiliation or ties to DDJC, allowing communities all over the country and the world to customize, remix, and implement as they see fit.
  • Although the CUTGroup (where “CUT” is short for “Civic User Testing”) was designed by Smart Chicago as a way for residents in Chicago to use civic apps and give feedback to developers, Smart Chicago released the nuts and bolts of the program as an online guide so that others can utilize and riff on the model. Note that the branding is not specific to Chicago or Smart Chicago and that the model is available for use without explicit consent from or identification with Smart Chicago.

Be a Participant

Ultimately, you can’t marshal a community’s energy unless you’re part of that community. To share experiences and engage in the wants, needs, and interests of the people your civic project is meant to serve.

Participation is a mindset shift. Instead of leading, you as a practitioner, are listening. (Much like the two-way teaching style talked about in Mode #3.) Whether you’re an individual doing work close to home or an organization supporting distant activity, to be a participant is to allot time and space to others and to seek opportunities to support work that supports them.

  • Laura Amico, a crime reporter and co-creator of HomicideWatch, a platform for following murder cases in Washington, DC, struggled to find information about the murder cases she cared about. After watching her neighbors and how victims’ and suspects’ family and family were haphazardly monitoring information on an individual level, Laura and her husband, Chris, began to design a platform that would allow for collaborative coverage, with more data sources and opportunities for communication. HomicideWatch is the product of innovation, yes, but also shared grief and shared struggle.
  • Public Lab’s paid staff directly coordinates with and wields a number of communications platforms to listen to its extended community and brings together its network in an annual meeting (called a “barnraising”) to build relationships, tinker with tech, make big decisions, and break bread.
  • EPANow is an ongoing experiment in youth-driven hyperlocal news co-founded by Stanford University Knight Journalism Fellow Jeremy Hay with residents of East Palo Alto, California. Jeremy is not an East Palo Alto (EPA) native, but is helping to steward the project after local community activists asked for his help. Hay started with a defined vision of what the news platform would be, but has since slowed his approach, both directly in response to community challenge and in response to his own revelations and experiences working with (and, increasingly as part of) the EPA community.

“While I am not superfluous to the process, and what I bring to it is important, I am of necessity secondary.”

(More about Jeremy’s journey participating in EPA as an outsider is documented here.)

Mode #4: Lead From Shared Spaces

This is the fourth piece in a five-part series exploring how to develop civic technology with, not for communities. Each entry in this series reviews a different strategy (“mode”) of civic engagement in civic tech along with common tactics for implementation that have been effectively utilized in the field by a variety of practitioners. The modes were identified based on research I conducted with Smart Chicago as part of the Knight Community Information Challenge. You can read more about the criteria used and review all of the 5 modes identified here.

MODE: Lead from Shared Spaces

Communities are built around commons— collaboratively owned and maintained spaces that people use for sharing, learning, and hanging out. Commons are the foundation upon which all community infrastructure (social, technical, etc) is built and are often leveraged by multiple overlapping and independent communities.

Although often thought of as semi-permanent physical spaces, like parks or town centers, commons can also be digital (i.e. online forums, email lists, and wikis), temporary (like pop-ups or weekend flea markets), or a variety of other set-ups beyond and in-between.

A commons is a resource, offering tools, news, and know-how that both community insiders and outsiders can wield. Tapping into a commons not only helps identify social and technical infrastructure, it provides a key opportunity to listen and learn about what matters most to a community. The following two tactics look at how civic tech practitioners can not only use commons for collaborative work, but can contribute to their stewardship, as well.

Leverage Existing Knowledge Bases

Knowledge commons are spaces where people collect and access information, be it archival info (like one would get from a library) or news (like one gets from a neighborhood listserv).

7r8dg7w7uz17paca (1)Depending on the circumstances and the folks behind the wheel, the creation of a knowledge commons can itself be a form of civic technology— a tool for a community to use for its own benefit.

DavisWiki is a hub for both hyperlocal history and current events in Davis, California. Launched in 2004, DavisWiki started as an experiment in collaboratively surfacing and capturing unique local knowledge that was otherwise locked in the heads of neighbors or lost in search engines. The site gained popularity by coordinating with existing social infrastructure, such as the university system in Davis and the local business community, and within a few years residents had contributed over 17,000 pages. 

As more residents use DavisWiki, the platform’s role has changed. In addition to being a popular catalog,  knowing that DavisWiki was available as a knowledge commons has enabled residents to leverage the platform for additional civic ends over time. For example, the wiki was part of coordination of the public response (and record-breaking rally) to a police officer pepper-spraying a student on the UC Davis campus in 2011 and has been used to explore, discuss, and collaborate with government a number of local planning initiatives.

Public Lab is a different sort of knowledge-based community: although many of the folks who participate in Public Lab (via their wiki, email listservs, in-person meetings, and other forums) work in their own local contexts, the community associated with Public Lab is international in scope, bringing together citizen scientists from around the globe who are researching and crafting inexpensive DIY tools for environmental science that anyone can use.

In this way, Public Lab plays the role of a bridge, connecting many knowledge commons together in one great public-facing resource that can boost local work by giving it a broader audience and more data inputs.

Community meeting. Image via Public Lab.

Community meeting. Image via Public Lab.

Leverage Common Physical Spaces

Although the network model of Public Lab enables a high degree of exposure for local work, nothing says “free PR” quite like door-knocking or standing on your neighbor’s roof to install an Internet router. Both the Detroit and Red Hook Digital Stewards instances lead with this idea, leveraging common spaces in their communities (neighborhoods and city districts) to plug into existing social infrastructure and get community members on board and involved.

Approaching technology development with an eye towards the physical world also enables an additional dimension of sustainability. While both Digital Stewards instances are ultimately about developing digital commons, by tapping into physical resources and the social structures that maintain them, the Stewards extend the communal care and maintenance to include the new technology over time.

Up next: Mode #5: Distribute Power.