Redesigning Civic Engagement

Transcript

1. Redesigning Civic Engagement Creating creative, collaborative and action-driven political participation.
2. Introductions
3. ANALISA LONO ASSISTANT EVENTS MANAGER AT ADAPTIVE PATH Political Science junky. Long history of civic engagement and youth programs. Believes that our nation is frustrated over the lack of channels for constructive engagement.
4. P.J. ONORI Formal educations in both computer science and design. 8 years of experience working as a developer, designer (and everything in between) Deep background in public-focused software projects. USER EXPERIENCE DESIGNER & TECHNOLOGIST
5. The Problems
6. THE POLITICAL PROBLEM
7. PEOPLE HAVE CHECKED-OUT There are few effective channels of engagement. Citizens are cynical of government’s efficacy. Young adults lack a path to civic participation that relates to their interests.
8. THE EDUCATIONAL PROBLEM http://abstrusegoose.com/418
9. STUDENTS ARE NOT EQUIPPED FOR SUCCESS IN TODAY’S WORKPLACE Curriculum cannot keep pace with reality outside of its campus. Traditional educational models do not encourage collaboration. There are far too few interdisciplinary opportunities for students in higher education.
10. An Alternative
11. Engage communities and government through creating disruptive software, apps, APIs and online services.
12. A COMPARISON...
13. 150 people × 18 hours per day × 60 days = 162,000 people hours (roughly) Result: TBD... OCCUPY MOVEMENT
14. 2 people × 12 hours per day × 8 months = 5,760 people hours (roughly) Result: Changed media forever. NAPSTER 1.0
15. Our goal is to create an entity with the inclusiveness of Occupy and the efficiency of a startup.
16. The whiteboard can become the new vehicle for civic engagement.
17. The Idea
18. Mentor young adults in multidisciplinary groups to create usable outcomes for social good.
19. GOALS Focus on civic action. Foster multi-discipline thinking and collaboration. Create an avenue for volunteerism and entrepreneurship. Conclude with tangible outcomes.
20. CONSTRAINTS Only software projects (web, mobile, desktop) in the first year. 1 Group per school only. Ideally 3 schools would participate, but 1 would be fine for first year.
21. ORGANIZATIONAL STRUCTURE CORE TEAM School Prof. of Design Prof. of CS Prof. of ??? Academic guidance. Student Team Designer Coder ??? Doers of awesome. TEAM OF ADVISORS & MENTORS Non-Profits, NGOs, etc. Red Cross EFF SF MUNI Subject matter experts. Private Firms IDEO Method Google Strategy/Design/Technology mentors.
22. PROJECT STRUCTURE The project will last one semester. Students will need to decide on a project and pitch it to professors and mentors. Weekly checkins with professors and mentors. Students will formally present final product.
23. TEAM STRUCTURE 1 Design major 1 Computer Science major 1 Wild-card major (e.g., Journalism, Biology, Philosophy, etc.) 3 Professors (representing each major) overseeing the work. 1 Professor acts as lead to ensure deadlines and goals are being met. STUDENTS FACULTY
24. SUPPORT STRUCTURE A private firm will be brought in to provide perspective on concept and execution. A non-profit or NGO will be available as subject- matter experts. Both groups will take part in monthly reviews and be available to provide guidance for specific challenges.
25. INTENDED OUTCOMES A product or service which they own and control upon completion of the project. A resume and portfolio builder with concrete experience. Encourage social entrepreneurship.
26. WHAT WE’RE LOOKING FOR IN STUDENTS People that care about making an impact in their community, country, world. Individuals who are able to work well in groups as an equal member and as a leader. A willingness to grow outside of their chosen major.
27. Thanks. Analisa Lono, analisa@adaptivepath.com P.J. Onori, pj@somerandomdude.com