In July, I wrote a post about how international development needs to disrupt itself. In talking to development practitioners since, I realized the issue of timing in ICT4D projects is one that many have encountered, so I thought I'd elaborate on what exactly I mean.
Of course there are many elements that make up an ICT4D project, but simplicity's sake, let's say we can roughly split up the project into two elements - the ICT platform itself and the international development context. The former is easy to understand; the latter includes everything from the problem statement, to the economic implications, to the need, to the funding, and the monitoring and evaluation metrics and systems.
For example, suppose you want to design a project that allows female small merchants in Senegal to deposit their earnings via a free SMS in order to reduce the rate of robberies in the area. Your ICT platform would obviously need to work with local Senegalese mobile phones and carriers, connect to relevant financial institutions, and be able to be monitored. Development of the ICT platform will certainly take time, though given the number of open sourced platforms there are, the amount of technical documentation, and prevalence of SMS campaigns and usage, one would imagine the ICT platform development is fairly straightforward in competent hands.
On the other hand, building the international development context is less straightforward. How many women have access to phones in this particular region of the country? Are there negative cultural implications to these women having phones or handling money, including electronically? Would the possible stakeholders/clients/beneficiaries use such a tool? Even if all of these questions have been answered before somewhere else, do those answers apply here? Further, who is going to fund the cost of development and implementing the project? How is success going to be measured, both in terms of usage and determination of usage?
Timeline of ICT Platform and International Development Context Development
Unsurprisingly, it has been both my experience and the experience of most (if not all) ICT4D practitioners I know that the project development timeline looks like the above. A working beta or even version 1.0 of the ICT platform is created and ready to be deployed well ahead of building the international development context, especially in determining steady funding and making sure beneficiaries/stakeholders/clients know about and are prepared to use the platform.
What this essentially means is that for two reasons, the ICT development lifecycle doesn't flow as it would otherwise:
ICT Project Development Lifecycle
First, after creating the beta/version 1.0, without having beneficiaries/clients/stakeholders ready to test the tool as it would be used in the actual project, knowing to whom, where and how to deploy is often unknown. Imagine building a piece of software that does taxes, only you're not entirely sure you'll have access to people who actually pay taxes, so you don't know whether to make the software into something else and expand the scope of people who might want to use your software.
Second, critical and relevant user feedback is therefore also often not possible. Instead of giving your software to people who pay taxes to check to see if the software calculated their tax return properly, all you can do is give the software to people who don't pay taxes and see how much they understand even though they're an irrelevant group of people. You'll get feedback on the interface, aesthetics, and functionality of the software, but you still won't know if the software actually works before you have go back and make corrections for version 2.0.
In an ideal world, the iterative process in ICT platform development would happen indefinitely as technology evolves. In reality, resources in international development are scarce given the size of a problem, and highly skilled technologists can only be secured for small periods of time.
Going back to my other post, what this means is that the international development side of ICT4D projects needs to disrupt itself. Personally, I think there are ways to use existing ICT platforms to more quickly, more efficiently and more accurately to build the international development context. I have a few ideas of how to break these context parts down, and the accompanying solutions are something I hope to explore in the future.
Of course there are many elements that make up an ICT4D project, but simplicity's sake, let's say we can roughly split up the project into two elements - the ICT platform itself and the international development context. The former is easy to understand; the latter includes everything from the problem statement, to the economic implications, to the need, to the funding, and the monitoring and evaluation metrics and systems.
For example, suppose you want to design a project that allows female small merchants in Senegal to deposit their earnings via a free SMS in order to reduce the rate of robberies in the area. Your ICT platform would obviously need to work with local Senegalese mobile phones and carriers, connect to relevant financial institutions, and be able to be monitored. Development of the ICT platform will certainly take time, though given the number of open sourced platforms there are, the amount of technical documentation, and prevalence of SMS campaigns and usage, one would imagine the ICT platform development is fairly straightforward in competent hands.
On the other hand, building the international development context is less straightforward. How many women have access to phones in this particular region of the country? Are there negative cultural implications to these women having phones or handling money, including electronically? Would the possible stakeholders/clients/beneficiaries use such a tool? Even if all of these questions have been answered before somewhere else, do those answers apply here? Further, who is going to fund the cost of development and implementing the project? How is success going to be measured, both in terms of usage and determination of usage?
Timeline of ICT Platform and International Development Context Development
Unsurprisingly, it has been both my experience and the experience of most (if not all) ICT4D practitioners I know that the project development timeline looks like the above. A working beta or even version 1.0 of the ICT platform is created and ready to be deployed well ahead of building the international development context, especially in determining steady funding and making sure beneficiaries/stakeholders/clients know about and are prepared to use the platform.
What this essentially means is that for two reasons, the ICT development lifecycle doesn't flow as it would otherwise:
ICT Project Development Lifecycle
First, after creating the beta/version 1.0, without having beneficiaries/clients/stakeholders ready to test the tool as it would be used in the actual project, knowing to whom, where and how to deploy is often unknown. Imagine building a piece of software that does taxes, only you're not entirely sure you'll have access to people who actually pay taxes, so you don't know whether to make the software into something else and expand the scope of people who might want to use your software.
Second, critical and relevant user feedback is therefore also often not possible. Instead of giving your software to people who pay taxes to check to see if the software calculated their tax return properly, all you can do is give the software to people who don't pay taxes and see how much they understand even though they're an irrelevant group of people. You'll get feedback on the interface, aesthetics, and functionality of the software, but you still won't know if the software actually works before you have go back and make corrections for version 2.0.
In an ideal world, the iterative process in ICT platform development would happen indefinitely as technology evolves. In reality, resources in international development are scarce given the size of a problem, and highly skilled technologists can only be secured for small periods of time.
Going back to my other post, what this means is that the international development side of ICT4D projects needs to disrupt itself. Personally, I think there are ways to use existing ICT platforms to more quickly, more efficiently and more accurately to build the international development context. I have a few ideas of how to break these context parts down, and the accompanying solutions are something I hope to explore in the future.
No comments:
Post a Comment
Thanks for your comment. Please note all comments are this blog are moderated and subject to approval.