The best datascience projects are ones that started collecting good data 3 months ago. The hardest thing I've had to do is convince engineers to involve DS people in the design phase of their work. Initially they just don't see us, or see us as an annoying extra stakeholder. But it's more annoying to go back to already deployed code and add data collection to it and then waiting, so they learn fast. Anyways, like the OP's link says, there's no magic modelling work that can bring back those missing features and data.
usehackernews|3 years ago
I spent a month writing and implementing a new company playbook on a building products with data science.
It boils down to including data science early during discovery (In part to help identify what data we have available up front), and viewing them as a squad stakeholder rather than a team for one-off work. It also pushed everyone to start thinking about the reliability of data for every product we release.
Some of the databases I’ve seen at companies is just an absolute abomination.