Difference between revisions of "NGO workflows and how to choose your tools"

From DevSummit
Jump to navigation Jump to search
Line 1: Line 1:
1. Introduction
+
==Introduction==
 
+
===Review of the work done in the [[Mapping_out_NGO_Workflows]] session on Day 2===
1.1 Review of the work done in the "Mapping out NGO Workflows" session on Day 2.
+
===Overview of key workflows emerged from discussions about technology infrastructure for NGOs===
 
 
See [https://devsummit.aspirationtech.org/index.php?title=Mapping_out_NGO_Workflows notes from the "Mapping out NGO Workflows"] session.
 
 
 
1.2 Overview of key workflows emerged from discussions about technology infrastructure for NGOs
 
 
 
 
* Share a file internally with trusted colleagues
 
* Share a file internally with trusted colleagues
 
* Share a file externally with known organizations and allies
 
* Share a file externally with known organizations and allies
Line 17: Line 12:
 
* Author a grant proposal
 
* Author a grant proposal
 
* Compile the end of the year budget
 
* Compile the end of the year budget
 
+
==Session Notes==
2. Session Notes
+
===Workflows taken as reference===
 
 
2.1 Workflows taken as reference
 
 
 
 
* Share a file internally with trusted colleagues
 
* Share a file internally with trusted colleagues
 
* Share a file externally with known organizations and allies
 
* Share a file externally with known organizations and allies
Line 30: Line 22:
 
* Annotate/ comment on document
 
* Annotate/ comment on document
  
2.2. What are folks current using?
+
===What are folks current using?===
 
 
 
* Email
 
* Email
 
* Dropbox, Box.net
 
* Dropbox, Box.net
Line 42: Line 33:
 
* GitHub
 
* GitHub
  
2.3 Values identified
+
===Values identified===
 
 
 
* Privacy
 
* Privacy
 
* Security
 
* Security
Line 53: Line 43:
 
* Openness
 
* Openness
  
2.4 Brainstorming: What questions should we ask?
+
===Brainstorming: What questions should we ask?===
 
 
 
* What is the tech literacy of participants?
 
* What is the tech literacy of participants?
 
* Who are the actual adversaries?
 
* Who are the actual adversaries?
Line 74: Line 63:
 
* Who needs what permissions?
 
* Who needs what permissions?
 
* How many people need access?
 
* How many people need access?
 +
 +
[[Category: 2016]] [[Category: Tools]] [[Category: Workflows]]

Revision as of 18:58, 22 November 2016

Introduction

Review of the work done in the Mapping_out_NGO_Workflows session on Day 2

Overview of key workflows emerged from discussions about technology infrastructure for NGOs

  • Share a file internally with trusted colleagues
  • Share a file externally with known organizations and allies
  • Share a file publicly
  • Set up a conference call
  • Set up a 1:1 call
  • Set up a webinar
  • Set up an in person meeting
  • Send an end-of-the-year donation-drive newsletter
  • Author a grant proposal
  • Compile the end of the year budget

Session Notes

Workflows taken as reference

  • Share a file internally with trusted colleagues
  • Share a file externally with known organizations and allies
  • Share a file publicly

Steps included in these workflows:

  • Coordinate document sharing
  • Annotate/ comment on document

What are folks current using?

  • Email
  • Dropbox, Box.net
  • Asana
  • Trello
  • Skype
  • Slack messages
  • Basecamp
  • Google Drive
  • GitHub

Values identified

  • Privacy
  • Security
  • Anonymity
  • Resiliency
  • Sustainability
  • Usability
  • Accessibility
  • Openness

Brainstorming: What questions should we ask?

  • What is the tech literacy of participants?
  • Who are the actual adversaries?
  • Where are the files?
  • What path do the files take?
  • How do we manage usability and security?
  • Who is watching?
  • Is there a "fear factor" in adopting new technology? e.g. fear of learning new? e.g. fear of the tech itself?
  • How do we determine/ maintain data integrity?
  • What is the server configuration?
  • What is the level of security culture (of the org)?
  • What is the path to adoption (within an organization)?
  • What factions are we dealing with?
  • What belief structures are embedded in existing ways of working?
  • What is the budget/ resources of the org?
  • What is the level of security culture of the provider?
  • What is the timeline/ time restraints?
  • What is the bandwidth?
  • Who needs what permissions?
  • How many people need access?