A quick personal update before I get into the meat of this post. As you might know if you’ve been following Erin’s blog there have been some staff changes and rejigging of roles on our team this year, which has left me in charge of driving our strategy development process for the next three months. This is a great role for me – I love thinking and acting on strategy and it’s allowing me to test out a bunch of ideas on how we can incorporate elements of Customer Development and a great framework on business models called the Business Model Canvas from the fantastic book Business Model Generation. I’m really excited about pushing these ideas into our strategy process so we end up with more scalable, more exciting, and more impactful interventions.
For the next couple of posts I’ll be writing an overview of strategy development process for a few reasons. First, we’ve got five fantastic university students that will be joining us this summer for our Junior Fellowship program, and they will be integral to this process. I want to capture the process and articulate it to bring them on board, and as a resource for new folks in the future. I also want to use the series as a way to better articulate our approach so that we can get external feedback on its validity and share some of the ideas with the broader development community. Lastly, this will both make me think out the details of the process, and practice articulation of a somewhat technical topic. I originally was hoping that they would be “bite-sized” chunks, but I’ve revised that to “small meal-sized”, which I think is more appropriate – so get ready to dig in!
Before I get into details on our actual program, it helps to know a bit of the theory behind our approach. We focus on capacity building for local partners, in my case with the Ministry of Food and Agriculture (MoFA), in order to improve the operations of those partners. Part of our value-add as EWB is to take the time to search for new ideas, test their ability to achieve impact and then work out the details to actually take that idea to an appropriate scale where we get a good return on the investment in searching for new ideas. This sometimes is talked about as the [Search] -> [Prototype] -> [Pilot] -> [Scale] model. While this may seem like an obvious cycle for many of the engineers reading this blog, it often doesn’t happen that way in the aid sector. What we see more commonly is something closer to [Write Proposal in Washington/Rome/Accra] -> [Confirm Funding] -> [Execute at Scale]. The more common approach leaves little room for learning and adapting. See my previous post comparing the aid sector to high tech entrepreneurship for more on the downfalls of this approach.
While there is still some debate exactly what each element of the [Search] -> [Prototype] -> [Pilot] -> [Scale] looks like, the general principle is to end with more effective approaches by taking the time to test the potential ways the idea could fail or be improved before the full-scale execution phase where there is a lot of money flowing into activities and little room to adapt if the program’s assumptions don’t match reality. The important take-away is to know that EWB’s work focuses on capacity building by searching for great ideas and working with our partners to then take them to scale effectively, getting more bang for our buck.
For this post I just want to share some of the background thinking and reasoning behind where we’re at and what we’re doing. As you may know, my team has been largely focused on implementing and scaling the Agriculture as a Business Program (AAB) in MoFA district offices. We’ve been developing the program with MoFA over the past three years or so. We’ve seen some positive results at the farmer and district level, and one of our staff is working on a much bigger impact exploration that will be taking place over the next three months. As we’ve attempted to understand how it will scale, it is clear that it will be difficult to keep AAB on MoFA’s radar without an EWB member driving the implementation in a district. Having staff in every district from now until AAB is no longer useful to farmers is not a sustainable route. We’ve come to the realization that the program is not offering enough value to district staff (or possibly we’ve just done a bad job at marketing it) to have it prioritized over the other development partner projects that seem to be bombarding districts recently. Going forward we need to understand how to avoid this problem and improve the process by which we invest our limited resources.
Over the next few posts I want to explore how our experience with AAB, the fundamentals of the [Search] -> [Prototype] -> [Pilot] -> [Scale] model, and influences from the high-tech entrepreneurship world (namely Customer Development and the Business Model Canvas) will be driving our overall strategy development process.
You may have noticed that I’m very interested in applying concepts coming from the high-tech startup world to our team. Is this wise? Why would ideas from a completely different context work here? While I’ve blogged a bit about this before, I’ll add another piece of justification from one of Steve Blank’s blog posts called What’s a Startup? First Principles. Steve defines a startup as “an organization formed to search for a repeatable and scalable business model.” Substitute business for impact and I think this is the essence of what we’re about at EWB. At the end of the day, we don’t have the resources to hire staff to implement our projects on a long-term basis, which is why we work with partners. Our job is to search for what that repeatable scalable impact model is and pass it off to our partner. In this sense, we’re operating exactly like a startup and so I’m betting that tools that work for startups will work for us too.
So, what’s next in this series? The first piece is to get up to speed on the big picture of our strategy development before diving into the Business (Impact) Model Canvas and what we’re actually learning. Here’s my rough guess at what the next couple of posts will look like:
- Customer Development and Our Strategy
- The Impact Model Canvas – Intro and Value Propositions
- The Impact Model Canvas – The Right Side
- The Impact Model Canvas – The Left Side
- Innovations on Impact Models
- Models We are Exploring
- Getting out of the Building
Thanks for sticking it out through a pretty technical post – and hope you enjoyed it. There’s lots more to come!