Crafting high-quality civic technology鈥娾斺妏rojects and tools designed with social impact in mind鈥娾斺妑equires thought, creativity, and intentionality鈥娾斺妕he strength to ask:
鈥淲ill this project actually have social impact? Is it being designed for the social/cultural/political context in which it will be implemented? And if not, what steps do we need to take and what people do we need to substantially involve to get there?鈥
Our approach to community-building in the name of civic tech should be the same.
, we review how open format models (like hackathons and unconferences) can be remixed and reinvented to encourage an outpouring of 鈥渘on-traditional鈥 engagement with civic tech without _alienating tech veterans. Our focus: The Tech Embassy, a a pop-up, interactive science fair for local tech and art that took place on May 3, 2014 during Washington, DC鈥檚 first-ever . (_Yes, that鈥檚 right: A 鈥淔unk Parade鈥 with a civic tech agenda.)
In parts 1 and 2 of our 6-part study, we review the framing exercise used to derive the criteria and audience for and guide organizing for The Tech Embassy. .
Part 1: Set Goals You Can Hold Yourself Accountable To
[Or, Why We Didn’t Have a Funk Parade Hackathon]
鈥淗ackathons.鈥 That鈥檚 one of the most popular answers to a question you haven鈥檛 asked yet: How do you organize your local tech community to do X/attend Y/engage with Z?
For several years now, 丑补肠办补迟丑辞苍蝉鈥娾赌鈥奼atherings of programmers (and, sometimes, issue-area practitioners) for deep dives into particular data-sets, problems, or concepts鈥娾斺奾ave been deployed like flytraps, tenuously designed to attract and entertain developers so that 鈥渢ech鈥 could be tied to this or that event, with extra cool points assigned for maximizing opportunities for free labor and 鈥渃ommunity building鈥. But hackathons (and their kin, code nights) aren’t the only way to attract and engage your local tech community鈥娾斺妏articularly when it comes to_ civic_ tech.
But not all hackathons are terrible and ill-deployed: Initially, hacks were designed as temporary spaces for group problem-solving and prototyping (think: business accelerator meets science lab) and sometimes, just for straight-up creativity (think: ). These kinds of hacks, when focused鈥娾斺妉ike that helped the city of Washington, DC radically open up its legal code鈥攃an be wildly effective platforms for production and (despite earlier grumbles) for community building鈥娾斺in-group community building.
At hackathons, people who speak the same language (i.e. Python, Ruby, GIS) or who care about the same issues (elections, transparency, their city) can quickly collaborate, form bonds, and share skills. In this way, hacks are not only useful iteration spaces, but also play the role of solidifiers for those _parts_of your tech community with technical commonalities鈥攖hose that code or see code鈥檚 value.
But what about the rest of your tech community? What happens when we scale the definition of 鈥渢ech鈥 beyond command lines? When we scale 鈥渢he community鈥 beyond tech creators?
Earlier this year (before my time at the Open Technology Institute), I was approached by the organizers of DC鈥檚 first-ever 鈥娾斺奱 street fair, foot parade, and music festival celebrating Washington, DC鈥娾斺妕o integrate the local tech community into the main event. Beyond the never-realized Robot Dance Competition (where one could could either compete with a robot or do 鈥娾斺奵ome on, comedy gold) and The Tech Embassy (which I鈥檒l get to in a minute), the initial scope of the work included (drumroll!) a hackathon.
Now, there was most certainly a world where, with the right combination of available data, tools, creativity, and time, we could have pulled together a pretty well-organized hack related to local music with a bunch of technologists and maybe some musicians, but that world was not this one. Besides a number of small design challenges (such as limited time to organize and lack of focus), our organizing team was stuck chewing on an important question: Who would a Funk Parade hackathon be for?
Most of Funk Parade鈥檚 programming was about building bridges鈥娾斺奲etween black and white, old and young, geographic divisions in the city, you name it. Could a Funk Parade hackathon function the same way and provide a bridge between DC鈥檚 tech scene and 鈥渢he rest鈥 of our local culture? Or, put another way: Was a hackathon the right vehicle to execute on the Funk Parade vision of unified community?
鈥
This was happening literally right outside The Tech Embassy for the entire afternoon. Could you resist checking it out? Photo by William McCann.
Many 丑补肠办补迟丑辞苍蝉鈥娾赌斺妏articularly in the civic tech space鈥娾斺奱re open to (if not craving for) non-technologists, but that doesn’t make them level playing fields. First-timers at hackathons face a learning curve (鈥渨hat is a hackathon鈥, 鈥渨hat can I contribute鈥), and most require a certain intensity of time and focus from participants that wouldn’t be a great match for the feel and flow of Funk鈥檚 other programming鈥娾斺奱 street fair with ongoing , , and other kinds of and . If we were going to create a centralized hub of activity for local tech, we wanted to build a space that fit right into the mix.
Our framing criteria were:
- Low barrier to entry: Attendees should be able to walk in, figure out what鈥檚 happening, and be able to quickly find a way to be involved (whatever their threshold for involvement).
- Pro-amateur and pro-expert: Attractive to attendees of different technology skills (in terms of a diversity of skills鈥娾斺妑obotics! Rails! avid Facebooking!) and skill levels.
- Easy to stay, easy to leave: No one should feel trapped inside all afternoon with a going on! Or friends to visit, kids to watch, laundry to do, etc.
- Interactive鈥娾斺妎ffline and online: Everyone should have the opportunity to play, build, or otherwise contribute to one or more tech-related projects present (emphasis on _everyone) without _opening a laptop. (Not everyone would have a laptop with them, nor are laptops perfectly suited for social engagement or essential for all types of tech.)
- Focused on 鈥渃ivic tech鈥 in the broadest sense鈥娾斺projects, tools, and tricks anchored in the social and political life of our neighbors. If nothing else, projects centered on improving, enjoying, and exploring the place we live would be something where 99% of Funk Parade attendees could find a piece of common ground.
Part 2: Let Your Audience Dictate Your Design
[An Intro to The Tech Embassy]
You can run through the criteria above and still end up deciding a hackathon would be the best fit. We almost did. But when we started sketching out the 鈥渨ho鈥 that we wanted to respond and feel invited by the event we were crafting based on our criteria, the event itself changed.
Our 鈥渨ho鈥 was two-fold: (1) technologists, geeks, nerds, makers, and other signifiers of the technically inclined and, more broadly, (2) DC-ers (age 2 to 92) out enjoying their Saturday afternoons.
To accommodate both 鈥済roups鈥, we needed an environment that simultaneously gave technologists the communal feel of a hackathon and gave those who_ didn’t_ identify as technologists the comfort of being in a space where their tech knowledge (or lack thereof) didn’t matter [Criteria 1]. To pull this off without trivializing the contributions of any one particular group, we decided to de-emphasize specific tech skills (i.e. coding) and instead prioritize interactivity鈥娾斺奱nd, dare I say, fun. Focusing on interactivity in this way meant thinking about unconventional learning opportunities (like turning pre-teens into teachers), being intentional about the physical layout and feel(!) of space, and diversifying the kinds of projects available to explore. [Topics we鈥檒l explore in more detail below.]
The model we ended up with we called , a pop-up, hands-on science fair for DC tech and art made by residents for residents.
The Tech Embassy was embedded within Affinity Lab, along the main strip of the street fair. The name was a play on the struggle we ourselves were having, defining a somewhat arbitrary line between the 鈥渢ech community鈥 and 鈥渢he rest鈥 of DC. Rather than continuing to ignore this tension, we saw 鈥淭he Tech Embassy鈥 as a chance to confront it and begin to address .
On May 3, 2014, we launched our experiment with over a dozen partners* from the local art and tech scene. The response was explosive: Over the 4 hours of the event, nearly 400 people visited to explore projects from local civic hackers like , , and tweens from (seriously, ), to with the Open Technology Institute () and doodle on a graffiti wall, to play Scrabble, make over 100 LED throwies (), learn how to 3D print with , dance to funk music from local DJs, learn the history of go-go music (a native DC genre of funk), and share memories of live local music for a .
For more from this case study, check out these excerpts:
Part 3:
Part 4:
Part 5:
Part 6:
[Full Piece]
More 国产视频 the Authors
Issues
Programs/Projects/Initiatives
Related
OTI鈥檚 Agentic AI Work Wins Privacy Papers for Policymakers Award
The App Store Accountability Act Poses Serious Concerns for Privacy, Security, and Free Expression
