-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convene co-design sessions with Milosh #94
Comments
Proposed times, based on availability and interest at: https://www.when2meet.com/?9700550-srArD |
@infectedroot record this? @benhylau to arrange with Milosh. Move this to handbook. In general, we don't record our meetings, but for workshops/interviews we should have three options in order of preference:
This is a choice of the facilitator/presenter of the session. When possible, closed caption via YouTube, etc. Logistically this will be done via a BBB room, when someone enters there is a disclaimer. |
Milosh will upload final assets before end of year. |
One more document to upload.. |
What doc is still needed? I thought @infectedroot put everything in there? |
This initial comment is collaborative and open to modification by all.
Task Summary
ποΈ Re-ticketed from: #
π Due date: Monday Nov. 30th
π― Success criteria: Toronto Mesh has participated as desired in contributing to Milosh's Service Design project
From Milosh:
My proposal consists of developing several scenarios for the future for Toronto Mesh that can be used to explore possible strategies for expanding the network, ... One approach is to develop these scenarios along a timeline, focusing on specific challenges at each stage of development. For an example, in a first phase, the focus would be on reaching a critical mass of users and how this might be accomplished, while later on, more speculative applications of the network can be explored. A scenario building process entails several general steps, including:
Depending on schedules, this can be done in several ways. One is to have two to three participatory sessions, where we can address the different steps. The first session would include steps 1 and 2, the second 3 and 4. A third would serve to verify the final scenarios, but isnβt strictly necessary, as I can share the finalized scenarios via email for feedback. If it is not possible to do several sessions together, I can conduct individual interviews, going through steps 1-3, then either do one participatory session for step 4, or do step 4 independently and send the results for feedback.
To Do
Evaluate and apply prototype to current objectives(out of scope, will happen over 2021)The text was updated successfully, but these errors were encountered: