Your team is hesitant about user feedback in software design. How can you convince them of its value?

One thing I've noticed is that most developers don't realize that the way they view an application and the way a user interacts with the same application are totally different. When building an application i regard user feedback as one of the most important features to consider if scaling such product is in high priority.

The team doesn’t receive feedback from the users. Have users talk to techies is a waste of time. The business and users convey what they want to the product owner or architect and the team is given its marching orders. If the feedback is infeasible then the users need to know. Users generally shouldn’t make technical decisions and technical don’t control the business. Be responsive to the business’ needs and be honest about red herrings, unicorns and frivolity. Ultimately there is a decider and respect that persons decisions after thoughtful deliberations. Most of technical team need not be involved.

To convince your team of the value of user feedback in software design, emphasize how it directly informs and improves the product by aligning it with real user needs and expectations. Share examples or case studies where user feedback led to successful design improvements or prevented costly mistakes. Highlight that early feedback can save time and resources by identifying issues before they become larger problems. Encourage the team to see user feedback as a tool for innovation and enhancement rather than criticism. Demonstrate the positive impact on user satisfaction and product success when feedback is integrated into the design process.

Software is built for users. If the user feedback is not incorporated into business and technical decisions the user satisfaction metric could be in a bad shape and the software success could become very questionable, which will jeopardise business goals and objectives of the software project. The best practice of modern software engineering is to receive user feedback early and incorporate it into the next software design phase as soon as possible. One note to keep in mind, a definition of a "user" may vary significantly depending on a software project specifics. "User oriented" culture of the software development teams should be cultivated together with their technical skills.

I mean why not catter the view of people who are going to actually use it. User feedback is going to validate the UI and UX. Developers will always incline towards which they think are going to work out for them and for the development but users feedback will tell what they actually need in the software.

User feedback is crucial for the success and longevity of any software project. It provides real-world insights into what users truly need. Beyond that, when users see their feedback being implemented, it creates a powerful sense of loyalty and ownership. This emotional investment drives not only more engagement and product adoption but also fosters a community that’s committed to your success. This kind of loyalty is a competitive advantage that’s incredibly hard to replicate, making user feedback an invaluable asset to your team’s strategy.