While writing and editing, we’ve realized that we indeed know why data spaces are complex beasts… but perhaps we’ve never read anyone trying to lay down the reasons in a clear way, trying not to scare people away. If you want to promote something – even when it is for the good of society, like enabling ourselves to share data to understand and address societal challenges or innovate – it feels counterproductive to be transparent about how much work that is. The YouTube generation needs to consume “Master data spaces in 15 minutes”-like videos. Gone are the days of Malcom Gladwell’s 10,000 hours rule of thumb. Well, I am sorry, data spaces are complex.
First of all, why do I feel I need to write “design, build and operate”, like I did a few lines above? It always feels like to me that, to be fair to the topic, I need to place it in the context of the data space’s lifecycle.
- When you design it, it does not even exist, you’re wondering about what your use cases are, and how to make it sustainable, from a governance and financial point of view, how to incentivize participants to join and value the opportunity. Is it worth it?
- When you build it, you need to find the money to kick it off, implement its technology, choose its legal form, write the rulebook and terms in general that the participants will have to sign off to. Will it work?
- When you operate it, besides oiling the machine, you need to promote the fact that the data space exists and it is trustworthy, fight the resistance to share data that is still common in most businesses, and – the hardest of all, perhaps – reach that critical mass of participants and activity beyond which the data space really makes sense and – possibly – would continue running even if you walked away from it. WIll it last?
Voila, you’ve created a stable, sustainable socio-technical system for sharing data.
Each stage has its best practices, pitfalls, successes and horror stories. If that wasn’t enough, complexity also comes from the time it takes. Many of the arguments I see among my illustrious colleagues are caused by misaligned expectations around timing. Some design a system that can go live before Christmas. Others design a system that will be stable and operational five years from now. Guess what? you’re both right, stop fighting.
Embrace complexity, be patient. Make things as simple as possible, but not simpler. And, most of all, work together. Whether you’re an expert or a user, there are venues for you to gather and bump your heads together.
We, at the International Data Spaces Association, are starting the Data Space User Group next month with a virtual kick-off, click here to join and support us, because it takes a village to make these complex beasts a success. See you there.
