3 ms·

I've worked on products with ALL of these exact issues. The answer is usually that the data isn't annotated well enough, or that there are not enough developer

I've worked on products with ALL of these exact issues. The answer is usually that the data isn't annotated well enough, or that there are not enough developer resources to make special case fixes for things 99% of people don't notice or care about (and so are not losing us money, they just annoy us). At the companies I worked for, fixing these problems was not within the remit of the head of product, they were cross-departmental issues and so were in that pernicious category of problems that are highly resistant to change. I assume the reason you think product people are responsible for this is because you aren't a product person, but in my experience those are the people who most desperately want this type of shit to be fixed, because it makes them look like clowns.

vasco 3y ago
The responsibility of a product person is that the product works well. This includes working with design and engineering partners as well as any data annotation departments. If the search experience is shit and the head of product doesn't think it's up to them, they aren't being responsible for the product.
whstl 3y ago
The reason the responsibility for this is on heads of products is not because they're directly responsible for annotating, it's because they're responsible for knowing what can and will get annotated so the feature they asked for actually works. The work of product person shouldn't stop at the idea phase.