| I'll dust off some old replies: On "How to properly manage a product roadmap": https://news.ycombinator.com/item?id=22827841 On "Should you listen to your customers": https://news.ycombinator.com/item?id=26814150 On "How to effectively get feedback from users": https://news.ycombinator.com/item?id=24971875 These mainly delve into extracting the job to be done, avoiding the XY problem, and looking at actual user behavior (actions or lack-thereof aka "non-consumption") to turn into issues/tickets to solve real problems as opposed to imaginary ones. You can even encode these in issue templates / ticket templates to avoid having frivolous feature requests or unimportant/non-urgent bugs and focus on things with high frequency and/or severity. i.e: product management. Now, for the engineering side of it... On "How do you develop internal tools for your organization?": https://news.ycombinator.com/item?id=29061808 The above link shows the inception of our product around a plugin architecture. More on that: https://news.ycombinator.com/item?id=25186586 The design principles I had set and enforced with iron fingers. The fist of someone who presses on keyboard keys may be weak, but his fingers are ruthless. https://news.ycombinator.com/item?id=29397405 One way to go about this is to improve the way you build product (product management, everyone is involved) or push for that, then get the engineering to deliver that in ways that make it easy to add/remove features, integrate with users (in the abstract sense, they could be humans or other systems), onboard developers. Other posts you could cherry-pick from can be found here: https://news.ycombinator.com/item?id=40482961 |