Timeline for How can I go about providing informal feedback to a vendor while making it clear that the feedback I'm providing is not sanctioned by my employer?
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| yesterday | comment | added | Flater | @JoelEtherton: You'll notice I never endorsed OP directly contacting the vendor and circumventing the company unless they were specifically given a channel to do so. Not in my comments to you, not in the answer I posted. | |
| yesterday | comment | added | JosephDoggie | I would say: don't. | |
| yesterday | answer | added | Dimitri Vulis | timeline score: 0 | |
| 2 days ago | answer | added | Joel Etherton | timeline score: 2 | |
| 2 days ago | comment | added | Joel Etherton | @Flater and their feedback for vetting should go to their own internal individual responsible for making the choice. OP may be someone with access to the system, and the question as asked makes it sound like they're NOT the individual responsible for the decision. It is entirely possible that leadership involved doesn't want OP making these recommendations or representing the company in this way. | |
| 2 days ago | comment | added | Flater | @JoelEtherton "employer is vetting an external software which means I get plenty of fun time playing around with it" This reads to me like OP has access to this tool specifically as part of the vetting process, making them a pilot user. I'd say the relevance of their feedback is even higher than for a regular user. | |
| 2 days ago | comment | added | Joel Etherton | @Flater: that's a fair reply because the core of my comment centered around "don't bring it up at all, there's a high chance no one cares and the ones you'd bring it up with have no capability to initiate change". What OP is suggesting is not what one would find in a "proper feedback channel" as they are not an actual user yet. | |
| Dec 11 at 22:35 | comment | added | Flater | [..] Giving feedback does not guarantee that the vendor will heed/action it, but not giving feedback ensures that they won't. | |
| Dec 11 at 22:34 | comment | added | Flater | @JoelEtherton My point wasn't so much that OP should definitely go around their company. My point is that "minding your business", as you said, implies not bringing it up al all, with anyone. I've seen dozens of cases where a company adopts (as a consumer) or develops (as a vendor) an ill-fitting tool because they did not listen to end user feedback - whether that is through willful ignorance of given feedback, not having a proper feedback channel, or users not raising feedback on the belief that they will not be heard anyway. [..] | |
| Dec 11 at 15:31 | comment | added | Joel Etherton | @Flater any tool that is being purchased at an enterprise level will have a support and feedback mechanism built into it for these kinds of things. Mentioning these things to sales people or implementation professionals isn't going to provide the value OP thinks it will. Your comment, though, would likely fit into Kate's answer I think. | |
| Dec 10 at 23:11 | comment | added | Flater | @JoelEtherton Generally speaking when vetting a tool you're not just interested in the product as is, but also about its future maintenance and expansion (if any). OP's questions would help shine a light on how the vendor intends to maintain this product going forward. If OP's feedback is more "I think this would look nicer", I agree with you, but if the feedback is on a particular behavior/feature of the tool in a way that impacts OP and their company as the end user of that tool, the feedback does seem sufficiently relevant. | |
| Dec 10 at 21:11 | comment | added | Joel Etherton | Why? What's the upside here? Sometimes "minding your business" is a perfectly acceptable way to navigate a situation. | |
| Dec 10 at 7:51 | comment | added | jwsc | What are you gaining by writing feature requests to them? Is this worth the hassle, if someone at your company feels you're stepping toes? I work at a company doing software. For every feature request we're accepting, there are hundred we are discarding. If there is a abundant resource, it's feature requests. Be aware of that, when you send them your thougts. | |
| Dec 10 at 2:01 | answer | added | Flater | timeline score: 4 | |
| Dec 9 at 20:58 | answer | added | Kate Gregory | timeline score: 9 | |
| Dec 9 at 20:13 | history | edited | Philip Kendall | CC BY-SA 4.0 |
Spelling
|
| Dec 9 at 19:03 | history | asked | Sidney | CC BY-SA 4.0 |