- What Code for San Jose Should Learn from OpenStreetMap
- Code for San Jose represents at the Civic & Gov Tech Showcase
- Code for San Jose Celebrates Open Data Day with Mayor Sam Liccardo
- BigData Analytics for Civic Innovation in Smart Cities
- Civic HackNights: Of the People, For the People, By the People
- Designing for the City, Inspired by the City
- Engaging new members with mini-projects
- Code for San Jose in the News!
- Five Key Takeaways from San Jose’s Open Data Roadshow
- San Jose hosts the California Open Data Roadshow
- All posts ...
Engaging new members with mini-projects
Oct 25, 2015 • James Tyack
This post was originally published on the personal blog of new Code for San Jose member James Tyack. We’re excited to have James join us from Philadelphia, where he was a valued civic hacker at Code for Philly.
Last weekend I attended a fun meet-up session organized by brilliant minds at Code for San Jose. The idea was to come up with a set of mini 2-hour civic projects for beginners. I wanted to share my thoughts on what we did because I think it’s something we should all be thinking about if we expect new people to feel welcome and engaged when they join our team, group or workplace.
I’ve been going to civic hacking events in Philly for some time and remember my first meetup over 2 years ago. There was a brief introduction. After that, I was surrounded by lots of talented civic hackers working on projects that seemed big, well established and, frankly, overwhelming. And that’s coming from a software engineer with years of experience.
Where to start? What problems were we trying to solve? What’s 311 and will I sound stupid if I ask? Where’s the open data coming from and why’s it so difficult to use?
Over time I learnt about open data portals, tools like Mapbox, CartoDB, data scraping, open data APIs, 311 systems, transit GTFS feeds etc. etc. I looked at work by rockstar Civic Hackers like Derek Eder and Chris Whong; and reached out to chat about their achievements. I met up with people from the City, SEPTA (Philly’s transit authority) and went along to other Code for America groups (“brigades”) like BetaNYC to find out what problems they were trying to solve.
Eventually, I figured out easy ways to do what I wanted to do: help get broken elevators at stations fixed by improving awareness of the outages. I cleaned up some open transit data, mapped it, tweeted my results and established a project, Unlockphilly.
I also discovered that some of the best civic work doesn’t involve extensive software development; just a great idea that solves a real problem and creative thinking combined with open data and simple, free tools.
In the meantime, I saw lots of people from different backgrounds with bucket loads of enthusiasm and valuable/diverse skill sets (technical and non technical) come and go after just one week. I think many of them found it difficult to see a quick way to contribute and found the experience confusing and overwhelming.
These problems obviously aren’t restricted to to the civic hacking world, they’re pervasive throughout most organizations and us ‘experts’ have a responsibility to have ‘beginners mind’ and think about ways to help new people feel welcome, engaged and valued.
Things have changed dramatically since I signed up. At Code for Philly we have great welcoming sessions led by an incredible team of dedicated and passionate people who understand the challenges of being a newbie. Mentors will help you find the right project match for your interests and skills set and even help you get started with your own idea. The brigade has high turnout with lots of regular members and incredibly active and impactful projects like CyclePhilly.
However, there are still challenges when it comes to knowing where to start with so many experienced experts and well established projects around.
That’s where mini projects come in. Team members with knowledge of easy-to-use tools and clean data sets devise small, well defined 2-hour tasks. New recruits pick up these tasks and pair up with someone who can help. Hopefully they then complete their first hack night feeling engaged and proud of what they’ve achieved.
Here are some of the ideas we came up with to get things started. We put these issues in our ‘Project Ideas’ repository and labelled them ‘Small Project’ so they’re easy to identify.
The first idea is a foundation to ensure beginners have access to free, simple (but powerful) data/hacking tools that require minimal setup.
- Build a template page that everyone can contribute to containing links and tutorials for simple tools like CartoDB, Mapbox, Google sheets etc. These tools can be used to build quick prototype or visualizations around data that can be shared and extended over future weeks. https://github.com/codeforsanjose/Project-Ideas/issues/35
- Analyze compensation of public workers in California. A clean, simple data set is given along with a suggestion of how to analyze the data https://github.com/codeforsanjose/Project-Ideas/issues/19
- Visualize trip purpose data by destination from transit survey using CartoDB – again, a nice data set is given in the issue and lots of helpful advice on how to carry out the task https://github.com/codeforsanjose/Project-Ideas/issues/36
We’ll be refining and building on these ideas in coming weeks based on feedback and success measures. I’m hoping to see lots of great work coming out of this from happy, engaged civic hackers!
“If your mind is empty, it is always ready for anything, it is open to everything. In the beginner’s mind there are many possibilities, but in the expert’s mind there are few.” Shunryu Suzuki – Zen Mind Beginner’s Mind