• SUBSCRIBE

    Sign-up for our e-newsletter to keep current on project opportunities, news, and events.

  • CONTACT

    info [at] catapultdesign [dot] org
    972 Mission Street Suite 500
    San Francisco, CA 94103

5 lies we tell ourselves (and funders) when developing new tech for people in need

Like any service-based organization, Catapult Bikesreceives requests from a variety of organizations and individuals.  Some come to us with little more than an idea, others have had their idea in the market for over a decade.  Some are based within the small community they’re trying to affect and others have never traveled to a developing country.  Regardless of the above, many organizations make similar statements regarding their idea. Over the years we’ve developed a healthy amount of skepticism for some of these statements.  In particular, we are always a bit wary when we hear these five most common claims:

Statement 1:  People in the developing world need more “time”

When people say their technology enables more “time” for income generating activity, social needs, education, etc. it’s okay to question that need.  Time is a very Western value not shared with many parts of the world.  When it comes to selling your technology in-country, keep in mind that there are other values your technology could provide that may be more provocative than “time savings.”

Statement 2:  The technology must scale in order to be effective or worthy of investment

There are many technologies designed to meet the needs of a specific population that have value, but will never reach production volumes in the millions. Our world is not homogenized; one size doesn’t necessarily fit all.  While it’s great if your idea translates globally, realize that many do not.

JikoOn a related note, a business plan that outlines first year sales greater than 250k I put in the naïve category.  While the number of people in our world who lack basic needs is on the order of 2 billion, the lack of effective marketing and distribution infrastructure in many countries is a roadblock for promising technologies. Establishing and implementing a marketing and distribution plan is achievable, but is often a task more complex and time-intensive than the design development.

Statement 3:  This technology is so clever; everyone will want one!

Beware the solution in search of problem!  Is the technology addressing a real need?  And can you articulate it through a business plan – a business plan that includes research of prior art, your market size, impact number, and implementation strategy? It may sound kinda mean, but it’s common for smart, well-meaning folks to be motivated by a problem highlighted in an article, a documentary, a trip, and to act on it without considering the challenges surrounding new technology development.  “Business” and “humanitarianism” are not contradictory terms.

Statement 4:  I designed a brand new solar cooker

No you didn’t. I don’t deny that there’s a small possibility you did, but it’s highly likely you did not. Hate to break it to you.  Reinvention of the wheel is one of the plagues of the development world. New websites intended to promote collaboration and shared knowledge are attempting to alleviate that problem. Please, please, please do a google search of your idea. Check Engineering for Change, Appropedia, Kopernik, the proceedings of ETHOS, etc. And everyone developing technologies, please document and publish your learnings on one of these sites.

Statement 5:  The development work will be done for free by volunteers

Take it from a crew of folks who spent three years volunteering their professional services – volunteerism is great for the volunteer, but often proves little benefit for the end-user of your technology.  As the saying goes, you get what you pay for.  The many drawbacks of a volunteer workforce is what drove us to start an organization to cater to the needs of promising organizations and ideas with tight financial capacity.  Check out D-Rev, Catapult, Design that Matters, etc.  All are specialized resources for developing humanitarian technology that employ staff with international development experience, design experience, field experience, and connections on the ground to get your project up and running.  When billions of people lives are at stake, it’s worth the investment to work with professionals.

COMMENTS

  1. Brendan. January 27, 2010 at 2:17 pm

    I love it. Spot on, and can completely relate. I’d add one: people won’t way for it: http://www.cashewman.com/2009/08/8-reasons-to-charge-people-for-your-development-solution/

    Cheers,
    B

  2. Lonny Grafman. January 27, 2010 at 7:50 pm

    Awesome work! You just saved me an entire day of class. This is going to be a required reading in Engineering 305, Appropriate Technology, at Humboldt State University!

    I really like Statement 2, especially since I work on a lot of service learning projects where the solution, as it is made, might only serve one client. Some of those solutions might only need slight adaption for other environments yet still not come close to that 1 million customers number suggested by the brilliant and kind Paul Polak.

    Statement 4 is cracking me up!

    Thanks to Paul Hudnut for pointing out the article.

  3. Chris Watkins. January 27, 2010 at 8:51 pm

    I think Paul Polak of D-Rev might partly disagree with point 2. To have a big impact, you need to scale. That’s not to say that it’s not worthwhile to build something that only 5000 people will use… but if we want to change the world, don’t we need to be looking for solutions that are as popular as mobile phones (or on the same order of magnitude).

  4. Anna. January 28, 2010 at 1:35 am

    Thanks for this great article! I’m a business student with a passion for product development (especially for the developing markets). Doesn’t this article highlight the importance of bringing in marketing/business knowledge early on in the product development process? Developing new technologies and developing end products that utilize some of those technologies and actually have benefits for the target buyer/user are two so different things…
    Also, if the product never becomes available for purchase, it doesn’t matter how great the product is. That’s why I especially love the statements “Establishing and implementing a marketing and distribution plan is achievable, but is often a task more complex and time-intensive than the design development” and ““Business” and “humanitarianism” are not contradictory terms”. :)

  5. paul polak. January 28, 2010 at 10:28 am

    I loved “5 lies” but I think the single biggest challenge in development is achieving scale for transformative tools and strategies.

    Fixing a water system that reaches a hundred people in one village may be just as important to each of them as a treadle pump is to each of the 2 million or more people who bought them.

    But only millions of radically affordable tools distributed through radically decentralized supply chains have the potential of transforming the lives 500 million poor people. Without this, I believe we have no hope of restoring the envirnmental balance of the planet.

    paul polak

  6. Heather. January 28, 2010 at 3:18 pm

    Chris, Paul,

    Great comments! I agree with you both that scale is challenging and important. From a design perspective, the power of consumer products (LED lights, cooking stoves, treadle pumps, etc) lies in the mass production of a single design capable of mass appeal.

    However, the over-emphasis on scale often translates to the design-for-all mentality that derails the development of promising technologies. Past clients with products developed with the intention of selling to “the world” are the ones that most frequently run into issues with adoption, long-term efficacy, etc. Whereas the org that starts with a well-defined user group, with applied constraints, that addresses a specific need, is the generator of innovation. These considerate designs have greater potential for global translation when combined with a thoughtful distribution strategy.

    Scale too easily translates to “design for all end-users”; but by doing so, we end up with a design that ignores all end-users.

  7. Rob. January 29, 2010 at 11:59 am

    Heather, I am going to share this post with my colleagues at Acumen Fund, where we evaluate lots of business plans for potential investments and see these sorts of landmines all over the place. It is good to have codified it. Thank you for writing it down. Keep up the good work!

  8. Heather. January 29, 2010 at 12:07 pm

    Rob,
    That’s awesome! Hope you are well and thanks for sharing the post! Would love to see Acumen’s list someday.

  9. Frank. January 29, 2010 at 12:29 pm

    I agree completely with the above lies… A lot of people and organizations try and boil the ocean to produce a cup of water… Relevance is the most important factor in determining product design. Stay focused on the solving a specific problem for a targeted group of people. THINK about how others can use and expand your market after you solve the specific issues facing your target user. The world is a very diverse place with many diverse cultures and there are very few products that can be universally marketed across many cultures without changes to the design.

  10. nicholas evans. February 24, 2010 at 8:55 pm

    Great thoughts Heather!

    I think scale is dependent on the end goals of the designer. If the goal is to fill a specific need for a niche market, then the scale of the solution, appropriately, may not touch millions of people. If the goal of the designer is to affect millions of people, then that should determine the types of problems being tackled; specifically, only problems that affect millions of people can have solutions that reach millions of people.

    So I think scale targets should be determined by the goals of the organization and designer and the scope of the problem.

    nicholas evans

2 Trackbacks

  1. [...] Fleming from Catapult Design has put together a list of 5 justifications people tell themselves when developing technology and products for people in need. Many apply to product development in [...]

  2. [...] 5 lies we tell ourselves (and funders) when developing new tech for people in need – Catapult Design Blog – very practical look at the truth behind common assumptions [...]

Post a comment

Your email is never shared. Required fields are marked *

*
*