Presentation for African Utility Week providing early lessons on the use of ICT (Information Communications Technology) in the water sector in developing countries. Given 15 May 2013 in Cape Town by David Schaub-Jones, co-founder of SeeSaw, an organisation that specialises in "smarter water systems through training, advice and software". Find more at http://greenseesaw.com

3. By mid-2013 more Africans will
have a mobile phone
subscription than access to an
improved water source
(Foster et al., 2012a)

4. In Zambia, Tanzania and Kenya
After installing digital monitoring
systems coverage rates in urban areas
were significantly revised.
 Before: coverage rates were being reported at
around 90% (across these three countries).
 After: rates were reported at solely 47%
(GIZ 2009)

5. Cape-Town based
Focus: ICT & WASH services
1. Advice
2. Training
3. Software
“ very interested not just in the technology, but
how and why it gets used “

6.  2 day workshop@ 40 people
co-hosted by SeeSaw and the
University of Cape Town
 explored ICT-related trends and challenges in
both the WASH & health sectors.

7. 11/2 day training course
@ 20 people
ICT-related trends and
challenges
Discussed potential use of
ICT in delegated regulation

8.  linear and closed flow of information

9.  new ICT tools allow radical changes

10. Simplified ‘service’
triangle
ProvidersGovernmental
authorities
Households
NGOs
Donors
Financiers
Stakeholders directly involved in service provision Indirect stakeholders
(Sattler & Schaub-Jones, 2012)

11. Simplified‘service’
triangle
Providers
Governmental
authorities
Households
Stakeholdersdirectlyinvolvedinserviceprovision
Indirec

12. Simplified‘service’
triangle
Providers
Governmental
authorities
Households
Stakeholdersdirectlyinvolvedinserviceprovision
Indirec
Regulators
Customers Providers

14. .
 what information to collect?
 from whom and how often ?
.... rather than ‘no data available’
A new issue?
 too much information,
 lack of relevant information

15. Too often the tools & the ability to collect
data in a different way is the focus
Not sufficient attention to:
1. what the data gets used for
2. how the provision of data can actually change
the dynamics of the situation
3. how reliable the data is
4. who will continue to provide it once
novelty value has worn off.

16. 1998 Google founded
2004 Facebook launched
2007 M-Pesa created
2008 More people access
internet on cellphones than PCs
2008 First android phone ships
2010 iPad launched

17. Before asking
What system?
come a range of other questions that
people making decisions about using ICT
need to ask

18. What
system is
appropriat
Hierarchy of
questions to ask in
developing a new
ICT system
(SeeSaw, 2013)
What system is
appropriate to local
conditions?
Will ICT change underlying
behaviours? Is it expected to?
Why will users provide reliable
information to the system? Are
there incentives?
What is the full 'cost' of
the system (time,
effort, $$$) and where
do these resources
come from?
When is the
info needed?
How often is it
sent?
What system
is appropriate
to local
conditions?

19. Key lessons

20. Can pay for itself quite quickly
• efficiency gains
• costs saved
Yet design system to local context
• just transplanting a system from one
context to a new environment is generally
troublesome.

21. 1) Understanding the system
2) Asking direct stakeholders what
- information they currently get &
- what information they need

22. Only then see whether ICT systems
can generate
- additional
- better or
- faster information
(and get it to where it is needed)
+ suit existing working patterns

23. Must integrate with existing government
systems.
There is a great risk of fragmentation
(Too many organisations piloting new ICT systems put in
place technologies or processes that cannot easily be
absorbed into existing government systems - or worse
still, undermine these).

24. More data (on its own)
=
Better Results

25. Technology itself is rarely the issue
Widely available or easily developed
Crucial to make technology demand-
oriented and fit-for-purpose.
Make data entry as simple as possible
Do not overburden participants
in any system

26. Above all pay close attention to
the incentives of key stakeholders
• those that need to adopt the system,
• those whose inaction can block it &
• those who will resist change altogether.