https://catechfest.aspirationtech.org/api.php?action=feedcontributions&user=Evelyn&feedformat=atomCalifornia Technology Festival Wiki - User contributions [en]2024-03-28T20:23:06ZUser contributionsMediaWiki 1.35.1https://catechfest.aspirationtech.org/index.php?title=Funding_Technology&diff=663Funding Technology2019-08-08T22:22:20Z<p>Evelyn: </p>
<hr />
<div>Funding Technology: Gunner<br />
<br />
Themes – fundraising, revenue generation, paying for technology<br />
<br />
* Poor economic decisions based on high need in low income communities <br />
* Nonprofits make poor tech decisions best on their need<br />
* Free dropbox, etc. These free tech tools place our data under their control.<br />
* Paying for tech is not about tech is about data. It is your digital power<br />
* Paying for tech should be based on the value and safety and power of your data. <br />
<br />
* We’re being taught tech in superficial terms vs data.<br />
* Smart phones are being used to surveille us<br />
* Social Justice workers are seen as terrorists<br />
* They want us to take the free stuff so they can hack data<br />
* We are headed to digital martial law (already happening in China)<br />
* Supporter lists are on google sheets, etc. they can just freeze and close our accounts<br />
* It’s about “they” (government, corporations) they want to take our data<br />
* They go after “Muslim” and “Black Lives Matter” (Black Identity Extremists, so called)<br />
* Retaining control of your data <br />
* Social Media – IG, implications, lots of nonprofits think that social media will help, per Aspiration it’s important to reach your people<br />
* Aspiration doesn’t put any data down on Facebook- you should not use FB to organize undocumented people <br />
* Data minimization – what you do and don’t ask <br />
* Data Gaps – Grindr allows people to indicate if their HIV+ , this is a big problem – permanent database, Grindr is monetizing that data. <br />
* Google Drive info stays there forever – even if you delete it<br />
* If your adversary is not the government – google is a more secure option<br />
* However government can access anytime via your google addy. Google pushes it out to an intermediary server that the government can access. <br />
* Use the minimum viable amount of tech you can possibly use. <br />
* Learn from your friends – use the tech that your friends use, so you can call on people for assistance<br />
<br />
* Funding tech – tech cost, data cost (it costs money to acquire signatures, doing research, staff time)<br />
* Aspiration runs on Linux system<br />
* Realize the risk of everyone using the same tech<br />
* Open Source technology, software – with Cloud this changed everything, <br />
* Electric Embers.coop alternative to gmail (activist hosting – would they fight if the Feds come for your data)<br />
* Riseup.Net - to join their coop you have to be willing to go to jail and stand up to the feds<br />
* Spread out internationally, to spread info around beyond a particular jurisdiction<br />
* FISA warrants – they can get the data without notifying anyone, however Riseup has a warrant canary b/c they can’t tell individuals that their info was breached<br />
* Government asks google for data 10,000 x’s per year<br />
* Social graph, refers to who you’re connected to is a finger print more precise than your actual finger print – guilt by association (being used as circumstantial evidence)<br />
* Block Chain is the new “e” – Block chain undermines real community connection, also not environmentally sustainability currently using more power than the country of Ireland. <br />
* Nonprofits exist to mitigate the negative externalities of the capitalist system – startup culture presumes that privilege is something you can buy. <br />
* Apple – is exploiting the concept of privacy – at least we understand privacy is something that matters, google says “just trust us”<br />
* Nonprofit work is a cost center <br />
* Freegeek.org -hardware recycling, can turn donating hardware into money <br />
* Pay for tech – learn to tell a new story<br />
* Bury the tech in your grant narrative applications<br />
* Aspiration can help you write grants etc.<br />
* Funding is a fashion show – everyone is into “AI”<br />
* Aspiration model – tech folks billing at market rates for large orgs ($150+/hour), to subsidize pro bono work for nonprofits that can’t pay for tech<br />
* Funding – invert power dynamic, critique the funder, and use the notes in your pitch back out at them<br />
* Talk to a funder like they work for you! I want to understand how you can help us. <br />
* Talk to them like a partner<br />
* Ask them a question they can’t answer, but in a sincere way. <br />
* Don’t act like you “need” it<br />
* Crowdfunding – overhyped, but worth trying because the costs are low.</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Funding_Technology&diff=662Funding Technology2019-08-08T22:22:03Z<p>Evelyn: Created page with "Funding Technology: Gunner Themes – fundraising, revenue generation, paying for technology * Poor economic decisions based on high need in low income communities * Nonpro..."</p>
<hr />
<div>Funding Technology: Gunner<br />
<br />
Themes – fundraising, revenue generation, paying for technology<br />
<br />
* Poor economic decisions based on high need in low income communities <br />
* Nonprofits make poor tech decisions best on their need<br />
** Free dropbox, etc. These free tech tools place our data under their control.<br />
* Paying for tech is not about tech is about data. It is your digital power<br />
* Paying for tech should be based on the value and safety and power of your data. <br />
<br />
* We’re being taught tech in superficial terms vs data.<br />
* Smart phones are being used to surveille us<br />
* Social Justice workers are seen as terrorists<br />
* They want us to take the free stuff so they can hack data<br />
* We are headed to digital martial law (already happening in China)<br />
* Supporter lists are on google sheets, etc. they can just freeze and close our accounts<br />
* It’s about “they” (government, corporations) they want to take our data<br />
* They go after “Muslim” and “Black Lives Matter” (Black Identity Extremists, so called)<br />
* Retaining control of your data <br />
* Social Media – IG, implications, lots of nonprofits think that social media will help, per Aspiration it’s important to reach your people<br />
* Aspiration doesn’t put any data down on Facebook- you should not use FB to organize undocumented people <br />
* Data minimization – what you do and don’t ask <br />
* Data Gaps – Grindr allows people to indicate if their HIV+ , this is a big problem – permanent database, Grindr is monetizing that data. <br />
* Google Drive info stays there forever – even if you delete it<br />
* If your adversary is not the government – google is a more secure option<br />
* However government can access anytime via your google addy. Google pushes it out to an intermediary server that the government can access. <br />
* Use the minimum viable amount of tech you can possibly use. <br />
* Learn from your friends – use the tech that your friends use, so you can call on people for assistance<br />
<br />
* Funding tech – tech cost, data cost (it costs money to acquire signatures, doing research, staff time)<br />
* Aspiration runs on Linux system<br />
* Realize the risk of everyone using the same tech<br />
* Open Source technology, software – with Cloud this changed everything, <br />
* Electric Embers.coop alternative to gmail (activist hosting – would they fight if the Feds come for your data)<br />
* Riseup.Net - to join their coop you have to be willing to go to jail and stand up to the feds<br />
* Spread out internationally, to spread info around beyond a particular jurisdiction<br />
* FISA warrants – they can get the data without notifying anyone, however Riseup has a warrant canary b/c they can’t tell individuals that their info was breached<br />
* Government asks google for data 10,000 x’s per year<br />
* Social graph, refers to who you’re connected to is a finger print more precise than your actual finger print – guilt by association (being used as circumstantial evidence)<br />
* Block Chain is the new “e” – Block chain undermines real community connection, also not environmentally sustainability currently using more power than the country of Ireland. <br />
* Nonprofits exist to mitigate the negative externalities of the capitalist system – startup culture presumes that privilege is something you can buy. <br />
* Apple – is exploiting the concept of privacy – at least we understand privacy is something that matters, google says “just trust us”<br />
* Nonprofit work is a cost center <br />
* Freegeek.org -hardware recycling, can turn donating hardware into money <br />
* Pay for tech – learn to tell a new story<br />
* Bury the tech in your grant narrative applications<br />
* Aspiration can help you write grants etc.<br />
* Funding is a fashion show – everyone is into “AI”<br />
* Aspiration model – tech folks billing at market rates for large orgs ($150+/hour), to subsidize pro bono work for nonprofits that can’t pay for tech<br />
* Funding – invert power dynamic, critique the funder, and use the notes in your pitch back out at them<br />
* Talk to a funder like they work for you! I want to understand how you can help us. <br />
* Talk to them like a partner<br />
* Ask them a question they can’t answer, but in a sincere way. <br />
* Don’t act like you “need” it<br />
* Crowdfunding – overhyped, but worth trying because the costs are low.</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6612019 Los Angeles Agenda2019-07-24T17:34:15Z<p>Evelyn: </p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants are encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Technology for multilingual spaces]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Speed Geeking ==<br />
<br />
Participants presented tools, skills and work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Where From Here ==<br />
<br />
The group paused to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations.<br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Technology_for_multilingual_spaces&diff=660Technology for multilingual spaces2019-07-24T17:31:30Z<p>Evelyn: Created page with "Technology for multilingual spaces breakout Facilitator: Mago Key Takeaways: *+2 Addressing different ways of using technology across generations and cultures so that no on..."</p>
<hr />
<div>Technology for multilingual spaces breakout<br />
<br />
Facilitator: Mago<br />
<br />
Key Takeaways: <br />
*+2 Addressing different ways of using technology across generations and cultures so that no one is excluded.<br />
**Thinking of IT as a language<br />
**Not speaking IT language while also working multilingual communities. → funding/time for IT training <br />
*+4 Resources + funding for interpretation and interpretation equipment + budgeting for interpretation <br />
**Skillsharing + solidarity network <br />
*** Training for bilingual folks (maybe retired?) to become skilled interpreters <br />
*+3 Time/capacity/compensation <br />
*+2 Just compensation for interpreters → shifting the dynamic <br />
**Systemizing our grant applications → keep interpretation as line item in all programs <br />
**Advocating for foundations to have a fund available for orgs to access when interpretation is needed <br />
*** Stats and resources about language justice to advocate<br />
**Hire staffed interpreters for orgs that have regular interpretation needs <br />
*How could Aspiration network advance this issue? <br />
**Start by naming it / sharing the story / the systemic need with foundations<br />
*What tech resources exist that can support multilingual spaces? <br />
**How can technology be of service to facilitating multilingual spaces online specifically? <br />
*** e.g. webinars → How to pull off simultaneous interpretation online?<br />
**Creating multilingual digital networks that can be accessed easily by phone / don’t require a high level of tech skill<br />
<br />
Go around<br />
<br />
M - Journalist <br />
*Learning to embrace my bilingual reality <br />
*How to create multilingual networks of journalists<br />
<br />
G - IDPSCA<br />
*Challenges with language, not just Spanish/English but also tech languages and indigenous languages <br />
*What are resources to improve our communication? <br />
<br />
S<br />
*Volunteers with API LGBTQ org and there are many different languages represented <br />
*How to find translators for materials<br />
*Website tips? <br />
**Google translate bar on <br />
<br />
A - L.A. Co-op Lab <br />
*Creating multilingual digital networks that can be accessed easily by phone / don’t require a high level of tech skill <br />
*S: Members start posting things that are <br />
<br />
Y - Refuge for Families <br />
*How can technology be of service to facilitating multilingual spaces online? <br />
*Works with folks in El Salvador and connects with <br />
<br />
Other challenges:<br />
*Lack of relationships with indigenous interpreters <br />
*For transnational work, people have different ways of speaking about things, need to know nuances<br />
*The way we prioritize language puts Spanish/English translation at the top and often sidelines other immigrant communities <br />
*Staff members who don’t speak the same language</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6592019 Los Angeles Agenda2019-07-24T17:30:54Z<p>Evelyn: /* Collaborative Working Sessions I */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants are encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Technology for multilingual spaces]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants presented tools, skills and work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group paused to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations.<br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Challenges_and_best_practices_for_managing_multilingual_work&diff=658Challenges and best practices for managing multilingual work2019-07-24T17:29:17Z<p>Evelyn: </p>
<hr />
<div>Technology for multilingual spaces breakout<br />
<br />
Facilitator: Mago<br />
<br />
Key Takeaways: <br />
*+2 Addressing different ways of using technology across generations and cultures so that no one is excluded.<br />
**Thinking of IT as a language<br />
**Not speaking IT language while also working multilingual communities. → funding/time for IT training <br />
*+4 Resources + funding for interpretation and interpretation equipment + budgeting for interpretation <br />
**Skillsharing + solidarity network <br />
*** Training for bilingual folks (maybe retired?) to become skilled interpreters <br />
*+3 Time/capacity/compensation <br />
*+2 Just compensation for interpreters → shifting the dynamic <br />
**Systemizing our grant applications → keep interpretation as line item in all programs <br />
**Advocating for foundations to have a fund available for orgs to access when interpretation is needed <br />
*** Stats and resources about language justice to advocate<br />
**Hire staffed interpreters for orgs that have regular interpretation needs <br />
*How could Aspiration network advance this issue? <br />
**Start by naming it / sharing the story / the systemic need with foundations<br />
*What tech resources exist that can support multilingual spaces? <br />
**How can technology be of service to facilitating multilingual spaces online specifically? <br />
*** e.g. webinars → How to pull off simultaneous interpretation online?<br />
**Creating multilingual digital networks that can be accessed easily by phone / don’t require a high level of tech skill<br />
<br />
Go around<br />
<br />
M - Journalist <br />
*Learning to embrace my bilingual reality <br />
*How to create multilingual networks of journalists<br />
<br />
G - IDPSCA<br />
*Challenges with language, not just Spanish/English but also tech languages and indigenous languages <br />
*What are resources to improve our communication? <br />
<br />
S<br />
*Volunteers with API LGBTQ org and there are many different languages represented <br />
*How to find translators for materials<br />
*Website tips? <br />
**Google translate bar on <br />
<br />
A - L.A. Co-op Lab <br />
*Creating multilingual digital networks that can be accessed easily by phone / don’t require a high level of tech skill <br />
*S: Members start posting things that are <br />
<br />
Y - Refuge for Families <br />
*How can technology be of service to facilitating multilingual spaces online? <br />
*Works with folks in El Salvador and connects with <br />
<br />
Other challenges:<br />
*Lack of relationships with indigenous interpreters <br />
*For transnational work, people have different ways of speaking about things, need to know nuances<br />
*The way we prioritize language puts Spanish/English translation at the top and often sidelines other immigrant communities <br />
*Staff members who don’t speak the same language</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Challenges_and_best_practices_for_managing_multilingual_work&diff=657Challenges and best practices for managing multilingual work2019-07-24T17:28:29Z<p>Evelyn: </p>
<hr />
<div>Technology for multilingual spaces breakout<br />
<br />
Facilitator: Mago<br />
<br />
Key Takeaways: <br />
<br />
*+2 Addressing different ways of using technology across generations and cultures so that no one is excluded.<br />
<br />
**Thinking of IT as a language<br />
<br />
**Not speaking IT language while also working multilingual communities. → funding/time for IT training <br />
<br />
*+4 Resources + funding for interpretation and interpretation equipment + budgeting for interpretation <br />
<br />
**Skillsharing + solidarity network <br />
<br />
*** Training for bilingual folks (maybe retired?) to become skilled interpreters <br />
<br />
*+3 Time/capacity/compensation <br />
<br />
*+2 Just compensation for interpreters → shifting the dynamic <br />
<br />
**Systemizing our grant applications → keep interpretation as line item in all programs <br />
<br />
**Advocating for foundations to have a fund available for orgs to access when interpretation is needed <br />
<br />
*** Stats and resources about language justice to advocate<br />
<br />
**Hire staffed interpreters for orgs that have regular interpretation needs <br />
<br />
*How could Aspiration network advance this issue? <br />
<br />
**Start by naming it / sharing the story / the systemic need with foundations<br />
<br />
*What tech resources exist that can support multilingual spaces? <br />
<br />
**How can technology be of service to facilitating multilingual spaces online specifically? <br />
<br />
*** e.g. webinars → How to pull off simultaneous interpretation online?<br />
<br />
**Creating multilingual digital networks that can be accessed easily by phone / don’t require a high level of tech skill<br />
<br />
Go around<br />
<br />
M - Journalist <br />
<br />
*Learning to embrace my bilingual reality <br />
<br />
*How to create multilingual networks of journalists<br />
<br />
G - IDPSCA<br />
<br />
*Challenges with language, not just Spanish/English but also tech languages and indigenous languages <br />
<br />
*What are resources to improve our communication? <br />
<br />
S<br />
<br />
*Volunteers with API LGBTQ org and there are many different languages represented <br />
<br />
*How to find translators for materials<br />
<br />
*Website tips? <br />
<br />
**Google translate bar on <br />
<br />
A - L.A. Co-op Lab <br />
<br />
*Creating multilingual digital networks that can be accessed easily by phone / don’t require a high level of tech skill <br />
<br />
*S: Members start posting things that are <br />
<br />
Y - Refuge for Families <br />
<br />
*How can technology be of service to facilitating multilingual spaces online? <br />
<br />
*Works with folks in El Salvador and connects with <br />
<br />
Other challenges:<br />
<br />
*Lack of relationships with indigenous interpreters <br />
<br />
*For transnational work, people have different ways of speaking about things, need to know nuances<br />
<br />
*The way we prioritize language puts Spanish/English translation at the top and often sidelines other immigrant communities <br />
<br />
*Staff members who don’t speak the same language</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=CRM_Tracking_leadership_development&diff=656CRM Tracking leadership development2019-07-24T17:24:40Z<p>Evelyn: </p>
<hr />
<div>Recap: We had a really robust conversation on constituent relationship management systems, which are used to track interactions between the organization and its base, which can be members/volunteers/donors, etc. <br />
<br />
1. An effective database builds up a picture of your constituents, both on individual level and big picture. You’ll need to decide what data you want to collect, and note the variability of contact info for marginalized communities<br />
<br />
2. It might be helpful to ask staff/Board/volunteers what changes you’re hoping to see/ accomplish (behavior, attitude, action).<br />
<br />
3. Differentiate what data is important for your organization and what is important to funders; it is equally important to collect both. <br />
<br />
4. When switching CRM’s or tweaking your current system to work better for you, onboard new staff, establish clarity of process and expectations, and create a rudimentary guide showing how to accomplish top tasks. <br />
<br />
<br />
What Brings You to this Session? <br />
* Nancy (IDEPSCA): <br />
** Starting to use Powerbase; wants to talk about the shift of using a new CRM <br />
** Other issues: reporting back to funders, tracking data takes time and effort, big accomplishments over time get lost<br />
** Jazmyn designed Powerbase for previous org, can help Nancy.<br />
<br />
* Shirley (API Equality LA)<br />
** Looking to synthesize communications & donor tracking in 1 software <br />
<br />
* Tiffany (UC Santa Cruz)<br />
** Nonprofit serves population of 1600 people and has a five-person Board. <br />
** Wants to learn how to store personal contact info safely, alternatives to Google Contacts <br />
<br />
* Jazmyn<br />
** Has a research/data background, currently bringing that knowledge to nonprofits in how to tell deeper stories and trends that data shows, has dealt with a lot of pushback from leadership not recognizing the value of data<br />
<br />
* Lisa <br />
** After Leadership Tracking seminar, the next logical step is to talk about how/where nonprofit data is stored <br />
** What interests Lisa is the data model, or structure of the information you need to collect and how they’re related to each other<br />
Discussion Topic 1: What would a database need or have in order to be effective? <br />
* It tracks something about people over time that involves collection of information from them<br />
* Ideally, it presents a holistic view of person/constituent, so staff/volunteers can look for themes and changes in individual growth, as well as a big-picture of the organization.<br />
** Example: - If someone comes to a membership meetings every month, that paints a really compelling story about their involvement. <br />
* Log every storytelling/relationship building activity (meetings, 1:1’s) – anything substantial.<br />
<br />
Discussion Topic 2: What questions should we be asking to collect good data?<br />
* Start with staff/volunteers: what changes do you want to see, what are you hoping to accomplish? Is it a behavior, attitude, or action? (Then, figure out your data collection method. Otherwise, you’ll be stuck with generic info like attendance.)<br />
* A follow up question for staff might be: what ladder of development opportunities are you offering for members of your organization?<br />
* How difficult is it to get to our event? How motivated are you to attend our events? What is your impression of X? <br />
* A lot of qualitative data lives internally within staff, volunteers, etc. Therefore, think about how to frame better questions to get rich story of constituents/members. <br />
* When intentionally collecting stories, ask “how does you current work relate to what you did with us X years ago?” Example: alumni tracking<br />
<br />
Discussion Topic 3: Data Analysis <br />
* You can do a word analysis and see which words/ themes are being most used.<br />
* When analyzing your data and impact, if you see that Person A and Person B have the same impact/result but have followed a widely different “ladder of engagement,” reassess your ladder. If skillset gained does not match up to activities to get there, evaluate program. <br />
* Capacity to do analysis is an ongoing issue. It has to be made a consistent priority. Clarity of process and expectations helps. Have the person you’re training use their notes to create a rudimentary process guide or top 5 tasks guide. <br />
<br />
Discussion Topic 4: What are the different CRM’s out there?<br />
* Saas can create mind maps but it needs the data behind it.<br />
* Atlas is a research tool. <br />
* Bloomerang is a CRM<br />
* Powerbase does have a volunteer tracking tool, it can track phonebank shifts or hours tracking. <br />
<br />
Discussion Topic 5: Qualitative vs. Quantitative Data<br />
* Most CRM’s don’t analyze your data for you, they only facilitate it so that you can perform your analysis.<br />
* Numbers don’t tell the full story to funders and the general public – stories do. Funders usually dictate how they want to see your data, but if we keep demanding stories over “hard numbers,” the world will eventually shift. <br />
** Example: IDEPSCA has a group of 15 workers who have been involved and active for X years consistently; even though it is a “small” number, the years of involvement tell a bigger story based on lifestyles/how hard it is for them to be involved. <br />
<br />
Discussion Topic 6: Making the switch to a new CRM<br />
* People often transition out of an organization before they get to document the important relational stuff, especially when working with marginalized communities.<br />
* With turnover, you can lose historical year-to-year information and/or have variable contact information, especially when working with marginalized communities.<br />
* Make it a priority to onboard staff/teach the important information to track. <br />
** Make sure your onboarding/database teaching is inclusive: a lot of people would rather watch a video than read a manual. To make your own video, record your computer screen doing database tasks while recording your voice.<br />
* When making the switch from paper to database, collect data/surveys on paper first, and then transfer data into the database at a convenient date, maybe via intern. Another option would be to use text recognition software exists. <br />
* Pinpoint what information is important for you and what funders want to know. Each are equally important.</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6552019 Los Angeles Agenda2019-07-24T17:13:14Z<p>Evelyn: /* Collaborative Working Sessions II */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants are encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants presented tools, skills and work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group paused to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations.<br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Facilitative_leadership_development_conversation_continued&diff=654Facilitative leadership development conversation continued2019-07-24T17:12:40Z<p>Evelyn: </p>
<hr />
<div>'''Tracking leadership development'''<br />
<br />
'''Why we are here'''<br />
<br />
* Our failed attempts at tracking this were driven by funder ideas/wants that were not connected to what was important to the community. Engagement not leadership. Higher end was political actions, lower end were community events--membership event participation were not tracked as a whole story, every month for 12 months.<br />
* Ladder/web/grid of engagement--want to know what practices people have used to ID where folks are at, where folks can be moved "up" or "sideways", what metrics people have used. Also HOW and actual mechanisms for tracking that are not linear/one-dimensional, like assigning points to signing a petition etc. Ladder, grid, web, etc.<br />
* Echo all this, esp tracking driven by fundable actions. We use Bloomerang (CRM) to track this. We track events that people attend and use the # of how many events they have attended to design our outreach, it's not working ok but could be a lot better. Also use RSPV forms. This is more engagement than leadership. Not tracked but think about it in a relational way--who knows who, what their interests are, what they want to do.<br />
* How do we systematize recording and analysis of this relational stuff?<br />
* New frontier in program to track leaders. Right now there is a form people fill out re their experiences with the leadership. Just a start. Lack of understanding of what leadership is doing? Mission is to empower students to use tech tools for social justice. Interested in the leadership of the program not the students bc that is taken care of in other ways<br />
* How do you grow in the work that you are doing? How do organizations transmit leadership to the communities they work with? 99Rootz talked about it yesterday. They are seeing high schoolers talk more about themselves and their work and that is sign of growth. More expansive ways of thinking about leadership. Finding your own voice. We also need that inside our organizations. Building confidence and participation. When we can transform our organizations, change hierarchies, when more voices are on the table regardless of the size org.<br />
* At my org we do a lot of tracking but it's not consistent. We do check ins with youth and have a form, have been able to ID different leadership skills they have and what they want to learn. Some are phone banking, some are mobilizing, some are public speaking. We go through the sheet of skills and show it to them and ask where they want to grow, check in emotionally and academically. Then we type it up and it gets lost in the digital world. How we publicize it to funders is through education rates, where they are going to higher ed and jobs. Wheere we have not done a good job is distinguishing leadership and organizing. Leader and front face and the work that organizers do. We are trying to develop long term community organizers. IN the parent component we don't do check ins, we track their leadership via attendance at events. Forms and spreadsheets. We don't follow up about what they learned. Parents don't age out of the program the way youth do, parents are long term. We need a different tool, more like what we do with the youth. There is no culmination like graduation with adult development, we need different metrics. FUnders want numbers. How do we develop parents to be community organizers and be the best community organizers ever. We also try to measure their comprehension of our campaigns. If they don't understand our work we need to get ourselves together. Where are we lacking in involving youth and parents in our larger work. Making sure we are prepping folks to talk about our work. HR is also underdeveloped so staff development is super disconnected. Review and reflection is imporant to continued growth!<br />
* Tracking adult development. Seen many orgs going courses for adults, diplomas for courses/certificates etc. Something you can count and that they can show for their efforts.<br />
<br />
'''General discussion'''<br />
<br />
* How did your evaluation work?<br />
* Based off of professionalism, working in coalition, and my own goals. Supervisor did survey based on my performance. I would have liked it to include a self-evaluation as well. It was great to hear his feedback but it was a missed opportunity. Any time for employees to reflect on their goals/role/opportunities for growth is ideal. Share ideas with other staff.<br />
* Put professional development in workplans, budgets, staff meetings (for the latter, time to discuss opportunities with each other)<br />
* Using belts/badges/milestones that people reach. Makes people feel good to reach things.<br />
* Using something like strengths-finder to ID and cultivate strengths/paths for leadership. This can also support matching people to work on stuff together.<br />
* Milestones for growth<br />
* Skills inventories that people fill out every 6th months, with where are you at with all these and where do you want to focus your growth? This can yield interesting longitudinal and individual data, can tell a story and also invite reflection for growth<br />
* Capacity for tracking is a real issue. Needs to be a conversation. Articulate the value of the data collection.<br />
* Having participants do their own entry via a form. THen you can do analysis/ID for outreach on the back end.<br />
* How to measure community outreach done by others/connections to people so that people's work on behalf of your org can be acknowledged<br />
* Aspiration's hypothesis is 1) tech skills lead to leadership development in orgs and networks and 2) participatory methods and facilitation skills lead to leadership development. These can be applied to people at every level of an org, not just leadership. Having these skills makes you valuable to an org. Tech capacity building is the carrot for leadership development. Very tactical skills. Then people use these skills in ways that elevate them within the organization. Cultivate people recognizing their own power. We can measure this by growth of skills and within the org.<br />
* We ID people in our networks who have the "spark" around participatory methods/frameworks and try to work with them to learn from them and bring them closer, elevating them within the network so the whole network becomes more participatory.<br />
* One to one, within an org, within a network <--this is how we scale/talk to funders about scale. We only call it leadership development when we need to for a grant.<br />
* Where is the space for conflict resolution/creative problem solving in this?<br />
* Great Q! People often are bringing those skills already (part of the spark?) We can also tap into our networks about that. Connect with people who can train on that, we don't focus on it.<br />
* Managing group dynamics/conflict is also important to facilitation<br />
* Could get better at managing vulnerability/supporting people's growth<br />
* Challenge: How do you track leadership development when people move around organizationally? We WANT people to go other places!<br />
* Alumni tracking--retain relationships and have people report back to you<br />
* Case management as a model. But this is can be heavy systems burden.<br />
* Are there sector-wide metrics we could track about how our ideas are taking root?<br />
* Story collection/story banking<br />
* We all take what we have learned, the good and the bad, with us when we move on<br />
* What does it mean to be developing leadership in a freelance context/without an organization?<br />
* There is an underrated social/relational element of leadership development</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Facilitative_leadership_development_conversation_continued&diff=653Facilitative leadership development conversation continued2019-07-24T17:12:23Z<p>Evelyn: Created page with "'''Tracking leadership development''' '''Why we are here''' * Our failed attempts at tracking this were driven by funder ideas/wants that were not connected to what was impo..."</p>
<hr />
<div>'''Tracking leadership development'''<br />
<br />
'''Why we are here'''<br />
<br />
* Our failed attempts at tracking this were driven by funder ideas/wants that were not connected to what was important to the community. Engagement not leadership. Higher end was political actions, lower end were community events--membership event participation were not tracked as a whole story, every month for 12 months.<br />
* Ladder/web/grid of engagement--want to know what practices people have used to ID where folks are at, where folks can be moved "up" or "sideways", what metrics people have used. Also HOW and actual mechanisms for tracking that are not linear/one-dimensional, like assigning points to signing a petition etc. Ladder, grid, web, etc.<br />
* Echo all this, esp tracking driven by fundable actions. We use Bloomerang (CRM) to track this. We track events that people attend and use the # of how many events they have attended to design our outreach, it's not working ok but could be a lot better. Also use RSPV forms. This is more engagement than leadership. Not tracked but think about it in a relational way--who knows who, what their interests are, what they want to do.<br />
* How do we systematize recording and analysis of this relational stuff?<br />
* New frontier in program to track leaders. Right now there is a form people fill out re their experiences with the leadership. Just a start. Lack of understanding of what leadership is doing? Mission is to empower students to use tech tools for social justice. Interested in the leadership of the program not the students bc that is taken care of in other ways<br />
* How do you grow in the work that you are doing? How do organizations transmit leadership to the communities they work with? 99Rootz talked about it yesterday. They are seeing high schoolers talk more about themselves and their work and that is sign of growth. More expansive ways of thinking about leadership. Finding your own voice. We also need that inside our organizations. Building confidence and participation. When we can transform our organizations, change hierarchies, when more voices are on the table regardless of the size org.<br />
* At my org we do a lot of tracking but it's not consistent. We do check ins with youth and have a form, have been able to ID different leadership skills they have and what they want to learn. Some are phone banking, some are mobilizing, some are public speaking. We go through the sheet of skills and show it to them and ask where they want to grow, check in emotionally and academically. Then we type it up and it gets lost in the digital world. How we publicize it to funders is through education rates, where they are going to higher ed and jobs. Wheere we have not done a good job is distinguishing leadership and organizing. Leader and front face and the work that organizers do. We are trying to develop long term community organizers. IN the parent component we don't do check ins, we track their leadership via attendance at events. Forms and spreadsheets. We don't follow up about what they learned. Parents don't age out of the program the way youth do, parents are long term. We need a different tool, more like what we do with the youth. There is no culmination like graduation with adult development, we need different metrics. FUnders want numbers. How do we develop parents to be community organizers and be the best community organizers ever. We also try to measure their comprehension of our campaigns. If they don't understand our work we need to get ourselves together. Where are we lacking in involving youth and parents in our larger work. Making sure we are prepping folks to talk about our work. HR is also underdeveloped so staff development is super disconnected. Review and reflection is imporant to continued growth!<br />
* Tracking adult development. Seen many orgs going courses for adults, diplomas for courses/certificates etc. Something you can count and that they can show for their efforts.<br />
<br />
'''General discussion'''<br />
<br />
* How did your evaluation work?<br />
* Based off of professionalism, working in coalition, and my own goals. Supervisor did survey based on my performance. I would have liked it to include a self-evaluation as well. It was great to hear his feedback but it was a missed opportunity. Any time for employees to reflect on their goals/role/opportunities for growth is ideal. Share ideas with other staff.<br />
* Put professional development in workplans, budgets, staff meetings (for the latter, time to discuss opportunities with each other)<br />
* Using belts/badges/milestones that people reach. Makes people feel good to reach things.<br />
* Using something like strengths-finder to ID and cultivate strengths/paths for leadership. This can also support matching people to work on stuff together.<br />
* Milestones for growth<br />
* Skills inventories that people fill out every 6th months, with where are you at with all these and where do you want to focus your growth? This can yield interesting longitudinal and individual data, can tell a story and also invite reflection for growth<br />
* Capacity for tracking is a real issue. Needs to be a conversation. Articulate the value of the data collection.<br />
* Having participants do their own entry via a form. THen you can do analysis/ID for outreach on the back end.<br />
* How to measure community outreach done by others/connections to people so that people's work on behalf of your org can be acknowledged<br />
* Aspiration's hypothesis is 1) tech skills lead to leadership development in orgs and networks and 2) participatory methods and facilitation skills lead to leadership development. These can be applied to people at every level of an org, not just leadership. Having these skills makes you valuable to an org. Tech capacity building is the carrot for leadership development. Very tactical skills. Then people use these skills in ways that elevate them within the organization. Cultivate people recognizing their own power. We can measure this by growth of skills and within the org.<br />
* We ID people in our networks who have the "spark" around participatory methods/frameworks and try to work with them to learn from them and bring them closer, elevating them within the network so the whole network becomes more participatory.<br />
* One to one, within an org, within a network <--this is how we scale/talk to funders about scale. We only call it leadership development when we need to for a grant.<br />
* Where is the space for conflict resolution/creative problem solving in this?<br />
* Great Q! People often are bringing those skills already (part of the spark?) We can also tap into our networks about that. Connect with people who can train on that, we don't focus on it.<br />
* Managing group dynamics/conflict is also important to facilitation<br />
* Could get better at managing vulnerability/supporting people's growth<br />
* Challenge: How do you track leadership development when people move around organizationally? We WANT people to go other places!<br />
* Alumni tracking--retain relationships and have people report back to you<br />
* Case management as a model. But this is can be heavy systems burden.<br />
* Are there sector-wide metrics we could track about how our ideas are taking root?<br />
* Story collection/story banking<br />
* We all take what we have learned, the good and the bad, with us when we move on<br />
* What does it mean to be developing leadership in a freelance context/without an organization?<br />
* There is an underrated social/relational element of leadership development</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=CRM_Tracking_leadership_development&diff=652CRM Tracking leadership development2019-07-24T17:12:09Z<p>Evelyn: Blanked the page</p>
<hr />
<div></div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6512019 Los Angeles Agenda2019-07-24T16:35:11Z<p>Evelyn: /* Collaborative Working Sessions I */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants are encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty (pending)<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants presented tools, skills and work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group paused to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations.<br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6502019 Los Angeles Agenda2019-07-24T16:34:33Z<p>Evelyn: /* Speed Geeking */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants are encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty (pending)<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants presented tools, skills and work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group paused to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations.<br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6492019 Los Angeles Agenda2019-07-24T16:33:10Z<p>Evelyn: /* Speed Geeking */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants are encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty (pending)<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants presented and shared work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group paused to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations.<br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6482019 Los Angeles Agenda2019-07-24T16:32:47Z<p>Evelyn: /* Where From Here */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants are encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty (pending)<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group paused to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations.<br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6472019 Los Angeles Agenda2019-07-24T16:32:18Z<p>Evelyn: /* Collaborative Working SessionsIII */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants are encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty (pending)<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6462019 Los Angeles Agenda2019-07-24T16:31:59Z<p>Evelyn: /* Collaborative Working Sessions II */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants are encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants chose from 5-7 working groups, and were welcomed to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty (pending)<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6452019 Los Angeles Agenda2019-07-24T16:31:03Z<p>Evelyn: /* Lunch */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants are encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty (pending)<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6442019 Los Angeles Agenda2019-07-24T16:30:51Z<p>Evelyn: /* Stories from Across LA and Around the State */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants engaged in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants will be encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty (pending)<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6432019 Los Angeles Agenda2019-07-24T16:30:33Z<p>Evelyn: /* Welcome and Opening Circle */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event started with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants will engage in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants will be encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty (pending)<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=All_about_worker-owned_cooperatives&diff=642All about worker-owned cooperatives2019-07-24T16:30:05Z<p>Evelyn: </p>
<hr />
<div>'''Day 2 Afternoon Session: Worker Owned Co-ops'''<br />
<br />
Find tech co-ops to hire: techworker.coop<br />
<br />
*It’s also a network for tech co-ops to join/share resources <br />
<br />
<br />
Co-ops are businesses. Not non-profit. Owned by workers. Vote on management. Pay vs investment. LA Coop Lab teaches in LA. Your introduction point depends on where you are in co-op organizing. El Centro promote co-ops. Business trainings. Different little co-ops sitting each other now. El Markedito Carousel. Cooperacion Central. Land Trust forming. Getting access to a public lot for community land trust. City is pro-gentrification, pro-police, anti-people.<br />
<br />
Lots of people like having idea of no boss. Community is collective boss -- collaboration is imperative. Member vesting. Patronage and vote come after this meeting period. Vote in new members. Some majority vote, some consensus (like new member acceptance). It's really hard to fire an owner. Owners have different rights than workers. Smaller is easier. <br />
<br />
Wanted infrastructure to have more employees. Hired too many people -- big mistake. New hires displaced earlier members. Trickier politics. Didn't have capacity to build proper relationships with so many new workers. Power dynamics and rifts exploded due to conflict avoidance. Hard to ease new people into old conversations.<br />
<br />
<br />
Zingerman’s <br />
<br />
*Books on co-ops<br />
<br />
Andrea from Design Action Collective -- web development/design worker owned co-op<br />
<br />
*Established “points of unity” <br />
*Only works with social justice and environmental justice organizations<br />
*Design Action Collective is happy to share experiences and tools with folks who want to start co-ops (e.g. bylaws etc) <br />
*Design Action Collective is a part of a union.<br />
*Design Action Collective. 40 years. Spin-off 3 years ago. Inherited bylaws, structure, added as new people come on. Cultural not just paper. Web development and tech harder to standardize than print. Co-ops are path to liberation. Point of reference to start thinking about own co-op business.<br />
*Goal to share learning experience about Co-op organization. <br />
<br />
<br />
The Working World is a radical lender that brought together co-op developers across the country who then developed a national financial co-operative called Seed Commons<br />
<br />
*L.A. Co-op Lab is a member of the financial co-operative and can help folks apply for financing (patient/non-extractive lending) <br />
<br />
<br />
What to do if you want to start a co-op? <br />
<br />
*Find a co-op developer in your city<br />
** In L.A.? → go to L.A. Co-op Lab<br />
** Santa Ana → Cooperación Santa Ana (part of a larger movement resisting gentrification in Santa Ana that also recently formed a land trust) <br />
<br />
<br />
What have you done to spread the word about co-ops? <br />
<br />
*Have parties, build the network <br />
*Hire co-ops for things and tell people about them (bookkeeping etc) <br />
<br />
<br />
Decision making process<br />
<br />
*At Design Action Collective: Processes to become a worker owner is 9 months as a regular employee. All worker owners have to be on board in order to vote in a new member.<br />
*In regular meetings DAC uses 1 person 1 vote decision making, simple majority. Certain decisions require quorum. <br />
*DAC is 6 owner members and 4 workers in the membership track <br />
*Approval voting and score voting are other options for decision making <br />
<br />
<br />
Challenges: <br />
<br />
*Health care plans / retirement plans / Mental health plan <br />
*Taking on new worker owners (don’t hire too many people at once) <br />
*Power dynamics that develop over the years → people have internalized racism/misogyny etc./ work patterns → at some point it might blow up<br />
<br />
<br />
Advantages<br />
<br />
*Book, “Lost Connections” By Johan Hari on social determinants of depression: <br />
**Mental health tied to work environment<br />
**Co-op as an anecdote to depression meaningless work</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=All_about_worker-owned_cooperatives&diff=641All about worker-owned cooperatives2019-07-24T16:29:46Z<p>Evelyn: </p>
<hr />
<div>'''Day 2 Afternoon Session: Worker Owned Co-ops'''<br />
<br />
Find tech co-ops to hire: techworker.coop<br />
<br />
*It’s also a network for tech co-ops to join/share resources <br />
<br />
<br />
Co-ops are businesses. Not non-profit. Owned by workers. Vote on management. Pay vs investment. LA Coop Lab teaches in LA. Your introduction point depends on where you are in co-op organizing. El Centro promote co-ops. Business trainings. Different little co-ops sitting each other now. El Markedito Carousel. Cooperacion Central. Land Trust forming. Getting access to a public lot for community land trust. City is pro-gentrification, pro-police, anti-people.<br />
<br />
Lots of people like having idea of no boss. Community is collective boss -- collaboration is imperative. Member vesting. Patronage and vote come after this meeting period. Vote in new members. Some majority vote, some consensus (like new member acceptance). It's really hard to fire an owner. Owners have different rights than workers. Smaller is easier. <br />
<br />
Wanted infrastructure to have more employees. Hired too many people -- big mistake. New hires displaced earlier members. Trickier politics. Didn't have capacity to build proper relationships with so many new workers. Power dynamics and rifts exploded due to conflict avoidance. Hard to ease new people into old conversations.<br />
<br />
<br />
Zingerman’s <br />
<br />
*Books on co-ops<br />
<br />
Andrea from Design Action Collective -- web development/design worker owned co-op<br />
<br />
*Established “points of unity” <br />
*Only works with social justice and environmental justice organizations<br />
*Design Action Collective is happy to share experiences and tools with folks who want to start co-ops (e.g. bylaws etc) <br />
*Design Action Collective is a part of a union.<br />
*Design Action Collective. 40 years. Spin-off 3 years ago. Inherited bylaws, structure, added as new people come on. Cultural not just paper. Web development and tech harder to standardize than print. Co-ops are path to liberation. Point of reference to start thinking about own co-op business.<br />
*Goal to share learning experience about Co-op organization. <br />
<br />
The Working World is a radical lender that brought together co-op developers across the country who then developed a national financial co-operative called Seed Commons<br />
<br />
*L.A. Co-op Lab is a member of the financial co-operative and can help folks apply for financing (patient/non-extractive lending) <br />
<br />
What to do if you want to start a co-op? <br />
<br />
*Find a co-op developer in your city<br />
** In L.A.? → go to L.A. Co-op Lab<br />
** Santa Ana → Cooperación Santa Ana (part of a larger movement resisting gentrification in Santa Ana that also recently formed a land trust) <br />
<br />
<br />
What have you done to spread the word about co-ops? <br />
<br />
*Have parties, build the network <br />
*Hire co-ops for things and tell people about them (bookkeeping etc) <br />
<br />
<br />
Decision making process<br />
<br />
*At Design Action Collective: Processes to become a worker owner is 9 months as a regular employee. All worker owners have to be on board in order to vote in a new member.<br />
*In regular meetings DAC uses 1 person 1 vote decision making, simple majority. Certain decisions require quorum. <br />
*DAC is 6 owner members and 4 workers in the membership track <br />
*Approval voting and score voting are other options for decision making <br />
<br />
<br />
Challenges: <br />
<br />
*Health care plans / retirement plans / Mental health plan <br />
*Taking on new worker owners (don’t hire too many people at once) <br />
*Power dynamics that develop over the years → people have internalized racism/misogyny etc./ work patterns → at some point it might blow up<br />
<br />
<br />
Advantages<br />
<br />
*Book, “Lost Connections” By Johan Hari on social determinants of depression: <br />
**Mental health tied to work environment<br />
**Co-op as an anecdote to depression meaningless work</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=All_about_worker-owned_cooperatives&diff=640All about worker-owned cooperatives2019-07-24T16:29:29Z<p>Evelyn: Created page with "'''Day 2 Afternoon Session: Worker Owned Co-ops''' Find tech co-ops to hire: techworker.coop *It’s also a network for tech co-ops to join/share resources Co-ops are bus..."</p>
<hr />
<div>'''Day 2 Afternoon Session: Worker Owned Co-ops'''<br />
<br />
Find tech co-ops to hire: techworker.coop<br />
<br />
*It’s also a network for tech co-ops to join/share resources <br />
<br />
<br />
Co-ops are businesses. Not non-profit. Owned by workers. Vote on management. Pay vs investment. LA Coop Lab teaches in LA. Your introduction point depends on where you are in co-op organizing. El Centro promote co-ops. Business trainings. Different little co-ops sitting each other now. El Markedito Carousel. Cooperacion Central. Land Trust forming. Getting access to a public lot for community land trust. City is pro-gentrification, pro-police, anti-people.<br />
<br />
Lots of people like having idea of no boss. Community is collective boss -- collaboration is imperative. Member vesting. Patronage and vote come after this meeting period. Vote in new members. Some majority vote, some consensus (like new member acceptance). It's really hard to fire an owner. Owners have different rights than workers. Smaller is easier. <br />
<br />
Wanted infrastructure to have more employees. Hired too many people -- big mistake. New hires displaced earlier members. Trickier politics. Didn't have capacity to build proper relationships with so many new workers. Power dynamics and rifts exploded due to conflict avoidance. Hard to ease new people into old conversations.<br />
<br />
<br />
Zingerman’s <br />
<br />
*Books on co-ops<br />
<br />
Andrea from Design Action Collective -- web development/design worker owned co-op<br />
<br />
*Established “points of unity” <br />
*Only works with social justice and environmental justice organizations<br />
*Design Action Collective is happy to share experiences and tools with folks who want to start co-ops (e.g. bylaws etc) <br />
*Design Action Collective is a part of a union.<br />
*Design Action Collective. 40 years. Spin-off 3 years ago. Inherited bylaws, structure, added as new people come on. Cultural not just paper. Web development and tech harder to standardize than print. Co-ops are path to liberation. Point of reference to start thinking about own co-op business.<br />
*Goal to share learning experience about Co-op organization. <br />
<br />
The Working World is a radical lender that brought together co-op developers across the country who then developed a national financial co-operative called Seed Commons<br />
<br />
*L.A. Co-op Lab is a member of the financial co-operative and can help folks apply for financing (patient/non-extractive lending) <br />
<br />
What to do if you want to start a co-op? <br />
<br />
*Find a co-op developer in your city<br />
** In L.A.? → go to L.A. Co-op Lab<br />
** Santa Ana → Cooperación Santa Ana (part of a larger movement resisting gentrification in Santa Ana that also recently formed a land trust) <br />
<br />
<br />
What have you done to spread the word about co-ops? <br />
<br />
*Have parties, build the network <br />
*Hire co-ops for things and tell people about them (bookkeeping etc) <br />
<br />
<br />
Decision making process<br />
<br />
*At Design Action Collective: Processes to become a worker owner is 9 months as a regular employee. All worker owners have to be on board in order to vote in a new member.<br />
*In regular meetings DAC uses 1 person 1 vote decision making, simple majority. Certain decisions require quorum. <br />
*DAC is 6 owner members and 4 workers in the membership track <br />
*Approval voting and score voting are other options for decision making <br />
<br />
<br />
Challenges: <br />
<br />
*Health care plans / retirement plans / Mental health plan <br />
*Taking on new worker owners (don’t hire too many people at once) <br />
*Power dynamics that develop over the years → people have internalized racism/misogyny etc./ work patterns → at some point it might blow up<br />
<br />
Advantages<br />
<br />
*Book, “Lost Connections” By Johan Hari on social determinants of depression: <br />
**Mental health tied to work environment<br />
**Co-op as an anecdote to depression meaningless work</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Managing_burnout&diff=639Managing burnout2019-07-24T16:24:09Z<p>Evelyn: Created page with "Session off the record."</p>
<hr />
<div>Session off the record.</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6382019 Los Angeles Agenda2019-07-24T16:23:49Z<p>Evelyn: /* Collaborative Working Sessions II */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event will start with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants will engage in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants will be encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty (pending)<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6372019 Los Angeles Agenda2019-07-24T16:23:30Z<p>Evelyn: /* Collaborative Working Sessions I */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event will start with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants will engage in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants will be encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner (pending)<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Storytelling_as_a_tool_for_reaching_our_goals&diff=636Storytelling as a tool for reaching our goals2019-07-24T16:16:07Z<p>Evelyn: Created page with "Session off the record."</p>
<hr />
<div>Session off the record.</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Deep_resistance&diff=635Deep resistance2019-07-24T16:15:28Z<p>Evelyn: Created page with "Session of the record."</p>
<hr />
<div>Session of the record.</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Facilitative_leadership&diff=633Facilitative leadership2019-07-23T22:57:50Z<p>Evelyn: Created page with " * Self Reflection ** On a piece of paper reflect (write, draw, doodle, etc.,) on a time that you experienced facilitative leadership * Principles of facilitative leadership *..."</p>
<hr />
<div><br />
* Self Reflection<br />
** On a piece of paper reflect (write, draw, doodle, etc.,) on a time that you experienced facilitative leadership<br />
* Principles of facilitative leadership<br />
** Collective input to get to a collective outcome<br />
** Creating space for creative freedom<br />
** Listening<br />
** Take responsibility<br />
*** For themselves and the space, <br />
*** know their power and understand their power<br />
** Doesn’t have to be the leader (usually isn’t)<br />
** Shared knowledge<br />
** Open<br />
** Connected to our experiences, personal<br />
** Nonverbal cues<br />
** Use Art <br />
** Engagement not lecturing<br />
** Use simple open ended questions<br />
** Allow people to take ownership since it’s a collect outcome<br />
* Group Discussion<br />
** There will be people who take too much space and folx who aren’t taking space<br />
** How to be a role model and creating space for those who are not talking. <br />
** Being Vulnerable and showing that you are still learning (transparency) <br />
*** How to navigate vulnerability? How to create that space where folx want to share<br />
**** Modeling it. Being vulnerable so they feel comfortable sharing as well<br />
**** Community agreements<br />
** Facilitated Leadership<br />
*** Guiding folx into leadership vs facilitating conversations<br />
** Creating space where people can share materials and resources<br />
** Where does manage up <br />
*** You yourself can work from a place of power to <br />
** Challenge tradition dynamics without the fear of losing our jobs<br />
*** Cultures and values of our orgs<br />
** So many barriers in place to where we don’t feel like we have any power<br />
*** Learning how to be a facilitative leader and have a lot of power in bureaucratic places <br />
*** Challenge traditional power dynamics ( ageism, sexism,)<br />
** Ex. Of Facilitative Leadership<br />
*** Crafting agenda’s and getting input from multiple people<br />
*** Young woman taking notes, YOU can frame and highlight the important information and help shape the dialogue<br />
** How to help others have these Facilitative principles so they can share them<br />
** Why do we need this type of leadership versus other types of leadership?<br />
** How do we do facilitative leadership with intergenerational community members<br />
*** Whoever is in the space creates the space<br />
*** Team building & pop ed<br />
*** Co – Facilitating (Youth & adult ) <br />
** Dark side of facilitation<br />
*** Recognizing your power as a facilitator <br />
*** Watching out for you own biases and that it is not being projected <br />
**** Be transparent and acknowledge them<br />
* Further discussion on following topics<br />
** Why facilitative leadership is even needed?<br />
** How to help people step in and share learning space<br />
** How do I get there (there as in good facilitation skills)?<br />
** How to navigate through vulnerability? <br />
** Specific techniques managing group dynamics<br />
** Misty: How do we maintain a network of people talking and sharing Facilitative leadership<br />
*** How would that network look like across the state<br />
** Misty: How can you apply these principles to your next facilitating workshop</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Bilingual_communications_processes_and_social_media_tactics&diff=632Bilingual communications processes and social media tactics2019-07-23T22:49:50Z<p>Evelyn: Created page with "* Group Expectations From Talks ** Video ** Engagements Through Comms ** How to devleop plan for strat engagement *** i.e. IG for education and uplifting Ed ** Personal use v..."</p>
<hr />
<div>* Group Expectations From Talks<br />
** Video<br />
** Engagements Through Comms<br />
** How to devleop plan for strat engagement <br />
*** i.e. IG for education and uplifting Ed<br />
** Personal use vs professional use<br />
** Highlighting key stories for work<br />
** Transform Ideas<br />
*** Challenge audience<br />
** Fundraising purposes<br />
* Looking over @greenaction_ej Instagram<br />
** Uses Google Docs for templates for posts<br />
** Can use different fonts/styles to capture audience eyes<br />
** Have someone double check your posts<br />
* Looking at posts as calendar events<br />
** When you're posting you're asking something of people <br />
** Before<br />
*** Invitation/Call<br />
** Day-of<br />
*** highlight the event<br />
** After<br />
*** Recap the event<br />
* Resources Online For Social Media Organization<br />
** Hootsuite<br />
*** You can log into all your social media platforms at once and post to all accounts at once<br />
** spanighdict.com<br />
*** For translating into Spanish<br />
** Canva<br />
*** For making flyers<br />
*** Doesn't seem to work with Arabic to well<br />
** Adobe Spark<br />
*** Another option for making flyers<br />
** InstaSaver<br />
*** Lets you save videos to re-post on your story<br />
** Repost for IG<br />
*** Helps you copy a link for a post and repost on your own IG<br />
* Social Media Organization Practices<br />
** Keeping record of people the we've worked with/tagged in our posts <br />
*** In order to recall collaborations<br />
** Knowing your audience<br />
*** Age Targetting depending on your audience<br />
**** Memes for teens<br />
**** Bilingual info for older folks who tend to prefer one language<br />
**** Knowing your audience will tell you what Social Media platform is most suitable for your org.<br />
*** Metrics on Social Media<br />
**** You can check metrics to narrow down your audience and reach<br />
* Balancing Types of Posts<br />
** Greenaction Example<br />
*** One day is for posting a certain "community"<br />
**** Each day is for posting about a different community in order to maintain a balance on social media<br />
** Calendar <br />
*** A calendar helps diversify posts<br />
*** Posting and tagging about partner orgs is important<br />
*** Backwards planning<br />
**** Using a calendar of all the events to anticipate posts<br />
***** Hootsuite has a queue option where you can schedule a posting ahead of time<br />
* Building a Strategy<br />
** Find the character that your page will have<br />
*** Follow your orgs. goal and stay true to it</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Challenges_and_best_practices_for_managing_multilingual_work&diff=631Challenges and best practices for managing multilingual work2019-07-23T22:33:05Z<p>Evelyn: </p>
<hr />
<div>Technology for multilingual spaces breakout<br />
<br />
Facilitator: Mago<br />
<br />
Key Takeaways: <br />
<br />
*+2 Addressing different ways of using technology across generations and cultures so that no one is excluded.<br />
<br />
**Thinking of IT as a language<br />
<br />
*Not speaking IT language while also working multilingual communities. → funding/time for IT training <br />
<br />
*+4 Resources + funding for interpretation and interpretation equipment + budgeting for interpretation <br />
<br />
**Skillsharing + solidarity network <br />
<br />
**Training for bilingual folks (maybe retired?) to become skilled interpreters <br />
<br />
*+3 Time/capacity/compensation <br />
<br />
*+2 Just compensation for interpreters → shifting the dynamic <br />
<br />
**Systemizing our grant applications → keep interpretation as line item in all programs <br />
<br />
**Advocating for foundations to have a fund available for orgs to access when interpretation is needed <br />
<br />
***Stats and resources about language justice to advocate<br />
<br />
**Hire staffed interpreters for orgs that have regular interpretation needs <br />
<br />
*How could Aspiration network advance this issue? <br />
<br />
**Start by naming it / sharing the story / the systemic need with foundations<br />
<br />
*What tech resources exist that can support multilingual spaces? <br />
<br />
**How can technology be of service to facilitating multilingual spaces online specifically? <br />
<br />
**e.g. webinars → How to pull off simultaneous interpretation online?<br />
<br />
**Creating multilingual digital networks that can be accessed easily by phone / don’t require a high level of tech skill<br />
<br />
Go around<br />
<br />
* M - Journalist <br />
<br />
Learning to embrace my bilingual reality <br />
<br />
How to create multilingual networks of journalists<br />
<br />
* G - IDPSCA<br />
<br />
Challenges with language, not just Spanish/English but also tech languages and indigenous languages <br />
<br />
What are resources to improve our communication? <br />
<br />
* S<br />
<br />
Volunteers with API LGBTQ org and there are many different languages represented <br />
<br />
How to find translators for materials<br />
<br />
Website tips? <br />
<br />
Google translate bar on <br />
<br />
* A - L.A. Co-op Lab <br />
<br />
Creating multilingual digital networks that can be accessed easily by phone / don’t require a high level of tech skill <br />
<br />
S : Members start posting things that are <br />
<br />
* Y - Refuge for Families <br />
<br />
How can technology be of service to facilitating multilingual spaces online? <br />
<br />
Works with folks in El Salvador and connects with <br />
<br />
Other challenges:<br />
<br />
* Lack of relationships with indigenous interpreters <br />
<br />
* For transnational work, people have different ways of speaking about things, need to know nuances<br />
<br />
* The way we prioritize language puts Spanish/English translation at the top and often sidelines other immigrant communities <br />
<br />
* Staff members who don’t speak the same language</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6302019 Los Angeles Agenda2019-07-23T22:30:17Z<p>Evelyn: /* Collaborative Working SessionsIII */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event will start with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants will engage in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants will be encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about worker-owned cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=All_about_cooperatives&diff=628All about cooperatives2019-07-23T22:24:54Z<p>Evelyn: Created page with " Day 2 Afternoon Session: Worker Owned Co-ops Find tech co-ops to hire: techworker.coop It’s also a network for tech co-ops to join/share resources Co-ops are busines..."</p>
<hr />
<div><br />
<br />
Day 2 Afternoon Session: Worker Owned Co-ops <br />
<br />
Find tech co-ops to hire: techworker.coop<br />
<br />
It’s also a network for tech co-ops to join/share resources <br />
<br />
<br />
Co-ops are businesses. Not non-profit. Owned by workers. Vote on management. Pay vs investment. LA Coop Lab teaches in LA. Your introduction point depends on where you are in co-op organizing. El Centro promote co-ops. Business trainings. Different little co-ops sitting each other now. El Markedito Carousel. Cooperacion Central. Land Trust forming. Getting access to a public lot for community land trust. City is pro-gentrification, pro-police, anti-people.<br />
<br />
Lots of people like having idea of no boss. Community is collective boss -- collaboration is imperative. Member vesting. Patronage and vote come after this meeting period. Vote in new members. Some majority vote, some consensus (like new member acceptance). It's really hard to fire an owner. Owners have different rights than workers. Smaller is easier. <br />
<br />
Wanted infrastructure to have more employees. Hired too many people -- big mistake. New hires displaced earlier members. Trickier politics. Didn't have capacity to build proper relationships with so many new workers. Power dynamics and rifts exploded due to conflict avoidance. Hard to ease new people into old conversations.<br />
<br />
<br />
Zingerman’s <br />
<br />
Books on co-ops<br />
<br />
<br />
Andrea from Design Action Collective -- web development/design worker owned co-op<br />
<br />
Established “points of unity” <br />
<br />
Only works with social justice and environmental justice organizations<br />
<br />
Design Action Collective is happy to share experiences and tools with folks who want to start co-ops (e.g. bylaws etc) <br />
<br />
Design Action Collective is a part of a union.<br />
<br />
Design Action Collective. 40 years. Spin-off 3 years ago. Inherited bylaws, structure, added as new people come on. Cultural not just paper. Web development and tech harder to standardize than print. Co-ops are path to liberation. Point of reference to start thinking about own co-op business.<br />
<br />
Goal to share learning experience about Co-op organization. <br />
<br />
<br />
The Working World is a radical lender that brought together co-op developers across the country who then developed a national financial co-operative called Seed Commons<br />
<br />
L.A. Co-op Lab is a member of the financial co-operative and can help folks apply for financing (patient/non-extractive lending) <br />
<br />
<br />
What to do if you want to start a co-op? <br />
<br />
Find a co-op developer in your city<br />
<br />
In L.A.? → go to L.A. Co-op Lab<br />
<br />
Santa Ana → Cooperación Santa Ana (part of a larger movement resisting gentrification in Santa Ana that also recently formed a land trust) <br />
<br />
<br />
What have you done to spread the word about co-ops? <br />
<br />
Have parties, build the network <br />
<br />
Hire co-ops for things and tell people about them (bookkeeping etc) <br />
<br />
<br />
Decision making process<br />
<br />
At Design Action Collective: Processes to become a worker owner is 9 months as a regular employee. All worker owners have to be on board in order to vote in a new member.<br />
<br />
In regular meetings DAC uses 1 person 1 vote decision making, simple majority. Certain decisions require quorum. <br />
<br />
DAC is 6 owner members and 4 workers in the membership track <br />
<br />
Approval voting and score voting are other options for decision making <br />
<br />
<br />
Challenges: <br />
<br />
Health care plans / retirement plans / Mental health plan <br />
<br />
Taking on new worker owners (don’t hire too many people at once) <br />
<br />
Power dynamics that develop over the years → people have internalized racism/misogyny etc./ work patterns → at some point it might blow up<br />
<br />
<br />
Advantages<br />
<br />
Book, “Lost Connections” By Johan Hari on social determinants of depression: <br />
<br />
Mental health tied to work environment<br />
<br />
Co-op as an anecdote to depression meaningless work</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Combatting_police_surveillance&diff=626Combatting police surveillance2019-07-23T22:19:43Z<p>Evelyn: Created page with "'''Police surveillance on Thursday with Ken & Shahid''' 1. Initial go around: what do folks want to learn? a. Fight to stop surveillance will grow harder as it gr..."</p>
<hr />
<div>'''Police surveillance on Thursday with Ken & Shahid'''<br />
<br />
1. Initial go around: what do folks want to learn?<br />
a. Fight to stop surveillance will grow harder as it grows more entrenched<br />
b. Wanting a personal gut check to understand how serious the issue is<br />
c. Deep-seeded resentment to police…militarization<br />
d. Border surveillance<br />
e. Learning more beyond the surface<br />
2. Ken re Stop LAPD Spying Coalition<br />
a. Prompted by SARs (pre-crime suspicious activity reporting)<br />
b. Architecture of surveillance<br />
i. Public benefits cards<br />
ii. Police tech<br />
iii. Social control over POC and low-income communities<br />
iv. Organizing from LA CAN (Community Action Network) on Skid Row<br />
1. 50% of unhoused folks are black<br />
2. Only 9% of the area is black<br />
c. History<br />
i. Lantern laws applicable to slaves = self-surveillance <br />
ii. Restrictions on native folks when off the reservation<br />
iii. Police as recession-proof<br />
iv. The “stalker state” was a term introduced by women organizers<br />
1. Stalkers (like police) think they’re serving their targets<br />
v. Surveillance used as a tool to effectuate gentrification<br />
1. Eg throwing away the belongings of folks experiencing homelessness to “abandon” their property to use a public bathroom<br />
vi. Surveillance of sex workers, gender non-conforming folks, differently abled folks<br />
vii. Police bulletins based on anthropological models applied to urban gangs; lacking any rationale; LA Police Commission eventually withdrew LAPD’s Chronic Offender Bulletin<br />
viii. China’s social credit score system is gnarly…and not so different than what’s already happened in the US<br />
d. Surveillance capitalism<br />
i. Private-public partnerships<br />
ii. Surveillance offends more than just privacy<br />
1. Privacy as a value enjoyed by privileged people<br />
2. Families on TANF (Temporary Assistance for Needy Families) have to let gov inspectors<br />
3. Surveillance beyond digital monitoring; it extends offline<br />
iii. Dissent<br />
1. CAPA: Coalition Against Police Abuse was infiltrated heavily by the LAPD<br />
2. Having a stalker can silence someone…in the same way as government surveillance <br />
e. The struggle in LA<br />
i. Role of legal system to liberation<br />
ii. People power to force change<br />
1. “Power Not Paranoia” = organizing must proceed regardless of surveillance<br />
2. Seattle gave LA a drone fleet in 2015…the Coalition grounded them for a year…LAPD bought more…the Police Commission accepted a public process…which rejected the drones…the LAPD decided to proceed anyway…culminated recently in formal approval<br />
iii. Abolition as the goal<br />
1. Cops lie<br />
2. Diversity of tactics<br />
3. Electronic Frontier Alliance: EFA<br />
a. What is the Alliance?<br />
i. Diversity of tactics made concrete through diverse membership<br />
ii. 89 groups in 30 states<br />
1. Oakland Privacy grew out of Occupy Oakland<br />
2. Hacker spaces<br />
3. Student groups<br />
b. Police tech<br />
i. Most tools of surveillance were developed for military purposes<br />
ii. Examples<br />
1. CSS<br />
2. Fusion Centers<br />
3. ALPR<br />
4. Shot Spotter<br />
5. CCTV<br />
6. Drones<br />
7. FR (biometric surveillance)<br />
a. You can’t really opt out of biometric surveillance <br />
b. It limits the opportunity to move around freely in public<br />
c. Parameters<br />
i. Collection<br />
1. Legislation can help put limitations on the tools of surveillance (e.g a warrant requirement)<br />
ii. Use<br />
1. Eg, not for immigration enforcement<br />
iii. Retention<br />
1. Purge data after x days<br />
iv. Dissemination<br />
1. Can’t share with federal agencies, etc.<br />
d. Remedies<br />
1. SFO moratorium on facial recognition<br />
2. Use laws help limit the use-case scenarios of surveillance tech used by LEOs<br />
ii. CCOPS: call for an end of “secret” surveillance civilian review<br />
iii. CCOPS + FR (SF): 1st bill of its kind which included a moratorium on facial recognition technology<br />
iv. CCOPS + M (STL): Community process which expands the above to include review for all military gear (including and also beyond surveillance tech) being acquired by police<br />
v. Providence<br />
1. If surveillance is a means for state social control, then our fight against surveillance is concretely a fight for a free society<br />
2. Examples of how this social control is based on Red Scares, COINTELPRO, and the war on “terror”<br />
3. Surveillance kills democracy<br />
vi. Legal mechanisms have not kept up with the technology & are largely tainted by latent white supremacy<br />
4. Discussion<br />
a. “Community control of police” has historically looked like black bodies hanging from trees and LGBT oppression<br />
b. Non-profit industrial complex goals<br />
i. Non-profits often settle for measurable, achievable victories<br />
ii. Community organizing (eg Stop LAPD Spying) fights for more visionary liberatory values<br />
1. Defunding and defanging police<br />
2. De-militarizing<br />
iii. How to push our allies at institutions that are willing to make concessions (eg ACLU, non-profits)<br />
iv. How also to uplift short-term victories<br />
c. How to play defense<br />
i. Out Data Bodies Playbook built by organizers working with folks experiencing poverty<br />
ii. Security workshops<br />
1. Security Education Compendium built by privacy groups<br />
2. Tactical Tech’s Data Detox Guide<br />
iii. Ridesharing regulation<br />
1. LA Dept of Transportation sought regulations to require location tracking of users by rideshare and scooter companies<br />
d. How to play offense<br />
i. Connect frontline communities and individuals to local groups<br />
ii. Organizing: start here, stay visionary and intersectional<br />
1. Building relationships beyond any discrete campaign<br />
iii. Policy advocacy: opportunistic</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Stories_and_lessons_learned_from_nonprofit_and_tech_shop_collaborations&diff=625Stories and lessons learned from nonprofit and tech shop collaborations2019-07-23T22:16:46Z<p>Evelyn: </p>
<hr />
<div>Background:<br />
<br />
Andrea - Works as a developer, exclusively as a non-profit. Goals is to better understand how to serve the community<br />
<br />
Jared - Data Roads Foundation (coop) — from tech IT side, video games, and dev ops. Didn’t realize his love for work with non-profits until recently. <br />
<br />
Maxwell - Worked in tech as a product designer for 6 years. Wanting to make amends for the things he’s done before.<br />
<br />
Ray - Previous tech experience has all been commercial, want to better understand how to organize tech into situations that can create change<br />
<br />
Elise - Doesn’t work in tech or non-profit, but transitioning into tech and wanting to make sure she learns about the stories in order to be better when she does transition into tech.<br />
<br />
Adriana - non profit sector - works with LA CoOp lab. Wants to see what has been working and what hasn’t been working. What kind of solutions can we come up with that are outside of the $$$ structures we have now. How do we not be so extractive with technology<br />
<br />
Dean - Been in tech for a long time, multi-million dollar budgets to small shoestring budgets. <br />
<br />
<br />
<br />
<br />
Maxwell - worked at first startup 6 years ago as a designer. Worked on car rental platform startup. Design from communications to product. Target audience - people who want to drive for Uber and Lyft (people who need a car for ST use). Called one of the higher money makers to get user research feedback on a product and was surprised by how taken aback the customer was that the company would even call her for feedback. She talked about how the company was ruining her life and putting her into debt. He started considering that the business is nasty, gives this feedback to the company but the company didn’t care and is changing their business model from one case. <br />
<br />
<br />
Lessons: Assess the companies you are joining and understand what they are doing, what the repercussions are for people on the fringes of the product<br />
<br />
As a creator, you underestimate the agency you have to say yes or no to. Be aware of what you’re doing or making<br />
<br />
<br />
Ray - worked commercial, he worked with everyone that is technical. Now in non-profit, not everyone is technical — and where the focus wasn’t the technology there were adjustments needed. He then went in and did assessments of security and technology. “Okay, well definitely the data that we’re managing should be protected”. He wrote up this document for a GPG security encryption (it’s a security encryption protocol), because everyone uses GPG, so eh. He was familiar with it and it seemed like all the staff were super confident - he presented it to the Executive Director, and she said “no, no… this is not going to work”. He decided to sit down with someone and actually try to generate keys, and he realized as he was sitting down with several folks — he realized that none of his grandiose plans were going to ever work. The plans didn’t necessarily match with the reality of his work place. <br />
<br />
<br />
Lessons: Assessments are academic — implementation is what really matters. Be more familiar with day-to-days of the actual people, and don’t assume / presume too much.<br />
<br />
Don’t treat technology as universal or first, the people should be the ones where the needs come from first.<br />
<br />
<br />
Jared - Working on this game for a new console that was coming out, called “Girl with a stick” (street fighter-esque // melee battle game). The character was this futuristic woman who was set in Africa. Jared had questioned “uh.. shouldn’t we get a black woman to help us to create this character?”. That whole comment and idea got shot down completely, and the majority white male company moved on in creating the game.<br />
<br />
<br />
Lessons: The whole game industry should unionize. The platform consoles are vertically monopolizing all things about games. Basically the old school studios of Hollywood — whom are dictating all the genre and media is going to be.<br />
<br />
There needs to be anti-trust action on all of the big companies of Sony, etc.<br />
<br />
<br />
Andrea - Many years ago Andrea was working 2 years in the non profit world. She got a request from this amazing organization about youth. They started the discovery process and started creating needs, etc… She was happy to be on the project no matter what. As the product finished in it’s lifecycle, they actually ran usability tests. When they ran into a problem. The user base didn’t realize they had to actually use the thing because they were in the demographic of elderly, old-school, in-real-life type people. The company hired consultants but the folks never took into consideration who was going to use it // and they never asked. It was a lot of effort and time wasted that could have been used on another organization.<br />
<br />
<br />
Lessons: Always understand who is going to use it. Know who your customers are and don’t just dive into spending time and energy. <br />
<br />
<br />
Adriana - Did a redesign of a website, she was the communications lead where she leased with the team. At some point, the designers came back with an amazing design. The project manager, was the middleman between her and the developers. Essentially they didn’t build out the design to spec and there were so many layers of back and forth between the two groups. She ended up doing the job of the project manager and was always “protective” of the time of the developers. But when she was finally able to talk to the developer — everything was gravy.<br />
<br />
<br />
Lessons: Having direct contact with the developers or their project management tools. If there is a way to do a shared project management system — that would create more agency.<br />
<br />
<br />
Dean - Running an R&D lab, Sony came to them, that they’re backing up huge amounts of files. Sony says we have a great solution, a device that will back up everything that they need — it was called the “Petafile”. Dean said “umm… maybe you should change that name” to the Sony people. Sony was like “Nah, you’re not a marketing guy — we’re not changing the name”. Eventually the device became known as the “PetaTower”.<br />
<br />
<br />
Lessons: Always have a bilingual person consulting you on the things you’re making in other languages.<br />
<br />
<br />
Question: What is a successful method or way that you work with technology in your environments?<br />
<br />
You have to be a psychologist and planting seeds of ideas to other people and pretend that it’s their idea in order to be able to take your initiatives forward.<br />
Assume NOTHING.<br />
Don’t create media outside your own experiences<br />
Know your audience<br />
Know your audience’s tech literacy (within or outside)<br />
Building trust and relationships with your community in order to better your work relationships<br />
<br />
<br />
Resources:<br />
<br />
Strive Digital (for texting)<br />
Hustle (for texting)</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Stories_and_lessons_learned_from_nonprofit_and_tech_shop_collaborations&diff=624Stories and lessons learned from nonprofit and tech shop collaborations2019-07-23T22:16:27Z<p>Evelyn: Created page with "Background: Andrea - Works as a developer, exclusively as a non-profit. Goals is to better understand how to serve the community Jared - Data Roads Foundation (coop) — fro..."</p>
<hr />
<div>Background:<br />
<br />
Andrea - Works as a developer, exclusively as a non-profit. Goals is to better understand how to serve the community<br />
<br />
Jared - Data Roads Foundation (coop) — from tech IT side, video games, and dev ops. Didn’t realize his love for work with non-profits until recently. <br />
<br />
Maxwell - Worked in tech as a product designer for 6 years. Wanting to make amends for the things he’s done before.<br />
<br />
Ray - Previous tech experience has all been commercial, want to better understand how to organize tech into situations that can create change<br />
<br />
Elise - Doesn’t work in tech or non-profit, but transitioning into tech and wanting to make sure she learns about the stories in order to be better when she does transition into tech.<br />
<br />
Adriana - non profit sector - works with LA CoOp lab. Wants to see what has been working and what hasn’t been working. What kind of solutions can we come up with that are outside of the $$$ structures we have now. How do we not be so extractive with technology<br />
<br />
Dean - Been in tech for a long time, multi-million dollar budgets to small shoestring budgets. <br />
<br />
<br />
<br />
<br />
Maxwell - worked at first startup 6 years ago as a designer. Worked on car rental platform startup. Design from communications to product. Target audience - people who want to drive for Uber and Lyft (people who need a car for ST use). Called one of the higher money makers to get user research feedback on a product and was surprised by how taken aback the customer was that the company would even call her for feedback. She talked about how the company was ruining her life and putting her into debt. He started considering that the business is nasty, gives this feedback to the company but the company didn’t care and is changing their business model from one case. <br />
<br />
<br />
Lessons: Assess the companies you are joining and understand what they are doing, what the repercussions are for people on the fringes of the product<br />
<br />
As a creator, you underestimate the agency you have to say yes or no to. Be aware of what you’re doing or making<br />
<br />
<br />
Ray - worked commercial, he worked with everyone that is technical. Now in non-profit, not everyone is technical — and where the focus wasn’t the technology there were adjustments needed. He then went in and did assessments of security and technology. “Okay, well definitely the data that we’re managing should be protected”. He wrote up this document for a GPG security encryption (it’s a security encryption protocol), because everyone uses GPG, so eh. He was familiar with it and it seemed like all the staff were super confident - he presented it to the Executive Director, and she said “no, no… this is not going to work”. He decided to sit down with someone and actually try to generate keys, and he realized as he was sitting down with several folks — he realized that none of his grandiose plans were going to ever work. The plans didn’t necessarily match with the reality of his work place. <br />
<br />
<br />
Lessons: Assessments are academic — implementation is what really matters. Be more familiar with day-to-days of the actual people, and don’t assume / presume too much.<br />
<br />
Don’t treat technology as universal or first, the people should be the ones where the needs come from first.<br />
<br />
<br />
Jared - Working on this game for a new console that was coming out, called “Girl with a stick” (street fighter-esque // melee battle game). The character was this futuristic woman who was set in Africa. Jared had questioned “uh.. shouldn’t we get a black woman to help us to create this character?”. That whole comment and idea got shot down completely, and the majority white male company moved on in creating the game.<br />
<br />
<br />
Lessons: The whole game industry should unionize. The platform consoles are vertically monopolizing all things about games. Basically the old school studios of Hollywood — whom are dictating all the genre and media is going to be.<br />
<br />
There needs to be anti-trust action on all of the big companies of Sony, etc.<br />
<br />
<br />
Andrea - Many years ago Andrea was working 2 years in the non profit world. She got a request from this amazing organization about youth. They started the discovery process and started creating needs, etc… She was happy to be on the project no matter what. As the product finished in it’s lifecycle, they actually ran usability tests. When they ran into a problem. The user base didn’t realize they had to actually use the thing because they were in the demographic of elderly, old-school, in-real-life type people. The company hired consultants but the folks never took into consideration who was going to use it // and they never asked. It was a lot of effort and time wasted that could have been used on another organization.<br />
<br />
<br />
Lessons: Always understand who is going to use it. Know who your customers are and don’t just dive into spending time and energy. <br />
<br />
<br />
Adriana - Did a redesign of a website, she was the communications lead where she leased with the team. At some point, the designers came back with an amazing design. The project manager, was the middleman between her and the developers. Essentially they didn’t build out the design to spec and there were so many layers of back and forth between the two groups. She ended up doing the job of the project manager and was always “protective” of the time of the developers. But when she was finally able to talk to the developer — everything was gravy.<br />
<br />
<br />
Lessons: Having direct contact with the developers or their project management tools. If there is a way to do a shared project management system — that would create more agency.<br />
<br />
<br />
Dean - Running an R&D lab, Sony came to them, that they’re backing up huge amounts of files. Sony says we have a great solution, a device that will back up everything that they need — it was called the “Petafile”. Dean said “umm… maybe you should change that name” to the Sony people. Sony was like “Nah, you’re not a marketing guy — we’re not changing the name”. Eventually the device became known as the “PetaTower”.<br />
<br />
<br />
Lessons: Always have a bilingual person consulting you on the things you’re making in other languages.<br />
<br />
<br />
Question: What is a successful method or way that you work with technology in your environments?<br />
<br />
You have to be a psychologist and planting seeds of ideas to other people and pretend that it’s their idea in order to be able to take your initiatives forward.<br />
Assume NOTHING.<br />
Don’t create media outside your own experiences<br />
Know your audience<br />
Know your audience’s tech literacy (within or outside)<br />
Building trust and relationships with your community in order to better your work relationships<br />
<br />
<br />
Resources:<br />
<br />
Strive Digital (for texting)<br />
Hustle (for texting)</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=CRM_Tracking_leadership_development&diff=623CRM Tracking leadership development2019-07-23T21:54:57Z<p>Evelyn: </p>
<hr />
<div>'''Tracking leadership development'''<br />
<br />
'''Why we are here'''<br />
<br />
* Our failed attempts at tracking this were driven by funder ideas/wants that were not connected to what was important to the community. Engagement not leadership. Higher end was political actions, lower end were community events--membership event participation were not tracked as a whole story, every month for 12 months.<br />
* Ladder/web/grid of engagement--want to know what practices people have used to ID where folks are at, where folks can be moved "up" or "sideways", what metrics people have used. Also HOW and actual mechanisms for tracking that are not linear/one-dimensional, like assigning points to signing a petition etc. Ladder, grid, web, etc.<br />
* Echo all this, esp tracking driven by fundable actions. We use Bloomerang (CRM) to track this. We track events that people attend and use the # of how many events they have attended to design our outreach, it's not working ok but could be a lot better. Also use RSPV forms. This is more engagement than leadership. Not tracked but think about it in a relational way--who knows who, what their interests are, what they want to do.<br />
* How do we systematize recording and analysis of this relational stuff?<br />
* New frontier in program to track leaders. Right now there is a form people fill out re their experiences with the leadership. Just a start. Lack of understanding of what leadership is doing? Mission is to empower students to use tech tools for social justice. Interested in the leadership of the program not the students bc that is taken care of in other ways<br />
* How do you grow in the work that you are doing? How do organizations transmit leadership to the communities they work with? 99Rootz talked about it yesterday. They are seeing high schoolers talk more about themselves and their work and that is sign of growth. More expansive ways of thinking about leadership. Finding your own voice. We also need that inside our organizations. Building confidence and participation. When we can transform our organizations, change hierarchies, when more voices are on the table regardless of the size org.<br />
* At my org we do a lot of tracking but it's not consistent. We do check ins with youth and have a form, have been able to ID different leadership skills they have and what they want to learn. Some are phone banking, some are mobilizing, some are public speaking. We go through the sheet of skills and show it to them and ask where they want to grow, check in emotionally and academically. Then we type it up and it gets lost in the digital world. How we publicize it to funders is through education rates, where they are going to higher ed and jobs. Wheere we have not done a good job is distinguishing leadership and organizing. Leader and front face and the work that organizers do. We are trying to develop long term community organizers. IN the parent component we don't do check ins, we track their leadership via attendance at events. Forms and spreadsheets. We don't follow up about what they learned. Parents don't age out of the program the way youth do, parents are long term. We need a different tool, more like what we do with the youth. There is no culmination like graduation with adult development, we need different metrics. FUnders want numbers. How do we develop parents to be community organizers and be the best community organizers ever. We also try to measure their comprehension of our campaigns. If they don't understand our work we need to get ourselves together. Where are we lacking in involving youth and parents in our larger work. Making sure we are prepping folks to talk about our work. HR is also underdeveloped so staff development is super disconnected. Review and reflection is imporant to continued growth!<br />
* Tracking adult development. Seen many orgs going courses for adults, diplomas for courses/certificates etc. Something you can count and that they can show for their efforts.<br />
<br />
'''General discussion'''<br />
<br />
* How did your evaluation work?<br />
* Based off of professionalism, working in coalition, and my own goals. Supervisor did survey based on my performance. I would have liked it to include a self-evaluation as well. It was great to hear his feedback but it was a missed opportunity. Any time for employees to reflect on their goals/role/opportunities for growth is ideal. Share ideas with other staff.<br />
* Put professional development in workplans, budgets, staff meetings (for the latter, time to discuss opportunities with each other)<br />
* Using belts/badges/milestones that people reach. Makes people feel good to reach things.<br />
* Using something like strengths-finder to ID and cultivate strengths/paths for leadership. This can also support matching people to work on stuff together.<br />
* Milestones for growth<br />
* Skills inventories that people fill out every 6th months, with where are you at with all these and where do you want to focus your growth? This can yield interesting longitudinal and individual data, can tell a story and also invite reflection for growth<br />
* Capacity for tracking is a real issue. Needs to be a conversation. Articulate the value of the data collection.<br />
* Having participants do their own entry via a form. THen you can do analysis/ID for outreach on the back end.<br />
* How to measure community outreach done by others/connections to people so that people's work on behalf of your org can be acknowledged<br />
* Aspiration's hypothesis is 1) tech skills lead to leadership development in orgs and networks and 2) participatory methods and facilitation skills lead to leadership development. These can be applied to people at every level of an org, not just leadership. Having these skills makes you valuable to an org. Tech capacity building is the carrot for leadership development. Very tactical skills. Then people use these skills in ways that elevate them within the organization. Cultivate people recognizing their own power. We can measure this by growth of skills and within the org.<br />
* We ID people in our networks who have the "spark" around participatory methods/frameworks and try to work with them to learn from them and bring them closer, elevating them within the network so the whole network becomes more participatory.<br />
* One to one, within an org, within a network <--this is how we scale/talk to funders about scale. We only call it leadership development when we need to for a grant.<br />
* Where is the space for conflict resolution/creative problem solving in this?<br />
* Great Q! People often are bringing those skills already (part of the spark?) We can also tap into our networks about that. Connect with people who can train on that, we don't focus on it.<br />
* Managing group dynamics/conflict is also important to facilitation<br />
* Could get better at managing vulnerability/supporting people's growth<br />
* Challenge: How do you track leadership development when people move around organizationally? We WANT people to go other places!<br />
* Alumni tracking--retain relationships and have people report back to you<br />
* Case management as a model. But this is can be heavy systems burden.<br />
* Are there sector-wide metrics we could track about how our ideas are taking root?<br />
* Story collection/story banking<br />
* We all take what we have learned, the good and the bad, with us when we move on<br />
* What does it mean to be developing leadership in a freelance context/without an organization?<br />
* There is an underrated social/relational element of leadership development</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=CRM_Tracking_leadership_development&diff=622CRM Tracking leadership development2019-07-23T21:54:17Z<p>Evelyn: Created page with "# Tracking leadership development ## Why we are here * Our failed attempts at tracking this were driven by funder ideas/wants that were not connected to what was important t..."</p>
<hr />
<div># Tracking leadership development<br />
<br />
## Why we are here<br />
<br />
* Our failed attempts at tracking this were driven by funder ideas/wants that were not connected to what was important to the community. Engagement not leadership. Higher end was political actions, lower end were community events--membership event participation were not tracked as a whole story, every month for 12 months.<br />
* Ladder/web/grid of engagement--want to know what practices people have used to ID where folks are at, where folks can be moved "up" or "sideways", what metrics people have used. Also HOW and actual mechanisms for tracking that are not linear/one-dimensional, like assigning points to signing a petition etc. Ladder, grid, web, etc.<br />
* Echo all this, esp tracking driven by fundable actions. We use Bloomerang (CRM) to track this. We track events that people attend and use the # of how many events they have attended to design our outreach, it's not working ok but could be a lot better. Also use RSPV forms. This is more engagement than leadership. Not tracked but think about it in a relational way--who knows who, what their interests are, what they want to do.<br />
* How do we systematize recording and analysis of this relational stuff?<br />
* New frontier in program to track leaders. Right now there is a form people fill out re their experiences with the leadership. Just a start. Lack of understanding of what leadership is doing? Mission is to empower students to use tech tools for social justice. Interested in the leadership of the program not the students bc that is taken care of in other ways<br />
* How do you grow in the work that you are doing? How do organizations transmit leadership to the communities they work with? 99Rootz talked about it yesterday. They are seeing high schoolers talk more about themselves and their work and that is sign of growth. More expansive ways of thinking about leadership. Finding your own voice. We also need that inside our organizations. Building confidence and participation. When we can transform our organizations, change hierarchies, when more voices are on the table regardless of the size org.<br />
* At my org we do a lot of tracking but it's not consistent. We do check ins with youth and have a form, have been able to ID different leadership skills they have and what they want to learn. Some are phone banking, some are mobilizing, some are public speaking. We go through the sheet of skills and show it to them and ask where they want to grow, check in emotionally and academically. Then we type it up and it gets lost in the digital world. How we publicize it to funders is through education rates, where they are going to higher ed and jobs. Wheere we have not done a good job is distinguishing leadership and organizing. Leader and front face and the work that organizers do. We are trying to develop long term community organizers. IN the parent component we don't do check ins, we track their leadership via attendance at events. Forms and spreadsheets. We don't follow up about what they learned. Parents don't age out of the program the way youth do, parents are long term. We need a different tool, more like what we do with the youth. There is no culmination like graduation with adult development, we need different metrics. FUnders want numbers. How do we develop parents to be community organizers and be the best community organizers ever. We also try to measure their comprehension of our campaigns. If they don't understand our work we need to get ourselves together. Where are we lacking in involving youth and parents in our larger work. Making sure we are prepping folks to talk about our work. HR is also underdeveloped so staff development is super disconnected. Review and reflection is imporant to continued growth!<br />
* Tracking adult development. Seen many orgs going courses for adults, diplomas for courses/certificates etc. Something you can count and that they can show for their efforts.<br />
<br />
## General discussion<br />
<br />
* How did your evaluation work?<br />
* Based off of professionalism, working in coalition, and my own goals. Supervisor did survey based on my performance. I would have liked it to include a self-evaluation as well. It was great to hear his feedback but it was a missed opportunity. Any time for employees to reflect on their goals/role/opportunities for growth is ideal. Share ideas with other staff.<br />
* Put professional development in workplans, budgets, staff meetings (for the latter, time to discuss opportunities with each other)<br />
* Using belts/badges/milestones that people reach. Makes people feel good to reach things.<br />
* Using something like strengths-finder to ID and cultivate strengths/paths for leadership. This can also support matching people to work on stuff together.<br />
* Milestones for growth<br />
* Skills inventories that people fill out every 6th months, with where are you at with all these and where do you want to focus your growth? This can yield interesting longitudinal and individual data, can tell a story and also invite reflection for growth<br />
* Capacity for tracking is a real issue. Needs to be a conversation. Articulate the value of the data collection.<br />
* Having participants do their own entry via a form. THen you can do analysis/ID for outreach on the back end.<br />
* How to measure community outreach done by others/connections to people so that people's work on behalf of your org can be acknowledged<br />
* Aspiration's hypothesis is 1) tech skills lead to leadership development in orgs and networks and 2) participatory methods and facilitation skills lead to leadership development. These can be applied to people at every level of an org, not just leadership. Having these skills makes you valuable to an org. Tech capacity building is the carrot for leadership development. Very tactical skills. Then people use these skills in ways that elevate them within the organization. Cultivate people recognizing their own power. We can measure this by growth of skills and within the org.<br />
* We ID people in our networks who have the "spark" around participatory methods/frameworks and try to work with them to learn from them and bring them closer, elevating them within the network so the whole network becomes more participatory.<br />
* One to one, within an org, within a network <--this is how we scale/talk to funders about scale. We only call it leadership development when we need to for a grant.<br />
* Where is the space for conflict resolution/creative problem solving in this?<br />
* Great Q! People often are bringing those skills already (part of the spark?) We can also tap into our networks about that. Connect with people who can train on that, we don't focus on it.<br />
* Managing group dynamics/conflict is also important to facilitation<br />
* Could get better at managing vulnerability/supporting people's growth<br />
* Challenge: How do you track leadership development when people move around organizationally? We WANT people to go other places!<br />
* Alumni tracking--retain relationships and have people report back to you<br />
* Case management as a model. But this is can be heavy systems burden.<br />
* Are there sector-wide metrics we could track about how our ideas are taking root?<br />
* Story collection/story banking<br />
* We all take what we have learned, the good and the bad, with us when we move on<br />
* What does it mean to be developing leadership in a freelance context/without an organization?<br />
* There is an underrated social/relational element of leadership development</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6212019 Los Angeles Agenda2019-07-23T21:53:33Z<p>Evelyn: /* Collaborative Working Sessions II */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event will start with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants will engage in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants will be encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner and Gilda<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Project_Management_101&diff=620Project Management 1012019-07-23T21:53:18Z<p>Evelyn: Created page with "Project management on Thursday with Gunner & Gilda 1. Needs a. How to keep long term projects from hitting the floor while pursuing short-term needs b. Re..."</p>
<hr />
<div>Project management on Thursday with Gunner & Gilda<br />
<br />
1. Needs<br />
a. How to keep long term projects from hitting the floor while pursuing short-term needs<br />
b. Remove blockers for a team; help accelerate progress<br />
c. Speeding discovery and post-mortem phases<br />
d. What software programs best allow coordination across organizations<br />
2. Philosophy / principles<br />
a. Gilda: What is a project? Anything with a<br />
i. Defined term: Beginning & end<br />
ii. Defineable elements<br />
1. Product<br />
2. Goal: a deliverable (not merely an update)<br />
a. Manageable pieces: sub-projects<br />
b. Something that can hold shared work / vs a solo task<br />
iii. The time required to support the project management process should not eclipse or antagonize the execution<br />
1. Software presenting the system’s needs…<br />
2. …vs. a user’s needs<br />
b. Gunner: Project management = community organizing; mobilizing stakeholders <br />
i. Overview<br />
1. Focus on narrative<br />
2. Clarity on process<br />
3. “Pragmatic pessimism”; now that people will let you down, and plan for it<br />
ii. Not car washing or closet cleaning<br />
3. Diving in<br />
a. Focus on narrative<br />
i. Good project managers are communicators able to build consensus<br />
b. Clarity on process<br />
i. Transparency: who’s doing what + status<br />
1. Unify understanding of the project<br />
a. Why are we doing this?<br />
b. What are we doing?<br />
c. What language are we using? <br />
i. Language ambiguity is often a locus of failure (eg “we need to build a website,” or “lunch needs to be spicy”)<br />
2. Discipline about language used can unify sense of purpose<br />
ii. Accountability<br />
1. It’s helpful for a tool that changes colors or yells at you when a deadline gets missed; when something is overdue<br />
2. Eg Excel isn’t automated vs. Basecamp turns red when a deadline is missed<br />
iii. “Pragmatic pessimism”; now that people will let you down, and plan for it<br />
1. When someone gives you a time estimate for a deliverable; pad it<br />
2. Presume that gaps will emerge in whatever you plan<br />
iv. Ensuring adequate resources<br />
1. If adding projects & time to someone’s workload, it can be helpful to take others off<br />
a. Gunner: conceptualize a table full of canned vegetables. Adding anything to the table will force something else off<br />
b. Federated: give people control over their projects <br />
2. Dynamic deadlines; adjusting expectations to account for hiccups<br />
3. Gantt charts: a standard tool which is more or less useless<br />
a. it doesn’t allow for dynamism / slipped deadlines<br />
b. They collapse quickly and are tough to rebuild<br />
4. Time & prioritization pairing<br />
a. Put each week’s priority at the top; focus on that<br />
b. Allow lower priority issues to attain a lower priority<br />
c. People generally can’t estimate how much time something will take<br />
d. Ideally, move priorities over to next week; it allows more flex in the joints<br />
e. Don’t call fire drills unless it’s actually critical; flex in the joints enables greater sustainability<br />
f. “Play the long game”<br />
v. “Humility to the learning”<br />
1. Good project management embeds learning along the way<br />
2. Recognize it as learning, rather than as inefficiency<br />
3. It’s easy to burn people out<br />
a. Crisis in the macrosphere is not a reason to place pressure across the project. <br />
b. “Emotional firewall”: don’t let your sense of crisis infect the rest of the team; rational thinking is critical<br />
c. Rudyard Kipling: “If you can keep your head while all those about you are losing their’s and blaming you, then you will be an adult.”<br />
d. Win at project management by not losing control<br />
vi. Core skill: negotiation (eg of deadlines, budget, resources, etc.)<br />
c. Tools<br />
i. Minimal consumption: Don’t use all the tools<br />
1. The more you use, the more time consuming<br />
2. In Basecamp, Aspiration uses only the calendar + the to do list + file upload<br />
3. Don’t succumb to “Feature underutilization guilt” <br />
4. But also be willing to adopt the features that can be actually helpful in your context<br />
ii. Software is designed to addict users<br />
1. Eg phones addict users due to collective expectations<br />
2. Eg project <br />
iii. Share affirmation, recognition<br />
iv. Channel<br />
1. Pain: catch gaps and <br />
2. Passion<br />
3. Fame: recognize progress and the people who enable it<br />
4. Fun: “this week we have only 6 overdue items, down from 10 last week!”<br />
v. Tools can be low tech<br />
1. Eg sticky notes on a calendar <br />
2. Key: everyone needs to use it; it must fit their workflow<br />
a. Gunner re “passive-aggressive non-adoption”; users often resist innovations<br />
b. The more complicated the tool, the tougher the adoption barrier<br />
d. Hosted software tools sometimes get bought or <br />
i. Hollywood marriage relationship: assume divorce as a given<br />
1. Vendors lie<br />
2. Consider future acquisition<br />
ii. If you can’t get your data out, might not make sense to put your data in<br />
1. Check the export function<br />
2. Interoperability: Test it to make sure that the export is in a useful format<br />
a. Try importing it to other platforms<br />
b. Major platforms export into an csv, which can be re-imported into a spreadsheet<br />
iii. To shift to a new project management platform<br />
1. Finish old projects on the old project management tool<br />
a. Migrating project management data might not make sense; a lot of project data expires quickly<br />
b. Time to migrate is often unnecessary <br />
2. Launch the new tool with new projects<br />
e. What is your information model?<br />
i. What is the scope of the information you’re managing<br />
ii. How might it be organized?<br />
iii. Tools are transient…but processes should transcend the moment<br />
iv. Model at the outset how you would extract / export and use your data on new platform<br />
1. Engage all your stakeholders in the dialog<br />
f. Don’t use free online tools: they have problems<br />
i. Free stuff will let you down<br />
ii. Free stuff is designed to spy on you<br />
1. “If you’re not paying for the product, you are the product.”<br />
iii. If you need something, pay for it<br />
1. Costs may be justified only in terms of data resiliency. Compare the cost against the cost of needing to recover all your project management tools<br />
2. If a free account loses data, you won’t likely get help from customer support<br />
3. This happens all the time. For-profit companies don’t care about you<br />
iv. Threat modeling<br />
1. Watching a kid who just learned to walk forces parents and caretakers to do threat modeling in real-time<br />
2. Putting strategy docs online allows gov transparency<br />
3. Greenpeace used Google for its data…and it’s classified as an eco-terrorist org…so Google is presumably leaking everything the org has to the gov</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Digital_inclusion_and_meaningful_access&diff=619Digital inclusion and meaningful access2019-07-23T21:51:09Z<p>Evelyn: Created page with "'''Digital Inclusion and accessibility of tech''' Facilitator: Maegan from IDEPSCA • Maegan: How do we deal with tech. when it comes to accessibility? ◦ Most..."</p>
<hr />
<div>'''Digital Inclusion and accessibility of tech'''<br />
<br />
Facilitator: Maegan from IDEPSCA<br />
<br />
• Maegan: How do we deal with tech. when it comes to accessibility?<br />
◦ Most documentation is in English so it is harder for folks without English as their first language to understand and implement technology.<br />
• Matt: From the Universe of Technology through the Everett Program<br />
◦ Accessibility of tech. for smaller nonprofits<br />
• Ryan: From School on Wheels<br />
◦ Became accidental tech. person <br />
◦ Providing tools and everything that the staff needs<br />
◦ Uses log in site to log their hours. Wants to make it a stress free process<br />
• Luis: From Armadillos Search and Rescue<br />
◦ Became accidental tech. person <br />
◦ Issue with technology being accessible to our own members<br />
◦ Audience is older, so it is harder to implement newer tech.<br />
◦ Moving from social media to a new website<br />
• Addison: From <br />
◦ <br />
• Erick: South Los Angeles organization built around forming community<br />
◦ Recently into environmental justice and fighting environmental racism<br />
◦ Has become the IT person at the office, just helping who he can and fixing what he can<br />
◦ Because of the age differences of his organization’s members, the comfort levels of implementing new tech. is variable<br />
• Maegan: Works with many different types of people, so she has to tailor her work to that<br />
◦ Most people don’t know the difference between an app or a website<br />
◦ Just because everyone has smartphones doesn’t mean everyone knows how to use one<br />
◦ Also became the accidental techy<br />
◦ People are not setting up their own accounts, so people really don’t know how to operate their accounts if they need to fix something<br />
◦ Although statistics are saying that the digital divide is closing, it is really only measuring whether or not someone has a phone in their pocket, not so much that they know how to use it<br />
◦ Big fan of going back to the basics, even if it would take more time<br />
▪ Easier to just do paper and work with them to teach them how to use the form or service<br />
• Erick: Talking about his experience with this<br />
◦ Part of organization doing outreach work<br />
◦ When doing the outreach work, they were limited by the structure of the outreach set by the company/service that tasked them to do it<br />
◦ It doesn’t work for the people they are trying to serve<br />
▪ Has to take data on a tablet<br />
▪ Applications are crashing<br />
▪ Makes working in the field very difficult<br />
◦ Reason why they switched back to pen and paper forms<br />
▪ Takes more time (two extra days)<br />
▪ But it works better for the community at large<br />
• Maegan: Depending on what power you have in your org, you may not have a say in what applications or programs you use<br />
◦ How comfortable are people talking with their leadership about the shortcomings of certain methodologies?<br />
• Ryan: Speaking on this<br />
◦ Had Salesforce system that was being used by org, but switched to a more “accessible” platform<br />
◦ Had a consultant build it and they are now stuck with it<br />
▪ They built it and they said: “Here, just use it”<br />
▪ But it doesn’t work well enough for what they are trying to accomplish<br />
◦ How do you go about fighting that beyond having conversations?<br />
• Matt: Get data to back up your fight for a new methodology<br />
◦ Get people’s opinions and survey members of your organization<br />
◦ If enough people say that something doesn’t work, then it might change<br />
• Maegan: Has to be a collective movement and decision to change something before it’s too late<br />
◦ It takes more time, but it will be more beneficial in the end<br />
◦ Taking the time to frontload training so that everyone is on the same page is what has worked for her org.<br />
◦ Why would a website would work better than social media?<br />
• Luis: A website tells a better story<br />
◦ Better when trying to acquire a grant<br />
◦ More accessible to a wider population<br />
◦ Social media can portray the wrong message or intent and you can get sidelined by advertisements or spam<br />
▪ Although it is useful for quick and efficient communication<br />
• Maegan: Who is it more important to reach?<br />
◦ Is it more important to reach the funder or the base?<br />
◦ Have a website from 2005 that needs an update, but it’s at the bottom of her list because she’s busy trying to reach her base<br />
◦ It is better for her to send her funders to the social media page<br />
• Erick: Speaking on this<br />
◦ Website developer left the organization website half done<br />
◦ Couldn’t get anything done with it because of this<br />
◦ But eventually, after enough money was saved for it, it was fixed<br />
◦ Although now presentable, the website is for everyone else<br />
▪ It is not for the core membership; that’s what social media is for<br />
▪ Almost acting like a resume at this point<br />
◦ Maybe try linking to a chat platform so that you can transition interested parties into a more face to face/direct line of communication<br />
• Maegan: Challenges of outside devs vs. having internal people; and the language of tech.<br />
◦ Importance of documentation<br />
◦ Importance of documentation in many different forms<br />
▪ Different languages<br />
▪ Different modes: graphically vs. text, ect.<br />
◦ Make the things that have been documented accessible themselves<br />
◦ What’s gonna make it simple for people to understand a certain system?<br />
◦ As long as people can be seen and heard, don’t worry so much about the production value<br />
• Erick: More about doing it a way you’ve seen somewhere vs. doing it the way that would be the best for you or your members<br />
◦ Shooting and editing videos on your phone vs. using a professional camera and editing software<br />
• Luis: Speaking on this<br />
◦ Using what you know to make it work and make it work for the most people possible<br />
◦ Trying a new platform or method that actually will have an impact on people<br />
• Erick: Goes back to organizing; meet people where they are and go from there<br />
◦ Keeping this philosophy in mind when trying to implement new tech.<br />
• Maegan: Push for more multilingual documentation<br />
◦ Need to bring down this elitism of who can use the technology or have an influence on the design<br />
◦ Translation is an afterthought when it needs to be talked about from the get go<br />
▪ Needs to be habitual<br />
• Ryan: Making a case for volunteers<br />
◦ Advocating for them and the fact that you’re bombarding them with new surveys and tech and what not<br />
▪ Erick: “Treating them like employees”<br />
◦ Trepidation when it comes to implementing a new piece of technology or sending out a new survey<br />
• Maegan: “Temp checks”<br />
◦ Gathering feedback from organization members on what they are comfortable with<br />
◦ Just talk with people about how accessible things are<br />
▪ Start those conversations, poll those surveys<br />
◦ Many opportunities to fill gaps where there might be lack of understanding</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=How_to_find_tech_solutions_as_a_low_resource_organization&diff=618How to find tech solutions as a low resource organization2019-07-23T21:48:57Z<p>Evelyn: Created page with "How empowered do you feel implementing tech within your org? * Depends upon the scope. Working with tech challenged Program Managers are very open to any help. * A dedicated..."</p>
<hr />
<div>How empowered do you feel implementing tech within your org? <br />
* Depends upon the scope. Working with tech challenged Program Managers are very open to any help.<br />
* A dedicated I.T. person is new to org. Infrastructure of process and procedures not in place. Security and setup needed. Varies depending upon project and the necessary infrastructure that comes with the project<br />
* Agency works in law that cannot be replaced by technology. Using same tech as all law firms. Lawyers who try to empower people themselves by solving problems themselves.<br />
** There is a need for more tech to filter applicants/clients calling & helping people to refer them to the proper agencies.<br />
* Consults with non-profits to provide technology services.<br />
* Works with non-profits on communication technology.<br />
* There is no real funding for what is done but the feeling is empowered.<br />
<br />
What does everyone hoping to get out of this session?<br />
* Need to learn more about efficiency and technology.<br />
* Project managers inform of stable tools.<br />
* Listen and learn, find what's out there, what alternatives exist that are less expensive.<br />
* Learn technology sustainability with Program Managers.<br />
* Listen and learn. Relatively new to non-profit space. Obtain feedback of how tech is working for them<br />
* Struggling/fascinated by "making the case"/build effective narratives that leads to funders.<br />
** how people go about building narrative that...<br />
** Empowerment piece but depth of projects. Bring in tech that bring in radically different.<br />
** Leadership buy in.<br />
<br />
Universe of Technology Team: Yesenia, I.T. Manager at UCSC. Jessie, Concept Director. Harrison, Front End. Matt, UX design. Max, UX Researcher.<br />
<br />
How did you determine next org priority project?<br />
* Talk with E-team, give tech perspective, customer interviews. Data management issues and org priority.<br />
* Find a sponsor, don't be alone. Iterating and maintaining needs more than one perspective. Someone in a leadership role is powerful from a change management perspective.<br />
* Think about training and support broadly. Find tech champions in org. Train the trainers. Enthusiasm makes a difference. They don't have to be a SysAdmin.<br />
* What is your strategic plan for org?<br />
* Using leadership sponsorship so that you can get ahead of the curve.<br />
* What are the internal surprises?<br />
* Use a SWOT analysis. <br />
* Part of assessment helps determine tech needs<br />
* There is the idea that an IT person holds entire knowledge of the world.<br />
** Miscommunication can occur because of this.<br />
** Having a timeline helps.<br />
** Technology committee helps so that one person doesn't hold all of the keys.<br />
** The team makes a decision.<br />
** There can be more than one tech sponsor.<br />
** What's writing for if no one reads it? Sometimes too many meetings already though.<br />
<br />
How do you determine core needs or goals of project?<br />
* The guide recommends having different perspectives, dev, management, infra operations<br />
* R&D: program managers will come with problem that is then addressed/implemented.<br />
* One of the needs is communication, working with people, establishing identity<br />
* Foundational infrastructure lacking readiness. Backups and network access are core needs, come ahead of other less basic needs. Social media grants still need infrastructure to accomplish.<br />
* Org needs identity definitions upfront, referrals not direct processing. Sorting technology.<br />
* Need a supporter. ED deadlines overridden by program manager emergencies. Which fire do I put out first? Another perspective helps to determine priorities in multiple fires.<br />
* 5 minute problems take hours.<br />
* Figure out who key stake holders in project, leadership and staff members.<br />
<br />
* Clear roadmap of implementing technology.<br />
* Trying to find right social media platform.<br />
* Needs to be a way for a clear plan.<br />
* Before implementing tech solution,<br />
** Want to understand what is the project going to look like.<br />
** What capacity in time and day to day in implementing tech.<br />
** Do you have any supporters?<br />
** Who do you need to onboard?<br />
** Who is going to need to know tech going forward?<br />
** Having an understanding of who people are.<br />
** Who you are as an org.<br />
** Measurable stuff needs to be tracked.<br />
<br />
Some way that information infrastructure might be lacking in categories.<br />
* Mitigating catastrophic data loss.<br />
* Do we have any gaps in foundation pieces?<br />
* Look at foundational needs and prioritize them. How can gaps be addressed.<br />
* Org needs more identity as a core need. Have different legal specializations. They don’t' provide legal advice but instead gather people.<br />
<br />
<br />
After knowing project needs, how do you determine technical capacity of your org?<br />
* Who is working how many hours/week?<br />
* Evaluating time/people over budget.<br />
* The app does use algorithms for assessment.<br />
* Opportunity considerations, untapped community support, threat considerations.<br />
* How much time do people in the org have? Uptake of new tech can be disruptive if work is 60-80 hours/week. How much habit formation can reasonably happen?<br />
* Lack of documentation can disrupt continuity should the IT person no longer be available.<br />
<br />
Would be great to have external resources to bounce ideas off of<br />
* Outsourcing to https://alternativeto.net/<br />
* Crowd sourcing reviews of alternative software to whatever you’re looking for<br />
* making digestible content of app/map is what is being aimed for<br />
<br />
KEY TAKEAWAYS<br />
* Assessments & finding supporters.<br />
* Aloneness is common.<br />
* Name roles for projects. Non-techs can provide valuable support. <br />
* Idea of a committee is a great idea. can be formed for 1 project and disbanded. How to incorporate people from all parts of the organization to have different lenses.</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Tech_roles_at_nonprofits&diff=617Tech roles at nonprofits2019-07-23T21:39:47Z<p>Evelyn: </p>
<hr />
<div>Tech roles and responsibilities (Lisa (facilitator) / Max / Ryan)<br />
<br />
In nonprofits: Sometimes someone becomes the “accidental techie” - the body of knowledge is vast!<br />
<br />
* '''Tech Support'''<br />
** Someone should be holding tech support (but not necessarily solely responsible for solving)<br />
** Rule of thumb: It generally requires 1 hour per week per person for tech support<br />
** One solution: outsource tech support<br />
** Another solution: empower others to research it OR share your problem-solving skillsets to those who seem interested in addressing issues on their own<br />
<br />
* '''Tech needs & Individual tool management'''<br />
** If someone is good at something, they should be the one that does it (given that it’s written in their job description)<br />
** Periodically assessing the tools being used - can two be consolidated into one, etc,?<br />
** Designate an owner for each tool (maybe the person who uses it the most)<br />
** Keep an inventory (whether it’s in your password manager or elsewhere) with notes: who’s responsible for the tool<br />
** Offboarding process should include a passing the torch of knowledge<br />
<br />
* '''Documentation'''<br />
** It’s irresponsible not to have documentation<br />
** It may feel like no one reads it, but nails down organizational practices<br />
** Focus on the 95% of the tool/process usage (the edge-use cases don’t need as much focus)<br />
** Pretend you’re leaving next week - what do you want your replacement to know?<br />
** New people will read it and they have fresh eyes <br />
** Training new people is sometimes a good reason to update documentation (the trainees can even help you)<br />
** FAQs - can point people to resource if something is asked repeatedly <br />
*** Example: “How do I set up my out of office message?”,<br />
<br />
* '''Planning, Implementation, Delegating'''<br />
** Shadowing is a valuable tool<br />
** Time/project management: blocks of time on your calendar specifically for projects (even if you have to later move it)<br />
** Ask yourself, “Is this really urgent?” or “Can it wait?” when receiving new requests, issues. Etc.,<br />
** Being interruptible (available) vs not - it takes time to refocus after interruptions<br />
** Taking a day “off” when you’re actually devoting time for non-interruptible projects<br />
** Orientation to organizational culture (part of onboarding process)<br />
** Communication channels - text versus call versus instant message versus email versus desk visits<br />
** Helps differentiate what’s urgent<br />
** Provides expected wait time for different types of responses<br />
** Expectation management<br />
<br />
<br />
Notes: NTEN Technology Staffing Reports are worth exploring: Report page</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Tech_roles_at_nonprofits&diff=616Tech roles at nonprofits2019-07-23T21:38:00Z<p>Evelyn: Created page with "Tech roles and responsibilities (Lisa (facilitator) / Max / Ryan) In nonprofits: Sometimes someone becomes the “accidental techie” - the body of knowledge is vast! '''Te..."</p>
<hr />
<div>Tech roles and responsibilities (Lisa (facilitator) / Max / Ryan)<br />
<br />
In nonprofits: Sometimes someone becomes the “accidental techie” - the body of knowledge is vast!<br />
<br />
'''Tech Support'''<br />
Someone should be holding tech support (but not necessarily solely responsible for solving)<br />
Rule of thumb: It generally requires 1 hour per week per person for tech support<br />
One solution: outsource tech support<br />
Another solution: empower others to research it OR share your problem-solving skillsets to those who seem interested in addressing issues on their own<br />
<br />
'''Tech needs & Individual tool management'''<br />
If someone is good at something, they should be the one that does it (given that it’s written in their job description)<br />
Periodically assessing the tools being used - can two be consolidated into one, etc,?<br />
Designate an owner for each tool (maybe the person who uses it the most)<br />
Keep an inventory (whether it’s in your password manager or elsewhere) with notes: who’s responsible for the tool<br />
Offboarding process should include a passing the torch of knowledge<br />
<br />
'''Documentation'''<br />
It’s irresponsible not to have documentation<br />
It may feel like no one reads it, but nails down organizational practices<br />
Focus on the 95% of the tool/process usage (the edge-use cases don’t need as much focus)<br />
Pretend you’re leaving next week - what do you want your replacement to know?<br />
New people will read it and they have fresh eyes <br />
Training new people is sometimes a good reason to update documentation (the trainees can even help you)<br />
FAQs - can point people to resource if something is asked repeatedly <br />
Example: “How do I set up my out of office message?”,<br />
<br />
'''Planning, Implementation, Delegating'''<br />
Shadowing is a valuable tool<br />
Time/project management: blocks of time on your calendar specifically for projects (even if you have to later move it)<br />
Ask yourself, “Is this really urgent?” or “Can it wait?” when receiving new requests, issues. Etc.,<br />
Being interruptible (available) vs not - it takes time to refocus after interruptions<br />
Taking a day “off” when you’re actually devoting time for non-interruptible projects<br />
Orientation to organizational culture (part of onboarding process)<br />
Communication channels - text versus call versus instant message versus email versus desk visits<br />
Helps differentiate what’s urgent<br />
Provides expected wait time for different types of responses<br />
Expectation management<br />
<br />
<br />
Notes: NTEN Technology Staffing Reports are worth exploring: Report page</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Communications_strategies_and_resources&diff=615Communications strategies and resources2019-07-23T21:33:37Z<p>Evelyn: Created page with "Comms strategies with Erick 1. Instagram a. Can be used from a desktop if you inspect the code b. First place to post new photos c. Photography ba..."</p>
<hr />
<div>Comms strategies with Erick<br />
<br />
1. Instagram<br />
a. Can be used from a desktop if you inspect the code<br />
b. First place to post new photos<br />
c. Photography basics<br />
i. Framing a shot<br />
ii. Capturing facial expressions, candid shots<br />
d. Bios are where people include links<br />
i. Services are emerging to expand from an IG bio link to an expansive list of further links<br />
2. Decentralizing content admin<br />
a. Lots of free tools obviate traditional skill barriers (eg graphic design)<br />
i. Tweetdeck, Hootsuite for scheduling posts<br />
ii. Photo editing<br />
1. Canva<br />
2. Background Eraser<br />
3. Spark Post for (even animated) flyers<br />
iii. Life Hacker for video tutorials<br />
iv. Google “how to…” anything to find tutorials<br />
v. Repost to allow cross-platform replication of photo & text content<br />
vi. Photo grid for collages<br />
vii. Advice Animals for memes<br />
viii. Snapseed<br />
ix. Adobe Clip for basic video editing<br />
b. Leverage young people who wield native tool literacy<br />
c. User-centered perspective; consider how you use social media<br />
i. Do you like things that are aesthetically engaging?<br />
ii. Or do you just support cool orgs doing good work?<br />
d. How to empower folks without requiring / re-introducing centralization<br />
e. On the other hand, it’s worth pitching to funders requests for support for a professional comms staffer to add focus & coordination<br />
3. Competing platforms<br />
a. Instagram: visual storytelling; skews younger<br />
i. Especially engaging signs at a rally<br />
ii. Volunteers in action<br />
b. Facebook: deeper dives; skews older<br />
c. Twitter: <br />
d. Meet people where they’re at<br />
i. Snapchat: ephemeral chat<br />
ii. Dischord?<br />
iii. Twitch: gamers<br />
4. General principles<br />
a. Storytelling is a basic skill applicable across platforms<br />
b. Get an account on all services, even if you don’t use it—if only to keep someone else from claiming your brand / handle / preferred profile name<br />
c. Don’t be afraid to replicate content; a photo with text is the most basic content and is worth sharing more than once<br />
d. Beyond posting content: organize<br />
i. Recruit supporters on each platform. Share content with them. Ask them to share<br />
e. Phones are often easier to use than desktop platforms<br />
i. Adobe apps on desktops are pricey…but their mobile apps are remarkably sophisticated and generally free. It requires an account, but that’s free<br />
f. Platforms will offer suggestions based on your behavior, not your preferences<br />
i. If you like posts on topics x y z, that’s what you’ll see…<br />
ii. …even if those interactions are (to you) more or less random<br />
5. FB <br />
a. real names policy; how to craft & share content without using your personal profile / name<br />
i. Even branded pages are associated with individual pages<br />
ii. FB is moving into a more (not less) accountable model in the face of concerns re content moderation<br />
b. Paid promotion should focus on your original content (eg a blog post responding to a policy proposal)<br />
i. Running a consistent paid promotion can diminish the visibility of your content; FB trains account holders to become paid customers<br />
6. Hardware<br />
a. A tripod + a grip (some of which can swivel from portrait to landscape) can turn any phone into an effective video capture device<br />
b. Battery chargers can liberate your use of mobile</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6142019 Los Angeles Agenda2019-07-23T21:32:02Z<p>Evelyn: </p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event will start with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants will engage in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants will be encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions II ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
* Universe of Technology - Everett Program crew<br />
* Aktioner, mobile app for local civic engagement - Nemo<br />
* Digital Security Checklists - Jonah<br />
* Mapping as a powerful tool - Mago<br />
* Phone photo and video editing - Erick<br />
* EFF tools - Shahid<br />
* Tor browser - Gunner<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working SessionsIII ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions. <br />
<br />
* '''[[CRM Tracking leadership development]]''' - Lisa<br />
* '''[[All about cooperatives]]''' - Andrea<br />
* '''[[Bilingual communications processes and social media tactics]]''' - JMo and Karen<br />
* '''[[Deep resistance]]''' - Maxwell<br />
* '''[[Combatting police surveillance]]''' - Ken and Shahid<br />
* '''[[Our relationship with our data]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=2019_Los_Angeles_Agenda&diff=6132019 Los Angeles Agenda2019-07-23T21:19:21Z<p>Evelyn: /* Collaborative Working Sessions */</p>
<hr />
<div>The following is the working agenda for the California Nonprofit Technology Festival in Los Angeles on '''July 10 - 11, 2019'''.<br />
<br />
<br />
= '''Tuesday, July 09, 2019''' =<br />
<br />
'''Afternoon: Travel Day'''<br />
<br />
Out-of-town participants start to arrive<br />
<br />
= '''Wednesday, July 10, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Welcome and Opening Circle ==<br />
<br />
The event will start with introductions and welcomes, an overview of the agenda and guidelines, and announcements.<br />
<br />
== Stories from Across LA and Around the State ==<br />
<br />
Participants will engage in story-sharing and conversations about work they are doing in their various communities and movements.<br />
<br />
* Supporting and organizing with young folks in Fresno and Merced - Ines and Vanessa<br />
* Issues and challenges of organizing day labor worker centers in LA - Guadalupe<br />
* Organizing for tenant's rights in East LA - JMo and Pamela<br />
* Advocating for active mobility and transportation justice throughout LA - Erick<br />
* Advocating for food justice and access throughout Los Angeles - Valeria<br />
* What it takes to mobilize a network advocating for Media Justice nationwide - Adrian<br />
<br />
== Break ==<br />
<br />
== Agenda Hacking: Mapping Technology Needs and Knowledge==<br />
<br />
== Lunch ==<br />
<br />
Participants will be encouraged to sit with friends they have not yet met!<br />
<br />
== Collaborative Working Sessions I ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[How to find tech solutions as a low resource organization]]''' - Yesenia<br />
* '''[[Communications strategies and resources]]''' - Erick<br />
* '''[[Phone security 101]]''' - Ken<br />
* '''[[Tech roles at nonprofits]]''' - Lisa<br />
* '''[[Challenges and best practices for managing multilingual work]]''' - Mago<br />
* '''[[Storytelling as a tool for reaching our goals]]''' - Gilda<br />
* '''[[Facilitative leadership]]''' - Misty<br />
* '''[[Funding Technology]]''' - Gunner<br />
<br />
== Break ==<br />
<br />
== Group Picture ==<br />
<br />
[https://www.flickr.com/photos/aspirationtech/48324150872/in/album-72157709746969291/]<br />
<br />
== Peer Skillshare ==<br />
<br />
== Closing Circle ==<br />
<br />
== Adjourn Day 1 ==<br />
<br />
Participants are welcome to stay after and ask additional questions.<br />
<br />
== Post-Event Hang Out ==<br />
<br />
= '''Thursday, July 11, 2019''' =<br />
<br />
== Coffee and light breakfast ==<br />
<br />
== Opening Circle ==<br />
<br />
== Collaborative Working Sessions ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions.<br />
<br />
* '''[[Project Management 101]]''' - Gunner<br />
* '''[[Digital inclusion and meaningful access]]''' - Maegan<br />
* '''[[Facilitative leadership development conversation continued]]''' - Misty<br />
* '''[[Stories and lessons learned from nonprofit and tech shop collaborations]]''' - Andrea<br />
* '''[[How to hold warmth and depth in virtual spaces]]''' - Jonah<br />
* '''[[Managing burnout]]''' - Marty<br />
<br />
== Break ==<br />
<br />
== Speed Geeking ==<br />
<br />
Participants present and share work they are doing in their various regions and fields, in a fast-paced collaborative format.<br />
<br />
== Lunch ==<br />
<br />
== Collaborative Working Sessions ==<br />
<br />
Participants will choose from 5-7 working groups, and will be welcome to suggest or request additional sessions. <br />
<br />
== Break ==<br />
<br />
== Where From Here ==<br />
<br />
The group will pause to take stock of the progress made to this point and to inventory action items, next steps, and other bridges to post-event collaborations. <br />
<br />
== Closing Circle and Appreciations ==<br />
<br />
== Adjourn ==</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Challenges_and_best_practices_for_managing_multilingual_work&diff=612Challenges and best practices for managing multilingual work2019-07-22T19:54:17Z<p>Evelyn: Created page with "Technology for multilingual spaces breakout Facilitator: Mago Key Takeaways: *+2 Addressing different ways of using technology across generations and cultures so that no o..."</p>
<hr />
<div>Technology for multilingual spaces breakout<br />
<br />
Facilitator: Mago<br />
<br />
Key Takeaways: <br />
<br />
*+2 Addressing different ways of using technology across generations and cultures so that no one is excluded.<br />
<br />
**Thinking of IT as a language<br />
<br />
*Not speaking IT language while also working multilingual communities. → funding/time for IT training <br />
<br />
*+4 Resources + funding for interpretation and interpretation equipment + budgeting for interpretation <br />
<br />
**Skillsharing + solidarity network <br />
<br />
**Training for bilingual folks (maybe retired?) to become skilled interpreters <br />
<br />
*+3 Time/capacity/compensation <br />
<br />
*+2 Just compensation for interpreters → shifting the dynamic <br />
<br />
**Systemizing our grant applications → keep interpretation as line item in all programs <br />
<br />
**Advocating for foundations to have a fund available for orgs to access when interpretation is needed <br />
<br />
***Stats and resources about language justice to advocate<br />
<br />
**Hire staffed interpreters for orgs that have regular interpretation needs <br />
<br />
*How could Aspiration network advance this issue? <br />
<br />
**Start by naming it / sharing the story / the systemic need with foundations<br />
<br />
*What tech resources exist that can support multilingual spaces? <br />
<br />
**How can technology be of service to facilitating multilingual spaces online specifically? <br />
<br />
**e.g. webinars → How to pull off simultaneous interpretation online?<br />
<br />
**Creating multilingual digital networks that can be accessed easily by phone / don’t require a high level of tech skill<br />
<br />
Go around<br />
<br />
* Mago - Journalist <br />
<br />
Learning to embrace my bilingual reality <br />
<br />
How to create multilingual networks of journalists<br />
<br />
* Guadalupe - IDPSCA<br />
<br />
Challenges with language, not just Spanish/English but also tech languages and indigenous languages <br />
<br />
What are resources to improve our communication? <br />
<br />
* Shirley<br />
<br />
Volunteers with API LGBTQ org and there are many different languages represented <br />
<br />
How to find translators for materials<br />
<br />
Website tips? <br />
<br />
Google translate bar on <br />
<br />
* Adriana - L.A. Co-op Lab <br />
<br />
Creating multilingual digital networks that can be accessed easily by phone / don’t require a high level of tech skill <br />
<br />
Shirley: Members start posting things that are <br />
<br />
* Yanely - Refuge for Families <br />
<br />
How can technology be of service to facilitating multilingual spaces online? <br />
<br />
Works with folks in El Salvador and connects with <br />
<br />
Other challenges:<br />
<br />
* Lack of relationships with indigenous interpreters <br />
<br />
* For transnational work, people have different ways of speaking about things, need to know nuances<br />
<br />
* The way we prioritize language puts Spanish/English translation at the top and often sidelines other immigrant communities <br />
<br />
* Staff members who don’t speak the same language</div>Evelynhttps://catechfest.aspirationtech.org/index.php?title=Phone_security_101&diff=611Phone security 1012019-07-22T19:48:12Z<p>Evelyn: Created page with "It's really important to understand that our phones are a combination of many different computers. Such an understanding helps us address the security risks they pose. Our ph..."</p>
<hr />
<div>It's really important to understand that our phones are a combination of many different computers. Such an understanding helps us address the security risks they pose.<br />
<br />
Our phones are often a GPS, accelerometer, altimeter, camera, modem, and sometimes even an FM radio!<br />
<br />
If we were to reduce this to what is practicable, here are 5 immediate steps we can take to increase security on our phones:<br />
<br />
1. Lock your phone with a PIN. There are instances, like a casino or<br />
heavily surveilled airport, where using a fingerprint makes<br />
sense...but largely, if you use a PIN greater six or more digits,<br />
you'll prevent a casual intrusion.<br />
2. Encrypt your phone and turn on secondary security on apps when<br />
possible. Most versions of iOS/Apple & Android mobile operating<br />
systems now come with encryption turned-on out of the box. Double<br />
check and if it isn't turned on, turn it on. Some apps, like Signal,<br />
allow you to have an app specific password so that if someone breaks<br />
the encryption on your phone, they don't have access to your<br />
messages in the secured application.<br />
3. Practice greater app security and permissions scrutiny. Does the<br />
flashlight app need access to your contacts? Why does your email app<br />
need access to SMS? Have a look at these permissions and if they<br />
don't make sense, don't grant permissions. Facebook is an app which<br />
should get a high degree of scrutiny: it attempts to take all your<br />
contact information and, even if you're careful, might take it after<br />
an app update. Try to access FB (if you must) through a browser<br />
interface.<br />
4. Know your environment and practice phone hygine: if you are engaged<br />
in work, even now and then, that could put traditionally targeted<br />
populations at risk, practice message hygine! Delete messages and<br />
photos that could put folks at risk. Our phones are like filing<br />
cabinets that rarely get cleaned out and sometimes what we keep...or<br />
forgot we have...can put folks at risk.<br />
5. Understand there are times where having no phone is the best<br />
strategy...this doesn't mean get rid of your phone but knowing there<br />
are times where an unplugged microwave oven or a faraday bag are<br />
your friends to go dark. There's something nefarious afoot when<br />
phones no longer have removable batteries.<br />
<br />
In the end, phone security begins with understanding our phones a little better and taking small practical steps to reduce the harm they can cause in our mission driven work.</div>Evelyn