Criteria: People First, Tech Second

What does it look like to build civic tech with, not for? What’s the difference between sentiment and action?

That’s the thrust of Experimental Modes in Civic Engagement for Civic Tech — a special initiative that I’m leading for Smart Chicago as part of their Community Information Deep Dive. The scope of this work is guided by the “civic” in “civic technology”, the idea that people need to be prioritized above production.

The project has three parts: (1) a scan of the field, identifying practitioners of needs-responsive, community-driven tech and the basic characteristics, best practices, and models that define their work, (2) a convening of practitioners at the Chicago Community Trust in April 2015, and (3) a book, documenting our investigation of the space and civic tech tactics and strategies that refocus the work on people.

Criteria

In order to inform the scan of the field, I developed a series of criteria for evaluating whether a project meets the standard of being needs-responsive and community-driven. To prioritize people and build with them is to:

  1. Start with people: Work with the real people and real communities you are part of, represent, and/or are trying to serve
  2. Cater to context: Leverage and operate with an informed understanding of the existing social infrastructure and sociopolitical contexts that affect your work
  3. Respond to need: Let expressed community ideas, needs, wants, and opportunities drive problem-identification and problem-solving
  4. Build for best fit: Develop solutions and tools that are the most useful to the community and most effectively support outcomes and meet needs
  5. Prove it: Demonstrate and document that community needs, ideas, skills, and other contributions are substantially integrated into — and drive — the lifecycle of the project 

Beyond direct application to the Experimental Modes initiative, my goal in creating these criteria was to define the leanest standard possible for translating the idea of “with” to a series of identifiable practices that can be used for further investigation, accountability, and guidance outside of this project.

Some of the principles defined above have been long mirrored in (and championed by!) the design community, but their expression has yet to become part of the primary approach to creating civic technology as commonly talked about today. Nor has there been much dialogue about what it means to do more than just design with a community, but to literally build and evaluate these civic tools together — to let community drive the whole process.

As we push this conversation — and active experimentation — forward, our next steps focus on sharing modes of existing community co-construction with high-value lessons and patternable best practices. We’re also organizing a convening of practitioners, so if your work/projects you know of meet the criteria above.

Co

Dig this inspiring stock image of collaboration? Learn more about it here.

PHOTOS: CUTGroup #14, Chicago Cityscape, Logan Square Public Library

Here’s a set of images of Sonja Marziano, Christopher Whitaker, and Josh Kalov conducting CUTGroup #14, which is focused on Chicago Cityscape, a site that tracks building permits, violations, and historic resources in all neighborhoods, community areas, and wards using open data.

Developer Steve Vance conducted a number of the tests, along with guest proctor Daniel Ronan.

Thirteen testers from all over the city showed up on a cold winter night, and we all learned a lot. Sonja is compiling the results— full report soon!

See a complete collection of photos from CUTGroup tests here.

Does your building not recycle? Report it here!

mybuildingdoesntThe Environmental Breakout Group at OpenGov Hack Night has been working on a site to report buildings that don’t recycle. Chicago’s ordinances require buildings with five or more rental units to provide recycling. However, the city doesn’t always enforce this law leading some landlords to not provide recycling.

Claire Micklin, Ben Wilhelm, and Alex Kahn put together to help residents report buildings that don’t recycle.

The team will be using the data to visualize reports of buildings that don’t recycle and provide a hub for residents seeking more comprehensive recycling services.  Already, the site has received 900 reports on 750 locations in the first week that it launched. (The site was getting hit so much that it was running into Google’s API limits – and so they started using Smart Chicago’s Google API account.)

Micklin first started the project after seeing so many of her neighbors blue bins filled up constantly because neighboring buildings weren’t providing recycling.

Micklin says she found working with the Environment Breakout to be really helpful for finding resources and coming up with ideas on how to do it. Scott Beslow, who helps lead the breakout group, helped put the bones together in terms of constructing the site and getting developers interested. The team used the OpenCity Apps Github repository to collaborate on the app.

The site was announced at last week’s OpenGov Hack Night to rave reviews and has appeared on WBEZ, the Mike Nowack Show, and DNAinfo. Here’s WBEZ talking to Micklin:

The group hopes to use the information to lobby for stronger enforcement of the recycling ordinance. The team will continue to work on the app during OpenGov Hack Night which happens every Tuesday at 6:00pm at the offices of Braintree.

Aldertrack: Your Guide to the 2015 Chicago Elections

Aldertrack-logoAt the February 3, 2015 Chicago OpenGov Hack Night, Jimm Dispensa talked about Aldertrack – A project to help residents of Chicago follow the 2015 Chicago Aldermanic and Mayoral elections.  The site offers race forms, analysis, webinars, as well as providing extensive social media coverage of each race.

History of Aldertrack

The site was first started by Dispensa in 2007 as a text only website that tried to gather details about Chicago’s elections and sort them out by ward. In 2010, he was joined by Mike Fourcher and the (now defunct) Chicago News Cooperative to create the first Early & Often site for the 2011 elections.

In 2010 Mike Fourcher became a part of Aldertrack and the group partnered with the Chicago News Cooperative to create the first version of Early & Often for the 2011 Chicago elections. (This may sound familiar since the Sun-Times’ had it’s own Early & Often site that was purchased from the Chicago News Cooperative.)

For this year’s elections, Ramsin Canon has also joined the team and is helping to make the site a more complete guide to this year’s elections.

Using tools to make the site cheap to run

The Aldertrack team uses several tools to make the site inexpensive to run. Here are the ones the teams lists as indispensable:

  • WordPress: WordPress is a popular blogging platform that’s simple to use. (We use WordPress as well!)
  • Mailchimp: Mailchimp is a platform that allows users to send out email campaigns. Aldertrack uses it to send out daily email updates about the election.
  • Slack: Slack is an internal communication tool that organizations use to communicate with each other in real time. It’s similar to the old IRC chat rooms, but it’s got a much better user interface and can integrate with other platforms like GitHub.
  • Stripe: Stripe is a payment system that integrates easily with apps. If you’ve ever used Lyft, you’ve used Stripe
  • Join.Me: Join.me is a screen sharing tool that the Aldertrack teams uses for Webinars.
  • data.cityofchicago.org: The Aldertrack team also makes extensive use of the City Data Portal

The Aldertrack Team also has several tools that they don’t love, but use anyway including

  • Microsoft Word and Excel
  • Adobe Acrobat for PDF reading
  • The Chicago Board of Elections Website: The team uses the site to get information, but says it’s not the most user friendly site.

There were also sites that the team called useless such as Facebook and printing their own newsletters. Dispensa said that while people will print things out themselves, it’s not cost effective to print for a medium-sized runs of things. The team at Aldertrack also finds Facebook useless for small audiences.

Lessons Learned

Dispensa shared several lessons that he’s learned in running the Aldertrack. The first few lessons revolve around knowing their audience. Dispensa says the audience for Chicago politics isn’t as big as you think and that their more interested in raw data than analysis. Dispensa also says it takes a lot of effort and inside knowledge of local politics to produce quality content for political junkies.

The team also found that traditional advertising doesn’t do much for increasing engagement among political junkies. They also found that exposure on other media hasn’t driven up readership or sales either.

The Aldertrack team found that while video doesn’t get many eyeballs – it does make the organization seem more professionals. For their webinars, the team uses two iPhones and a lapel mic.

Dispensa also says that more open government data has leads to more, not less, information arbitrage opportunities.

You can watch the entire presentation below:

To get more information about Aldertrack, visit their website here! 

Slow Roll Chicago Rolls Into Hack Night

At this week’s Chicago OpenGov Hack Night, Oboi Reed and Steve Vance presented about Slow Roll Chicago and about improving equity in bike infrastructure in the City of Chicago.

Oboi Reed of Slow Roll Chicago talks about their work

Oboi Reed of Slow Roll Chicago talks about their work

Slow Roll Chicago is a community bicycle ride in Chicago founded by Jamal Julien and Olatunji Oboi Reed in 2014. Slow Roll Chicago rides on a regular basis from April to October. The ride meets at various locations & venues and takes a unique route for each ride. Slow Roll is for everyone; all ages, skill levels and types of bikes are welcome. They are called Slow Roll as our their slow riding pace keeps the group safe and gives riders a unique perspective of our great city and its beautiful neighborhoods.

One of Slow Roll Chicago’s major initiatives is advocating for more equitable bike infrastructure in the city of Chicago. Currently, the City of Chicago places bike infrastructure where there are the most bikers. Slow Roll Chicago believes that if you place biking infrastructure in places where none exist, more people from those areas would ride bikes.

To help map out the disparity in biking infrastructure, Slow Roll Chicago worked with Steve Vance and the  Transportation Breakout Group at Chicago’s OpenGov Hack Night to build the Chicago Bike Equity Map.

Chicago Bike Equity Map

Chicago Bike Equity Map

The map shows current bike lanes overlaid by population density. Clicking on the bike lanes will show you what type of bike lane it is. For example, is it a buffered bike lane or simply a painted one?

You can see from the map that the bulk of the bike infrastructure is on the north side of the city

You can use the map to show different points of interest – including grocery stores.  You can download the data that powers this straight right from the site’s menu bar.

The project is open source and uses the Bootleaf as a base.  You can view their entire presentation below.

If you’d like to learn more about how data and technology can help solve our city’s transportation problems – you should join the Transportation Breakout Group at OpenGov Hack Night! 

“Hacking Design Research” Interview in Civic Quarterly

Here’s an interview in Civic Quarterly about the CUTGroup. Snip:

Part civic duty, part solicited opinion, Smart Chicago’s CUTGroup is comprised of “regular Chicago residents who get paid to test civic apps.” This, in turn, allows developers to get citizen feedback on demand and learn how well their civic technology works when put through its paces.

In the Fall of 2014, O’Neil published a book chronicling the creation and execution of Smart Chicago’s CUTGroup. After giving it a read, I reached out for some clarification. As a formerly private-sector user experience designer turned public-sector advocate, I wondered how Smart Chicago’s approach differed from the design research methods I was more familiar with.