If this efficiency-optimizing author were to take his SV mindset to tackle thise inefficiencies at industry scake, what this author will quickly find out is that it is an impossible task. The industry itself is necessarily slow and its not by accident. It can be fast when it absolutely needs to be e.g Covid vaccines. That alone should let you know those inefficiencies are only inefficiencies to you because you are naive to what the industry is actually optimizing for.
At best, you sound like the impatient driver honking on a crowded street, aggressively driving into every available opening thinking you're optimizing for efficiency. You arent.
I will note that you addressed none of the points made in the article. My assumption is that either you feel the need to attack the authors conclusion, having no defense of your own, or you’ve foregone reading the text altogether.
Edit: After looking at your post history, I realize you just want to tell people they are wrong and you are smarter than them. Don’t bother responding, I don’t care what you have to say.
It's only an "inefficiency" from the perspective of the person who doesn't understand what the system is optimizing for. This author is ML engineer commenting on a field he is relatively new to and doesn't yet fully understand. To a person wanting to drive highway speeds in a crowded downtown street, everything would seem 'inefficient'. In reality, they aren't. The objectives are just different. Once you understand the larger objective, you start seeing what the true problems are, you start understanding that some things that look like inefficiencies at first glance, are actually features serving a purpose within a larger context, that you initially didn't understand.
Some things mentioned in the article clearly increase risk to participants: manually re-assembling translated documents, using custom software and paper forms, and diluting important documentation with boilerplate. Other things seem to purely increase cost: starting meetings with smalltalk, overcharging for server hosting, and cronyism.
The ethos in tech is just fundamentally different. Move quickly, break things. Its an Agile mindset of quick changes, pivots, rapid advances. Inefficiencies get identified and are tackled.
Medical world is different. The inefficiences are a feature not a bug. They are there to exactly do what they are doing, slow the rate of change. Clinical trials is one place where both worlds collide, the fast pace technical innovation world is about to interface to the slowly changing medical world. All of these guys frustrations is exactly about that.
He might think the solutiom is to speed up clinical trials phases. It isn't. Even if you did, sooner or later you will still come to another traffic stop of slow changes and inefficiencies because the medical world moves at a different pace, and necessarily so. When lives are directly involved the burden of proof to enact changes have to necessarily be very very high.
And what techies do not understand and probably keep asking is "doee it have to be so?". Yes it does. We didnt arrive here by accident. Even if we started healthcsre industry anew, it will inevitably end up in this slow-changing equilibrium. When lives are directly involved, better to leave things as is, than change and make worse. The burden of proof for even the slightest of changes is extremely high. what's optimal for health is indeed a slowly changing world. It is not for lack of talent or intelligence, as this author naively suggests. If you want to solve problems with quickly, don't go near that world. Stick to the world of optimizing ads