"subjective factors in ict4d deployment"
DESCRIPTION
presentation by David isaak of SixBlue Data at Catholic Relief ServicesTRANSCRIPT
Subjective Factors in ICT4D Deployment
Catholic Relief Services ICT4D 2010
El Salvador VietnamBangladesh HaitiGuatemala Mali Bolivia Guinea
Tajikistan Armenia
Philippines MalawiEgypt MyanmarUganda Jordan
Pakistan YemenSudan West Bank
Where I Have worked
Each deployment has unique
characteristics and logistic needs.
ICT4D Deployments
We used to bring our work to the computer…
Now, we take computing to our work
Centralized Information Management
Survey Coordinator – Bolivia (Save the Children USA)
Microfinance Registries – Myanmar (Save UK)
Awaiting Data Input – Haiti (Save the Children USA)
Increasingly, technology is becoming easy.
Technical problems can be solved…since they
are technical by nature.
There are many device tools….
Cell PhonesPDA
NetbookLaptop
The Tools
There are many fine software solutions…
Solution Providers
Tool Name Developed By Runs On Service Model
Data
Transfer
Method
Souktel Souktel
SMS-enabled
phone web server SMS
FrontlineSMS Kiwanja.net
SMS and Java-
enabled phone free SMS
RapidResponse UNICEF
SMS-enabled
phone enterprise - server SMS
JavaRosa OSC
Java-enabled
phone free (open source) GPRS only
Mobile Researcher Clyral
Java-enabled
phone pay-per-survey
SMS or
GPRS
EpiSurveyor Datadyne Palm O/S only free (open source)
USB or
GPRS
Nokia Data Gathering Nokia Nokia O/S only free for NGO's
SMS or
GPRS
Open Data Kit Google
Android O/S
only free (open source)
But, there are other factors to consider…
User Acceptance
Curious, but Skeptical…
I am Curious….
Let Me Try That!
Trust
What is that?
Interesting….
What Device?
Cultural Context
Cultural
Cultural
Gender
Listen to the Users
“If it doesn’t work in the field…
…then it doesn’t work”.
First Things First…
So….which mobile solution should I use?
The “What” determines the “How”
The technology “tool” comes Last - Always
Don’t try to force the solution to the need
“Tool” Determinants
Do the hard work (requirements) first,
or else you will have to do the hard work later…
If you decide to choose the tool first, then:
Best scenario: added cost, delay and poor program quality.
Worst scenario: resulting failure possibly costing lives.
“Tool” Determinants
Connectivity: not available available
Power availability: low (car battery/solar) high
Data transfer method: USB SMS GPRS VPN
Data quality: not important important
Survey structure: simple complex (branching)
Information complexity: text-only data/spatial/image
Data security: low high
Environmental: mild severe
Technical Support: low risk high risk
Tool” Determinants - continued
Risk Mitigation
Fearlessly face what could go wrong….
Develop a plan for when it does go wrong!
(something will happen unexpectedly)
Recommended Best Practices
• Use technology that is simple, relevant, local.
• Build on what is already working.
• Assess and mitigate risks
• Engage Stakeholders
• Build local capacity to develop and maintain the solution.
• More is learned from what fails, than from what succeeds…
Questions….?