At the time I joined it seemed like it would be pretty easy given that Larry Page greenlit Google Health (a terrible idea).
At the time I joined it seemed like it would be pretty easy given that Larry Page greenlit Google Health (a terrible idea).
I'm curious why you think Google Health was a terrible idea. I'm not disagreeing, just wondering your opinions on the matter from a more inside point of view.
Thank you.
That's not how health records work in the US where Google tried to start the product. HRs are effectively owned by the companies that provide health care, while patients have access to the records. There is a multibillion industry dedicated to keeping things that way (Cerner, Epic, the hospitals themselves) and even with Google's ostensible ability to change the world (at that time), they would never have been able to build a product that sustained itself because there wasn't a market for the product.
In short Google tried to compete with EPIC and Cerner without a market for their alternative product.
Individuals in the US (present company excepted) aren't interested in owning and managing their own health records; they want their HRs to be managed conveniently for them.
Today, Google (and AWS and Azure) makes deals with EPIC and the Hospitals (to host infra in their cloud) and also makes research deals (to help build their health research projects). This is a much more realistic approach given the constraints.
In the case above, it was really about a pivot of Google Cloud Genomics- my market research suggested that people wanted to store large amounts of BAM files cheaply and access them via an API, when they really wanted Spark for Genomics. I brought that up with our leadership and they declined to make that pivot early.
Here's what the Cloud Genomics product eventually evolved into, which actually is pretty good: https://verily.com/solutions/terra/ (I was the person who set up the original Google/Broad relationship that led to all of this).
This seems to be a fairly common thing at Google. I hear Google "hoards" a lot of PhDs who are just "refactoring APIs and doing migrations". Is this not seen as a problem there wrt retaining talent?
Ah, taking a page out of IBM's recent playbook.
Would you care to elaborate or link to an article that explores this view?