Timeline for How to solicit new product recommendations from existing clients?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Nov 24, 2014 at 16:54 | vote | accept | Michael | ||
| Nov 20, 2014 at 19:25 | answer | added | John R. Strohm | timeline score: 1 | |
| Nov 20, 2014 at 13:10 | comment | added | ben rudgers | Maybe your clients do not find the idea of a new product attractive. Often stability, from a business standpoint, is an important feature. | |
| Nov 20, 2014 at 11:49 | answer | added | Doc Brown | timeline score: 1 | |
| Nov 20, 2014 at 2:21 | comment | added | Brendan | Have you considered asking people who are not current customers why they aren't current customers? | |
| Nov 20, 2014 at 2:21 | comment | added | Brendan | Interpreting silence. Possible interpretations include, "We don't care about your product", "We think your product is awesome exactly how it is now", "I don't have time for (what I've incorrectly assumed is) an annoying marketing pitch" and "My only suggestions are things you won't want to hear, like removing subscriptions". | |
| Nov 19, 2014 at 18:30 | comment | added | Michael | Primarily because they aren't necessarily waterfall clients. They use our current system, but had no say in it's development. And, while they occasionally make suggestions from time to time (it's a cloud based service with a monthly subscription), they don't actually view themselves as part of the development process because the product they use currently is already designed and functional. It's not a question of requirements upfront or a continuous feedback loop - it's a question of getting them involved at all. | |
| Nov 19, 2014 at 18:12 | comment | added | gnat | nice edit. But then... it is difficult to see how is this question different from one that was linked to suggested duplicate: How to sell Agile development to (waterfall) clients | |
| Nov 19, 2014 at 17:58 | review | Close votes | |||
| Dec 10, 2014 at 19:55 | |||||
| Nov 19, 2014 at 17:57 | history | edited | Michael | CC BY-SA 3.0 | Response to suggested duplicate |
| Nov 19, 2014 at 17:53 | comment | added | Michael | @gnat Interesting...I had no idea the "question may already have an answer" only appeared to the answer until the question was closed. | |
| Nov 19, 2014 at 17:49 | comment | added | gnat | meta.stackexchange.com/questions/194476/… | |
| Nov 19, 2014 at 17:48 | comment | added | Michael | @gnat I'm not trying to find a way to accomplish this without client involvement - we can do that if necessary, and have done so in the past. What I'm hoping for are suggestions on how to better spur client involvement. How can we make them see why their input is necessary and to their benefit without patronizing them? | |
| Nov 19, 2014 at 17:44 | comment | added | gnat | possible duplicate of Can Agile be accomplished without client involvement? | |
| Nov 19, 2014 at 17:35 | history | asked | Michael | CC BY-SA 3.0 |