Go Go Power Rangers (of Autonomy)

Remember how I talked about why interoperability is important outside of video games and NF-bloody-Ts? Well, this time I want to order the autonomy part of the autonomy, mastery and purpose menu, with a side of interoperability, please. I’ll drive around to the collection window, and we can munch through this section. Remember: we’ll be hungry again in 20 minutes.

K.I.S.S Me

In digital landscapes and ecosystems, autonomy is a prized asset. It grants individuals and organisations the ability to exercise control over their digital interactions and data. The Mom Test by Rob Fitzpatrick is a must if you want to understand interoperability. Moreover, this book more than hints at the importance of autonomy in our digital experiences, and this is where interoperability plays a pivotal role. Up to this point in video games at least, most things we make pass some equivalence of the Mom Test. My argument is that everything must pass the Mom Test if it is to be interoperable. Here’s why: you can only be successful in what you make if your non-demographic can use it with ease. That’s quite a controversial statement, isn’t it? What if you, the stakeholder, doesn’t want just anyone to use it? Then your product will never be interoperable.

Exchange and make use of...

Keep it simple, stupid. Interoperability is not something you can pick and choose the parameters of. Interoperability is “the ability of computer systems or software to exchange and make use of information.” Exchange and make use of information. That means all information, not the bits that you don’t want people to see. ?

If you think I’m being controversial now, wait until you read my book! From Pixels to Portals: Exploring the future of the metaverse through the evolution of video games does not hold back on controversy and opinion. So, buy it or I’m sending the boys ‘round.

Tech Fixing Tech Then Breaking Tech

Interoperability isn't confined to the digital realm alone; its influence extends far beyond, touching every sector, including healthcare, finance, and manufacturing. By seamlessly connecting disparate systems and platforms, interoperability empowers individuals and organisations with greater control over their digital interactions.

In healthcare, for instance, interoperability should enable health records to be efficiently and securely shared across different institutions. This newfound freedom allows patients to make informed decisions about their care and choose healthcare providers without being bound to a single system. They can access their medical history, track their health data, and exercise their autonomy to the fullest. Isn’t that the dream?

The financial sector presents a similar narrative, where interoperability connects different financial institutions, enabling individuals to manage their finances holistically. I’m sure you’ve read about open banking initiatives, you haven’t? Let me help you. The future of banking technology on the customer facing side is no longer about being tethered to one bank's interface; autonomy is about having the flexibility to choose services and applications that align with personal preferences. But whether that will ever work in tech infrastructure concerning everything from cybersecurity and banking secrecy to AML and global affairs policies is anyone’s guess.

When I built the tech stack for NAK3D, it was impossible to just break current systems because everything is so connected; so what I did was a bit of stealth disruption. I developed a rollout and rollback solution. I did that because we won’t be in this holding pattern of decision making for long. I see the fashion industries in particular, exploring a more immersive internet rather than the boring old ecommerce model and for that I needed to develop the best case and worse case models for adoption. They say it’s better to build something big first and then making it smaller, that doesn’t help when the user experience is changing on an almost hourly basis. That forms my argument for why I think classic video game hierarchies in tech simply won’t work in other sectors and why we must work together to make every sector of industry interoperable. You get me?

Cornerstones and Pillars

Unravelling the core principles of interoperability, for me, is a joy. I must really like hate mail because every time I bring this to discussion I am faced with a barrage of criticism. You don’t get a prize for knowing who is doing the criticising, sorry friends. Among these principles, data standards, open protocols, and cross-platform compatibility stand as the keystones to unlocking autonomy for the user and your back end or tech stack. Data standards ensure that information is universally comprehensible, irrespective of the system or platform it originates from. It means users are no longer locked into proprietary data formats, giving them the autonomy to choose how to use their data.

We have so many stupid standards that are not made to be agile, that do not suit the changing times of technology movements and frankly, (I won’t name them directly) but they are so caught up in their own bureaucracy that passing a standard in this organisation has so far taken 18 months for one project standard (not the whole thing). It’s outdated and it’s stupid. But we need something. Anything!

You call this agile?

Open protocols foster communication between different platforms, eliminating the barriers that siloed systems create. Autonomy is thus magnified, as users can choose which applications and services to integrate, ensuring that their digital experiences align with their unique needs and preferences.

Even user models are outdated and tired. No seems to want to fix something because it isn’t broken, but they are super happy to drag us through a design dirge of the same ol’ concept where the end user fits the tech and not the other way around. We call this agile?

Let’s set out some hypothetical pillars: 1. We must be interoperable which means we can use products and services simply and within the same software constraints. 2. User access and experience models have to be agile and tuned to the user/player/consumer, not the tech. 3. Rollout and data are specified before the build process rather than 10 years later in a class action or federal hearing. 4. Iteration is consistent (no handbrake turns). Any more pillars and I’ll be building a roman loggia. You get the general idea. ?

I Want My MTV

The benefits of autonomy through interoperability deserve deeper exploration. Autonomy isn't merely a theoretical concept; it delivers tangible advantages. First and foremost, it leads to increased efficiency. When individuals and organisations can connect and share data seamlessly, they eliminate redundancy and streamline their operations, freeing up time and resources (you know that means money, right?)

Therefore, better user experiences emerge as a direct consequence of autonomy. When users have the freedom to choose their preferred tools and services, they enjoy a more personalised and user-centric digital journey. The power is in their hands, and they dictate how they want to interact with the digital world.

Don't you want to make money?

Innovation is my cornerstone of progress, which is also fuelled by autonomy. When individuals and organisations have control over their data and interactions, they can explore uncharted territories, fostering creativity and technological advancement.

Ultimately, autonomy granted through interoperability offers your users the control they need over their digital interactions and data. It's a transformation that leads to more efficient, user-centric, and innovative digital experiences, underscoring the gravity of interoperability in everything. To be honest we’re learning from games, but games will ultimately learn from everyone else that’s just the way it is.

And if you want more? Don’t worry, it’s a-coming. Oh and, my book drops on November 3rd through Byte Bound.