请问HN：你是如何让你的开发人员理解客户的需求的？
我是一个SaaS公司的首席技术官。我们开发的软件并不是面向软件开发者的。因此，我们并不是为了自己而开发软件，除了在一些小众或特定的情况下，我们没有理由进行自我使用测试。
我们有一支强大的产品管理团队和优秀的工程领导。从我的角度来看，我们通常在做正确的事情，并且能够相对迅速地以较高的标准完成这些工作。
每当我发出征求反馈、问题或改进建议的通知时，常常会提到“我们需要提高开发人员对客户如何使用产品的理解”。我相信这并不是我们独有的情况。
多年来，我们尝试了许多方法，我不能说找到了一种灵丹妙药。我们尝试过亲自拜访客户，鼓励开发人员主动联系客户，鼓励开发人员与客户服务团队在会议上进行配对合作。我们还指出现有的缺陷跟踪系统和客户反馈论坛，作为开发人员可以了解客户意见的地方。这些措施都有一定帮助，但“开发人员并不真正理解客户如何使用产品或为什么这样使用”的普遍感觉依然存在。
我很想听听其他公司是如何解决这个问题的！
查看原文
I am the CTO of a SaaS company. The software we make isn't software for software developers. So we aren't building it for ourselves, and except for in some niche or contrived cases, don't have a reason to dogfood it.<p>We have a strong product management team, and a strong engineering leadership. From my perspective, we generally work on the right things, and get them done reasonably quickly to a reasonably high standard.<p>Whenever I put the word out for feedback, questions, or suggestions for things we could improve on, something that always comes up is "we need to improve developer understanding of how our customers use the product". I'm sure this isn't unique to us.<p>We have tried many things over the years, I wouldn't say I've found a silver bullet for it. We've tried things like visiting customers in person, encouraging devs to reach out to customers, encouraging devs to pair with customer-facing staff internally on meetings. We've also pointed to existing bug trackers and customer feedback forums as a place where devs can hear the word of the customer that's already been written down. All these things help a little bit, but the general vibe of "devs don't really understand how the customers use the product or why" persists.<p>Interested to hear how other companies approach this!