As a tech lead, how do you balance between the big picture roadmap and iterating on user feedback? I seem to always get stuck on either side 😔

E.g. Kiwi News has tons of issues on the low level APIs (users tell me). I could fix all of those vs. I could build a web UI and render them less relevant. What is best?

Founder /kiwi-news, a decentralized Hacker News

It might be controversial but I think at the early stage majority of user feedback is irrelevant. 

People will try to use your app in 100 different ways and every one of these ways will have some issues or some 'that would be cool to have', features. It's a distraction from the primary use case you should deliver on.

Building @kiwi 
Writing @ https://kanfa.macbudkowski.com/

In other words - if you produce pet food, decide if you want to focus on dog food, cat food, or fish food. And then determine if you make main dishes or snacks. And then what flavors do you want to bet on.

And don't ask cats what they think about the dog food :)

When you deliver on the primary use case that provides the most value for the niche you have chosen, then it's time to check if it works and collect these people's feedback.

There will always be 100 ideas on where to pull the project and if you're not disciplined about it, users will make it 'everything for no one.'