Did he consider that the way he wanted Discourse to be used may not have tallied with the way his users wanted to use it? That's the underlying disconnection.

Did he consider that the way he wanted Discourse to be used may not have tallied with the way his users wanted to use it? That's the underlying disconnection. I am now working on my 3rd message-transformation/integration middleware product for a large corp. In each case, the issue tracker has been stock full of problems from people who took the product, read all the manuals about what they were supposed to do, then did it their way anyway. Because, well if they can, they will. I think the basic problem is not challenging your personal assumptions about how you want your beloved system to be used.