A useful heads-up on The Unquiet Librarian's site (thanks again to Marianne for the link).
It's a variation on the "can't see the wood for the trees" problem where the purpose of a development activity has become ill-defined. In this case the key question for the developer is: "are we wanting to improve [however defined] the product or are we wanting to improve its sales?" If the former, then the behaviour of the product is paramount. If the latter, then the behaviour of the [potential] customer is paramount.
It doesn't matter how excellent your product is if the customer can't, or won't, use it or afford it. A 'good enough' product that doesn't require the customer's having to radically modify their usual behaviours is always going to have something going for it.
OUseful.Info, the blog... » Using WriteToReply to Publish Committee Papers. Is an Active Role for WTR in Meetings Also Possible?
Programming in Jupyter Notebooks, via the Heavy Metal Umlaut - Way back when, I used to take delight in following the creative tech output of Jon Udell, then at InfoWorld. One of the things I fondly remember is his Hea...
6 hours ago