|
The article names its archetypes not entirely fairly, based on my experience at three MIT startups. Two were novel-tech academic spinoffs, and the third was alumni applying/integrating COTS tech driven by customer problem domain. Of those three, two were business-thinking much like the article's "Stanford" archetype. The other had, like the article's "MIT" archetype, a period to develop tech from the lab, and a challenging changing of gears to be cutting-edge product-driven. Also, a fourth MIT startup, which I recently almost co-founded, even before I joined the nascent team, the inventor-CEO had already done impressive customer-oriented legwork, and found Bay Area advisors, more like "Stanford" in the article. > The team has 9 PhDs and just hired an MBA to start finding customers. This is a problem, if none of the PhDs happen to have non-academic strong experience in product, nor in industry team engineering. An academic environment will tend to make people think they know more than they do, about things academia doesn't know. Also, academic degree and career paths in some ways reward the opposite of how I think people in a startup, or other effective company, should be thinking. (Unless the startup is more the VC growth investment scheme kind, which can be mostly about appearances.) One MBA (even if very experienced) probably can't, by themself, counterbalance all those experience gaps, nor those lessons to unlearn. > The MIT startup has no sales to customers, but possibly a DARPA grant to develop their technology. I don't know about the more involved DARPA grant-writing, but SBIRs do seem to be popular seed-ish funding: https://www.sbir.gov/ |
Some programs are specifically designed for commercialization and want to see a product available at the end. There was a big shift to that post 9/11 (sometimes called "little 'r', big 'D'": less research, more development.