Code for Europe demo 2013-04-17 at Stadsdeel West Amsterdam

Uploaded on

Code for Europe Amsterdam Fellows present the updates of the challenges in Amsterdam West, Zuid and Oost.

Code for Europe Amsterdam Fellows present the updates of the challenges in Amsterdam West, Zuid and Oost.

More in: Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide
  • Log social network check-ins Provide data connection for their devices Create meaningful stories Engage people with direct contact
  • (Building tech tools to support it, if it proves successful)
  • Create an information collaborative tool supporting service professionals from different organizations (and citizens) working closely together


  • 1. Demo DayApril 17, 2013
  • 2. Agenda• Introductions• Projects • Oost • Zuid • West• Discussion
  • 3. TeamGiovanni M Ohyoon KwItaly aggini on Piotr Steininger South Kore tes a Poland and United Sta
  • 4. Giovanni Maggini • Business and process management consultant, iOS developer • Computer Science background • Developed prize-winner Open Data app for Italian contest • Moved to Amsterdam to become a Code for Europe Fellow @maggix • Recently became #1 Stroopwafel fan
  • 5. Ohyoon Kwon • Concept Designer • Backgrounds in architecture and industrial design • Originally from Seoul and based in Europe since 2009 • Developing his own social enterprise based in Eindhoven @ohyoonkwn • Team camera man
  • 6. Piotr Steininger • Business and Techology Consultant • Web and Mobile Developer • Enterprise integration and B2B apps • Recently more of iOS, Android and Ruby on Rails • Passion for solving problems with technology @polishprince • Always hungry
  • 7. Oost: Social AccommodationsZuid: Tourism and CongestionWest: Buurt Praktijk Team
  • 8. Oost: Social AccomodationsMission:Matching supply and demand for socialaccommodations•Cultural Events•Education Opportunities•Gathering spaces•Community initiatives
  • 9. One of a kind neighborhood
  • 10. Indische Buurt Communities Timorplein Makassarplein MeevaartAmsterdam Muiderpoort station Ambonplein 22.000 inhabitants Four active community clusters 50 community builders 200 initiatives
  • 11. Status• Engaged with various people in the neighborhood• Identified some immediate needs, focused on DeMeevaart• Developed first iteration of a social neighborhoodplatform • Room Booking
  • 12. Interview residents & entrepreneurs• Interviewed a number people living in Indische Buurt• Capture their experience about initiating or participating in neighborhood activities
  • 13. Current booking practice: flyers + calendar• Flyers in main lobby• Weekly room schedule posted on the board (static)
  • 14. Iterative approach 1 2 3 4• Prioritize the most necessary functionality• Neighbors and Meevaart can both use the public calendar• Derive directories of rooms, people, activities
  • 15. Low Fidelity Prototypes
  • 16. Low Fidelity Prototypes
  • 17. Room Request Confirmation 17
  • 18. Room Requests 18
  • 19. Room Inventory 19
  • 20. Dashboard for admins 20
  • 21. Dashboard for admins 21
  • 22. Challenges Encountered• Identifying and selecting opportunities – Meaningful, yet feasible• Identifying key decision makers• Communication issues
  • 23. Next steps• Complete booking portion of the tool• Expose a public calendar of events• Add functionality to allow residents to publish initiatives and reach interested people
  • 24. Zuid
  • 25. Mission• Enable and encourage visitors to explore outside of the center of Amsterdam
  • 26. Investigation
  • 27. Concept•How to get information from event organizers•Connect with and engage tourists•Scavenger hunts, story telling, data collection
  • 28. Scavenger hunt concept Vondelpark Architecture Art
  • 29. Scavenger hunt backend & front-end 3 Collect and measure the check-in info of visitors 1Pieter@IAmsterdam 5 routes with 5 “attractions”Elvria @ 2Stadsdeel Zuid Expose the attraction info to visitors through location based social media platform
  • 30. Itineraries• Green Route (parks)• Sports Route• Architecture Route• Shopping Route• Museums and Fashion Route
  • 31. Sketching Maps of Trails
  • 32. Exploring Zuid
  • 33. Deadline: 24H Zuid
  • 34. Questions• Will people participate?• Will visitors love the experience?• Is this the type engagement they are looking for?
  • 35. Next StepsLow-tech:•Implementing the “scavenger hunt” proposalHi-tech:• “Automating” the process?• Making it re-usable for other citiesBoth:• Exploring “Game” concept
  • 36. West: Buurt Praktijk Team
  • 37. MissionSupport activities of Buurt Praktijk Teams, projectmanagers, and directors•Engaging citizens to solve local problems•Working with professionals like Police, teachers andsocial workers as a team•Take meaningful actions and reflect on methods andresults
  • 38. Status• Refining questions to resolve ambiguities • Privacy • Integration with existing systems • Inside/Outside communication• Made essential decisions for experiments • Who, Scope, Tools, Learning Objectives• Begin to conceptualize possible solutions
  • 39. Shaping the product that fits the unknown context Unknown factors: •privacy regarding citizen information •collaboration acrossorganizations/citizens Product •integration with existing information Productsystem (that does not even exist yet!) Product Product
  • 40. Formulating questions to identify the unknown factors Unknown factors: What is the minimum privacy related information that is •privacy regarding citizen information included in the product? •collaboration acrossorganizations/citizens How to support the learning Product •integration with existing information process of professions? Productsystem (that does not even exist yet!) Perhaps it is too difficult to engage! Product Product
  • 41. Involved people at different layers directors team manger Runner team leaders staff
  • 42. Concept: “one bucket for one project”
  • 43. Concept: “one bucket for one project” Support collaboration Support collaboration between BPT membersbetween BPT members and professions from and citizens other organizations
  • 44. Next steps: experiments to answer the questions• Select two projects & recruit people who will participate in experiments• Enable people to use an existing tool to support their practice• Use existing tools offering relevant features responding the needs of BPT • Highrise • Facebook • Adding a simple SMS interaction• Conduct experiments for a limited period and learn valid interactions and features from real use stories
  • 45. Highrise• Simple CRM• Centralized contacts repository• Start projects (cases), record notes, relate to contacts• Email gateway integration (interact with system via email)• Tasks: checklists, reminders, etc
  • 46. Facebook• Facebook Page Only• Timeline feature• Widely used and familiar• Provide space for discussion and interactions• Low barrier of entry• Publicly accessible (read only)• Group messaging
  • 47. Learning objectives• Which features are useful, unnecessary or missing• What to include and what not to include in messages originating from team members• How to provide insight for team leaders, managers and directors• How to combine internal and external features into one system
  • 48. Q&A• Questions? Comments?
  • 49. Thank you Bedank