Node Knowledge… November 2013

ODI Node

As I wrote in July, we’ve had many, many requests to help start “an ODI” in other places. We still hadn’t finished working out this ODI, and everyone we spoke to had a different idea about what an Open Data Institute might do.

ODI is non-profit. Non-partisan. We responded to these requests by creating an open process, and an open conversation.

In a remarkably short period of time (4 months), we went from some ideas, to documents, to signed agreements with 13 organisations around the world.

I have spoken to well over 100 people, from dozens of groups, from over 30 countries. By email, by video Skype (with up to 4 organisations/countries at a time), and in person. It’s the beginning of a voyage.

I’d like to share some of the things we’ve learned over the last 16 weeks.

  1. There is huge positive intent almost everywhere: a willingness to try.

  2. You can build quickly.

  3. There are consequences of doing so. There is confusion.

  4. Lack of understanding had led to some distrust.

  5. How we follow-through will be critical.

ODI Annual Summit: 2013

Before we started, we looked at a lot of different models, from Médecins Sans Frontières to Human Rights Watch, from Github to Ushahidi. I combined this with my personal experience of creating organisations (ODI is the 9th company I’ve helped to build over the last 20 years), with insights from our team, and many others.

The ODI is new, it’s well-funded, has unique founders and an amazing team. This is a privilege, and with such privilege comes a responsibility. I made a decision that it was our responsibility to experiment in the creation of a global open organisation. I didn’t want to over-think this, I felt we would learn more by trying it. The ODI board, and the team, agreed.

If you want to go fast, go alone. If you want to go far, go together. — proverb

We made a choice, an active choice, to go fast. We chose to run with people and organisations that could wonder, and run, with us at a pace.

I’ve been blown away by the number of people willing to commit their time and energy to collaboration. People I’ve never met have worked together, with obvious positive intent, built trust with us (we don’t know everyone), trusted us (ODI is the new kid on the block, after all), and looked to a future where a global network might be able to make a difference.

We are definitely not alone, but we (the whole open data community) are also not together. That we have any Nodes at all is a better outcome than I was expecting: the worst would have been that no one noticed.

Our choice was to create a lightweight, fail-fast, “many-parts loosely-joined” network — to see what was possible. To “shake the tree”.

Don’t let the perfect be the enemy of the good

A natural and considered consequence of this was, and is, that we won’t get it right. But, as we do with all our projects, it’s better to start development, test it, fix it, iterate… my operating principle was — and still is — “code-test-fix-repeat”, in an open environment.

http://github.com/theodi/ODI is where that happens.

People are (always) a lot harder than code

I set up a mailing list. I added over 50 people who had explicitly asked to join in the conversation. Very few people used it. I think (but don’t know) that many were interested in what might be being said, but very few were willing to put their own hand up (maybe they didn’t feel empowered). So, after trying to stimulate conversation this way, I stopped.

Instead I put out a call for “open discussion sessions”: time slots where I would be available on a video Skype or Google Hangout for anyone from the group to join, and discuss what we all might want to do. We set them up for 8am, 5pm, 10pm, to cover all the time-zones. I turned up. Almost no one else did. So we stopped trying that.

We then went for the labour-intensive route. My (exceptional) assistant, Jade, contacted people individually to set up small, dedicated calls for me with 3-4 people from different organisations or countries. We did over 20 of these in 2 weeks. During each call I made an open Google Doc for everyone on the call to see my notes, and their notes, about the call.

Suddenly, we had progress. Fast progress. People edited the proto-contracts during the calls. Everyone, collectively, came up with the names of the Nodes: Country, City/Region, Communications (initially I called them level 1, 2, 3). People asked lots of questions. Then we all answered them.

The single most powerful component of the process was this (on first calls with new people):

me: “here is the draft contract we’ve created”
them: “we don’t understand how X might work” [slightly apprehensive about ODI’s intent]
me: “neither do I, could you edit it with what you think?”
them: “oh!” they edit in changes to the contract [trust built, this is now a collaboration]

I can’t overstate how often this repeated and how much it broke the ice on a new relationship. Quickly the questions turned into patterns, and everyone became “comfortable enough” with the intent, the deliverables, and the financial model.

For me, it was quite a “high density” data and communications process. I think there was only one time I introduced someone to the person who’d introduced them to me in the first place.

Open Data Institute Annual Summit 2013

Outcomes

In the 2 weeks leading up to the first ODI Summit, 13 organisations from around the world, signed a contract to become an ODI Node. Their commitment: time, energy, and money. Our commitment: time, energy, and money. More on the money later…

The ODI provides training, research and development, and incubates startups. It bridges between commercial, public sector, research and third sector communities.

Nodes are attached to existing organisations (for-profit, non-profit, or academic), and not to individuals, in-part to reflect the ODI’s commercial focus.

The focus for our Node conversations were to

  1. Support a community.

  2. Bring a project to collaborate on.

    (or, if you are a Communications Node, bring stories and use-cases)

Key themes are around amplifying what is there, growing the reach of open data — for everyone.

The risk

The board, rightly, asked me a very important question.

We’re a new organisation. You don’t know what these Nodes might do, we don’t have much/any control. Why would you put our hard-won brand at such risk with this idea?

My answer was

It is a risk. But what is the risk if we don’t do it? What is the opportunity? The worst-case is we pick the wrong organisation to be a Node, or they do something damaging. If they do, they stop being a Node. This is why we have an ODI Charter, a licensed brand, and a central registry. It’s certain we won’t be able to have certainty, and we’ll make mistakes.

And, certainly, we will.

Even before the Nodes idea, we heard that some felt confused or even threatened by ODI. Since, I’ve heard comments ranging from

ODI, are they friend or foe? to They ignored existing open data community X in Y to We’ve been doing this for X years. Who do they think they are?

We recognise that there are lots of people already working in the space, and doing great things. We want to add to those activities, not take away from them. We are coming to this with positive intent. We are working it out as we go along, and have to be able to make mistakes rather than being frozen into inactivity for fear of doing the wrong thing.

  1. We are working to build a new organisation, called the Open Data Institute.

  2. ODI’s mission is to help catalyse the evolution of open data culture.

  3. We’ve done almost everything completely in the open.

  4. We don’t know everything, or know everyone, and we never can.

  5. Everyone is limited in time, energy, and money.

  6. We’re all, every one of us, working it out.

If people are asking about what the ODI does, please share this page, or our first Annual Report. Please ask if you’d like hard-copies to share (they are lovely things). If you know anyone we should be reaching out to, please let me know (my email is gavin@theodi.org).

About the money

Money is like a sixth sense without which you cannot make a complete use of the other five. — Maugham

I strongly believe that part of the ODI’s responsibility is to increase the amount of money to the whole the open data landscape.

I have been reminded, almost daily, of the 1990s. Huge numbers of talented, passionate people built the open web, often unpaid, and the foundations of where we all are today. Then, as the money flowed in, different sets of people benefited. Often the volunteers, the innovators, who made amazing things, stayed unpaid or worse, unrecognised, for their works. There are many stories on those mountains.

I don’t want to see this happen again, but I see it coming in the open data landscape. McKinsey said only 2 weeks ago that open data would be worth up to $5 trillion a year. I’m concerned that the same things will happen again as in the 90s. We want to help do things differently this time.

Tim and Nigel’s vision was that the ODI should catalyse the demand-side of open data. If there isn’t demand, then there’s no need for the supply — that’s a big risk.

My job is to help ODI make that demand-side work. For me, to make it work, everyone’s work needs to be operationally sustainable, which means people need to be paid, properly. A lot more money has to flow towards open data people, and open data places.

We have already demonstrated that it is possible to bring in new money: over $1m of commercial income from ODI Members in 6 months, over $3m of prize funds, over $20m of development funding. These are big numbers with one lens, and tiny numbers when we look at the scale of what’s needed.

How do we get a million people involved in making a difference (social, economic, and environmental) using open data? How do we help bring 0.1% ($1bn) of that McKinsey figure to making that difference?

ODI charges Nodes

To instil this commercial focus in the Node models, we have borrowed from franchise-like models. ODI licenses its brand. For small companies this is a “nominal amount”, £50. I picked a number (it could have been £1) so we could raise an invoice. Raising an invoice and getting paid tests a lot about processes, and cements our contracts. The fee is more for big organisations.

For material work, we have put an initial stake in the ground of 10% of Node-related revenue (with the ability to exempt certain work). For example, some Nodes want to provide paid-for training, and are happy passing 10% back to us. Some will get local grants which 10% can’t be shared from. This is fine.

I don’t know if 10% is the right number, but I do want to create an economic flow. If we get this right, I believe we can do three critical things:

  1. we can help co-fund projects across the network

  2. we can help fundraise both centrally to support projects, and support local/distributed fundraising

  3. we can communicate the economic growth of the open data community, which is crucial to points 1 and 2

Open Data Institute Annual Summit 2013

What next

I thought we might, with a favourable wind, have 4 or 5 Nodes by the Summit. We have 13 in 9 countries, and this is set to grow very soon.

Our next step is to talk, with each other, with you. We now have time to put in some code (e.g. what project will someone deliver), some tests (e.g. did it have any impact), processes (e.g. how well was communication managed), and iterate (e.g. adding metrics). The commitment we’re making is to iterate.

ODI has run, quickly, to establish the beginnings of a global presence. The cadence we have inside the UK ODI is to move quickly, then take time to listen and reflect on concrete evidence, test, and iterate. This is our mode of development.

Questions we’ll address include accrediting trainers, syndicating membership, and using open data certificates. We will share our knowledge, showcase the work of the Nodes and the whole community, and work out how the global network can coordinate on issues, resources, and funding.

We want to solve problems. Our mission statement is, I hope, really clear: “catalyse the evolution of open data culture”. This, is for everyone.