This document discusses the use of digital tools and ICT4D (information and communication technologies for development) in development programs. It notes that there is no single standardized approach or methodology, and focus should be on demonstrating benefits rather than just using tools. It outlines a 4-step methodology for designing programs based on user needs. It also lists 6 rules of thumb for selecting digital tools, emphasizing mapping needs, considering existing tools, testing options, planning for adjustments, and reflecting on what works. Overall it stresses the importance of focusing on impact and sustainable systems designed with local partners and beneficiaries rather than just projects or tools.
4. there is no standard answers / tools /
methodologies easily and broadly replicable
=> the sector if far from being mature
the shortcoming of doing what is easier (the
tools) vs complex (the benefits) is broadly
present
=> there is room for (new) actors that will
effectively demonstrate that focus
25/11/2016 Agridays BTC 2017 5
My conclusions
5. 25/11/2016 Agridays BTC 2017 6
Design from the needs / be flexible
Building blocks (source: Matt Morris (YBI)
ICT4D2016 8th conference)
6. • SIMLab 4-step simple methodology
(i) define persona of users, (ii) map the
system, (iii) formalize the needs, and (iv)
define your tech. specifications
• “The engine room” (38 Ke/SA org choose
digital tools => less than 1/4 were happy
with the choices)
Tool selection assistant and 6 rules of thumb
25/11/2016 Agridays BTC 2017 7
Design from the needs / be flexible
7. 1. Map out what you need to know: 1) the goal or problem (2) the
interests and needs of the people and (3) the tool options
available (video)
2. Think twice before you build: Look for existing tools
3. Get a second opinion: Someone has probably tried it before
4. Always take it for a test drive: Trial the tool with the people you
want to use it, before making a choice
5. Plan for failure: budget for a series of adjustments
6. Reflect on what you're doing: Keep thinking about what is
working, and what isn’t. and share with other organisations
(video)
25/11/2016 Agridays BTC 2017 8
6 rules of thumb
9. We can have (i) as many data as we want, (ii) that we
share as openly as feasible, and (iii) that we have
assessed their SMARTness as rigorously as
workable
If we do nothing with it, their value is NULL
A corollary is that as long as it helps us find some
interesting information leading us towards a
sustainable (and if possible maximised) impact
we can even use raw and/or incomplete data
21/06/2016 Agridays BTC 2017 11
Focus on Impact
10. • too easy too cheap: paradox and major risk of ICT4D => Impact
(use of the data and tools) should remain the goal
• sustainable systems are the ones that allows flexibility in their
conception and tools used => there is no “one size fits all”
• “less advanced” technology and tools such as SMS and IVR or
even the paper forms
• scale-up should be considered from the start
• data and systems with local partners and beneficiaries VS
project (or own organisation)
• Costs of tools is only one element => support and operation
25/11/2016 Agridays BTC 2017 12
too easy too cheap
