Appropriating Technology via Rural Hackspaces

In his recent blog-post Emeka Okafor raised the issue of appropriate technology and illustrated the concept with case studies.

According to Rolfe Leary’s article, appropriate technology is defined as “a simple technology created for, but not by, the people“.

Compared to the practice of international technology transfer that it eclipsed, appropriate technology was a progressive form of technology for development. Rather than transferring capital-intensive technologies from industrialised countries, appropriate technology practitioners consciously set out to design technology appropriate, as they saw it, to the needs of non-industrialised countries.

Although progressive relative to technology transfer, appropriate technology remained fundamentally flawed in at least two respects. In the first place the appropriate technology movement was premised on a belief that the solution was technology and they thus operated with a ‘technological imperative’ to improve whatever already exists through the application of new technology. Secondly the technology solution was almost invariably devised, designed and delivered by foreign experts – especially in the early decades.

Today we find both failings in some ICT4D practice. Both errors – starting with technology rather than community, and locating power in the hands of foreign experts – disables local people. We need to improve our practice in both regards.

If the appropriate technology movement (or ICT4D) relies for its solutions on engineers in London or Washington who have been socialised in technocratic cultures and who live in industrialised economies, then we should not be surprised if they continue to prescribe technical fixes for development; nor should we be surprised if those solutions often misjudge local priorities, fail to reflect local custom and practices, or prove to be unaffordable or otherwise unsustainable.

In order to create truly ‘appropriate technology’ we must take an altogether different approach to ICT4D – one which from the outset is community-owned and directed, and where decision-making power, resources, and capacity are located as near as possible to intended the site of development. Rather than transferring technologies internationally ICT4D agencies might think constructively about transferring the location of their HQ, decision-making, and budget-holdings to developing countries?

A re-engineered ICT4D should aim to avoid dependency on foreign experts, donors or institutions, and instead set out to develop participatory people-processes that enable communities to define their own development objectives, priorities and activities. To reduce dependencies there is also a need to build operational capacity in the field that is able to innovate new solutions to development challenges – or appropriate and modify (hack) existing solutions according to identified needs.

One possible way to build such delivery capacity is to use the kind of hackspaces and iHubs that are gaining such popularity worldwide. Hackspaces are places equipped with engineering tools and workspaces where people can meet, share skills and work on collaborative projects. iHubs are similar except that they focus on software development projects. Hackspaces provide a vibrant community of makers, engineers and tinkers able to learn from and teach each other the practical skills of manufacture and production.

ICT4D agencies could set up rural hackspaces and iHubs and employ engineering and development graduates from African universities to hack solutions to community-defined problems. Regular opportunities to share experience and expertise with co-creators from other communities would need to be a feature to enable cross-pollination and diffusion. This could be facilitated through open-days, volunteering schemes and hacker-in-residence programs. Rural Hackspace R&D teams could work on community-identified challenges such as alternative power for rural areas, open-source adaptive technologies for the disabled, or irrigation pumps for arid areas..

Instead of running apps4dev competitions out of UN agencies with sponsorship from multi-national corporations, ICT4D agencies could run Maker Faires and Hackathons in rural Africa, catalysing creative solutions to rural problems, and building sustainable capacity to address development challenges. One example of work in this vein is the establishment of an Ubuntu Campus in rural Macha in Zambia’s Southen Province in collaboration with the University of Zambia (UNZA).

I believe that a Rural Hackspace would result in indigenous solutions that are grounded in an appreciation of the local operating environment: context, culture and markets. I think that enabling people to appropriate technology for development would be a powerful way to build self-reliance and local capabilities.

Instead of running apps competitions in New York judged by corporate CEOs let the communities around the Rural Hackspace award their own prizes to the solutions that they have most reason to value.


About Tony Roberts

Founder & ex-CEO of co-founder & ex-Executive Director of co-founding Trustee co-Founder & Director of currently PhD student of ICT4D at University of London Gooner
This entry was posted in Africa, Development, ICT4D. Bookmark the permalink.

4 Responses to Appropriating Technology via Rural Hackspaces

  1. Pingback: How Not To Do Rural Technology Development | Box Of Rats

  2. Pingback: Rural Hacker Spaces – Tony Roberts and Focus on Impact & Sustainability | Global Entrepreneurship and Maker Space Initiative

  3. Pingback: Tony Roberts and Rural Hacker Spaces « Global Entrepreneurship and Maker Space Initiative

  4. Jaume Fortuny says:


    On this post, you made a great explanation of where should be focus efforts and strategies of ICT4D, putting technology as a complementary element and not the as the main one. As ICT4D Jester says: “The real gap to be closed is a gap of human capacity and intent, and not for temporary outcomes.” 

    But, as ICT4D Jester is silent, let me be ICT4D Jester for a moment (no desire to supplant him, because ICT4D Jester in one and only). and let me ask you three questions:

    1 .- How to transfer the technology to implement the hackspaces and iHubs? With traditional practice of international technology transfer? Or through appropiate technology prescribed from London and Washington? Apparently we would be committing the same mistakes basis. Would we obtain a different result?

    2 .- These ideas are questioning the work of UN agencies and of the multinational corporations that sponsor activities. Wouldn’t be then more difficult to find funding and collaboration for setting up hackspaces or hackathons?

    3 .- Now running apps4dev competitions, and this allow that the struggle for resources and for results makes rethink and innovate in how it carries out the action. I try to imagine an unique strategic line, with all actors following this line. Wouldn’t it cause a leverage (instead of a continuous improvement) on the action of the actors? Usually the competition serves to improve the offer in favor of the plaintiff. 

    What can you say about that? 

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s