6 ms·
If you don't already have one, have you considered having a collection of users who you can privately ask about potential features (or run email wording by) to
by JoshTriplett 6y ago
If you don't already have one, have you considered having a collection of users who you can privately ask about potential features (or run email wording by) to figure out how it would go over? A user of the product could easily have told you, in advance, "some people are looking for a job secretly and this would be a problem".
You could also come up with incentives to encourage job seekers to opt in; for instance, you could temporarily tag such users as "likely to get hired sooner" in reports for prospective employers.
- ammon 6y agoI really like this idea. I'll talk to my head of product about it.
- sockr8s 6y agoNow I am curious what the conversations so far have been about if opt-in was never discussed? Are you looking for product managers?
- mosselman 6y ago> you could temporarily tag such users as "likely to get hired sooner" Lets start lying to the customers on top of this fiasco.
- hysan 6y agoI'm actually surprised that I didn't see this posted in the TripleByte Alum Slack for feedback prior to announcement or even announced there at all. It was the first place I checked after seeing the email/post on HN.
- fma 6y agoI woulda thought they have enough engineers in the company that the engineers would have raised a red flag...
- colejohnson66 6y agoStudies actually show that subordinates generally do not raise concern to their superiors about issues for either fear of reprimand or thinking the superior knows more than you. If @ammon had said, “this will be a great feature,” the devs would keep quiet because they either (1) don’t want to be fired, or (2) trust he knows better than them.
- JoshTriplett 6y agoThat's part of why you should 1) ask before starting development, and 2) ask for feedback rather than telling people what to think.