Single developer building an internal tool for a team for an entire quarter. Acting as my own designer and PM. Need advice on how to manage requirements gathering and feedback.

Title.

To start, myself and my “customers” agreed on one core feature/story. I have been working on that core story and meeting with them weekly to demo my progress and get feedback. Based upon what they tell me, I adjust my priority and tell them what I hope to share with them the following week.

One concern I have is that during feedback I hear a lot of “this is cool” or “this is really useful”, but the numbers say that the app isn’t being used much. This could be the nature of their workflow, but it could also mean the app is investing in the wrong direction. I’m concerned that bluntly asking them what they want/need isn’t as effective as gathering feedback through some other indirect method (like a free-form visioning session, for example), but I’m not sure where to start, or what resources to read to better inform my methods.

These feedback meetings are pretty informal. We’re generally just clicking through the app together and discussing what features or changes would be useful for them.

Should I take a step back and reevaluate how I’m handling this, or does this direction seem fine for the time being? For context, we’re about to enter our third week of feedback.