On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
Awaiting Data Input – Haiti (Save the Children USA)
Survey Coordinator – Bolivia (Save the Children USA)
Microfinance Registries – Myanmar (Save UK)
Laptop Netbook PDA The Tools Cell Phones
Because it is everywhere…
Start with the end-user in mind. How can mobile technology help them do what they’re already doing? - Adam Slote Chief Health Advisor, USAID Global Health, GH Mini U, October 2010
“People don't want to have apps which solve what YOU think are problems They want apps which solves what THEY think is a problem.” - Christopher Kusek (@CXI), retweeted by Ed Jezierski (@edjez) 3 May 2011
The Users Photo: CommCare – Futures Group, 18 Dec 2009
Each technology deployment has unique characteristics and needs.
The solution must be carefully thought out. It must be inclusive of all stakeholders.
Fight the urge to push the solution without input of all stakeholders.
The solution must satisfy the program need. But, it must work in the hands of the User.
It’s not about technology… it’s about People.
Afghanistan March 2011
Technology is becoming easy... Problems can be solved - they are technical!
The Challenge is: Point of interaction between user and beneficiary
How should I begin?
Technology Solution Criteria Functionality - What can it do? Usability - Can it be used? Scalability – Can it be used on a wider scale?
Functionality 1st – clearly understand your “What”
Program and intervention needs.
M&E indicators(Results Framework)
Functionality The “What” always precedes the “How” (The “How” is the technology “Solution”)
Functionality Technology serves your “What”… …not the other way around. Resist forcing your “What” to fit the “How”.
Usability Technology always works in the lab and during training… …it can quickly become irrelevant in the context of field conditions.
Usability “If it doesn’t work in the field… …then it doesn’t work”.
Scalability Small pilots are often successful… but they seldom scale up to wider implementations
Scalability So….Your solution worked! Can your solution expand to additional locations? Hint: Consider “Cloud”-based Software as a Service” (SaaS) solutions.
Additional Considerations Before You Begin Connectivity: not available available Power availability: low (car battery/solar) high Data transfer method: USB SMS GPRS Network Data quality: not important important Survey structure: simple complex (branching) Data Privacy and Security: low high
mHealth and the CHW Google Groups: ICT4CHW firstname.lastname@example.org Moderated by Dr. Neal Lesh of D-Tree