+ All Categories
Home > Business > Considerations for the successful design & implementation of ICT systems in the WASH sector

Considerations for the successful design & implementation of ICT systems in the WASH sector

Date post: 09-Aug-2015
Category:
Upload: irc
View: 231 times
Download: 0 times
Share this document with a friend
31
Considerations for the successful design & implementation of ICT systems in the WASH sector David Schaub-Jones www.greenseesaw.com
Transcript
  1. 1. Bymid-2013 more Africans willhave a mobile phonesubscription than access to animproved water source (Foster et al., 2012a)
  2. 2. InZambia, Tanzania and Kenya Afterinstalling digital monitoringsystems coverage rates in urban areaswere significantly revised. Before: coverage rates were being reported ataround 90% (across these three countries). After: rates were reported at solely 47%(GIZ 2009)
  3. 3. Cape-Townbased Focus: ICT & WASH services1.Advice2.Training3.Software very interested not just in the technology, buthow and why it gets used
  4. 4. 2 day workshop@ 40 peopleco-hosted by SeeSaw and theUniversity of Cape Town explored ICT-related trends and challenges inboth the WASH & health sectors.
  5. 5. 11/2 day training course @ 20 people ICT-relatedtrends andchallenges Discussed potential use ofICT in delegated regulation
  6. 6. linear and closed flow of information
  7. 7. new ICT tools allow radical changes
  8. 8. Simplified servicetriangleStakeholders directly involved in service provision Indirect stakeholdersGovernmentalProviders authorities NGOsDonors FinanciersHouseholds(Sattler & Schaub-Jones, 2012)
  9. 9. ce rvid se f iep liS im n g le c ire Ind triai on vis prorvicee rs sevid edin Pr oolv y inv ctl d iree rsold eh akt alSt en nm sver ritieGo utho as old ehusHo
  10. 10. ceGovt, Regulators, Donors, NGOs rvi dsef ie p li S im n g le c ire IndProviderstriai on vis prorvicee rs sevid edin Pr oolv y inv ctl d iree rsold eh akt alSt en nm sver ritieGo utho as Customers old ehusHo
  11. 11. . what information to collect? from whom and how often ?.... rather than no data availableA new issue? too much information, lack of relevant information
  12. 12. Too often the tools & the ability to collect data in a different way is the focusNot sufficient attention to:1. what the data gets used for2. how the provision of data can actually change the dynamics of the situation3. how reliable the data is4. who will continue to provide it oncenovelty value has worn off.
  13. 13. Agent-basedsystems (i.e. staff)Crowd-sourcedsystems(i.e. public)Automated monitoring (e.g. via mobile networks)
  14. 14. Challenges with crowd-sourcing Vested interests remain Not all are literate Not all tech just works Distrust of the system can lead to lowparticipation Seeing is believing
  15. 15. USSDSMSVoiceInternetportalsAndroid phones & appsAutomatic sendingetc ...
  16. 16. 1998 Google founded2004 Facebook launched2007 M-Pesa created2008More people access internet on cellphones than PCs2008 First android phone ships2010 iPad launched
  17. 17. Before askingWhat system? come a range of other questions that people making decisions about using ICT need to ask
  18. 18. Will ICT change underlyingbehaviours? Is it expected to? Why will users provide reliableinformation to the system? Are there incentives? What is the full cost ofthe system(time, effort, $$$) andwhere do these resources come from?When is the info needed?What system How often is itis appropriate sent?to localconditions?Hierarchy of What system isquestions to ask indeveloping a new appropriate to local WhatICT systemconditions?system is(SeeSaw, 2013) appropriat
  19. 19. Key lessons
  20. 20. Can pay for itself quite quickly efficiency gains costs savedYet design system to local context just transplanting a system from onecontext to a new environment is generallytroublesome.
  21. 21. 1) Understanding the system2) Asking direct stakeholders what - information they currently get & - what information they need
  22. 22. Only then see whether ICT systemscan generate- additional- better or- faster information(and get it to where it is needed)+ suit existing working patterns
  23. 23. Must integrate with existing governmentsystems. There is a great risk of fragmentation(Too many organisations piloting new ICT systems put inplace technologies or processes that cannot easily beabsorbed into existing government systems - or worsestill, undermine these).
  24. 24. More data (on its own)= Better Results
  25. 25. Technologyitself is rarely the issueWidely available or easily developedCrucial to make technology demand- oriented and fit-for-purpose.Make data entry as simple as possibleDonot overburden participantsin any system
  26. 26. Above all pay close attention tothe incentives of key stakeholders those that need to adopt the system, those whose inaction can block it & those who will resist change altogether.

Recommended