I worked at a startup that had <4 months of runway left and thought the best plan was to bring on a VP of Data Science because of their resume/history, in spite of the fact that we had no data to do science on and no customers for which to provide value via data science. That VP of Data Science turned out to be a person that didn't know how to do much more than, as the article said, "build and scale amazing teams".
The story ends as you'd expect, we all got laid off and the founder was shitty.
> I worked at a startup that had <4 months of runway left and thought the best plan was to bring on a VP of Data Science because of their resume/history, in spite of the fact that we had no data to do science on and no customers for which to provide value via data science.
Reminds me of a project life cycle cartoon I first saw in a software book early in my career.
Just now searched for "systems analysis tyre cartoon" and selected this page, which seems the best, on a brief look, since it has both some history and multiple versions of the cartoon:
I like number 7, the documentation one, which really goes to show how little the real item is understood while everyone else is creating/imagining their own version. Dissociation within the whole team.
The story ends as you'd expect, we all got laid off and the founder was shitty.