David Levine Alice Agogino UC Berkeley Designing products and services that improve poor peoples lives at scale Is it hubris to engineer development For over five centuries people from the ID: 224910
Download Presentation The PPT/PDF document "What is Development Engineering?" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
What is Development Engineering?
David LevineAlice AgoginoUC Berkeley
Designing products and services that improve poor people’s lives at scaleSlide2
Is it hubris to “engineer” development?
For over five centuries people from the Global North have “designed solutions” for those in the SouthSlide3
Profound humility
For over five centuries people from the Global North have “designed solutions” for those in the SouthOften with tragic consequencesSlide4
Profound humility
Foundation of development engineering is realizing:How little we understand needsHow bad our initial ideas and prototypes areLearn from and with local partners For scaling: Need local partners to own & scale the projectPlan for unintended consequencesSlide5
Adding Development to Design Thinking
Our complementary
additions
Design thinking
Development
Business model / scaling / system thinking
More tools: sensors, experiments, and biggish data
Needs
assessment
Qualitative toolsIdeationCreativity toolsContinuous improvementRapid prototyping
Social goals
to improve people’s lives at scale
Barriers to
design
from geographic and cultural distance
Constraints
of poverty, remoteness, liquidity constraints, gender roles,…
Opportunities
of donors, mobile phones, microfinance,…
Tools
like
impact
evaluations Slide6
Development Goals & Constraints
Framework
(Insights)
Observations
(Contexts)
Imperatives
(Concepts)
Solutions
(Prototypes)
Qualitative &
Quantitative
Data
Scaling for ImpactDesign Thinking in Development Engineering?Slide7
Example: cooking over biomass fires kills 4 million people per year
(Lim, 2014) http://blogs.civicus.org/worldassembly/2012/07/14/wood-fuel-destroying-the-environment-and-harming-the-african-woman/. Slide8
Example: Development issues & stoves
Needs assess
Creativity
Improvement
Social goals to improve people’s lives at scale
Who breathes the most smoke?
How can we reduce smoke exposure?
Are we reducing smoke exposure?
Barriers to design from geographic and cultural distance
How can we learn when far?
How learn problems with out solutions?Constraints of poverty, remoteness, liquidity constraints, gender roles,…How sell when liquidity constraints?Find 20 solutions to liquidity constraintsTest our solutionsOpportunities of donors, mobile phones, microfinance,…What role for mobile phones?How use mobile banking?How collect data via phone?Tools like impact evaluations What impacts do donors care about?How roll out our product to build in learning?Low-cost RCTSlide9
Development Engineering
Dev
Eng
complementary additions
Design thinking
Development
=> More objectives, constraints & opportunities
Business model / scaling / system thinking
More tools:Needs assessment Qualitative toolsAdd questions to inform the business modelIdeationCreativity toolsApplied to business modelsContinuous improvementRapid prototypingOf the business modelSlide10
More quantitative tools
Our complementary
additions
Design thinking
Business model / scaling / system thinking
Development=> More objectives, constraints & opportunities
More tools
Needs assessment
Qualitative tools
Creativity
Creativity toolsContinuous improvementRapid prototypingBeyond rich qualitative methods:Sensors embedded in products, smart phones,…Experiments (A/B testing, etc.)Large data from satellites, clicks, mobile phones…Slide11
Cook Stove Workshop
http://
bit.ly
/
deveng
-cookstoveSlide12
Sensor DataSlide13
UCB-SUMS Stove Use Monitoring System
Maxim
iButton
:
http
://
www.hedon.info
/BP55:Low-
costTemperatureLoggersAsStoveUseMonitorsSlide14
What is Said – What is Done
Comparison between ODK survey data and sensor data85% over-estimated cooking hours & events Users over-reported time spent cooking by 1.2 hours (almost double)Non-Users over-reported by 1.7 hours.
Users
Non-UsersSlide15
Development Engineering
Dev
Eng
complementary additions
Design thinking
Development
=> More objectives, constraints & opportunities
Business model / scaling / system thinking
More tools: sensors, experiments, and large dataNeeds assessment Qualitative toolsAdd questions & overcome barriersAdd questions to inform the business modelUsing more tools IdeationCreativity toolsUse as cues for creativity Applied to business modelsUse tools as cues for creativityContinuous improvementRapid prototypingAddress barriers & use opportunities
Of the business model
Using more tools