How I learned to Innovate (a bit more) in Regulated Industries

First published on

Here's a short story about how I learned to innovate (a bit more) in regulated industries.

In the summer of 2020, Yves Prevoo had got easee in the first Techleap batch. Pretty cool! I was invited to join one of the sessions for the CTOs in which Ali Niknam talked about his adventures. I didn't know anything about him then but I liked him right away as he also wore a black t-shirt and a Casio F91w, my standard outfit.

I had been struggling with innovating in a highly regulated industry. I dreaded the yearly ISO 13485 audits and always had the feeling we were doing everything wrong or breaking some law that we didn't know about yet. It didn't help we didn't have anyone with Medical Device experience and it didn't help that we had a very strict auditor. To be frank, I really had no idea how to develop anything new and get it certified without going bankrupt from the clinical trials. I didn't know what to do or how to lead my team in an inspiring way because of all the regulations.

Hearing Ali speaking about Bunq in such an optimistic sense was surprising. Wasn't banking also highly regulated? How did he keep the can-do attitude that I lost? So I decided to ask him about this during the Q&A. As I stood up he complimented my Casio and I made some stupid joke that didn't land, but then I asked "How do you keep innovation and fun alive in a highly regulated industry?"

I think he understood the pain where my question was coming from and his answer was short and spot on. This is how I remember it:

"Auditors are not omniscient, they are typically pretty boring and their job is to go through checklists. This is how the system works and it's a necessary evil. Now, it's your job to figure out what's on their checklists and how to give an answer to each item on the list. But don't start by focusing on doing everything right, first focus on what you want to achieve, and then figure out the checklists. After all, auditors are not leading industry advances, we need you to do that."

What a fantastic call to action! I felt very empowered and my whole way of thinking about auditors made a 180 in that moment.

In the next year I felt better, was able to file two innovative patents and ship a lot of improvements with my team. There was still quite some residual fear, and the EU really put a hard break on innovation with the "no significant changes" clause in the MDR.

But now, in every new project I take on in a regulated industry, I see my role vs the auditor's role crystal clear. My job is to innovate, their job is to make sure the necessary checklists are checked.

Thanks Ali!

(this is a cross-post from LinkedIn  https://www.linkedin.com/feed/update/urn:li:activity:7200829829997359104/ )

Comments

Post a Comment

Popular posts from this blog

"Security Is Our Top Priority" is BS

First published on
A couple of years ago I was asked to give a conference talk about software security. Well, actually I wasn't really asked, my company bought a sponsorship package with a speaker slot and I replied to the internal email asking for volunteers  🤣  Anyway, while preparing my talk, I realized a couple of important points about security that have not left my mind since: Security is limitless . You can always spend more effort to make things more secure. The same goes for quality, safety, employee happiness, etc. The needs of security are opposed to the needs of a convenient user experience . Improving one typically hurts the other. Now some organizations say "Security is our #1 priority". Really? You want to make something that has no limits your number one priority? I mean security is a good thing, but this seems a bit too simple? In fact, hollow marketing claims like that can make me a bit angry. In this post I'll help you understand what to make of statements like that...
Read more

AI programming tools should be added to the Joel Test

First published on
Here's a wake-up call to all CTOs: AI programming tools are getting freaking amazing and if you don't allow your teams to use them somehow, it will bite you in the ass in a couple of years. You will be slower and you will lose your best people. The infamous Joel Test is a list from the year 2000 of 12 things all great software companies do. Since then most companies have implemented Git and CI/CD, checking of three items, so we have some space left in the 2024 update ;) I believe "Do you allow your developers to use AI assisted development environments?" is a necessary addition. I get that you don't want your source code to end up on some OpenAI / Microsoft / Github server somewhere, sure, but find a way to use your own models or learn to live with it. Note that this is often not the same as "#9 - Do you use the best tools money can buy?" as blocking AI tools is about data security, not money. So why do I think developers need AI programming tools? I...
Read more

The long long tail of AI applications

First published on
Image
Last year multiple companies asked me for advice. " We are evaluating this AI powered product, but do you think it makes sense at all? It seems a bit niche and we think ChatGPT might make this entire thing obsolete soon. " Long tail - credit to Wikipedia My answer so far has always been: "No, bare LLMs are not going to compete with this product." I think that people are failing to understand the distinction between different classes of AI companies. I see it like this: Foundational AI - creating models like GPT-4 (text), Sora (video) etc. Applied AI - using existing models to create smart applications. Note that there are also companies not focusing on AI - they will start lagging behind, let's forget about them ;) There are orders of magnitude  (!)   more companies that will deal with Applied AI than Foundational AI, and they will be very busy for decades to come. Here's why: To get the most out of LLMs, you have to ask the right questions. LLMs have acc...
Read more