"In academia, in order to publish a paper, often you just have to get it to work one time out of ten – so you think, OK, I’ll just keep doing the experiment until it works. We need it to work nine or ten times out of ten."
So the author confuses it with engineering. Then -- allow me to be a bit cynic -- the actual meaning of the article would be something like:
"If you want to be a scientist at a startup, you need to become an engineer."
There are some cases where it's obvious how to be faster (and occasionally more rigorous): judiciously throw money at the problem. In academia, where grant funding is pretty limited and equipment is expensive, you probably want to only have enough infrastructure for, say, the 50th-90th percentile of load (microscopes, thermocyclers, analysis compute power, what have you), and accept that 10-50% of the time there will be a queue. If the difference between being successful in the market and having your lunch eaten by someone else truly is a matter of weeks, then it makes sense to you and your investors to put some extra money into a widget that will sit idle for most of the time but that helps when things are crunched.
That said, money can't fix everything---9 women can't produce a baby in one month!
> Then you're just not thinking hard enough!
- My boss
Ironically, using the 'rigour' of science, startups require much less rigour - startups just need something that works enough, not something that is as correct as can be done.
Of course, the story is different in pharma and a few such fields. Theranos is an example of how lack of rigor and openness can damage healthcare startups.
Startup's goals are generally completely orthogonal to publishing.
A related consideration is that training grad students and post-docs is a key component of most academic science. The requirements of training often limit the size of teams working on a single project with the PI-trainee relationship dominating the organizational structure.
As the "PI" of a science startup R&D team, I can start and stop new projects at will with varying team sizes and mandates without the consideration that my folks need to produce a body of published work to further their careers.
It's a terribly inefficient process that could be optimized by changing the goal from "publishing" to "making something that actually works". Thus you could achieve greater speed and more rigor at the same time.
(Basic research could probably be optimized too, although not through market incentives.)
I don't think this is a new concept; Jon Gertner in his excellent book "The Idea Factory" writes how the researchers at Bell Labs switched from basic research to development during WW2 and operated in a similar way. If anything, the urgency of development in the war effort resembled a startup in how it accomplished within a few short years projects that would have taken decades in peacetime.
If you're building a company, odds are you aren't doing fundamental research (and you might not even be doing translational research).
In our academic lab, if we knew how to be faster, more rigorous, or both, we'd be doing it.
The notion that a startup can do rigorous research faster than academia is curious. The scientific journals are not full of the output of startups. Industry in general, and startups in particular, can't expend the resources on covering corner cases and tidying loose ends. The profit is generally in getting the gist of an idea, not in writing it down, vetting every detail, and sharing it broadly for free.