Exploring how innovation, design & technology can reduce poverty at the Base of the Pyramid

Friday, May 21, 2010

Where the Rubber Meets the Road (... or Where the Silicon Meets 1818 H Street)

On May 11, 12 and 13, I joined WBI’s Learning Journey team – Eric Chinje, Kirsten Spainhower, Alexis Sampson, Katherine Park, and Marilyn Markman – for visits to IDEO, Singularity University, Stanford’s D School, Berkeley’s I School, and UC Santa Clara's GSBI Program. To say that it was an edifying several days might be the understatement of the decade. Who wouldn’t want to sit around a sparsely furnished room with a cross-section of Silicon Valley elite, spitballing ideas that are … what’s the word? Cool. But this was only a small part of the experience. I, like my colleagues, participated in these meetings with several particular priorities in mind: to examine the core elements of these organizations’ product innovation culture, process and philosophy; to bring this information back to WBI; and, hopefully, to start a dialogue with colleagues on both sides about what we observed and what it might mean for WBI in a practical sense.

I should begin by mentioning that the Kool-Aid looked delicious. But I didn’t drink it. To paraphrase Samuel Butler, an open mind is important, but watch that your brain doesn’t fall out. More on that in a moment.

A key task of the trip was to observe at least a snapshot of what these organizations are doing, to enable our team to take the long view: what value do these organizations/institutions add to connect supply to demand up and down the value chain? This naturally implicates avoiding replication of effort. In that spirit, I won’t try to re-capture the information which is already excellently provided by Eric, Kirsten, Alexis, Katherine, and Marilyn – please be sure to read their contributions to this blog (either before or instead of this one). This entry instead comprises an initial, cursory attempt to connect the dots, and to segue into a dialogue about the experience through the prism of what might be learned on both sides. To that end, as each meeting at each location unfolded, certain common practices and characteristics became apparent.

Take, for example, IDEO’s fairly straightforward methodology by which it executes ‘human-centered design’:

Phase 0: Understand/Observe (understand client’s business and feasibility of product; empathize with end-user)
Phase 1: Visualize/Realize (Form three-dimensional model and manufacturing strategy in close coordination with client)
Phase 2: Evaluate/Refine (enhance design prototype through testing)
Phase 3: Implement/Detailed Engineering (design and verify product works and can be manufactured)
Phase 4: Implement/Manufacturing Liaison (product moves from shop floor to client’s manufacturing)

Each organization and institution we visited pointed to some iteration of these five steps as comprising their development framework, each of which are viewed as more of a flexible guideline than a hard and fast rule. A premium is placed on collaborative experimentation—we heard the phrases ‘collaboratory’ and ‘pfab-lab’ (as in “participatory fabrication laboratory”) – and each organization celebrates (and so has institutionalized) experimentation, which is generally termed “the room to fail.” Further pervasive practices include:

Multi-Disciplinary Teams: Teams are loosely assembled (in many cases, particular client needs are advertised throughout the organization and teams actually self-select instead of waiting to be assigned) to solve problems; teams comprise a spectrum of disciplines, and reflect a range of perspectives. Each organization emphasizes and actively searches for so-called “T-shaped” people, who possess a broad range of skill-sets, with some intersection of an impressive academic pedigree and robust operational experiences in a variety of contexts.

Focus on the End-User and Leveraging Existing Momentum: Each organization/institution is completely focused on the needs of the end-user, to the point of collaborating with clients from project inception to completion. To this end, client strengths are carefully identified, and not only inform the project team’s priorities, but are actually assimilated into its project development methodology. This enables the teams to build onto existing momentum on the ground, and so most projects achieve traction before operational work begins.

Room to Experiment: All team members (from junior staff to senior management) are encouraged to “fail often to succeed sooner.” Prototyping is likewise important; we heard a team leader say, “If a picture is worth a thousand words, a prototype is worth ten thousand.” We likewise heard the phrases “the 3 R’s: Rough, Rapid and Right” and “the Deep Dive approach,” which both describe prototyping as an iterative and potentially time consuming process. Efforts to perfect a model prior to deployment are thought to be a waste of time. Brainstorming sessions are convened around ideas, with teams (no more than 8 people in a session) encouraged to express wild ideas, to build on ideas of others, and to hold only one conversation at a time. Some discarded ideas are archived for potential future use.

These ideas are interesting; members of our Learning Journey team reacted to them in different ways. They might have sounded great because we were dazzled by the inviting spaces, with candy and toys, funky seating, and demos of projects everywhere (most of the organizations we visited seemed to have the psychology of the first impression fairly well figured out). But are these ideas really that mind-blowing? Or even valuable? Could we learn from them? Or could they learn from us? Perhaps both? The team is anxious to discuss these questions with colleagues from throughout WBI.

Before we launch an in-person discussion, I’m interested in assaying a handful of (what will likely be horribly overgeneralized) differences between WBI and Silicon Valley. Here’s a quick example:

WBI. At the risk of painting with a broad brush, an important dimension of WBI’s (as well as other parts of the Bank’s) value added is that it generally develops and executes technical assistance and training activities using the same rigorous analytical approaches used to make traditional economic and financial decisions. This includes the use of measurable, evidence-based indicators of improvement (the conventional wisdom is that without pointing to evidence, it is difficult to authoritatively demonstrate improvement).

Silicon Valley. Project heads emphasized the need to stay ahead of the curve, to keep innovating, and to stay hungry. I asked about the kind of quantitative analysis undertaken to identify certain clients’ needs and general trends, and how these might inform the organizations’ approaches. The short answer from each – and this includes IDEO, Singularity University, Stanford’s D School, Berkeley’s I School, and GSBI at UC Santa Clara – is that they generally do not undertake such analysis. Interestingly, each organization/institution we visited recognized both the analytical gap in their practices and the value of WBI’s and the Bank’s broader analytical approaches, and each indicated an interest in exploring opportunities to partner or to otherwise inculcate similar practices in their own product/service development methodologies. These organizations/institutions also generally point to the accelerating obsolescence of technology as a key challenge, which is why they typically start from scratch after each project or semester. When I asked how one project or semester informs subsequent ones, it became clear that this was likewise not a normative practice. Most acknowledged that the knowledge and practices of each organization/institution are not systematically captured, and much rests with the institutional memory of the people working for them. Each recognized that sustainability might be problematic as a result.

So what, if anything, does this mean for us? And are these gaps deal-breakers? Or perhaps I’m over-emphasizing quantitative indicators of progress? What do YOU think?

These and other questions will be taken up at a BBL focused on this Learning Journey in the coming several weeks, and we encourage you to participate, and to otherwise contact us to discuss the details of the Learning Journey. We hope to hear more from you, and to see you at the BBL. The details will be posted on this blog in the coming few days.

Monday, May 17, 2010

What is on your walls?



When talking about how we innovate and the setting in which we worked, a professor from Berekely asked, "tell me, what is on your walls at the World Bank." On our walls are beautiful photos of diversity represented by numerous cultures that could be featured in National Geographic. In a sense, the people in these photographs are an abstraction - degrees of separation from government officials that serve as our primary clients - and are hardly factored into the work we really do.

Aside from photos there a lot of walls, a huge departure from all of the open spaces and white boards that were present in almost every organization we visited. At both IDEO and Stanford's Design School (both bore the mark of David Kelley's design ethos) we saw temporary team place that served as mini-workshops or "collaboratories" for collaborative work. Workers were mobile and only use their more individual work stations on an as needed basis rather than as a tethered location.

We all remarked on the freedom this offered, but also the energy that sprung from these spaces. We at the Innovation Practice are trying to influence the way our workspace is designed and visiting other organizations gave me a lot of ideas to bring back.

A Case for an Innovation Facility: Creating Opportunity on the Fringes:


Launching grenades in an institution to bring about change was advice we got from Berkeley Professor John Danner, Senior Lecturer at Hass School of Business. Even today a revolutionary spirit exists at Berkeley. When discussing our agenda of change management here at WBI, Professor Danner asserted that to catalyze change, one must inject a sense of urgency by launching mini-grenades to force an institution to grapple with what it means NOT to act. Institutional change must be presented in ways that are urgent yet intuitive, logical and emotional. Looking back to the rich history of change in the Bay Area, we know that change was built by those active on the fringes.

The Development Marketplace began on the fringes and has been used to scan pilot and test innovation from the external world and inform its operations. After 10 years of implementation, the Development Marketplace has gained a certain amount of traction and is poised to make an even larger impact if it can effectively leverage what it has learned over the last decade and press forward using the strength of its partners and operate from a design that addresses gaps, while being nimble, flexible and iterative.

Here within the Innovation Practice, we have a real opportunity to act with urgency but also to learn from one of our longest standing partners the Global Environment Facilty. This was also a program that started on the fringe when the environment agenda was seen as tertiary. But with GEF funded project funding linked to Bank loans in projects such as infrastructure, the environmental agenda has been mainstreamed and is no longer considered an innovative add-on but a necessary component.

I am advocating for the creation of an Innovation Facility designed to deploy a variety of funding modalities: stand-alone preparation grants along with small and medium sized projects, and full sized project grants blended with Bank operations. With a suite of funding windows, innovative approaches can be conceptualized from the beginning to affect larger Bank investements if successful.

The GEF began in the Bank in 1991 as a pilot and was formalized in 1994, at the Rio Earth Summit, when the GEF was restructured and moved out of the World Bank system to become a permanent, separate institution. At the Earth Summit the world began envisioning a what would happen to the world if we did NOT act - and that future looked grim.

It is now time to ask the same question when considering the possiblity of an Innovation Facility. What would happen if we did nothing to support the burgeoning class of social entrepreneurs? I think it would be a bit like keeping our heads in the sand. Continuing to rely on service delivery supported by government and civil society lacks out-of-the-box thinking and sustainable funding models that social entrepreneurs are looking to test.

Saturday, May 15, 2010

A Culture of Failure

Some places simply hum with the energy of creation. San Francisco is one of those places where the vibrancy of the creative class of social entrepreneurs is palpable and one can sense in the population the urgency to do something that makes a difference and contribute to developing solutions to the world's most pressing problems.



We were told yesterday when we visited the Bay Area Hub that 1 in 5 ventures in the Bay Area and Silicon Valley succeed. One entrepreneur confessed, "we fail more quickly and start again more quickly." In this environment that gave birth to the Dot.com era, people have made a lot of money on their success only to fail the next day. Simply put, inherent in the tech and dot.com culture is an internalization of risk and a lack of fear to fail. This essentially means that these folks are not afraid to try, and that is admirable.

Here social entrepreneurs understand that to affect change, you have to remain lean and mean, keep overhead costs low, and stand on the shoulders of your colleagues who can shore up gaps in skills required to test innovative approaches.

But what is the relationship of social entrepreneurs in the creative class to those in more established institutions? My immediate response is that the establishment must strategically tap into the pipeline of creative enterprises that pass through the proof of concept threshold and are ready to replicate or scale up. This is the critical point where we must help them source seed capital to grow and thrive. But even though one must factor in failure, it is important to capture a body of knowledge to help inform, screen, and identify key aspects of those likely to rise to the top of the heap most successfully. As I bring back some new knowledge I gained here I will be applying some of these lessons to my work at the Development Marketplace to create linkages between successful ventures and the abundant capital to tap into to support such risk and innovation.

What does Innovation Look Like?



What do you think of when you hear the word "cupcake"? Perhaps a sugary snack with heaps of whipped frosting and sprinkles? Well, to the students of Richmond High School "cupcake" is an activity where kids embrace their blossoming needs as young adults. Whether you are a teacher, parent, or student, the map above can help you locate specific areas where you can either participate or regulate hot cupcake behavior.

Meet Local Ground (soon to be localground.org), an online tool that adds local perceptions to geospatial maps. By superimposing hand-drawn images from paper maps onto digital images Joyce Tsai and Sarah van Wart, students of Berkeley's School of Information (ischool), have created a new tool that allows the end-user to understand local behaviors within a physical space. The power of this tool is that it not only redefines our normative perceptions and purpose for traditional maps but it increases the number of stakeholders that can speak to a common issue, enhancing the change process so that the end result may better reflect initial demands.


To assist in the redesign of Nystrom neighborhood in Richmond, CA, students of various schools and organizations were given maps and cameras to capture their understandings of the community and were also asked to draw their vision for the space in the next 10-15 years. All maps - geospatial, current, and future perspectives - were synthesized together so that current problems and future solutions were integrated into a common interface. Policy makers, city planners, students gathered around computer screens to discuss the various options for Nystrom and begin the political process for change.

Friday, May 14, 2010

Wrapping Up


My tweet this morning: "Last day of Learning Journey to Silicon Valley. Debunking a lot of preconceptions. The folks here are not all dollar-chasing nerds."

A few things surprised me on this trip: the human-centered focus of all project designs in Silicon Valley and the implications for project outcomes; the notion of "empathy" as a design concept; the singular focus on the Micro; the emphasis on value propositions, and this statement by Jim Koch: "there are grand challenges...but no grand models". Everything seemed to emphasize the base unit in all development paradigms: the individual.

We spent Thursday morning with Jim and his colleagues, Sherrill Dale and Vicky Mattson of the Global Social Benefit Incubator (GSBI) program at UC Santa Clara. The GBSI team has had the most contact with the Bank of all the groups we met in the Bay Area. It was easier here to see that points of convergence between the Bank's approach to development and how Silicon Valley is seeking to change the world, one client at a time!


This region has its share of entrepreneurs - some of the most successful in the world - but I was surprised by the number that see themselves as social entrepreneurs. We discussed the important difference in focus between "entrepreneurship" and "social entrepreneurship"; the latter specifically targets the base of the pyramid - the same population segment that all development agencies seek to attain.

Of the many ideas we are throwing around in our LJ group, two seem to be generating the most interest: instituting a system for regular, if not permanent, World Bank presence in Silicon Valley (and other global centers of innovation) and the establishment at headquarters (with mini versions in country offices) of a summer "university" program - an open source multidisciplinary collaborative that runs for 4 - 6 weeks a year. The group will be debating these and other ideas that have emerged from this amazing journey to the heart of technological innovation and discovery.

Thursday, May 13, 2010

D.School - What do you think?


Day Three of our Learning Journey to Silicon Valley and Bay Area institutions took us to Stanford University's Design School and into conversations that left me with a whole range of questions on our development work.


We audited a session on entrepreneurial design for extreme affordability with Krista Donaldson, a leader in design thinking. With the assertion that "without manufacturing there is no (development) sustainability" her lecture examined what makes manufacturing different in developing societies: the characteristics of product design; the notion of recycling and reuse; the difficulty of maintaining quality and safeguard standards, etc. She made some conclusions: poor infrastructure hinders efficiency; socio-economic/cultural/political factors impact everything. And the ultimate questions: who are the end-users? what are their needs?


Entrepreneurial design for extreme affordability is for the base of the pyramid - the same category of citizens who constitute the primary target in the Bank's development endeavors. After extensive work in some of the world's poorest countries, the D-School team came to identify a process that goes from "deep empathy" to prototyping to testing. Professor James Patell: "We do not start from the technology; we start with the consumer..... It would be crazy for us to go into a country and say 'we are from Stanford and we are here to help you'!" Hmmmm!

My first set of questions: Are there any lessons for us here? How client-centric is the Bank in its project design? Will understanding the needs and circumstances of the client significantly disrupt time-tested processes and raise project preparation costs beyond acceptable limits? Does empathy - the preliminary needs assessments and ethnographic work in d-school thinking - have a place in the conceptualization of our development programs?



We participated in Heather Fleming's course on Design for Sustainability on projects in health, education and small-scale manufacturing in Kenya, Rwanda and a US Indian reservation. I retained a suggestion from David Lehr of Mercy Corps, one of the speakers, to "blend methods and ideas from the worlds of business, government and civil society to create social value that is sustainable." [LJ team member Craig Hammer was our designated lead and made a great presentation about the Bank and its approach to development.] I pursued a discussion with Lucky, another speaker, who felt that development could be a more rational science and the Bank could contribute significantly to this by producing micro-data on issues such as population growth.

My second set of questions: have we been focusing too much on the macro environment and not enough on the micro? How would a focus on outcomes data at the sub-national level impact trends in development practice? With scientific evolution advancing in the direction of micro and nanotechnologies, is it inappropriate (too expensive) for development work to evolve toward micro solutions? Should the Bank not have a permanent presence and participate fully in the ongoing conversations in Silicon Valley on how and which technologies are changing the lives of many in the bottom billion?