What foundational parts of the technology ecosystem do we own, and what are we reliant on others for?

What I’m talking about here are the items deeper down the stack, the core components that allow a country to own its own technological future. Here are some examples:

• Do we build our own software, or are we importing it?
• Can we prototype and build our own hardware, even if not at the scale of China?
• Are we investing in our own startups, or is that being done by foreigners?
• Do we have our own researchers, or are we okay with people parachuting in from abroad to do that for us?

It’s quite difficult for me to do much about any of this beyond Kenya, so I focus on what I can do here and hope that it works and the model can transfer elsewhere. The iHub, m:lab, iHub Research and Savannah Fund are examples of this, where our efforts are focused on local software, startups and funding.

The newest additions are the iHub’s UX Lab and a new high performance computer cluster, both filling a void not just in Kenya but in the continent as a whole. Both of which will come online this Summer. Beyond that, we’re looking at hardware, thinking about what it would look like to have our own hackerspace and TechShop, in a model suited for Kenya.

The iHub UX Lab and Supercomputer Cluster

We are fortunate to have excellent corporate partners at the iHub, one of which is Google, who provided some funding to get two initiatives off the ground.

Creating a UX Culture in Kenya
In the software space design is one of our weakest points. This isn’t just web or mobile design, this is product design and it’s rooted in a lack of understanding or desire to provide a better user experience. Core to providing better products is doing research on what users are looking for and how they are using technology in the first place.

Shikoh Gitau has worked closely with the iHub Research team for the past year, in fact the core ideas that presented the challenge for that space to come into existence was from a paper she wrote, where she showed how little of the technology research done in Africa was by African researchers. Shikoh works with the user experience teams at Google, and started talking to us about the UX Labs that they run around the world.

I had also had the chance to do a workshop with Andy Budd at Tech4Africa, and then chat again in the UK later on. First hand, I got to know Gabriel White through some work he did for Ushahidi. Both of them helped me get to a better understanding of the value of UX research in the product design process.

All of this led to us deciding that the iHub should create a UX Lab, a resource that would serve the region. A place where companies and startups learn about and begin thinking about user experience as they develop new products. We’ll do this through masterclass training on skills, partnering with the top UX experts in the world, and by providing the resources for this to happen.

Mark Kamau has joined the team to lead this initiative.

The iHub Cluster

At the end of 2011 I was approached by one of the iHub Green Members, Idd Salim, about an idea of building our own supercomputer. Why?

Outside of South Africa, there is little to no capacity for cloud computing on the continent. This means that few of the programmers in this region have the skill sets necessary to work and build out this infrastructure. We have a severely limited foundation on which to build future services in an increasingly cloud-based computing world.

Some of the use cases where we see the need for this:

• Research and training opportunities for super computer enthusiasts and university students
• Training people capable of being SREs (Service Reliability Engineers)
• Power-Computing service for local content [video editing and production]
• A host for parallel and resource-hungry applications such as weather prediction, draught prediction and real-time information dispatch.

The initial funding for a small HPC deployment has been funded by Google Africa Inc. Intel have further added to the project a Intel MultiFlex® Server for use as the “master” component of the HPC cluster.

Bob Aman works at Google here in Kenya, and has become a staple at the iHub where he runs his office hours twice per week. He, along with Idd Salim and Jimmy Gitonga are building the first 4 nodes of what we hope to be a 24 node cluster. The most I had done before this was build my own gaming rig, so I’ll be honest in saying that I’m the noob in this group, where most of the conversations are beyond me.

As with the UX Lab, the iHub Cluster will be for people to learn what goes on under the hood of HPC’s by building it, and to learn how to use the power in it to solve big data problems. It will also be made available to the animation and ad agencies in town for rendering services.

In Summary

The UX Lab and iHub Cluster will come online this summer. Both projects have the leadership in place to run them and the resources to build them out. They’ll both be located in the same building with the iHub, and both are being built with the greater Kenyan tech community in mind. Like all of the iHub initiatives, they only work when people from the community are a part of them.

If you would like to get involved in either, reach out to the respective leads: Mark Kamau for the UX Lab, and Jimmy Gitonga or Idd Salim for the Cluster.

“Nearly every start-up working in payments is simply creating a new front end for your credit card. That’s not a small thing; we need new ways to use our credit cards. But we shouldn’t forget the true winners in this new marketplace—whatever innovations we see in payments over the next few years, there’s a very good chance that most of the rewards will flow to Visa and MasterCard.”

This is true… if you live in the US or Europe.

It’s also why Mpesa is so important, as it represents a new form as well as a new source.

Mpesa destroys the paradigm of payments as we knew it

It’s a good thing that Mpesa happened in Africa. It offered a new way of thinking about money and payments, without the legacy baggage of banks and regulations meant for another century. The powerful banking interest were held at bay, not by great power, but by indifference – this is Africa afterall, who cares about this market?

With Mpesa, and without a bank account:

• People can send and receive money.
• People can store up to $1000 in the system, creating a pseudo-savings account.
• There are no credit card companies involved.
• There are no banks involved.

Mpesa is big now too, big enough to garner a lot of attention from the the credit card companies and banks. M-PESA has over 14 million users in Kenya, 9 million in Tanzania, and hundreds of thousands in Afghanistan and South Africa now too. It now processes more transactions domestically in Kenya than Western Union does globally, somewhere in the range of 25% of Kenya’s GDP is transacted on it.

The banks actively lobby against mobile-based payment and money systems now, globally, as it constitutes a massive competitive threat that they are unable to compete with due to a multitude of reasons, one of which is simple transaction costs. The credit card companies are watching closely too, and moving. Mastercard and Visa both are working on mobile offerings, seeking to link with mobile operators in order to bypass a would be competitor.

Mpesa isn’t perfect – we need a payment system that works across mobile operators and can be synced (easily) with any bank, if needed. While it could improve, it’s still worth pointing out the really big missed opportunity here is by Vodafone. Like I’ve said before, if Mpesa was rolled out at as an independent company led by Michael Joseph, it could battle the credit card companies of the world and unseat them in many markets.

What’s interesting to me is that in the arguments in the US and Europe on “the future of payments” the real innovation, with real numbers, isn’t being mentioned.

Update. some new blog posts on this topic:
Could we live without cash?
Payments, the more things change…

This weekend the iHub Advisory Board met with the managers (Tosh and Jessica) to discuss the future direction of the space and what our focus should be for the coming year. The meeting was facilitated by my friend Peter Durand of Alphachimp Studios, who is in town as a part of the PopTech Lab.

The iHub Advisory Boards is made up of 5 people who come from the Nairobi tech community, and represent the community when important, or difficult, decisions have to be made. They are:

• Riyaz Bachani, Wananchi executive, now in charge of Wazi WiFi
• Josiah Mugambi, Co-Founder of Skunkworks, works at Nokia Siemens
• Rebeccah Wanjiku, Tech reporter and founder of Fireside Communications
• Conrad Akunga, Blogger, co-founder of Mzalendo and highly respected software architect
• Erik Hersman, Tech blogger and co-Founder of Ushahidi

Looking at 2012

Our overall focus has always been that we should look to serve the tech community first, and that everything else would come from that foundation. As we stepped back to look at what’s happened in the last (almost) 2 years, we tried to identify what worked and where there gaps were.

We first worked through the a “business model canvas”, putting our minds together to find out if we all saw the iHub in the same way, and if what we were doing was what we should be doing. As you can see in the diagram above, we tried to list out all of our partners and community members, then map how we add and receive value from each of them.

A key point of discussion was how do we add value to not just the 250 green members who can come in and use the space, but also the serve the needs of the other 6,000 white members in the “virtual” community. We’ll have more thoughts and announcements on this over weeks and months ahead.

Going Deeper by Improving Freelancer Skills

We delved deeper into this, separating the types of individuals between the startup types vs the freelance types. One of the biggest gaps we’ve found is that there are many freelancers, some of whom are working on a startup on the side, but need the funds from their freelance activities to pay the rent.

Our questions became:

• How does the makeup of the iHub green membership reflect different levels of what’s needed for projects to be done? In other words, are we diverse enough?
• How can we help get freelancers more projects?
• How can we help them become better at delivering on their projects?

In order to do freelance work, you often times have to team up with others who offer the skills that you lack. We’ve noticed that we’re primarily developers at the iHub, with some designers sprinkled in, but don’t have enough project managers or quality assurance types. So, our first order of business is to make sure we’re letting the people with these other skill sets know that they’re welcome to be a part of the iHub community too.

A gap that our sector has in Kenya is that companies who want to get a software project done don’t necessarily want to go with just any freelancer. We’ve discussed for some time the way the iHub brand can be used as a vector to find freelancers, but we’ve shied away from doing anything more than connecting people through the job board or through referrals.

The iHub is now looking into doing the following (and for this, we need some community feedback and help).

• Standardize a process for clients to interact with iHub freelancers, using the iHub brand as a vector for business needs to be solved by the technology community.
• Creating a way for developers, designers, project managers and QA people to collaborate and form teams to work on client projects. To be on the “shortlist” of freelancers, each would have to pass a test to make sure they are at the appropriate level.
• Bring in a very specific and targeted type of mentoring and business skill training to focus on the individuals in this program, so that we can get a better culture of on-time delivery, communications and quality of work.
• Put in place a system, upon project completion, for clients to rate the team, or individuals, who do the work. This would be tied to iHub member’s profiles, and anyone who under-delivers would be dropped from the pool of freelancers.

If you think you have the skills necessary to be on the initial shortlist for paid project work, and are a member of the iHub, let me or Tosh know as we think through this process. We’re looking for 5-10 people to explore this new area with us. Specifically, we’re also looking for a leader with great project management experience.

What YOU Do

As we stated at the beginning, the iHub is about doers not talkers.

Our final takeaway was on communication by the green members on what they’re doing. To this end, we’ll be putting together a schedule for each of the 250 green members to do a 5-minute presentation, followed by a 5-min Q&A. There will always be a quorum of the iHub Advisory Board present, as they’re the ones who make the final decision on who gets and retains membership. It will also be in front of the other community members who would like to attend so that there is a better understanding in the community of what each of us do.

We’ll subscribe a very tight template, likely 15 slides that automatically progress, much like Pecha Kucha (or Ignite talks). You won’t be required to give up competitive details, this is more for you to give us an overview of what you’re working on, how the iHub is helping with that, and where the gaps are that you need assistance.

Look for more details on this in the near future, and be ready to sign-up for one of the slots. If you don’t do a presentation, you will lose your green membership.

Final Thoughts

The iHub has been operational for 1.5 years and we’re about to celebrate our 2 year anniversary in March. This cushion of almost 2 years has allowed us to do a lot of experimentation, and we’re still in the process of gathering feedback from the community to get a better understanding of how the iHub is doing and what we can do better.

As that information comes in, we’ll do what we always do, and that is double down on what works and throw out what doesn’t. It would help us greatly if you take part in this feedback process, run by Hilda Moraa out of the iHub Research arm.

Finally, a HUGE thank you to everyone who makes the iHub possible!

I like the analogy of Kikuyu Grass to discuss an issue that I see as a major issue in certain industries in regards to how technology solutions get critical mass and go mainstream, or don’t.

The Macro and Micro Problem

I call this a “macro and micro problem”, where you have to solve a big overarching issue of scale at the same time as solving needs for individuals at a very hyper-local level. This is a particularly difficult problem for bootstrapped startups to manage, because they don’t have the money or access to infrastructure to scale wide, even though they might have an excellent micro-level solution that individuals want to use.

There are two industries in Africa that I see this problem at it’s greatest, though I’m sure there are more; agriculture and healthcare. In both agriculture and healthcare you need to serve the finite needs of a farmer or someone who is sick or injured, yet it’s difficult to provide that any one solution to millions of people. Academically, you can do it, it’s easy to come up with a solution sitting in a room somewhere with a whiteboard. It’s also feasible to roll out a pilot project and make it work well in one area.

What’s difficult is replicating that same working idea at scale. This only gets more difficult as you take in the hyper-local technology demands and cultural context across a country. In fact, there are few organizations who have figured out how to roll out new technology at a national level, the best being large corporations such as bottling and soap companies, and of course the mobile network operators.

Let’s look again at healthcare. There are some great solutions coming out of the tech community for problems surrounding patient information, clinic and doctor information, medicine supply chain management, drug reminders and more. Some are at pilot stages, but none have critical mass at a national level. They simply can’t build the infrastructure fast enough, can’t market widely enough and aren’t trusted by everyone, everywhere yet. Can they do any of these? Yes, but it takes funding and great execution.

Examples from the payments space

The payments industry is on that has been able to solve this from both a macro-to-micro level, and also from the micro-to-macro level.

Macro-to-micro
The too often talked about mobile money solution in Kenya, Mpesa, is actually a really good example here. The product innovation came from outside the company, but the execution on it came from inside, as did the strategy to focus on getting thousands of Mpesa agents going all over the country. This focus on hyper-local agents solved the micro problem, and the national infrastructure and brand of Safaricom allowed it to proliferate and gain trust.

Micro-to-macro
PayPal began as a solution for small businesses or individuals (and grew largely through use on eBay) to accept payment via credit card, which was expensive or hard to do back in the early 2000′s. They were small, serving individual needs, but were able to grow their brand and scale their infrastructure to what they are today due to large VC investments.

Outstanding Questions

The question is, are there ways to solve this problem in healthcare and agriculture?

In agriculture, how will the Esoko‘s and M-farms of the world do it? Can they do this on their own, will it have to be take in by a larger company to hit critical mass?

In healthcare, will MedAfrica be able to get enough data and downloads for mainstream use? Will mPedigree and Sproxil be able to scale their counterfeit drug solutions?

I think these types of startups can, though some will have to broker partnerships with larger organizations, like the government or the mobile operators to do so. Each of them will also have to work very hard in order to meet the demands of putting a new technology solution in play at a large scale.

Like Kikuyu Grass, which has many touch points to the ground as it’s runners spread across and takeover a whole field, startups trying to solve problems in a big industry vertical need to have many local touch points as well.

• iHub reaches one year, clocks over 6,000 members and more than 100 events. Companies were founded, business got funded and many companies found CTOs and employees through the network. (What makes the iHub work?)
• The m:lab (East Africa’s mobile lab) was founded, with a testing center, 7 companies incubating and 2 classes of mobile app development trained.
• AfriLabs was founded and now has grown to see over 15 labs in Senegal, Uganda, Kenya, Nigeria, Ethiopia, Zambia, Cameroon, Ghana and South Africa.
• The first Pivot pitching competition and conference was a massive hit. Look for regional versions in South and West Africa in the coming years.
• Ushahidi has over 20,000 deployments in 132 countries, the community grows.
• Kenya leads an open data revolution in Africa, and we also held the IGF which brought many big names into town.
• African tech startups start to get some real attention globally.
• Massive growth in bandwidth mixed with lower costs on smartphones, internet itself and mobile services as well as increases in internet and mobile users across the continent.

2012 looks to be even better

The past few years have been about building an infrastructure that improves the chances of the technology startups in Africa to succeed. Seeing this buildout in action in 2011 was exciting, but it should be recognized for what it really was: a setup for 2012 and beyond.

You see, all those labs and hubs around the continent, the startups and the media coverage? They’re all about getting attention and increasing the awareness of the pent up startup potential in Africa’s technology space. Media and funders both have a bigger target to hit when looking for entrepreneurs. We were setting the stage to broaden the base of our startup pyramid: finding the local innovators and entrepreneurs and getting more of them funded.

Where we stand now is an order of magnitude beyond what we had just a few short years ago. In 2006 if you stated that you want to be a web or mobile entrepreneur you weren’t taken seriously. Five years later and it’s a legitimate position to take. We now have some successes to point out (think mPedigree, Mxit, PesaPal, Sproxil and Ushahidi etc), which make it a lot easier for the new breed of startups to get started.

This is what we’re aiming for: a playing field that allows more entrepreneurs to startup, get some seed funding and fail fast if necessary. The ones who make it, the ones who get beyond the startup phase and become real companies with cashflow and employees, are why this is being done. This will make some people a lot of money, and it will make millions of others lives a lot better because they have better and more relevant products locally.

2012 is set. It’s the year where we grow the seed funding and early stage venture capital investments so that five years from now we have the ecosystem needed to support a much larger investment and startup community.

My prediction is this: In 2012, if you have a startup in one of the main tech cities in Africa and are unable to get funding, it is due to one of two things: Your idea isn’t viable or you don’t know how to pitch.

The funding is coming, and it’s up to you to create a business and make it succeed.

(To do this, I suggest you read 2 posts on the Afrinnovator blog: “15 Skills African Tech Talent Must Acquire in 2012” and Mbwana Alliy’s “12 Predictions for African Tech in 2012“.)

Instead, the disruption comes from the open web. Whenever the operators put up a blocker to what users want, usually in the form of price or access to their infrastructure, the web finds a way of displacing them. Examples abound in location based services, text messaging, video and photos.

There’s a reason operator revenue is shifting away from voice and SMS towards data. The products that got the operators here are receding in relative value. The user wants what’s available in the open web, and that’s just not found, or being provided, by the operators.

So, what is an MNO to do?

Change. Disrupt someone else. Innovate.

One of the biggest disruptors, even in this decade of MNO mediocrity, has been Safaricom – the 800lbs gorilla in my own back yard. They’ve invested in new technology, products and business models like few others, and are reaping the rewards of those strategic moves.

Do I like having a monopoly player in my market? No.
Do I feel bad for the other MNOs (Orange, Airtel and Yu) who are crying now? No, they did this to themselves.

Let’s dig into their golden-child, Mpesa, the mobile peer-to-peer payment system that’s did $3.15 billion in transaction in just the last 6 months(!). How do you know they succeeded in innovating? Well, the easy answer is looking at their profitability and user tie-in that they get from Mpesa. Look more closely and you’ll notice the other signal, all of the bank lobbies in other countries have put up huge walls, blockading an aberration like Mpesa from having sway in their country.

[Sidebar: A warning to everyone who wants to see innovation in their country. Over regulation of telecommunications and banking strangles it. South Africa and Nigeria are cases in point.]

So, Mpesa sounds to everyone like a huge success story. It is, and it’s not. What we think of as an amazing disruptive product is really only halfway up the mountain. There are too many corks being popped while money lies sitting on the table. This stems from 2 main things, which seem to be an issue of Vodafone primarily, since they own the IP for Mpesa and own a 40% stake in Safaricom:

1. The lack of leadership by Vodafone to NOT open up an API that other businesses could build on and increase usage. They’ve stifled innovation on their own product.
2. Their lack of vision in the global payments space. Their shortsideness in not spinning out Mpesa as its own company to take on Visa and Mastercard directly. This was one of the few products and business models that could do that.

More MNO Innovation

So, Safaricom might be stifling its own product, but they’re still not short on disruptive features and products. They do fall prey to bureaucracy and political infighting, but they’re also one of the most aggressive MNOs globally, always trying new things. Three more examples:

• Creativity in 3g data pricing and accessibility down market.
• First-movers in 3g and exceptional data coverage countrywide.
• Okoa Jihazi, their product that gives a loan of credit from the operator to users who are tight on cash.

Other examples of MNOs who are innovating in Africa are:

Airtel Madagascar working with Movirtu with their new Cloud Phone, a way for people to share a phone, but keep the SIM card in the cloud.

MTN, testing Mobile Phonebook by FeePerfect out of Cameroon, a product that puts a phone book into everyone’s phone.

Small + Big

Clearly, innovative products can come to market through MNOs. What’s the common denominator on these products though? Most of them came from small companies and were then incorporated into the MNO.

Ideas come from outside, they come from the edge. Scale comes from inside, from the massive infrastructure provided by the MNO. They have to work together to succeed.

I work with, and talk to, hundreds of entrepreneurs. They have ideas, prototypes and products that just might be what the users want. They lack the access to the infrastructure to roll it out.

As an MNO, you boost your chances of success in this increasingly chaotic space by not walling everything off, but by opening it up.

The iHub is Nairobi’s nerve center for technology; a place where we can grab coffee, create apps, find funders and build businesses. It’s where the community of web and mobile programmers connect with each other, businesses, the government and academia.

[TLDR version: Championed by credible people, alongside advisors from the community. Experimental mindset. Strong connections to corporates. Strict community focus.]

A brief history

There was a discussion at Barcamp Nairobi 2008 about how valuable it would be for the Kenyan tech community to have a static space of our own. No one would fund that idea. My organization, Ushahidi, decided that we liked it the idea enough that we would fund it. It fit with our overall thoughts on being “open”, it would serve as Ushahidi’s home in the region, and most of all, we thought we could use our good fortune to find and help the next startups in Kenya.

Thus, I moved back to Nairobi in 2009, with funding from Ushahidi via Omidyar Network and Hivos, to build the iHub. I quickly selected a space, and picked the energetic and gifted Jessica Colaco as the Manager. In March 2010 we started work on the space, and in June it was open for use.

Though we had provided funding for the first 2 years, the iHub is an independent Ushahidi initiative. Meaning, that it runs outside of the normal Ushahidi operations and organization. Though the Ushahidi team has full access for the space, we have a very light footprint, and use it the same way everyone else in the community does. We knew that even though we were the most neutral of parties, with a ton of local credibility, trying to “own” the space would fail – just as it would if it had been named the “Google iHub” or the “Nokia Innovation Hub”. It had to be owned by the community, and that meant name and usage both.

The community

At the heart of all that happens at the iHub is the community. They designed the room layout and logo, run the network, hold events, built the website, create the house rules and drive the direction of the space. The management of the space is there to provide basic infrastructure support, a foundation, which the community then builds on to make the space what it is today.

What’s important to understand is that we come from this community too, we are it. We knew it could work because it was ourselves we were building for. When people ask me if I could do the same thing in another city, I respond that it would be questionable. A space like the iHub needs to be put together by someone from that community of techies who understands at a basic level the needs and has the credibility within it to make it happen.

As the iHub grew, we realized that all of the administrative duties, mixed with community interaction, were too much for one person. Thus we brought on Tosh to be the community manager, where he is in charge of working with people, memberships and events. His job is to aggregate, translate and enable the communities needs.

The advisors

That “being part of the community” was what drove me to start looking for a small team of advisors who could help make decisions, especially early on. This iHub advisory board was made up of 4 influential and highly credible technology players from Nairobi, plus myself. The greater community could appreciate that they were being represented well, and it provided a small enough team to move quickly.

Initial roles for this team were to make the final decision on build out design, logo and name, as well as figure out how to deal with an influx of members in a tiered membership model if the need arose (and it did, quickly). With over 4,300 white-level members, this team is also responsible for making the decisions on who gets green-level membership, the people who ultimately get to have free and unfettered access to the iHub facility.

The design

The design of the space was very important, and we were lucky to have Fady Rostom and Kwame Nyongo to lead the design team. They spent a lot of time listening to the ideas and thoughts of the advisory team before they started drawing, and it shows in what was built.

We needed a place that was open, and could be flexibly turned from community commons to event space. We wanted a subsection of the space to be rentable desks, for pre-incubation and co-working activities. At no time was a coffee shop not included – it was seen as core to the vibe and culture of what would happen here. We’d need a secure server room, and plenty of ethernet and electrical points, both inside and outside.

Most of all, the iHub needed to be a place where Kenyan techies were proud of. A place that was uniquely ours, and that we could show off to our visiting friends from abroad. It had to have the feel of being any high-tech community space in the world, with a Kenyan flavor. And it is.

The sustainability strategy

Early on we had no idea how we would pay for things beyond the first 2 years. We projected costs, but didn’t know where the revenue would come from. We had some ideas, but instead of creating a grand plan, we decided to take a very experimental approach, iterating on what worked and killing ideas that didn’t fit.

Right now the iHub has revenue coming in from red members (co-working desk rental), events and the new research arm. Events and desk rental were obvious and worked from very early on. The R@iHub arm didn’t come into being until January of this year, and was very much a big experiment – which appears to be working marvelously well. Jessica’s background is as a technology researcher, and she’s built a brilliant team around her to focus on this. Already we can see that 50%+ of future income will come from this initiative.

The other experiment was taking lead on the m:lab, a space the same size as the iHub which sits one floor beneath us. It’s an incubator. It plays the iHub’s foil, where upstairs is about community, openness and fun, the m:lab downstairs is about professional tech companies building quality products and making it into the market. We took the lead on the consortium behind this, and it is seen as a sister-facility to the iHub, with many shared services between the two.

The corporates

Both the iHub and the m:lab have strong corporate partners. Early on, before the first brush of paint was dry in the iHub, we had started talking to big technology corporates who call Nairobi home. Large tech corporations need an active dev community, and the dev community needs them. Luckily, Kenya is geographically well-positioned for some great companies to make it their home in the region, which worked well for us. We also happened to know a number of them personally, which sped up the discussions and interactions considerably.

We didn’t want to just have corporate partners who were sponsors. We made it very clear early on that their money was less important to us than what value they could add to the space that would help the dev community, but that it was a 2 way street. If we couldn’t facilitate a strong value back to them from the local tech community, then it was a no-go.

Fortunately, despite our lack of a clear idea of exactly how things would work, or what our metrics of success would be, we found some great patners. Nokia, Google, Wananchi and Microsoft are corporate partners with the iHub, and downstairs we have MIH, Nokia and InMobi working with us.

A small aside here, which isn’t corporates, but we’ve also nurtured strong connections with the Kenyan government, though we take no money from them. This also applies to academia.

Final thoughts

By the end of 2010 people were already claiming that the iHub was a model for technology engagement, aid stuff (gah!), etc… in Africa. I thought that was a premature statement, it was an experiment and it still is. The success of the iHub has come from a strong foundation of advisors and community members who understand their city, their peers and their region.

The success of other tech hubs across Africa will be based on leadership credibility, and ability to engage their community.

Much of the iHub’s success comes from a community that works together. In that spirit of “harambee” that is so much a part of our Kenyan life. While there is always healthy competition, we would rather work together and celebrate each others success, and ultimately help each other along with the knowledge that if more of us succeed, then we all benefit.

I hope to see many more labs and hubs across the continent, and we’re seeing them grow too, in Cameroon and Ethiopia, Uganda and Nigeria. Though some of them will need financial assistance to get going, like Ushahidi did with the iHub, they’re organic growth is what makes them viable.

The Kenya Open Data Initiative (KODI) goes live this morning in a big event that includes President Kibaki, as well as many politicians, government officials and local technologists. The World Bank, who has been instrumental in organizing and helping publish the data is here as well, along with Google, Ushahidi, the iHub community and a large selection of youth.

Data Sets

The data is available online through the Socrata platform, which allows users to view different data at national, county and constituency levels. They can compare different data sets, create maps and other visualizations.

Data sets are categorized into 6 main categories: Education, Energy, Health, Population, Poverty and Water & Sanitation. It includes data from the national census, the ministry of education, ministry of health, CDF projects and many more.

Here’s an example of that data, “county expenditures by administration”:

Mashing up the Data

This all came together rather quickly, starting about 3 weeks ago. The tech community was immediately reached out to, and as the data sets have come online over the last week, we’ve had access to them early in order to show what can be done. Here’s a few samples of that.

The Ushahidi team is taking the census data and overlaying healthcare institution data on top of it into our Huduma site. It’s still very beta, but it shows what can be done in just a few days.

We’ve also built a simple SMS query tool. If you’re in Kenya, send an SMS to 3018 with the name of your county or constituency and you’ll get back an SMS with the demographics and MP of that location.

The Virtual Kenya team has built an app that shows which MPs refuse to pay taxes.

The iHub community has done some things around tracking CDF fund usage in the constituencies. There’s a mobile app called “Msema Kweli” that allows you to find CDF projects near you, and for you to add pictures of them.

I will bring them your answers to the questions below:

• What is Google doing well in Africa that they should continue?
• What should Google be doing better, differently or new in Africa?

A Few of My Thoughts

Google has done what few other tech companies have done on this continent. Having 54 countries to scale across isn’t easy, so anyone trying it gets a lot of credit.

• They’ve invested in people; both their own and the community in general.
• They realized early that there was a need for tech policy change, and put time, resources and energy into that.
• They have surfaced content, from maps to books to government data that wasn’t available before.
• They have localized search into multiple local languages, made their services more mobile phone friendly and experimented with services for farmers, health workers and traders.
• Their Google Global Cache has sped up the internet by upwards of 300% for some countries.

Here’s are my suggestions:

Double down on Android. Do this in two ways; first, keep driving the costs down, like what was done with the IDEOS handset. Second, help your partners (Huawei and the operators) push the spread of these beyond the few countries they’re in now (and at the same price as in Kenya).

Gmail ties everything together. Google has been the beneficiary of most other companies ignoring Africa. Facebook is the only challenger in the chat, mail and social spaces. Get started on zero-rating Gmail with the mobile operators, figure out how to make Google Voice work here, and extend Gmail SMS Chat beyond the 8 countries that it currently works in.

Figure out payments. It’s still difficult to get paid if you’re running ads or making Android apps, you’re not on an even playing field with your counterparts in other areas of the world. It is clear that Google Wallet is a strong personalized LBS play on consumers in the US. Take that same energy and figure out how to crack Africa, realize just how much money there is in a payment system that spans the continent.

Keep experimenting. Many don’t know of the apps and services you build and test out in various hyper-local areas. Some work, some fail. This curiosity and willingness to try something innovative and new is what makes the open web such a great space, and it is what helps us all overcome the walled gardens of the operators. Don’t stop.

Finally, though you have all the power and brand name needed to make things happen, remember that it’s the local devs and companies who need to own their space and especially their data. While flexing your muscle, especially with government types who own vasts amounts of data, do push for local ownership over taking it for yourself.

[Notes: hat tip on this post goes to Steve Song who started thinking through this years ago. Image credits from Memeburn.]

It goes something like this.

We have a few good success stories in any one of these cities. There are a handful of great tech companies and organizations that have “made it”. This can be seen as a success in innovation or in business (or in both). Everyone wants to be at the tip of this, and these are the examples we hear of at international conferences and read about in the media.

In the middle we have everyone else, the guys who are still slugging away. They have some clients and revenue streams, but they’re not at the top (yet).

At the bottom, that’s what we deal with in places like the iHub and m:lab. These are those scrappy startups that might or might not have any right being in the place. They’re risky, probably don’t have a solid business model yet, and only a few of them will graduate into the SME space above them.

What to do?

To make the tip of the pyramid bigger, to have more success stories in the tech space, there is only one option: you have to make the base of the pyramid broader.

If your job is to see more innovative new tech companies come out of Africa, the recipe is quite simple:

• Invest seed funds into local tech entrepreneurs.

(that’s my only bullet point, it’s that simple)