3 ms·
Ah yes, the mythical customer that can tell you exactly what they need, and even prioritize it. This customer probably also can be bothered to give usable feedb
by rob74 4y ago
Ah yes, the mythical customer that can tell you exactly what they need, and even prioritize it. This customer probably also can be bothered to give usable feedback on what you have built in a timely manner. But I've yet to see such a customer...
- troupe 4y agoIf there is no customer for the software that is being built, then there is no one who would be disappointed if it was not built. :). So the most efficient thing to do is to do nothing. There usually is a customer. It may not be the person who is called the customer, but somewhere there is someone who is spending money on development and is wanting to be able to us or benefit from whatever is being produced. If the customer doesn't have time to collaborate with the devs to provide feedback, it might be a sign that what is being built isn't valuable to them. This could be either because it doesn't address a real need or because the cycle time is so slow it isn't going to help them any time soon. When a dev team is working on the customer's biggest pain point and has a track record of delivering a solution in a few days, customers will magically have time to talk about it.
- hbrn 4y agoIt doesn't literally have to be a customer talking to you. You could measure engagement, conversion, churn, or any other meaningful metric. The main point is shortening feedback cycle.